Copilot oversharing has become a problem nobody can ignore any longer. Since January, Microsoft has had an official deployment blueprint that covers the issue in detail, and admins are taking a much harder look at who can access what in SharePoint. In most tenants I've worked in, the same problems come up again and again: old "Everyone except external users" links, guest access on important sites that nobody remembers granting, and site owners who have no idea which content Copilot can see. The new guidance is pleasantly practical. The hard part is deciding where to start and actually cleaning up before Copilot rolls out to more users and workloads.

The blueprint treats oversharing as an ongoing process

The Microsoft 365 Copilot blueprint for oversharing sets out a clear approach in three phases: pilot, deploy, operate. Its main focus is on finding and reviewing sites with risky sharing, particularly sites with lots of guests or broad share links. I like that it expects admins to do more than adjust technical settings. The blueprint asks for regular site access reviews rather than a single cleanup. In practice that means a structured process you can repeat, one that brings site owners in and makes them part of the solution. Many organisations underestimate how much technical debt they've built up and how much communication this takes, especially with older Teams and SharePoint sites.

Data access governance reports and access reviews give me the clearest picture

When I want to find risky sites, I now go straight to the Data access governance reports in the SharePoint admin center (→ Reports → Data access governance). If you have SharePoint Advanced Management (an add-on licence), you can start access reviews directly from these reports. Site owners get pulled in automatically, and following up as an admin becomes far easier. Visibility and action finally sit in one place, and I've seen that make a real difference in projects. The process looks roughly like this:

flowchart TD
    Scan["Data Governance Report"] --> Filter["Filter risky sites"]
    Filter --> Review["Start access reviews"]
    Review --> Owner["Site owner checks access"]
    Owner --> Action["Remove or restrict sharing"]

Figure: How a report turns into action in the oversharing flow with SharePoint Advanced Management.

Without the SAM licence you can still use the reports, but you'll have to track follow-ups manually. I described how this plays out in real deployments in an earlier post: /blog/sharepoint-advanced-management-copilot-access-control.

My advice: Set a fixed review cadence (for example, every six months) for the sites with the most guests and document every conversation with owners. Awareness only lasts if you keep track of it.

Restricted SharePoint Search limits what Copilot can reach

Restricted SharePoint Search is one of the most precise new controls. You define exactly which sites Copilot and M365 search can see. For sensitive or regulated areas this can save you a lot of trouble. You can exclude sites so that Copilot doesn't suggest or surface content from HR, executive or project sites you'd rather keep out of its scope. I've written about how this works in practice and how to fit it into your pilot phase here: /blog/restricted-sharepoint-search-copilot-oversharing.

You only get real value from it if you combine it with access reviews. First confirm who has access to the site, then restrict Copilot's search visibility where needed. And don't treat it as something you set once. Sites change, so this has to be maintained over time.

Sensitivity labels and Purview keep an eye on AI access

Good sensitivity labels for SharePoint sites and document libraries are still underused, and with Copilot around they matter more than before. Default labels make sure new files in critical sites are protected automatically. In reality, many tenants either don't have a usable taxonomy or have never switched on default labelling. Fixing that is a quick win. If you need a practical way to build a taxonomy, have a look at my post /blog/microsoft-purview-data-classification-protection.

For ongoing monitoring, Purview Data Security Posture Management for AI adds a useful layer on top. It shows you how Copilot and other AI features access sensitive data and flags anything unusual. Keep in mind, though, that monitoring comes second. The actual risk comes from excessive permissions, not from the AI features themselves.

I prioritise sites by a handful of practical criteria

In my projects, this combination works best:

  • Sites with "Everyone except external users" links
  • Sites with many guests
  • Communication/project sites with sensitive content
  • Sites lacking a sensitivity label or default label
  • Sites targeted for restricted content discovery

With this shortlist, the few critical sites stand out quickly, even in a tenant with thousands of them. For everything else, an annual access review is usually enough. Copilot oversharing isn't a project you finish once. It's ongoing work that combines technology and process. If you start using the new reporting and control features now, you'll be well prepared when the next wave of Copilot rollouts arrives.