Reviewed
What can Microsoft 365 Copilot see?
Microsoft 365 Copilot can make information easier to find. That is useful when permissions match people's jobs, and uncomfortable when old project sites, broad groups or sharing links expose more than their owners intended. Start with the access your staff already have, not an assumption that enabling an AI assistant fixes or bypasses it.
Know which product and account you are reviewing
This article concerns Microsoft 365 Copilot and connected work content. Do not apply the same conclusion automatically to a personal Copilot account, another AI service, or every agent and connector. Record the product, licence, account, connected data sources and enabled features before reviewing access.
Microsoft's privacy and security documentation states that Microsoft 365 Copilot only surfaces organizational data for which the user has at least view permissions. It also describes how prompts, responses and data accessed through Microsoft Graph are not used to train foundation models. These statements do not mean that prompts are never stored, that every employee should see every file, or that third-party connections have identical terms.
Look for information that is already overshared
Choose a small set of sites with clear business owners: client work, finance, people operations and an ordinary team project. Ask each owner who should have access, then compare that answer with actual permissions. Review:
- Site and group membership, including broad organization-wide groups.
- Direct file and folder access, sharing links and external guests.
- Inherited permissions and exceptions left behind by old projects.
- Ownership of inactive sites and the process for removing access when roles change.
Use administrators to inspect configuration and representative ordinary user accounts to check the resulting experience. An administrator's view is not a substitute for a staff member's access. Use synthetic test files rather than asking the assistant to display real payroll or client records just to prove a point.
Distinguish access restrictions from discovery controls
Microsoft's SharePoint readiness guidance describes tools for identifying and reducing oversharing. Choose controls by the problem they solve and verify licensing and availability in your tenant.
Restricted access control can add a site-level boundary based on specified groups. Membership in an allowed group does not itself grant permission: a user still needs access to the content. This is different from merely making a site less discoverable.
Restricted content discovery limits how selected sites appear in organization-wide search and Microsoft 365 Copilot discovery scenarios. It does not revoke existing permissions. A person with access can still reach content through other supported paths. Do not use “it did not appear in an answer” as proof that access was removed.
Restricted SharePoint Search is retiring. It is not a recommended new control for this plan. Repair permissions and evaluate current access and discovery controls instead; check Microsoft's documentation again before implementation.
Test the boundary after a change
Agree on a few expected outcomes before the pilot. For example, a member of the client delivery group should retrieve a synthetic project note, while an unrelated staff account should not open that note directly or receive its restricted contents through the assistant. Check both the underlying file access and the Copilot experience. Allow for documented propagation and indexing behaviour when interpreting a result; a single missing answer proves little.
Record the account role, data source, expected outcome, observed result and configuration date. If a test fails, fix the permissions or integration and repeat it before widening access. Keep the test evidence free of confidential content and credentials.
Decide who maintains the result
Assign a business owner for sensitive sites and an administrator for access changes. Revisit broad groups, guests, new connectors and agent capabilities as part of normal account and site reviews. Tell staff which account to use, what not to enter and how to report an unexpected result in the acceptable-use policy.
A readiness review produces a permissions inventory, a prioritized cleanup list and evidence from a defined pilot. It is not a claim that every possible exposure has been eliminated. This is general readiness guidance, not legal advice; confirm your privacy and contractual requirements with a qualified professional.
Source: https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-privacy. General readiness guidance — not legal advice.