Microsoft 365 Copilot does not bypass your permissions. That is the good news and the problem. Microsoft's data and privacy documentation says Copilot "only surfaces organizational data to which individual users have at least view permissions." If a spreadsheet is open to everyone in the company by accident, Copilot will happily summarise it for anyone who asks.
This guide is for the admin who has to say yes or no to a rollout. It covers the order of work, the SharePoint and Purview tools Microsoft documents, one retired feature, and a checklist. If you are still deciding whether to buy, read our beginner's guide and pricing and licensing guide first.
TL;DR: the readiness order
| Step | What to do | Main tool |
|---|---|---|
| 1 | Find overshared sites and files | SharePoint Advanced Management data access governance reports |
| 2 | Hold back the riskiest sites during review | Restricted Content Discovery |
| 3 | Fix permissions and ownership | Site access reviews, ownership policy, restricted access control |
| 4 | Label sensitive content | Purview sensitivity labels |
| 5 | Add guardrails on prompts and content | Purview DLP for Copilot |
| 6 | Control agents, audit and retention | Admin center agent settings, Purview audit and retention |
| 7 | Pilot, then widen in waves | Your rollout plan |
Why is oversharing the main Copilot risk?
Copilot builds answers from Microsoft Graph content the user can access: documents, email, chats, meetings and calendar. Microsoft's privacy documentation says the permission model keeps data from leaking between users, groups and tenants, and that Semantic Index honours the user's identity-based access boundary. It also says prompts, responses and data accessed through Microsoft Graph are not used to train foundation models.
So the question is not whether Copilot is safe in the abstract. It is whether your permissions are right. Years of "Everyone except external users" links, old project sites and forgotten shared folders were harmless when nobody could find them. Copilot makes anything findable. Microsoft's own Contoso example in its Restricted SharePoint Search page shows a budgeting site with weak permissions that Copilot used to answer a question for someone who should not have seen it.
Microsoft's Secure and Governed Data Foundation blueprint, updated November 2026, organises the work into three pillars:
- Remediate oversharing
- Set up guardrails
- Meet regulations
It says SharePoint Advanced Management (SAM) is included with your Microsoft Copilot licence, and pairs it with Microsoft Purview for data loss prevention, insider risk and compliance. The blueprint is also available as a PowerPoint deck and PDF.
A filing cabinet behind a small gate with a green key slot, showing a Copilot readiness review that checks who can open which SharePoint site
Step 1: How do you find oversharing?
Use the SAM reports. Microsoft's SharePoint Advanced Management overview lists the data access governance (DAG) reports, which identify sites that might hold overshared or sensitive content:
- Permission state reports for sites, OneDrive sites and files, a snapshot of how broadly data is exposed
- Site permissions for a given user, listing every site a user can reach and how
- Sensitivity label snapshot, showing how labels are distributed across sites
- Sharing links activity, showing sites where users created the most new links in the last 28 days
- Everyone except external users (EEEU) insights, showing the top items and groups shared with EEEU and the policies on those sites
You can generate DAG reports through the admin center or the SharePoint Online PowerShell module, and ask for AI insights that highlight risk patterns. Microsoft also lists the content management assessment, the SharePoint Admin Agent and catalog management as ways to find sites that need review.
Start with the sites that hold finance, HR, legal, board and customer data. Then check EEEU and anyone-links. Those two sharing types create most surprises.
Step 2: How do you hold risky sites back while you fix them?
Use Restricted Content Discovery (RCD). Microsoft's RCD page, updated October 2026, says it limits discovery of content from specific SharePoint sites, including recently interacted files, in organisation-wide search and Copilot responses while reviews happen.
What it does and does not do:
| Point | Detail, per Microsoft |
|---|---|
| Permissions | RCD does not change them. Users with access can still open content directly |
| Scope | SharePoint sites only, not OneDrive |
| Entry points | Removes AI entry points on those sites, such as the Copilot button, AI actions menus and Create pages with AI |
| Search index | Content stays in the index. Purview eDiscovery and auto-labelling continue to work |
| Effect on Copilot | Does not affect experiences on content already in use, such as summarising an open document |
| Speed | For sites with more than 500,000 items, an update can take more than a week |
| Licence | Needs a Microsoft Copilot licence and SAM |
| Intent | A temporary control. Use selectively, because excessive use reduces the content available to search and Copilot |
You turn it on per site with the Restrict content from Microsoft Copilot setting in the SharePoint admin center, or in PowerShell with Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true. By default only SharePoint admins can manage it, and delegation to site admins requires a justification on each change. Changes are audited in Purview.
A door with a stuck key and a warning light above, a reminder that Restricted Content Discovery hides content from Copilot but does not fix permissions
What happened to Restricted SharePoint Search?
It is retiring. A notice at the top of Microsoft's Restricted SharePoint Search page says: "Starting July 31, 2026, new enablement is blocked. Use comprehensive data controls such as Restricted Content Discovery (RCD)." It was an allow list of up to 100 sites, it "isn't a security boundary," and it never changed permissions. A site a user recently accessed, or one shared with them in Teams or Outlook, could still appear even if it was off the list.
If you enabled it earlier, Microsoft's process is: use SAM to remediate oversharing, use Purview for labels, DLP and auditing, then disable it and tell Copilot and agent owners that responses use existing SharePoint permissions.
Step 3: How do you actually fix permissions?
RCD buys time. The fix is permissions. SAM includes these tools:
- Site access reviews, which delegate DAG report review to the owners of overshared sites
- Site ownership policy, which sets minimum owner counts and notifies when sites do not meet them
- Inactive site policy and site attestations, which prompt owners to confirm a site is still needed and its members are right
- Restricted access control, which limits access to a SharePoint or OneDrive site to specific groups
- Block download policies for sensitive sites and Teams recordings
- Site policy comparison, which compares a baseline site against up to 10,000 target sites
A sensible order: remove EEEU and broad groups from sensitive sites, assign two owners per site, archive dead sites, then restrict the few sites that must stay narrow.
Step 4: What do sensitivity labels do for Copilot?
Microsoft's privacy page says that when data is encrypted by Microsoft Purview Information Protection, Copilot honours the usage rights granted to the user, whether the encryption comes from sensitivity labels or from restricted permissions through Information Rights Management. Labels also give your DLP rules something to key on.
Keep the taxonomy small. Microsoft's own DLP example uses five labels: Highly Confidential, Confidential, Internal, Public and Personal. Label the files that matter first, then expand with auto-labelling.
Two cautions. Labels apply to content, so unlabelled legacy files stay unprotected. And encrypted mail or files can break Copilot features: our Outlook guide lists the mail Copilot cannot read.
Step 5: What can Purview DLP do for Copilot?
Microsoft's DLP for Microsoft 365 Copilot and Cowork page, updated November 2026, describes four controls. All use the Microsoft Copilot, Copilot Chat, and Copilot Cowork policy location, available only in the Custom policy template.
| Control | Status per Microsoft | Effect |
|---|---|---|
| Block external web search when a prompt has sensitive information types | Available | Copilot answers from permitted internal sources instead |
| Block processing of prompts with sensitive information types | Preview, rolling out | Copilot does not respond and does not search for that prompt |
| Block files and emails with sensitivity labels | Available | Content is not used in the response, though the item can appear in citations |
| Block external email as grounding data | Preview, not yet supported for Cowork | Copilot ignores emails from outside your accepted domains, judged on sender metadata |
The limits matter as much as the controls. DLP cannot scan files uploaded into a prompt, only the text typed. In Word, Excel and PowerPoint the label policy is checked when a file opens, so a label added mid-session applies from the next open. Calendar invites are not supported, labelled email is covered only if sent on or after January 1, 2025, and policy changes can take up to four hours to reach Copilot. Policy simulation mode is available, so test before you enforce.
The external email rule is worth a look. External messages are untrusted input, and prompt injection through mail is a real risk, as we explained in the Word document AI worm and the ChatMate remote prompt execution research posts.
Step 6: How do you govern agents, audit and retention?
Agents inherit user permissions, so they need the same care. Microsoft's Agent Builder pages say admins control agent access under Agents, Settings, User access in the Microsoft 365 admin center, and org-wide sharing under Sharing. Publishing to your org catalog needs admin review. Creating agents in Agent Builder is a core Copilot capability when agents are enabled and cannot be disabled separately. See Agent Builder vs Copilot Studio for the licensing and sharing details, and review the permissions an agent requests before you allow it.
For records, Microsoft says Copilot stores the prompt, the response and the citations as "Copilot activity history." Admins can use Content search or Purview to view and manage it, and set retention policies for Copilot chat interactions. Users can delete their own history from the My Account portal.
Three more switches from the same page:
- Connected experiences. If you turn off connected experiences that analyse content, Copilot features stop working in Excel, OneNote, Outlook, PowerPoint and Word.
- Third-party models. Admins decide whether to use Anthropic and OpenAI models as subprocessors. Microsoft says models from Anthropic are currently excluded from the EU Data Boundary.
- Web search. Policy controls whether Copilot can use web content, and it overrides agent toggles.
The rollout checklist
Before the pilot
- Confirm licences and the base plan. See our pricing guide.
- Run the DAG reports and list the top 20 overshared sites.
- Apply Restricted Content Discovery to finance, HR, legal and board sites.
- Disable Restricted SharePoint Search if you used it, after validating permissions.
- Decide the label taxonomy and label the highest-risk content.
- Draft a DLP policy and run it in simulation mode.
During the pilot
- Choose 20 to 50 users across roles, and two real use cases per team.
- Ask users to report any answer that shows content they should not see.
- Review Purview audit and activity data weekly.
- Remove RCD from a site only after its permissions are fixed.
Before each wave
- Re-run DAG reports and compare with the baseline.
- Brief users on prompt habits. Share our Copilot prompt guide.
- Set agent sharing and catalog rules.
- Publish a one-page "what Copilot can and cannot see" note.
Operate
- Review sharing-link and EEEU reports monthly.
- Run site attestations quarterly.
- Check Microsoft's Message Center for retirements. Restricted SharePoint Search is one, and Prioritize my inbox in Outlook is another.
If your team wants a guided session on rolling this out alongside the end-user skills, our Microsoft Copilot and Copilot Studio workshop runs on December 20 and 21, 2026. For the security incidents that make this work urgent, read our ChatMate analysis. And if you run AI agents beyond Microsoft 365, the AgentBeam platform from the explainx.ai team blocks agents before they take dangerous actions.
Related reading
- What is Microsoft 365 Copilot? A beginner's guide
- Microsoft 365 Copilot pricing and licensing
- Copilot security: the Word document worm
- Copilot security: ChatMate remote prompt execution
- Microsoft Copilot in Outlook
- Agent Builder vs Copilot Studio
- Researcher and Analyst agents
- Official: Secure and governed data foundation for Copilot, Restricted Content Discovery, DLP for Microsoft 365 Copilot
Tool names, preview status and dates reflect Microsoft Learn pages as of November 19, 2026. Preview features move quickly, so confirm availability in your tenant and test every policy before you enforce it.
