What Can Microsoft Copilot Actually See in Your Organisation?
The most common question before a Copilot deployment is also the most important one: what can it actually see? The honest answer is that Copilot can access everything your users can access - emails, files, calendar, Teams messages, SharePoint documents, and more. Understanding exactly what that means, and what it does not mean, is the starting point for any responsible deployment.
How Copilot accesses your data
Microsoft Copilot is built on top of the Microsoft Graph - the same API layer that connects all Microsoft 365 services. When a user asks Copilot a question, it queries the Graph on behalf of that specific user, using that user's own credentials and permissions.
This is the critical point: Copilot does not have its own elevated access. It does not have a service account with special permissions. It can only see what the user asking the question is already permitted to see. If a user cannot access a file directly, Copilot cannot access it for them.
The inverse is equally important. If a user has access to a file - even a file they have never opened, never searched for, and never knew existed - Copilot can retrieve and present that file in response to a relevant query.
What is in scope for Copilot
- Emails in the user's Exchange Online mailbox - sent items, received mail, and any shared mailboxes they have access to
- Files in the user's OneDrive, including files shared with them
- SharePoint sites and document libraries the user has been granted access to, whether through a group membership, direct permission, or a sharing link
- Teams chat messages - both one-on-one conversations and channel messages in Teams the user is a member of
- Meeting recordings and transcripts stored in OneDrive or SharePoint that the user has access to
- Outlook calendar events and meeting content
- Loop components, OneNote notebooks, and Planner tasks connected to accessible workspaces
What is not in scope
Copilot cannot access content in systems outside Microsoft 365 unless a specific connector has been configured to bring that content in. It cannot access your CRM, your accounting software, your phone system, or third-party tools unless those integrations have been explicitly built.
It also cannot access content that the user cannot access. Files with restricted permissions, SharePoint sites the user is not a member of, and emails in another user's mailbox are all outside Copilot's reach - assuming your permissions are correctly configured.
Copilot does not expand what your users can access. It makes what they can already access dramatically easier to retrieve. The governance problem is not Copilot - it is that most organisations have never had a reason to carefully examine what each user can actually reach.
The oversharing problem Copilot makes visible
In most Microsoft 365 environments, permissions have accumulated over years without systematic review. A SharePoint site created for a project in 2021 still has its original membership. A document shared via link with a client five years ago still has an active link. A team member who left has a guest account that was never deprovisioned.
Before Copilot, this was a latent problem. Users accessed files they knew about. Broad permissions existed, but the practical exposure was limited by the need to actively search.
Copilot changes this. It actively retrieves relevant content from across everything a user can access. A finance manager asking Copilot to summarise last quarter's performance may receive content from a SharePoint site they were added to years ago and have never visited - because they technically have access and the content is relevant to the query.
This is not a Copilot security flaw. It is the permission environment working exactly as configured. The problem existed before Copilot - Copilot just makes it visible.
The four most common exposure risks
- 01
Everyone and Everyone except external users group sharing
SharePoint sites or document libraries shared with these groups are accessible to every authenticated user in your tenant - including new starters on day one. Copilot will retrieve content from these sites for any user who asks a relevant question, regardless of whether they should practically have access.
- 02
Broad membership in Microsoft 365 groups
Teams channels and Microsoft 365 Groups are often created with broad membership for convenience. Every member of the group can access the associated SharePoint site and files through Copilot, not just the files they have personally worked on.
- 03
Unexpired sharing links
Files shared via 'Anyone with the link' or with specific people using a link remain accessible indefinitely unless the link is revoked. These links do not appear in standard permission reports - they live on the individual file. A document shared with a client six months ago may still be retrievable by Copilot for that external guest.
- 04
Retained guest accounts
External users invited to Teams channels or SharePoint sites remain as Entra ID guests until explicitly removed. If a guest's business relationship with your organisation has ended but their account remains active, they retain access to whatever was shared with them - and Copilot respects that access.
What controls Copilot actually has
Microsoft provides a set of Copilot-specific controls that sit on top of the underlying permission model. Sensitivity labels from Microsoft Purview can restrict how Copilot handles labelled content - content marked Highly Confidential can be excluded from Copilot responses, for example. Copilot can also be restricted to specific Microsoft 365 groups during a phased rollout rather than enabled for all users at once.
These controls are valuable, but they are secondary. The primary control is your underlying permissions. No Copilot setting compensates for a SharePoint environment where sensitive content is broadly accessible. The governance work comes first.
Next step
Copilot Readiness Assessment
The Copilot Readiness Assessment maps exactly what your users can access, identifies the highest-risk exposure patterns, and gives you a prioritised remediation plan before Copilot deployment.
Learn more