Skip to content
An IT security leader and SharePoint administrator review a restricted content discovery setting that excludes a SharePoint site from Copilot.

Restricted Content Discovery: Keeping Sites Out of Copilot

On January 31, 2027, Restricted SharePoint Search switches off for good, and new enablement already closed on July 31, 2026. If your tenant leaned on it to keep certain sites out of Copilot’s reach, here is the part that catches people: Microsoft is not carrying those settings over to anything. The sites that control was holding back can start surfacing in Copilot answers and organization-wide search unless someone re-restricts them first.

Two similarly named controls sit at the center of this. Restricted SharePoint Search is leaving, Restricted Content Discovery is staying, and neither one fixes the problem people usually reach for them to solve. Sorting that out is worth doing before the deadline rather than after.

What is Restricted Content Discovery?

Restricted Content Discovery is a per-site control that keeps a SharePoint site’s files out of Microsoft 365 Copilot and organization-wide Microsoft 365 search. When Copilot goes looking for content to answer a prompt, it queries Microsoft Search, and files on a site with Restricted Content Discovery turned on are left out of those results. If Copilot cannot see the files, it cannot use them to build an answer.

A mid-2026 update went a step further. On sites with the control enabled, Microsoft now removes the Copilot entry points from the interface as well, so the buttons and menus that would invite someone to ask Copilot about that content are gone rather than just quiet. The change is applied automatically inside the service, with no admin action required. The practical effect is a clean way to take a high-risk site off the table for AI-assisted discovery while you decide what to do about it.

Restricted SharePoint Search is retiring: what changes and when

Restricted SharePoint Search, a separate and older control, is being retired on a fixed schedule. New enablement is already blocked, and the feature goes away entirely at the start of 2027. Existing configurations keep working through the retirement window, which is the runway you have to act.

The dates that matter:

  • New enablement blocked as of July 31, 2026.
  • Existing configurations keep working through the retirement window.
  • Full retirement on January 31, 2027.
  • The related PowerShell cmdlets discontinued on February 28, 2027.

The detail that turns this from housekeeping into a real task is that Microsoft will not move your configuration to Restricted Content Discovery for you. Whatever Restricted SharePoint Search was holding back does not transfer. When the feature retires, that protection ends, and the content underneath it is governed by whatever permissions and discovery controls you have put in place by then.

Microsoft’s own description of Restricted SharePoint Search and Restricted Content Discovery is the reference for how each control behaves; the retirement schedule is published through the Microsoft 365 message center.

Why the two controls get confused

The two controls get confused because their names are nearly identical and their jobs overlap, but they work differently. Restricted SharePoint Search was a tenant-wide approach built as an allow-list and capped at 100 sites, which made it a blunt instrument for a large environment. Restricted Content Discovery is applied per site, with no small cap, so you point it at the specific sites that need it.

That difference matters for your migration. You are not flipping one switch off and an identical switch on. You are moving from a tenant-level list to a site-by-site model, which means someone has to decide which sites actually warrant the restriction rather than assuming the old scope carries over. It does not carry over, and the old scope was never a security boundary to begin with.

Comparison of the retiring Restricted SharePoint Search and Restricted Content Discovery, the per-site control that keeps SharePoint content out of Copilot.
Restricted SharePoint Search retires January 31, 2027; Restricted Content Discovery is the per-site replacement.

What happens to your content when Restricted Search retires

When Restricted SharePoint Search retires, content it was keeping out of search and Copilot can become discoverable again unless you have re-restricted it or fixed the permissions underneath. The exposure was technically always present. Copilot grounds its answers only in content a person already has permission to open, so it never granted new access. What Restricted SharePoint Search did was hide weak permissions from easy discovery.

That is the uncomfortable part. If a site was overshared – a library opened to “Everyone except external users,” a folder shared far past its intended audience – the restriction masked the problem rather than resolved it. Remove the mask, and Copilot will surface that content to anyone who technically has access, at conversational speed. A permission review before Copilot rollout is how you find those sites, and Data Access Governance reports help rank them by exposure before the retirement date removes the cover.

The honest limit of any discovery control

Restricted Content Discovery keeps content out of Copilot’s view, and it does nothing to the permissions underneath. The people who should not have access to a site still have it after you turn the control on. They simply cannot surface that content through Copilot or search for the moment. Treating the control as the finish line leaves the real exposure sitting exactly where it was.

This is the position worth being clear about. Restricted SharePoint Search was never a security boundary, and Restricted Content Discovery is the same category of tool, built to contain exposure rather than remove it. It has a real and useful job, which is to buy you time. It takes a high-risk site off the AI-discovery table today so you are not forced to choose between blocking a Copilot rollout and exposing content you have not cleaned up yet. What it cannot do is stand in for fixing the access. Used as a temporary hold while you correct permissions, it is exactly right. Used as the permanent answer, it quietly preserves the oversharing it was supposed to buy time against. The architecture and governance work underneath is what turns the restriction from a lasting crutch into a short one.

What to do before the deadline

The move is to contain first and correct second, on a schedule you control rather than one the retirement date forces on you. Before Restricted SharePoint Search retires, work through these steps:

  • Inventory which sites Restricted SharePoint Search is currently holding back, while the configuration still exists to read.
  • Re-restrict the genuinely high-risk sites with Restricted Content Discovery so nothing on them becomes Copilot-visible when the old control retires.
  • Correct the permissions on those sites so the content is only reachable by the people who should reach it.
  • Remove Restricted Content Discovery from each site once its permissions are fixed, so the restriction stays temporary.

One licensing note belongs here. Restricted Content Discovery is part of SharePoint Advanced Management, which is included with a Microsoft 365 Copilot license – one assigned Copilot license enables the capabilities for administrators – or through a separate SharePoint Advanced Management add-on for tenants without Copilot. Confirm what your tenant carries before you plan around it, since these terms move. SharePoint Advanced Management for Copilot covers what the tier adds for oversharing and access review.

Where this fits in a Copilot rollout

Restricted Content Discovery is one containment step inside a Copilot readiness effort, not the whole of it. It lets you turn Copilot on for the organization while a handful of high-risk sites stay off the AI-discovery table, so a few unresolved areas do not hold up the entire rollout. The broader work of correcting permissions and assigning clear ownership is what makes the answers Copilot returns worth trusting.

The rest of that work, from source-of-truth decisions to lifecycle cleanup, is mapped in the SharePoint AI Readiness Center.

If you are early in that planning, a Copilot readiness assessment identifies where oversharing and stale content create the most risk, and the wider Copilot readiness model connects permissions, content quality, ownership, and governance into a sequence you can actually run. Restricted Content Discovery earns its place in that sequence as the fast containment move. It should not be the only move you make.

If your tenant still relies on Restricted SharePoint Search, the inventory and re-restriction steps above take a few weeks to do properly, and the deadline is fixed. Talk to dataBridge if you want the migration and the permission cleanup underneath it planned as one sequence.

Frequently asked questions

What is the difference between Restricted Content Discovery and Restricted SharePoint Search?

Restricted SharePoint Search was a tenant-wide allow-list capped at 100 sites, and it is being retired. Restricted Content Discovery is a per-site control with no small cap that keeps a specific site’s files out of Copilot and Microsoft 365 search. They are not the same feature, and Microsoft does not convert one into the other.

When is Restricted SharePoint Search being retired?

New enablement of Restricted SharePoint Search was blocked as of July 31, 2026, and the feature is fully retired on January 31, 2027. The related PowerShell cmdlets are discontinued on February 28, 2027. Existing configurations keep working through the retirement window, which is the time you have to migrate.

Will my content become visible to Copilot when Restricted SharePoint Search retires?

It can. Content that Restricted SharePoint Search was holding back may become discoverable by Copilot and organization-wide search once the feature retires, unless you have re-restricted those sites with Restricted Content Discovery or corrected the underlying permissions. Microsoft does not migrate your old configuration, so nothing is protected by default after retirement.

Does Restricted Content Discovery fix oversharing?

No. Restricted Content Discovery hides a site’s content from Copilot and search, but it does not change who has permission to that content. It is a containment control that buys time to correct permissions, not a replacement for fixing them. Used as a permanent solution, it leaves the oversharing in place.

What license do I need for Restricted Content Discovery?

Restricted Content Discovery is part of SharePoint Advanced Management, which comes with a Microsoft 365 Copilot license or through a separate SharePoint Advanced Management add-on. Confirm your tenant’s exact entitlement before planning, since licensing terms change.

Reviewed By

Liya Hagos
Liya HagosSharePoint and Power Platform Developer
Liya focuses on building practical SharePoint and Power Platform solutions that improve productivity and simplify work. She combines development skill with platform knowledge to create business applications, automate processes, and strengthen the day-to-day usability of Microsoft 365 environments.

Author

  • Andrea Skinner Bio Square

    Andrea leads operations at dataBridge and plays a key role in keeping complex SharePoint and Microsoft 365 engagements organized, efficient, and well managed. She brings a strong blend of project leadership, platform knowledge, and operational discipline that helps clients move forward with confidence.

SHARE ON SOCIAL MEDIA