Restricted SharePoint Search is retiring: a practical transition to Restricted Content Discovery

Microsoft describes Restricted SharePoint Search (RSS) as a retiring temporary control. New enablement has been blocked since 31 July 2026. That statement does not mean every existing tenant configuration stopped working on that date, and it does not create a safe one-click migration to Restricted Content Discovery (RCD). First determine whether RSS is still active, why its allowlist was created and which actual permissions problems it may be masking. Microsoft recommends broader content governance and access controls. The objective is to preserve legitimate access, reduce unintended discovery and avoid depriving search and Copilot of useful content.

What is retiring and what has not been announced

RSS uses an allowlist of SharePoint sites to narrow organization-wide search and some Copilot or agent experiences. Microsoft explicitly says that new activation is blocked from 31 July 2026 and calls the feature retiring. The cited guidance does not provide one universal date when all previously enabled configurations stop operating. Do not translate the announcement into a claim that RSS was fully shut down on that day. If your tenant still uses it, plan a controlled disablement after checking actual permissions, Microsoft Purview policies and the effect on search results for different user groups.

RSS and RCD take opposite approaches to discovery

RSS starts with a short list of sites allowed into broad discovery. RCD is a site-level setting that temporarily suppresses selected higher-risk sites from organization-wide search and Microsoft Copilot answers, while the rest of the estate remains discoverable. RSS has a 100-site allowlist limit and does not scale as a long-term model in a large tenant. Microsoft says RCD can be applied to as many as 20,000 sites but cautions against indiscriminate use because it can reduce the completeness and relevance of results. This is an architectural change rather than a conversion of one list into another.

Discovery controls are not a security boundary

Neither RSS nor RCD repairs permissions that are too broad. A user who already has access may still open the document directly. Under RCD, users can still find their own files or content they recently interacted with, and the setting does not remove content from the Microsoft 365 search index. Search initiated inside the site and some other intelligent experiences may behave differently from organization-wide search. If the requirement is to control who can open a site, fix membership and sharing links or consider Restricted Access Control. That separate policy restricts access to specified groups, and Copilot and search honor the resulting boundary.

Inventory the reason for the old exception

Record the RSS status, allowlisted sites, hubs and associated sites, content owners and the reason those sites were once considered safe. Also identify sites outside the allowlist that staff visit frequently or share directly. Microsoft states that RSS never guaranteed absolute exclusion: previously accessed or shared files could still matter to results. An inventory is therefore more than an export of configuration. It maps real workflows and data exposure, and it should be reviewed jointly by SharePoint administration, security and the owners of important sites. Without that context, replacing a technical setting may preserve the underlying oversharing.

Identify risky sites by content and access

Before disabling RSS, find sites with broad groups, anonymous or persistent links, unclear ownership and sensitive material. Use available Data Access Governance reports, sharing information and site access reviews in SharePoint Advanced Management. An HR workspace may need prompt scrutiny, whereas an internal knowledge base should remain discoverable so employees and Copilot can find approved answers. Microsoft positions RCD as a temporary protection for selected sites while review is under way, not as a new tenant-wide prohibition. Prioritize by risk and business impact, not by alphabetic order or site count.

Fix permissions before changing discovery

For each candidate site, compare the intended audience with actual members and visitors. Review groups, guests, sharing links and files that owners cannot classify confidently. Remove unnecessary access and define approval for future sharing. Where access itself must remain limited to specified groups, Restricted Access Control may be appropriate; for sensitive files, consider relevant Microsoft Purview labels and DLP policies. RCD can then act as a time-limited supplement until this remediation is finished. Hiding an item in a broad result does not make an oversharing incident resolved. Record who approved each change and how direct access is expected to work afterward.

Introduce RCD in small, measured batches

Administrators can manage RCD from the settings of an active site in the SharePoint admin center or with Set-SPOSite and the RestrictContentOrgWideSearch parameter. Confirm the SharePoint Advanced Management requirements, administrative role and Copilot licensing prerequisites in current Microsoft guidance before the change. Select pilot sites with named owners, capture the original state and document the reason for restriction. Propagation across search and Copilot takes time; a test in the first minute can be misleading. Avoid switching an entire estate based on one account or one search query. Test each wave before expanding to more sites.

1. 01

   Measure the starting state

   Capture RSS status, the site list and representative queries from several user roles

2. 02

   Review the risk

   Agree permissions, sensitivity and the business reason for each restricted site with its owner

3. 03

   Apply RCD selectively

   Enable it on pilot high-risk sites and record a date for the next review

4. 04

   Test the experience

   After propagation, check direct access, search and Copilot answers from different accounts

5. 05

   Disable RSS deliberately

   After security and site-owner sign-off, test results without the old allowlist

6. 06

   Maintain the control

   Track exceptions, change audit and removal dates after remediation

Test more than one role and one route to content

Build scenarios for the file owner, an ordinary site member, a user with recent access, someone without permissions and an administrator. Each should test direct opening, organization-wide search, site-context results and the relevant Copilot experience. Record the exact query, account, time and expected result. RCD should not remove direct access from an authorized user, but it should reduce wider discovery. When results differ, check propagation delay and the user’s previous interaction with the content first. A single search that happens not to show a title is not proof of a secure configuration.

Turning off RSS is a change in its own right

Once access has been corrected and selected sites have documented temporary controls, disabling RSS can broaden organization-wide results and agent responses. Treat it as a service change with an owner, schedule, communication plan, regression queries and a way to investigate surprising findings. Tell agent owners that answers can draw on a wider set of permission-governed SharePoint material after the allowlist is removed. The change is not complete when a PowerShell command succeeds. It is complete when representative results have been measured and any newly discovered oversharing is owned and remediated.

Operate RCD as a temporary governance measure

RCD should buy a site owner time to repair risk, not become a permanent unexplained label. For each restricted site, retain an owner, reason, permissions plan, next review date and criteria for removing the setting. Microsoft allows management to be delegated to site administrators and records their justification, but delegation does not replace a central overview. Monitor whether too many restricted sites are degrading knowledge discovery. Continue periodic reviews of sharing and access because new groups, guests and links can recreate exposure even on a site that passed the initial pilot.