Copilot only surfaces data a user already has at least view permission to, so Copilot oversharing comes from grants that already exist (Everyone except external users grants, oversized groups, redeemed links), which Copilot turns into answers. Microsoft's fastest controls change discoverability, not access: Restricted SharePoint Search is retiring and has blocked new enablement since 31 July 2026, and Restricted Content Discovery changes no permissions, does not cover OneDrive, and can take more than a week to process on a site with over 500,000 items. Restricted access control is the interim control that gates access, covers OneDrive, and is honored by Copilot, but it leaves the underlying grant in place. Only a permission fix, typically delegated to site owners through site access review, closes the exposure. A single assigned Copilot licence unlocks the SharePoint Advanced Management features that do this work, while Microsoft 365 E5 alone gives activity reports capped at 10,000 sites and no snapshots or remedial actions. Moving to a self-hosted assistant does not escape the problem: the broad grants travel with any permission-trimmed index, and Microsoft's discoverability controls do not. Start this week with the site permissions snapshot and the Everyone except external users report on your five most sensitive sites.
The Copilot pilot is ready, the licences are bought, and then someone asks the question that stalls the rollout: what happens when a junior analyst types "show me salary bands" or "summarize the open litigation"? That is Copilot oversharing, and the first thing to understand is that Copilot is not the cause. Microsoft's Copilot privacy documentation states that Copilot "only surfaces organizational data to which individual users have at least view permissions." The salary file was already readable. Copilot made it findable.
So Microsoft 365 Copilot oversharing is a permissions problem that predates Copilot: sites and libraries granted to Everyone except external users, security groups that grew to the whole company, and sharing links people clicked years ago. Microsoft ships several controls for it, and they split cleanly into two kinds. Some change what Copilot and search can find. Others change who can open the file. The fastest ones are in the first group, and a regulated firm that funds only those has hidden the problem, not closed it.
Sort every control into "hides it" or "closes it" before you fund any of them, because the grants follow you if you later point a private assistant at the same SharePoint, and the hiding does not. If you are still choosing between Copilot and a self-hosted workspace, our comparison of AI workspaces for teams covers that decision; everything below applies to both.
Why Copilot oversharing is a permissions problem
Copilot grounds on the Semantic Index, and Microsoft's privacy page says the index "honors the user identity-based access boundary so that the grounding process only accesses content that the current user is authorized to access." There is no bypass to patch. The same page tells administrators to use SharePoint's permission models so that "the right users or groups have the right access to the right content." Everything else in this post is a way of doing that, or a way of buying time until it is done.
The exposure that matters is the kind that reaches everyone. Three cases need separating, because the distinction changes what you remediate first.
Everyone except external users and Everyone grants
A site, library, folder or file granted to the special groups Everyone except external users (EEEU) or Everyone is readable by every internal account. Every internal Copilot user can ground on it. This is the org-wide case, and it is the one the data access governance reports are built to find.
People in your organization links
These are not org-wide exposure on creation. Microsoft's shareable links page is explicit: "Creating a People in your organization link doesn't make the associated file or folder appear in search results or make it accessible through Copilot. It also doesn't grant access to everyone within the organization." The link has to be redeemed. When it is sent from the SharePoint or OneDrive web interface, Outlook or a Teams chat, it is auto-redeemed for individual recipients, up to 100 of them, but not for groups or Teams channel posts. Anyone links work the same way: content becomes searchable for a person only after that person redeems the link. The exposure is per redeemer, which is narrower than an EEEU grant but can still be wide after years of forwarded links.
Specific people links
These make the item appear in search and Copilot for every user and security-group member added to the link. Picture a Specific people link shared with a security group of several thousand members: for Copilot purposes, that is a grant to every one of them. The practical consequence: an EEEU grant on an HR library is a higher priority than a hundred People in your organization links on marketing decks. Rank remediation by who can actually reach the content today, not by link type.
Copilot SharePoint oversharing controls: discovery vs access
The control map below has five rows: two change discovery (Copilot and search cannot find the content), one changes access (users cannot open it), one changes permissions (the grant itself is removed), and one is a diagnostic report that supports the cleanup.
Read the table by its second column. Only two rows change who can open the file, and only one of those removes the grant.
Restricted access control is containment that works on access
Restricted access control (RAC, also called restricted site access control) is the control Microsoft's own data access governance page names for "immediate action". The RAC page says users not in the specified group "can't access the site or its content, even if they had prior permissions or a shared link," and that Copilot and organization-wide search honor it. It applies to group-connected, Teams-connected and non-group sites, and to OneDrive, which makes it the only interim containment on this map for overshared OneDrive content. It is still a gate, not a fix. Microsoft states that a user "needs both the site or content access permission and be a member of the restricted access control group." Adding someone to the control group grants nothing. Our reading of that rule: the EEEU grant still sits beneath the gate, and removing the policy brings the old exposure back. Three further caveats belong in any risk register: RAC also produces evidence. Delegated changes by site admins require a justification, Purview audit events record applying and removing policies, group changes and the justification, and an insight report shows access denials over the past 28 days, downloadable for up to 10,000 denials. Permission hygiene is one layer. Controls on what the assistant is allowed to emit are another, covered in our guide to preventing data leakage in AI applications.
- Shared and private Teams channel sites are separate site collections. A policy on the parent team site does not cover them; each needs its own.
- External participants from another tenant in a shared channel are not evaluated against the policy at all.
- Restricting sharing to people outside the control group is an opt-in setting. By default, the RAC page says, sharing "doesn't follow the restricted site access policy."
| Control | What it changes | Covers OneDrive? | Time to take effect | Licence | What it does not do |
|---|---|---|---|---|---|
| Restricted SharePoint Search | Discovery: org-wide search and Copilot limited to an allow list of up to 100 sites | No: users' own OneDrive files still appear | Within an hour | Legacy: no new enablement since 31 July 2026 | Not a security boundary; recent, frequently visited and directly shared content still surfaces |
| Restricted Content Discovery | Discovery: a site is removed from org-wide search and Copilot responses | No: SharePoint sites only | Can exceed a week on sites over 500,000 items | Copilot licence in the tenant plus SAM | Changes no permissions; open documents, site-scoped search and the Feed are unaffected |
| Restricted access control | Access: only members of up to 10 control groups who also hold permission can open the site | Yes | Up to an hour to enable; longer for search and Copilot on large sites | Included with a Copilot licence | Leaves the underlying grant in place; channel sites need their own policy |
| Site access review plus permission removal | Permissions: the site owner removes the broad grant | No: SharePoint only | When the owner completes the review | Included with a Copilot licence | Up to 100 sites per review from the web view, 1,000 per month from the permissions report |
| Change history report | Nothing: diagnostic record of site and setting changes over 180 days | Not applicable | Not applicable | Included with a Copilot licence | Fixes nothing on its own |
Restricted Content Discovery: what Microsoft says it is for
Restricted Content Discovery (RCD) has the name that sounds most like a fix, so start with Microsoft's own description of it: "Restricted Content Discovery is designed as a temporary governance control that gives organizations time to review and right-size access while continuing their Copilot deployment." The FAQ is shorter: it "affects discoverability, not access permissions."
What it does: it limits discovery of a site's content, including recently interacted files, in organization-wide search (SharePoint home, Office.com, Bing) and in Copilot responses. It removes the Copilot button, the AI actions menus (including creating agents) and Create pages with AI from the site, and shows a Restricted tag. Microsoft's example is temporarily restricting a group of Finance or Human Resources sites while owners review access, then lifting the restriction.
What it does not do matters more for a regulated firm:
The latency is the operational trap. Microsoft says that for sites with more than 500,000 items, an RCD update "could take more than a week to fully process and reflect in search and Copilot experiences," and latency also depends on how many sites are updated at once. A control applied on Monday to a large claims archive may not be in force by the pilot launch on Friday. Microsoft also cautions against overuse, because every restricted site shrinks what Copilot can answer from.
RCD has one strength worth funding: its governance trail. It needs a Copilot licence in the tenant and SharePoint Advanced Management (SAM). Only SharePoint administrators manage it by default, and when it is delegated to site administrators they "must provide a justification for the change," which lands in the Purview audit log alongside enable and disable events. That is a record an internal auditor can read.
Restricted SharePoint Search: legacy only
Restricted SharePoint Search (RSS) was the original stopgap. Microsoft's page now says: "Starting July 31, 2026, new enablement is blocked," and directs customers to RCD. Where it is still on, it limits org-wide search and Copilot to an allow list of up to 100 sites (a hub site counts once, and its associated sites ride along) and takes effect within an hour. It has no deny list. Microsoft calls it "a short-term solution" that "isn't a security boundary and doesn't change any permissions." It also leaks by design. Results still include a user's OneDrive files, chats, email and calendar, files from frequently visited sites, files shared directly with the user, and files the user viewed, edited or created, the last three capped at the most recent 2,000 entities. The page says outright that a recently accessed site, or one shared with the user in Teams or Outlook, still shows up. It also restricts ordinary enterprise search for every user, including Exchange, To Do, Planner and Loop searches of SharePoint content, so it was never a Copilot-only switch. If your tenant still runs it, plan the move off it; do not build a new rollout on it.
Copilot oversharing reports: data access governance
Microsoft's foundational deployment guidance for Copilot, the page previously published as the Copilot oversharing blueprint, rests on three pillars: remediate oversharing, set up guardrails, meet regulations. Its first step is identifying high-risk sites and files. The tool for that is the data access governance (DAG) reports in the SharePoint admin center.
Snapshot reports
Snapshots show current state, and the DAG page describes these:
- Site permissions across your organization, which Microsoft marks as recommended. It covers all SharePoint and OneDrive sites and surfaces sites with thousands of users, guests, or EEEU permissions.
- Site permissions for users, which lists every site a named user can reach and whether access is direct or through groups. Run it for the accounts that worry you most: a new intern, a contractor, a shared service account.
- Sensitivity label applied to files, to see where labelled content sits.
- Sites and files shared with special SharePoint groups (EEEU or Everyone). This one is item-level: the page says it "tells you exactly which items are overshared and how access was granted."
Activity reports
Activity reports cover the last 28 days: sharing links created (Anyone, People in your organization, Specific people) and items shared with EEEU. They tell you whether new broad sharing is still being created while you clean up the old. Microsoft's recommended cadence is quarterly for the site permissions snapshots and monthly for activity reports. DAG is not available on Microsoft 365 operated by 21Vianet.
From report to remediation
The DAG page names the path: restricted access control for immediate action, the Change history report to find recent permission changes (it covers site and setting changes from up to the last 180 days), and site access review for the fix. Site access review is the step that actually removes grants, and it is designed around a compliance constraint. Microsoft's site access review page says "compliance reasons prevent IT administrators from accessing file-level or item-level details," so the review goes to site owners, who get an email tied to the specific report and a review page with a Manage access button. The status stays pending until the owner completes it, and completion records the reviewer's name, the date and comments. That record is the evidence you want in the file. Its limits shape the project plan. It covers SharePoint sites only, not OneDrive accounts. One review from the web view takes up to 100 sites, and the site permissions report allows up to 1,000 site access reviews per calendar month. The "Number of permissioned users" figure owners see is not deduplicated: Microsoft's worked example counts 40 users through a group, 10 direct and 20 through links as 80, even where the same people overlap. Do not report that number upward as a head count.
SharePoint Advanced Management licensing for Copilot
The licence question decides whether you can run the audit at all.
The middle row applies to any tenant running a Copilot pilot. Microsoft's SAM licensing page says that if an organization "assigns at least one Microsoft Copilot license to a user, SharePoint administrators get access to the SharePoint Advanced Management (SAM) features that support your Copilot deployment," and the prerequisites page adds that the user holding it does not need to be an admin. The licensing table marks those features available in worldwide, GCC, GCC High and DoD clouds. The base licence still has to be Office 365 E3, E5 or A5, Microsoft 365 E1, E3, E5 or A5, or Microsoft 365 GCC, GCC High or DoD.
The trap is the first row. A firm on E5 that has not assigned a Copilot licence can open DAG reporting, but Microsoft's page says the reports "don't provide snapshot reports or remedial actions." Collection only holds data from the day it was switched on. If the plan is to audit before buying Copilot, enable collection now, or assign one Copilot licence to a pilot user early so the snapshots and remediation controls are available for the audit.
| Licence position | Data access governance | Remediation controls | Watch for |
|---|---|---|---|
| Microsoft 365 E5, no Copilot licence and no SAM | Activity reports only, up to 10,000 sites; no snapshot reports | None of the SAM controls | Data collection must be enabled first; 28-day retention; reports appear 24 hours after enabling; collection pauses after 3 months without a report |
| At least 1 Copilot licence assigned to any user | Snapshot and activity reports, EEEU insights, permission state reports for sites, OneDrive and files | RAC, RCD, site access review, change history, block download policy, site attestation, inactive site and site ownership policies | Sensitivity labels report requires E5 or G5 |
| SharePoint K, P1 or P2 plus the SAM Plan 1 add-on | SAM features | SAM features, including restricted site creation by apps, which Copilot licences do not include | RCD still requires a Copilot licence in the tenant |
Does a private or self-hosted assistant fix oversharing?
This is where the on-premise question changes the answer, and the honest version is a correction. Moving from Copilot to a private assistant does not fix oversharing. In the private assistants we build over SharePoint, the permission audit is the go-live gate for exactly this reason.
Any assistant that respects SharePoint permissions has to read them. An index that trims results by user computes an effective permission per item from the site, library, folder and file, the same item permissions Copilot honors. An EEEU grant on a claims library is still an EEEU grant when your own index reads it. The broad grants travel.
The containment does not. Restricted Content Discovery is documented as affecting "organization-wide search experiences (SharePoint home, Office.com, Bing) and Microsoft Copilot discovery scenarios." Restricted SharePoint Search "impacts modern search and Copilot experiences" and "won't affect any other features based on the Microsoft Index." Neither page claims any effect on a third-party index or another application's reads. A firm that hid its HR sites with RCD while owners reviewed access, and then pointed a self-hosted RAG pipeline at SharePoint, has re-exposed those sites to whoever the grants allow.
Connector behaviour varies, so it is a go-live question, not an assumption. One documented example: Azure AI Search's SharePoint ACL ingestion, in preview, supports only Specific people links, not Anyone or People in your organization links, and does not support external or guest users. It also says SharePoint Information Management policies applicable to user access are not evaluated or honored at query time. Another connector may treat special groups differently. Index-side mechanics such as revocation lag and ACL entry limits are covered in our post on stale ACLs in RAG over SharePoint, and the same permission-aware retrieval requirement applies to any enterprise deep-search agent.
Before a connector touches a regulated library, put these to its vendor, or test them in your own tenant:
What self-hosting does change is real. The index, prompts and logs sit inside your perimeter, your security team can query them, and a regulator's question about who saw what is answered from your logs, not a vendor's. That matters under regimes that demand provable least privilege, which our overview of AI compliance in financial services sets out. Microsoft's broader zero-trust framing for agents and Purview guardrails is covered in our ZT4AI post. Neither replaces the audit.
Copilot readiness checklist for regulated SharePoint libraries
Define "done" for each class of sensitive library before any assistant, Copilot or private, is allowed to ground on it. The table below is the working version.
"Done" means three things are true for the library: no EEEU or Everyone grant remains, the people who can reach it match what the business owner signed off, and the record of that review is filed. Interim containment is allowed to sit in front of an unfinished library, but it does not count as done. When the inherited grants are clean, designing who should see what for an internal assistant is its own exercise, covered in our guide to role-based access control for AI applications. The wider strategy questions sit on our AI for business hub.
| Library class | First check | Interim containment | Permanent fix and owner | Evidence for the file |
|---|---|---|---|---|
| HR and payroll | Special-groups (EEEU or Everyone) report; site permissions for users on a new-joiner account | RAC with an HR control group | Site owner removes EEEU through site access review | Completed review with reviewer, date and comments |
| Credit and underwriting | Site permissions snapshot for sites with thousands of users | RAC; RCD only if SharePoint and the site is small enough to process in time | Site owner via site access review; IT removes EEEU at scale where owners are absent | Review record plus Purview audit justification |
| Claims | Special-groups report at item level; 28-day sharing links activity | RAC (large archives make RCD latency a risk) | Site owner via site access review | Review record; Change history entry for the permission change |
| Patient or clinical | Site permissions snapshot including OneDrive | RAC, since OneDrive is out of scope for RCD and site access review | Site owner for SharePoint; IT for OneDrive grants | Review record; RAC access-denial report |
| Legal hold and board | Site permissions for users on named high-risk accounts | RAC on each channel site as well as the parent team site | Site owner via site access review | Review record; Purview audit of the policy and its group changes |
How to start fixing Copilot oversharing this week
Run two reports: the Site permissions across your organization snapshot and the special SharePoint groups (EEEU or Everyone) report. If you are on E5 without a Copilot licence, switch on data collection today so you have 28 days of activity by next month. Pick the five most sensitive SharePoint sites those reports surface. Put restricted access control, not just Restricted Content Discovery, on any of them that show an EEEU grant, including their channel sites. Then send site access reviews to their owners with a completion date. By Friday you will have containment requested on the libraries that matter most and a dated record of who owns the fix.
FAQ
Quick answers to the questions this post tends to raise.



