Copilot data privacy comes down to one rule: Microsoft 365 Copilot works with the data the signed-in user can already open, and it respects the permissions that are already in place. If you can’t open a mailbox, file or site today, Copilot can’t use it for you either. So Copilot is as safe as your current permission settings. That is good news if those settings are tidy, and a reason to check them before rollout if they are not.
What data can Microsoft 365 Copilot access?
Copilot answers prompts using content from your organisation’s Microsoft 365 environment, limited to what each user has access to.
The scope is set per person. Two colleagues who type the same prompt can get different answers, because each of them has access to different mailboxes, files and Teams. A project lead sees results drawn from the project’s documents; a new hire without access to that project does not.
Copilot can also use content from the web, depending on how your organisation has set it up.
How Copilot respects existing permissions
Copilot adds no new rights. It inherits the permissions each user already has in Microsoft 365. When someone asks Copilot to summarise a client project, it can only pull from the messages and documents that person could open themselves. A confidential HR folder that only HR can open stays out of reach for everyone else’s prompts.
There is a flip side. Copilot finds things much faster than a person scrolling through folders. A file that was shared with everyone in the organisation years ago and then forgotten is still readable for everyone, and Copilot can now bring it up in an answer. Permissions that were too broad but never caused trouble, because nobody went looking, suddenly matter.
For decision makers this shifts the question. Whether Copilot can be trusted with your data depends largely on whether your sharing settings reflect who should see what.
What this means for your email in Outlook
When you use Copilot on your inbox, it works with the messages you can already read in your own mailbox. Your colleagues’ mailboxes stay closed to you, and so they stay closed to your Copilot prompts as well.
Shared and delegated mailboxes need a separate check.
You will also want to know what happens to the prompts you type and the answers you get back; check this in Microsoft’s documentation before rollout.
What this means for your documents
Files in OneDrive, SharePoint and Teams follow the same logic. If a document is shared with you, Copilot can use it in your answers. If it isn’t, Copilot leaves it alone.
That puts the focus on how files are shared in practice. Links that give access to anyone in the organisation, team sites with broad membership and old project folders that were never cleaned up all widen what a single prompt can reach.
Many organisations also mark sensitive documents with labels or encryption. Check how Copilot handles those labels in Microsoft’s documentation before you rely on them.
Can you use AI on your Outlook inbox without giving away company email?
Yes, provided the AI works inside your organisation’s Microsoft 365 account and its permissions. Copilot in your work account uses the access you already have, so your company email stays within the same controls your IT team manages today.
The risk sits elsewhere. When an employee copies email content into an AI tool outside your Microsoft 365 environment, that content leaves the permission model your organisation controls. Your IT team can no longer see or manage who has access to it.
A common follow-up question is whether your data is used to train AI models. Look up Microsoft’s own statement on this before rollout.
In short: Copilot sees your email because you can see your email. It does not open mailboxes you have no rights to.
What to check before you roll out Copilot
Because Copilot follows your permissions, the most useful preparation is a look at those permissions. Start with these checks:
- Which SharePoint sites and Teams are open to the whole organisation, and should they be?
- Which files are shared through organisation-wide links that nobody uses anymore?
- Who has access to shared mailboxes, and does that list still match the current team?
- Do employees know that Copilot only works with what they can already open?
Ask your IT team to run the first two checks before Copilot goes live.
The last check is about people. Employees who understand that Copilot follows their own access are more likely to use it on their inbox and documents with confidence, and less likely to paste company email into tools outside your environment.