Copilot in Outlook Privacy Settings: What Data is Sent

Official documentation checked October 14, 2026.

Copilot in Outlook is a cloud-assisted feature, not an offline mailbox tool. Before using it with sensitive mail, distinguish the work or school service from a personal account and identify the task: summarizing a thread, drafting, scheduling, and chatting do not necessarily use the same sources.

This guide covers organizational Microsoft Copilot in Outlook. There is no verified universal admin page with Mail and Calendar checkboxes that selectively disables each source while leaving every other Copilot feature unchanged.

Identify the account and the information involved

Check the signed-in Outlook account and the Copilot experience you are actually using. For a work task, confirm with your administrator that this is the organization-approved service. Do not assume a personal Copilot window has the same contractual protections because it has the same logo.

Microsoft describes organizational Copilot as using the prompt and relevant authorized content to produce a response. It does not grant the user new permissions. This does not establish that every attachment, embedded image, link target, contact field, or calendar entry is read in every Outlook action. Consult the Outlook feature FAQ for the feature and client involved.

For a practical check, use an ordinary test thread containing a harmless unique reference, ask for a summary, and compare it with the source. Inspect references where provided. A correct answer is evidence that the detail was available for that response, not a complete inventory of all processing.

Separate model training, processing, and retained history

Microsoft states that organizational prompts, responses, and Graph-accessed data are not used to train foundation models. That does not mean nothing is stored: interaction history can contain prompts, responses, and citations. Nor is there a blanket guarantee that every request is processed in the tenant’s own geographic region. Review the applicable commitments, cloud, model, and exceptions in Microsoft’s Copilot privacy documentation.

For a residency requirement, write down precisely what must remain where: stored mailbox content, interaction records, temporary processing, or optional feedback. Ask the organization’s privacy or security owner to confirm the applicable service terms. A “not used for training” statement cannot answer all four questions.

Use controls that match the privacy objective

• Prevent access to unauthorized information: review the underlying mailbox, file, and sharing permissions. A prompt saying “ignore confidential mail” is not an access-control policy.
• Restrict sensitive content in Copilot: have the administrator evaluate supported sensitivity-label and Microsoft Purview DLP controls, including their workload coverage. See Purview protection for Copilot.
• Control web grounding: review the separate web-search policy. Bing search queries are distinct from the full conversation and have their own data-handling explanation. Disabling web search does not disable authorized mailbox grounding.
• Disable content-analyzing connected experiences: this can disable Copilot in supported Office apps rather than provide a mailbox-only filter. Assess the effect on other required features before deployment.

Review feedback and retention separately

Administrators can use Microsoft 365 Cloud Policy to manage feedback submission and whether users may include screenshots, attachments, logs, and content samples. Search that policy interface for feedback; review the documented policies before changing them. Feedback can include more than a thumbs-up count when the user chooses to submit supporting material.

For retained interaction records, use the organization’s Copilot retention policy. Removing a conversation from a user interface is not proof that every compliance copy has been deleted. Preserve records subject to an investigation or retention requirement and involve the authorized records owner.

Investigate unexpected information without deleting local caches

1. Record the account, Outlook client, feature, approximate time, and the unexpected source. Redact sensitive values in the support ticket.
2. Check whether the user can open that source directly and whether it had already been included in the conversation.
3. Ask the administrator to verify the actual policy assignment and its supported scope. Repeat a harmless test in a new conversation after the change takes effect.
4. If access appears unauthorized, stop sharing the result and escalate through the organization’s security process.

Deleting Outlook’s RoamCache is not a method for deleting cloud Copilot history, enforcing retention, or proving that access has been removed. Keep the original evidence intact while the responsible administrator investigates.