Skip to content
Book a free call
Easify AI

Copilot Oversharing: Check What Microsoft 365 Copilot Can See Before Rollout

By Shaghil Shahzad, Easify AI · · 6 min read

The worry IT leads raise most often before a Copilot rollout is not about the AI. It is this: "What if someone asks Copilot about salaries and it tells them?"

Copilot will not break your permissions. But it will use every permission you have already granted, including the ones nobody remembers. This guide is a practical pre-rollout check, using the tools Microsoft provides, so you know what Copilot can see before your whole company starts asking it questions. It reflects Microsoft's guidance as of November 2026.

How Copilot decides what to show

Microsoft 365 Copilot grounds its answers in the content the signed-in user can already access: files in SharePoint and OneDrive, emails, chats and meetings. It does not see more than the user does.

That sounds reassuring until you look at how most tenants have grown. Sites shared with "Everyone except external users". Folders opened up for one project years ago. "Anyone with the link" sharing on files that were meant for one person. Before Copilot, finding those files took effort. With Copilot, a plain question surfaces them in seconds.

Example: an HR spreadsheet sits in a team site that was set to company-wide access when it was created. Nobody has opened it in two years. A new starter asks Copilot "what is the salary band for my role?" and gets an answer drawn from it. No permission was broken. The permission was simply wrong.

The tools you have, and what they cost

Microsoft's deployment blueprint for Copilot is organised around three pillars: remediate oversharing, set up guardrails, and meet regulations. The main tools:

Tool What it does for oversharing Licensing (as of November 2026)
SharePoint Advanced Management (SAM): data access governance reports Finds sites with sharing links, "Everyone except external users" access and broad permissions Included once at least one user has a Copilot licence
SAM: site access review Sends findings to site owners and asks them to confirm or fix access Included with Copilot
SAM: Restricted Content Discovery Hides chosen sites from organisation-wide search and Copilot Included with Copilot
SAM: restricted access control Limits a site to members of chosen security groups Included with Copilot
SAM: inactive sites and site ownership policies Finds abandoned sites and sites without enough owners Included with Copilot
Microsoft Purview Data Security Posture Management (formerly DSPM for AI) Weekly data risk assessment of your most-used sites, and recommended fixes Depends on your Purview licences; check before relying on it
Sensitivity labels and DLP for Copilot Label sensitive files, and stop Copilot summarising content with chosen labels Labelling and the sensitivity label report generally need E5-level licences

Note: the list of SAM features included with Copilot is set by Microsoft and has changed before. A few features, such as restricted site creation by apps, still need the separate SAM Plan 1 add-on. Check the current Learn page for your tenant type.

The pre-rollout check, step by step

Work in this order: find the problem, contain it, fix it properly, then keep it fixed.

  1. Get your own access in place. You need a SharePoint admin for the SAM reports, and a compliance admin role in Purview for data risk assessments. Confirm Purview Audit is on, so Copilot activity is recorded from the first day.
  2. Run the data access governance reports. In the SharePoint admin centre, run the sharing links report, the "Everyone except external users" report and the permission state report. These show which sites are open far wider than their content suggests.
  3. Check the Purview data risk assessment. It runs weekly on your most-used sites and flags sensitive information in places with broad access. Use it alongside the SAM reports, not instead of them.
  4. Shortlist the sensitive sites. HR, finance, legal, board and leadership sites, plus anything the reports flag with sensitive content and wide access. This list is usually short, often a few dozen sites even in a large tenant.
  5. Contain the worst cases now. For sites you cannot fix before rollout, use Restricted Content Discovery to keep them out of Copilot and organisation-wide search, or restricted access control to limit them to a security group.
  6. Start site access reviews. Send the findings to site owners and ask them to confirm who should have access. Owners know their content; IT does not.
  7. Fix ownerless and inactive sites. Use the site ownership and inactive sites policies to find sites nobody looks after, then assign an owner, archive or delete.
  8. Label what is truly sensitive. Apply sensitivity labels to HR, finance and legal content, and consider a DLP policy that stops Copilot processing items with your most sensitive labels.
  9. Test as a normal user. With a pilot account, ask Copilot the questions you are worried about: salaries, redundancies, board papers, client contracts. Fix anything that comes back.

Watch out: Restricted Content Discovery does not change permissions. Anyone who already has access can still open the files, and a user who recently worked with a file can still see it in Copilot. Treat it as a temporary barrier while owners fix access, not as the end state.

Who does what

  1. TriggerReports run

    Sharing links and broad access

    SharePoint
  2. StepSensitive sites flagged

    Data risk assessment

    Microsoft 365
  3. YouSite owners review

    Confirm or remove access

  4. StepRestrict or label

    Stopgaps, labels and DLP

    SharePoint
  5. ResultPilot approved

    Test prompts pass as a normal user

    Microsoft Copilot

The step that decides success is the human one. IT can run the reports and apply stopgaps, but only site owners can say whether "Everyone" on the Finance Archive site is a mistake. Give them a deadline, a short explanation and a named contact.

Keep it clean after go-live

Oversharing comes back. New sites are created, projects open folders to the company, people share links to get something done quickly. Build a light routine:

Task How often Owner
Re-run data access governance reports Monthly SharePoint admin
Review the Purview data risk assessment Monthly Compliance or IT security
Site attestation by owners Every 6 or 12 months Site owners
Inactive site clean-up Quarterly SharePoint admin
Review Restricted Content Discovery list Quarterly, aim to shrink it IT lead

Tip: change your defaults as well as your existing sites. Set the default sharing link to "specific people" or "people in your organisation" rather than "anyone", and require at least two owners on new sites. Fewer problems get created in the first place.

Where this fits in a rollout

The oversharing check is the first stage of a Copilot rollout, not a separate project. Once access is under control, run a small pilot, train people by role, and widen access team by team. Our guide on how to set up Microsoft Copilot for your team covers the licensing and setup side, and our Microsoft 365 Copilot rollout shows how the readiness check, pilot and training fit together.

Summary

  • Copilot respects permissions: the risk is permissions that are already too broad.
  • SAM is included with Copilot: its reports, access reviews and site restrictions are the core toolkit.
  • Work in order: find, contain, fix with site owners, then keep it clean.
  • Stopgaps are temporary: Restricted Content Discovery hides sites from Copilot but does not fix access.
  • Test as a normal user with the questions you fear most before the wider rollout.
  • Repeat the check on a schedule, and fix sharing defaults so oversharing does not return.

Frequently asked questions

Does Microsoft 365 Copilot ignore SharePoint permissions?
No. Copilot only uses content the signed-in user already has permission to access. The risk is that existing permissions are often too broad, for example sites shared with everyone in the organisation, and Copilot makes that content much easier to find.
Is SharePoint Advanced Management included with Copilot?
Yes, as of November 2026. If at least one user in the tenant has a Microsoft 365 Copilot licence, SharePoint admins get the SAM features that support a Copilot deployment, including data access governance reports, site access reviews, Restricted Content Discovery and restricted access control. A few features, such as restricted site creation by apps, still need the SAM Plan 1 add-on.
What is the difference between Restricted Content Discovery and restricted access control?
Restricted Content Discovery hides a site from organisation-wide search and Copilot, but people who have access can still open its files. Restricted access control limits who can open the site at all, to members of chosen security groups.
How long does an oversharing check take?
For a small or mid-sized tenant, the first pass usually takes a few weeks, mostly waiting for reports and for site owners to respond. It should be done before the wider rollout, and then repeated on a schedule.