A glowing AI assistant helps office workers manage files, permissions, and cybersecurity on digital dashboards.
Microsoft 365 Copilot doesn't create an oversharing problem. It finds the one you already have, and it finds it quickly. That's the central argument of a governance piece from cyber-risk firm Kovrr, syndicated on Security Boulevard. Microsoft's own documentation mostly backs it up. The piece also points to a deadline many tenants may be underestimating: Restricted SharePoint Search, the allow-list control that let organizations start Copilot rollouts before cleaning up permissions, is being retired.

Microsoft's documentation states the principle directly. Copilot works in the signed-in user's context, and it can summarize or reference only content that user is authorized to access. Copilot gives nobody new rights. What changes is how easy things are to find. A budget workbook sitting on a site that was opened to "Everyone except external users" years ago used to depend on nobody knowing where to look. Now an AI assistant can surface it in a summary.

Kovrr's conclusion is that Copilot governance is mostly permissions work, and that work existed before the license did.

Summary: Copilot doesn't widen access, but it makes access that was already too broad easy to exploit by accident. Fix the permissions and you've fixed most of the Copilot exposure.

A glowing AI assistant helps office workers manage files, permissions, and cybersecurity on digital dashboards. Step one: build a baseline before you watch for changes​

SharePoint's Data access governance reports come in two kinds. They answer different questions, and Kovrr argues that many teams use only one of them.

  • Snapshot reports show the current state. Microsoft says the site permissions report covers the permission structure across all SharePoint and OneDrive sites. It flags sites with the broadest access, such as sites with thousands of users, external guests or "Everyone except external users" permissions. Other snapshot reports cover site permissions for a specific user and sensitivity labels applied to files.
  • Activity reports cover potential oversharing in the last 28 days. They focus on recently active sites where users created sharing links or shared content with large groups. The two types are the sharing links report and the "Shared with Everyone except external users" report.

Kovrr's point is simple: if you only run activity reports, you are measuring change against a baseline nobody ever set. Microsoft recommends the same order. Run site permissions reports first and repeat them quarterly. Then run activity reports monthly. Those intervals are recommendations, not requirements.

Activity reports also have limits. They track specific sharing activity on recently active sites, not every permission change in the tenant. That makes them narrower than Kovrr's line that they "catch new oversharing as it occurs."

The licensing detail that's easy to miss​

Kovrr says many organizations already have the snapshot tooling and don't know it. The documentation supports that, with some caveats:

Licensing situationWhat you get (per Microsoft documentation)
Microsoft 365 E5 without SharePoint Advanced ManagementActivity reports only, up to 10,000 sites. No snapshot reports or remedial actions
Tenants without SAM, before running activity reportsData collection must be switched on first. Reports appear 24 hours later, contain data only from that point, keep 28 days of data, and collection pauses if no report is generated for three months
At least one Microsoft Copilot license assigned to any userSharePoint admins get the SAM features that support Copilot, including permission state reports, RAC, RCD and site access reviews

Kovrr describes this as "an enterprise subscription." Microsoft's note names Microsoft 365 E5 specifically, so check your own SKU rather than assuming. Also, the Copilot-bundled SAM features are not identical to the standalone SAM Plan 1 add-on. Microsoft says restricted site creation by apps still requires Plan 1.

To find the reports: sign in to the SharePoint admin center, expand Reports, and select Data access governance. Microsoft labels the site permissions report as recommended. It's the one to run first.

Step two: pick the control that matches the problem​

This is where Kovrr says most deployment guidance goes wrong. The two site-level controls that will remain after the retirement solve different problems.

Restricted Content Discovery (RCD): it hides sites, it doesn't block them​

According to Microsoft's documentation, RCD keeps a SharePoint site's content out of organization-wide search and Copilot discovery. Site permissions don't change, and anyone who already had access can still open the content directly. Details admins should know:

  • It works only on SharePoint sites, not OneDrive.
  • It doesn't affect searches started from inside the site, or experiences such as Microsoft 365 Feed and Recommendations.
  • Content isn't removed from the search index, so Purview eDiscovery and auto-labeling keep working.
  • It removes SharePoint AI entry points from the restricted site, including the Copilot button, AI actions menus and Create pages with AI.
  • Changes can take a while to propagate. For sites with more than 500,000 items, Microsoft warns an update can take more than a week.
  • Microsoft calls RCD a temporary governance control and warns against overusing it, because heavy use reduces the completeness and relevance of search results and AI answers.

You can turn it on in the SharePoint admin center (Sites > Active sites, select the site, Settings tab, then switch on the content-restriction setting) or with PowerShell:

Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true

To check a site's status, run Get-SPOSite -Identity <site-url> | Select RestrictContentOrgWideSearch. For a tenant-wide view of which sites are restricted, run Start-SPORestrictedContentDiscoverabilityReport. Enabling, disabling and the justifications given for changes all appear in the Purview audit log.

Restricted Access Control (RAC): it actually blocks access​

RAC limits a site to designated Microsoft Entra security groups or Microsoft 365 groups. Microsoft's Copilot-readiness guidance says users outside those groups can't access the site or its contents, even if they previously had permissions or a sharing link. Per the SAM licensing table, RAC covers both SharePoint and OneDrive sites. To set it up, go to Policies > Access control in the SharePoint admin center and select Enable site access restriction.

Which one to use​

Kovrr's rule of thumb lines up with Microsoft's own guidance:

  • Use RCD when the content is legitimately available to a broad audience but shouldn't appear in org-wide search or Copilot answers.
  • Use RAC when the permissions themselves are wrong.

Kovrr warns that using RCD where RAC is needed "leaves the exposure intact and the search results tidy." If a junior analyst shouldn't be able to open the HR investigations site at all, hiding it from Copilot doesn't fix that. It only removes the easiest way to stumble onto it.

Summary: RCD controls what can be found. RAC controls who can get in. They don't substitute for each other.

The 2026 change: Restricted SharePoint Search is retiring​

The third control, Restricted SharePoint Search (RSS), is the one Kovrr says has dated a lot of published guidance. RSS was a tenant-wide allow-list: it limited org-wide search and Copilot discovery to up to 100 curated sites. Microsoft's documentation says it is not a security boundary and changes no permissions. It also doesn't guarantee that only allow-listed sites appear, because recently accessed sites and content shared in Teams or Outlook still show up.

Kovrr mentions only the July 31, 2026 block on new enablement, which has already passed. The full schedule comes from Message Center post MC1395311, published June 18, 2026:

  • July 31, 2026: New RSS enablement will be blocked.
  • July 2026 to January 2027: Retirement period.
  • January 31, 2027: RSS will be fully retired (no extensions or exceptions).
  • February 28, 2027: RSS PowerShell cmdlets will be retired.

The most important detail is in the same notice: organizations must transition to Restricted Content Discovery (RCD) or other controls to manage content discoverability, as Microsoft won't migrate RSS settings automatically. Directions on Microsoft puts it more bluntly: "There is no migration path."

The two controls also work in opposite directions. As Creospark's comparison describes it, RCD restricts specific sites at the site level, while RSS allow-listed approved sites across the whole tenant. Once RSS switches off, organization-wide search and Copilot will use only the permissions already set on each site. Any site that was kept out simply by not being on the allow list becomes discoverable again unless someone applies controls to it before then.

If RSS is still on in your tenant​

Kovrr suggests treating the allow-list as a record of which sites were reviewed, then moving controls onto the sites themselves. Microsoft doesn't require that, but it's a sensible approach. Combined with Microsoft's documented process, a workable sequence looks like this:

  1. Confirm whether RSS is enabled and export the current allow-list. The Message Center notice lists both as first steps.
  2. Run the site permissions snapshot report to find broadly accessible sites that RSS was quietly keeping out of view. Remember that those sites are not on the allow-list.
  3. For sites where access itself is wrong, apply RAC or fix permissions directly. Microsoft also offers site access reviews to delegate this to site owners.
  4. For sites that are legitimately broad but shouldn't surface in Copilot, apply RCD, allowing time for index propagation.
  5. After permissions and governance are validated, disable RSS with Disable-SPORestrictedSearch, and tell Copilot agent owners and IT that responses may change. Microsoft recommends both steps.

Don't wait until January. RCD can take more than a week to take effect on very large sites.

What Kovrr gets right, and where its pitch comes in​

Kovrr's piece ends with a monitoring framework and a request to book a demo, so it's worth separating the parts Microsoft's documentation supports from the parts that are vendor argument.

Kovrr lists three things to monitor once Copilot is live: newly overshared sites, regulated material appearing in summaries, and whether the same user who gets turned away by Copilot goes to an unlicensed AI tool instead. Kovrr admits that only the first is covered by Microsoft's own tooling.

The second is more covered than Kovrr suggests. Microsoft documents Purview audit records for Copilot prompts, responses and referenced content, along with sensitivity-label inheritance and DLP-based restrictions. Kovrr is right, though, that permission reports alone don't tell you what categories of data show up in Copilot answers.

The third claim is that strict restrictions push workers toward shadow AI that nobody logs. It's plausible, and anyone who has watched users route around a blocked tool will recognize the pattern. However, Kovrr offers no data for it, and its proposed fix (cross-assistant monitoring on a governance platform) is the product it sells. Treat that as an argument to weigh, not a finding.

Kovrr's advice to restrict narrowly holds up better, and Microsoft's own caution about overusing RCD supports it. Apply access controls to the usually small set of sites holding regulated or highly confidential material that ended up with broad access by accident. Use RCD carefully. Don't strip Copilot's reach across ordinary working content, or you'll pay for licenses nobody finds useful.

Summary: In practice, that means three steps. Run the site permissions snapshot, which your Copilot license may already include. Choose RCD or RAC based on whether the problem is visibility or access. Remove any dependence on RSS before January 31, 2027. Whether you also need tooling that tracks AI use outside Microsoft 365 depends on your organization, but that's a separate decision from getting the SharePoint permissions right.

 

References

  1. Governing Microsoft 365 Copilot at Work | Kovrr - Security Boulevard Security Boulevard 2026-10-25T07:05:01+00:00
  2. Restricted SharePoint Search Limits Copilot Results - Directions on Microsoft directionsonmicrosoft.com
  3. Copilot’s New Security Controls for SharePoint: Understanding RCD and RSS creospark.com