Fix SharePoint Oversharing Before Microsoft 365 Copilot: The 2026 Readiness Runbook

Microsoft 365 Copilot does not create oversharing — it exposes the oversharing you already have. Because Copilot retrieves content through Microsoft Graph and honors your existing SharePoint permissions, sharing links, and policies, it will surface anything a user technically has access to, including the site someone overshared three years ago and forgot. The fix before you turn Copilot on is a governed readiness sequence: find your overshared sites with Data Access Governance reports, clean up the worst offenders (starting with “Everyone except external users”), apply the right containment control per site, then pass a go/no-go gate before you scale.

This guide is written for the IT directors, SharePoint admins, and security leads on the Microsoft stack who have bought Copilot licenses and now have to answer their CISO’s question: “What will Copilot expose?” It walks through the exact controls Microsoft ships — SharePoint Advanced Management, Restricted SharePoint Search, Restricted Content Discovery, and Restricted Access Control — what each one does and does not change, and the phased remediation runbook that lets you deploy Copilot safely without waiting years for a perfect permissions cleanup.

Key takeaways

Copilot inherits your permissions, it doesn’t rewrite them: it retrieves content via Microsoft Graph and respects existing access, so oversharing becomes instantly searchable in plain language rather than newly created.
SharePoint Advanced Management is now effectively free with Copilot: one Microsoft 365 Copilot license unlocks SAM — and its oversharing controls — for the whole tenant, versus the former $3 per user, per month add-on.
Discovery comes before remediation: Data Access Governance reports and the Content Management Assessment tell you which sites are overshared; snapshot reports can take up to five days to run on large tenants, so start them early.
RSS, RCD, and RAC are not interchangeable: Restricted SharePoint Search is a temporary 100-site allow-list, Restricted Content Discovery hides a site from Copilot without changing access, and Restricted Access Control actually blocks who can open a site.
The “Everyone except external users” group is the most common landmine: it grants your entire organization access, and it is the first thing to hunt down and remove from sensitive sites.
Readiness is a gate, not a project you finish: you can ship Copilot on a clean subset while the multi-year permissions journey continues in the background.

The short answer: the pre-Copilot readiness sequence

If you only remember one thing, remember the order. Copilot readiness fails when teams jump to containment controls before they know what is actually overshared, or when they treat a temporary safety net as a permanent fix. The sequence that works is discovery first, then triage, then per-site control, then a gate.

Discover: run Data Access Governance reports and the Content Management Assessment to rank sites by exposure.
Contain fast: optionally switch on Restricted SharePoint Search to limit Copilot to a vetted allow-list while you work.
Remediate: fix permissions on the highest-risk sites, starting with broad org-wide sharing and “Anyone” links.
Cover the gaps: apply Restricted Content Discovery to sites that must stay accessible but shouldn’t be discoverable yet, and Restricted Access Control where you need a hard fence.
Gate: pass a go/no-go check before you expand Copilot beyond the pilot group.

Does Microsoft 365 Copilot respect SharePoint permissions?

Yes. According to Microsoft’s own Copilot readiness guidance, Copilot and agents retrieve data from Microsoft Graph and respect existing permissions, sharing settings, and policies. Copilot never shows a user a document they couldn’t already open on their own. That is the reassuring half of the story.

The uncomfortable half is that most enterprises have far more standing access than anyone realizes. A permission granted “temporarily” to a broad group in 2022, an “Anyone” link buried in a document library, a site shared with the whole company for one project — all of it was low-risk when finding content took effort. Copilot removes that effort. A natural-language prompt now traverses every location a user can technically reach and summarizes it in seconds. The risk isn’t a breach of your permission model; it’s the sudden visibility of everything wrong inside that model.

How do you find overshared SharePoint sites before Copilot?

You can’t remediate what you can’t see, so discovery is the first real work. Microsoft gives you three complementary lenses, all reachable once SharePoint Advanced Management is active.

Data Access Governance (DAG) reports. Found in the SharePoint admin center under Reports, DAG surfaces sites with oversharing signals. The Everyone except external users (EEEU) report flags the top 100 sites where content was shared with your entire organization in the past 28 days, and the sharing-links reports rank sites by “Anyone,” organization-wide, and specific-people links. Snapshot reports scan the whole tenant but can take up to five days to complete on large environments, so kick them off before anything else. Activity reports only cover a rolling 28-day window — if you don’t run them inside that window, data collection pauses and you lose the history.

Content Management Assessment (CMA). This guided assessment in SAM categorizes sites that need attention, identifies potentially overshared or ownerless sites, and returns remediation recommendations. Microsoft recommends rerunning it every 30 days to track progress — treat readiness as a recurring scan, not a one-time audit.

Microsoft Purview DSPM data risk assessments. For sensitivity-aware discovery, Data Security Posture Management runs a default data risk assessment weekly for your top 100 SharePoint sites by usage, showing how many items are shared with “anyone,” shared org-wide, or shared externally, and how many contain sensitive information types. That distinction matters: a site with 30 users and a folder of passport numbers is a bigger problem than one with 300 users and nothing sensitive.

Do you need SharePoint Advanced Management for Copilot?

You need it to use most of the controls in this guide, and the good news is you almost certainly already have it. SharePoint Advanced Management is Microsoft’s governance layer for SharePoint and OneDrive, covering three jobs: managing content sprawl, managing the content lifecycle, and preventing oversharing. It powers DAG reports, the Content Management Assessment, Restricted Content Discovery, and Restricted Access Control.

SAM used to be a standalone add-on at roughly $3 per user, per month, which many organizations skipped because the math ballooned across a large tenant, as practitioner reporting notes. That changed: SAM is now included with Microsoft 365 Copilot, and a single Copilot license unlocks it for the entire tenant. In practice, if you’re deploying Copilot at all, the oversharing toolkit is already paid for — the only remaining cost is the human effort to use it.

RSS vs. RCD vs. RAC: which oversharing control should you use?

This is where most readiness projects go sideways, because the three site-level controls sound similar and do very different things. One limits what Copilot can search tenant-wide, one hides a single site from discovery, and one actually blocks access. Pick the wrong one and you either leave a gap or break legitimate work.

The three SharePoint oversharing controls compared

Restricted SharePoint Search (RSS)

What it does: Limits Copilot and org-wide search to an allow-list of vetted sites; everything else is excluded, even sites users have access to.
Scope and limit: Tenant-wide allow-list, capped at 100 sites.
Changes permissions? No — it’s a discovery filter.
Best for: A temporary safety net at the very start of a rollout while you triage; Microsoft designs it to be turned off later.

Restricted Content Discovery (RCD)

What it does: Makes a specific site invisible to Copilot and organization-wide search and removes AI entry points such as the Copilot button, while leaving direct access intact.
Scope and limit: Per site; a blocklist approach with no hard site cap, set with Set-SPOSite -RestrictContentOrgWideSearch $true.
Changes permissions? No — users who already have access keep it.
Best for: Sensitive-but-needed sites (HR, legal, board) that must stay accessible while permissions are reviewed. Per Microsoft’s RCD documentation, propagation can exceed a week on sites with more than 500,000 items, so apply it early.

Restricted Access Control (RAC)

What it does: Blocks anyone outside named security or Microsoft 365 groups from opening the site at all, overriding other permissions and even sharing-link tricks.
Scope and limit: Per site; access granted through assigned groups.
Changes permissions? Yes — it’s a real access fence, the strongest oversharing control Microsoft ships.
Best for: High-sensitivity sites you want IT to gatekeep permanently.

The mental model: RSS calms the whole building down temporarily, RCD makes one room invisible to the librarian, and RAC puts a guard on the door. RSS and RCD manage discovery; only RAC manages access.

Copilot doesn’t break your security model — it reads it back to you out loud, and you don’t want the first audience to be your whole company.

Sequencing these controls, mapping them to license entitlements, and proving the result to a nervous security team is exactly the kind of work BabyBots runs as a fixed-fee Copilot data-readiness assessment — a scoped engagement that produces your exposure map, remediation runbook, and go/no-go recommendation in a single working sequence rather than an open-ended cleanup. It pairs naturally with our Shadow AI governance guide for teams tackling both problems at once.

How to fix the “Everyone except external users” landmine

The single most common source of pre-Copilot exposure is the “Everyone except external users” (EEEU) group. It grants access to every internal employee, and it gets attached to sites silently — often as the default when someone shares broadly “just to be safe.” Before Copilot, that meant content was technically open to the whole company but practically buried. After Copilot, it means any employee can summarize it on demand.

Work the EEEU report from DAG top-down. For each flagged site, decide whether org-wide access is genuinely intended (a company handbook, yes; a folder of offer letters, no). Remove EEEU where it doesn’t belong and replace it with a scoped group. Where you can’t remediate immediately — because a site is large or ownership is unclear — apply RCD as interim cover so the site stops surfacing in Copilot while the review plays out, then use site access reviews to delegate the permission cleanup to the actual site owners rather than absorbing it all as an admin.

The pre-Copilot remediation runbook: a phased sequence

A readiness effort that tries to fix everything at once stalls. Phasing it lets you deploy Copilot to a safe subset in weeks while the long tail of cleanup continues.

Phase 1 — Baseline (days 0–7): Confirm SAM is active, start DAG snapshot reports, and optionally enable RSS to limit Copilot to a vetted allow-list while you assess.
Phase 2 — Assess (days 7–21): Run the Content Management Assessment and a Purview DSPM data risk assessment; rank sites by combined exposure and sensitivity.
Phase 3 — Remediate and cover (weeks 3–12): Fix permissions on the highest-risk sites via site access reviews, starting with EEEU and “Anyone” links; apply RCD to sensitive-but-needed sites as interim cover.
Phase 4 — Fence (weeks 6–14): Apply RAC permanently to the sites that need a hard access boundary, such as HR, finance, and leadership.
Phase 5 — Lift the net (week 12+): Once the vetted set is clean, disable RSS so Copilot can search the broader, now-governed estate, and move stale sites to Microsoft 365 Archive so Copilot stops reasoning over dead content.

The go/no-go gate: when is your tenant Copilot-ready?

Readiness isn’t “zero oversharing everywhere” — that’s a multi-year journey. Readiness is a defensible gate for the scope you’re about to enable. A workable go/no-go check for a pilot or wave asks: have you run DAG and CMA in the last 30 days; have you remediated or covered every high-risk site in scope; is EEEU removed from all sensitive sites in scope; is RAC applied to your crown-jewel sites; and have you archived or lifecycle-flagged the obviously dead sites? If every answer is yes for the population you’re enabling, you can go — and keep the scans running as you expand.

Frequently asked questions

Does turning on Copilot expose confidential SharePoint data?

Only data users could already access. Copilot honors existing SharePoint permissions and retrieves through Microsoft Graph, so it never bypasses your security model. What it does is make pre-existing oversharing — broad groups, stale “Anyone” links, forgotten sites — instantly findable through natural-language prompts, which is why remediation should happen before rollout.

Do I need SharePoint Advanced Management for Copilot?

You need it to use Restricted Content Discovery, Restricted Access Control, Data Access Governance reports, and the Content Management Assessment. SAM is included with Microsoft 365 Copilot — a single Copilot license unlocks it tenant-wide — so if you’ve licensed Copilot, you already have the oversharing toolkit.

What’s the difference between RSS, RCD, and RAC?

Restricted SharePoint Search is a temporary, tenant-wide allow-list capped at 100 sites that limits what Copilot can search. Restricted Content Discovery hides a specific site from Copilot and org-wide search without changing who can access it. Restricted Access Control actually blocks anyone outside named groups from opening a site. RSS and RCD govern discovery; only RAC governs access.

How do I find overshared sites before rolling out Copilot?

Start with Data Access Governance reports in the SharePoint admin center — especially the “Everyone except external users” and sharing-links reports — then run the Content Management Assessment and a Microsoft Purview DSPM data risk assessment for sensitivity context. Snapshot reports can take up to five days on large tenants, so start them first.

How long does SharePoint oversharing remediation take?

Plan for a phased effort measured in weeks to a few months for a defensible pilot scope, not a single sprint. Discovery reports alone can take up to five days to run, RCD can take more than a week to propagate on very large sites, and permission cleanup depends on how many owners you can mobilize. The point of the phased runbook is to deploy Copilot safely to a clean subset while the long tail continues.

Can I block Copilot from accessing specific SharePoint sites?

Yes. Apply Restricted Content Discovery to make a site invisible to Copilot and org-wide search while preserving direct access, or Restricted Access Control to block access entirely for anyone outside approved groups. RCD is the right choice when the content must stay usable but shouldn’t be discoverable during a review.

Where this is heading

Copilot is only the first agent to read your tenant; Microsoft’s broader agent platform points to many more autonomous consumers of the same SharePoint content, each inheriting the same permission model. That makes data readiness a durable operating discipline rather than a one-time gate before a single product launch. The organizations that treat oversharing remediation as recurring governance — scans every 30 days, ownership enforced, sensitive sites fenced — will be the ones that can safely say yes to each new agent, while everyone else re-litigates the same exposure question every launch.

Get your Copilot data-readiness assessment

If your CISO is asking what Copilot will expose and you need a defensible answer, book a BabyBots Copilot data-readiness assessment. We map your oversharing exposure, sequence the right RSS, RCD, and RAC controls per site, and hand you a phased remediation runbook and a go/no-go recommendation — a fixed-fee engagement that turns “we’re not sure it’s safe” into a documented rollout plan. For teams pairing this with agent and shadow-AI controls, our AI agent knowledge grounding breakdown covers how SharePoint content feeds those systems.