When Microsoft 365 Copilot answers a question, it isn't making things up from a training set. It's retrieving content from inside your tenant — SharePoint, OneDrive, Teams, Exchange, Loop — and grounding its response on what it finds. The thing most people miss on day one is how faithfully Copilot respects your existing access controls. It doesn't open any door that was previously closed. It also doesn't close doors you already left open.
That distinction is the whole story of Copilot readiness. Microsoft has built Copilot's access model to be correct by design. It inherits the SharePoint and OneDrive permissions each user already has. If that inheritance delivers the outcome you want, Copilot makes your organisation genuinely smarter. If your permissions model has quietly drifted over the years, Copilot surfaces the drift at conversational speed. The fix isn't a Copilot setting — it's the tenant hygiene Microsoft has been recommending for a decade.
The access model in one paragraph
Copilot queries run through the Microsoft Graph under the signed-in user's identity. Whatever the user can see through Graph — SharePoint sites they have access to, Teams chats they're part of, OneDrive files shared with them, mailbox content they own or delegate — becomes eligible retrieval for Copilot. Content the user cannot see remains inaccessible. Microsoft documents this formally as the Copilot identity and access model and it is unusually tight: no service account masquerading, no tenant-wide index bypass, no elevation through an agent.
There are three subtleties worth stating plainly, because most first-rollout problems come from misunderstanding one of them.
Subtlety 1 — "Effective access" is broader than people realise
Most IT teams think of SharePoint permissions as "who's on the site." The effective access set is larger. A user might reach content through: direct site membership, inherited permissions from a parent site, a "Shared with me" OneDrive link somebody sent them two years ago, a SharePoint site shared to Everyone or Everyone except external users, an anonymous anyone-with-the-link share forwarded into a Teams chat, or a Microsoft 365 group they're a member of that happens to own a sensitive site. Copilot retrieves against the full effective access graph. If any of those paths leads to sensitive content, Copilot can surface it.
The practical check: before turning Copilot on tenant-wide, run the SharePoint Advanced Management (SAM) sharing report and the content oversharing report. Both are Microsoft-native and free to inspect inside the SharePoint Admin Center. They answer the question "what is currently reachable by whom?" that Copilot is about to answer at speed for every user.
Subtlety 2 — Sensitivity labels do exactly what Microsoft says they do
Microsoft Purview sensitivity labels are honoured by Copilot. If a document is labelled Confidential and the label carries encryption with a scoped usage policy, Copilot cannot surface the content to a user outside that scope. This is one of the cleanest ways to constrain Copilot's retrieval boundary without redesigning your SharePoint permissions from scratch.
The practical move is to deploy a small four-label taxonomy (Public, Internal, Confidential, Highly Confidential), set Internal as the default applied to every new document, and auto-label against sensitive info types (TFN, credit card, Medicare, passport, driver's licence, financial account). The Purview auto-label simulation mode is worth running for at least 30 days before enforcement. Copilot will then retrieve against labels as well as permissions — which closes the subset of oversharing risk that raw permissions can't easily reach.
Subtlety 3 — Restricted SharePoint Search is the scoping lever
Microsoft shipped Restricted SharePoint Search as a tenant-level control that constrains which SharePoint sites are eligible for tenant-wide search and Copilot retrieval. With it enabled, only sites on a curated allow-list are searchable tenant-wide; everything else still works for members of the site, but no longer feeds into Copilot's tenant-scope retrieval. It is, in effect, the "start small" switch for Copilot rollout — allowing you to enable Copilot licences while scoping the retrieval surface to a governed subset of sites.
This is one of the most under-used Microsoft features we see. It is specifically designed for organisations who want to deploy Copilot before their tenant-wide oversharing work is complete. It isn't a substitute for cleaning up permissions — it's a staging mechanism that lets you do the cleanup in parallel with rollout rather than serially before it.
Try it
Score your tenant hygiene before Copilot
Before the first Copilot seat goes live, run the SharePoint Oversharing Risk Check. Twelve questions, Microsoft-native recommendations per gap, PDF for the board.
Score each of the 8 strategies
Where are you on the Essential Eight — honestly?
Eight strategies. Four levels each. Pick the statement closest to your reality today. We'll map it to the Microsoft 365 tooling that closes the gap.
What's your target Maturity Level?
Maturity Level 2 — most orgs' pragmatic target
- 01
Application control
Only approved applications can execute on workstations and servers.
- 02
Patch applications
Internet-facing apps, browsers, Office, PDF readers patched promptly.
- 03
Microsoft Office macros
Macros disabled unless from trusted locations and signed by a trusted publisher.
- 04
User application hardening
Web browsers and productivity apps hardened against the most common attacks.
- 05
Restrict administrative privileges
Admin accounts limited, separated and reviewed — the crown jewels of the tenant.
- 06
Patch operating systems
Operating system patches applied on a schedule that matches the risk.
- 07
Multi-factor authentication
MFA everywhere that matters — privileged accounts, remote access, important data.
- 08
Regular backups
Backups of important data, configuration and software — and restores you have actually tested.
What this means for your rollout plan
Three practical implications follow from the inheritance model, each of which should be reflected in the Copilot rollout plan you hand to your audit committee.
- Tenant hygiene is the rollout prerequisite, not a parallel workstream. An hour spent cleaning up Everyone-shared sites pays Copilot dividends for every user for years.
- Sensitivity labels + Copilot are an intentional pairing. If you don't have Purview labels deployed, you're leaving one of the cleanest Copilot controls on the shelf.
- Restricted SharePoint Search lets you move before you're perfect. Use it to scope retrieval to governed sites during the first 90 days of rollout, expand scope as hygiene work completes.
Everything above is built into Microsoft's own documentation and rollout guidance. The controls are there. The capability is there. The work that remains is the configuration and the discipline — which is where a Microsoft MVP–led partner matters more than usual. If you'd like a second opinion on your sequence before a Copilot go-live, book a 30-minute readiness review.