Content reviewed: 12 October 2026

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 allowed entries for broad discovery. RCD instead temporarily limits discovery of selected SharePoint sites while other content can remain available through normal permissions. RSS allows 100 entries, but hub-associated sites are not counted individually. The current RCD guide emphasises risk-based targeting. Do not mechanically turn the RSS allowlist into a restriction on every other site.

How the temporary SharePoint controls differ
QuestionRestricted SharePoint SearchRestricted Content Discovery
SelectionAllowed list for organisation-wide discoverySpecific restricted SharePoint sites
Scope100 entries, with special treatment of hub-associated sitesSite-level setting; apply according to risk
PermissionsDoes not change actual accessDoes not change actual access
Typical purposeShort transition barrier during reviewTargeted temporary protection while risky sites are remediated

Discovery controls are not a security boundary

Neither RSS nor RCD changes permissions. The current RCD description includes recently interacted files in broad discovery restrictions, while authorised users retain direct access. Working on an already open document is different from discovering it through broad search. Content remains indexed and site-context search has a different scope. For access restrictions, evaluate membership, sharing and Restricted Access Control.

One file, different access routes

RCD tests after propagation
RouteExpected scopeWhat it does not establish
Organisation-wide search / broad Copilot queriesRestriction of the selected site, including recently interacted filesRemoval of permissions.
Direct document URLAuthorised user can still open itBroad discoverability.
Search within the siteRCD does not restrict it like organisation-wide searchRCD failure.
Summarising an open documentWork on content already in use can remain availableAn exception to all broad discovery restrictions.
Purview eDiscovery / auto-labellingIndex remains; those features continueIdentical scope in ordinary user search.

Microsoft’s guide and FAQ define this scope. RCD supports SharePoint sites, not OneDrive sites. It also removes some AI entry points inside restricted SharePoint sites, such as the Copilot button and agent-creation menus. Distinguish a missing button, a missing result and denied access: they are different outcomes.

RAC needs permission and group membership

Restricted Access Control does not grant new content access. Users need underlying permission and membership of a permitted control group. A shared link does not bypass the group requirement. A site can have up to ten supported groups; a parent Teams site policy does not automatically cover separate private/shared-channel sites. Assess those sites separately.

Illustrative result with active RAC
File permissionPermitted group memberResult
YesYesAccess can succeed unless other controls prevent it.
YesNoRAC blocks access.
NoYesMembership does not create content permission.
NoNoAccess is not allowed.

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.

RCD has specific licensing prerequisites

The current RCD guide requires an organisation Copilot licence and available SharePoint Advanced Management. The SAM prerequisites describe administrator access with at least one Copilot licence assigned to a user; that user need not be the SharePoint administrator. Other SAM routes include an eligible standalone add-on or E7, but general SAM access does not establish every RCD-specific prerequisite. Verify base subscription, assignment, role and feature.

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.

The current admin-centre control is Sites → Active sites → selected site → Settings → Restrict content from Microsoft Copilot. Verify the saved state separately from completed search propagation.

  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

Propagation has no universal short deadline

The RCD FAQ says sites with more than 500,000 items can take more than a week to process. Concurrent updates also affect the outcome. Do not promise a one-hour estate-wide migration. Record setting, change time and later results for several accounts; one immediate query cannot prove success or failure.

A three-site transition model

An internal knowledge base should remain discoverable. An overshared HR site receives temporary RCD while permissions are fixed. A project site restricted to a particular audience needs an access design, potentially RAC. These are three different changes. After disabling RSS, verify knowledge-base discovery, restricted broad discovery of HR content and denied direct access to the project for an unauthorised user.

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.

Frequently asked questions

Is Restricted SharePoint Search already completely switched off?

Microsoft confirms that new enablement has been blocked since 31 July 2026 and calls RSS retiring. Its cited guidance does not set a universal shutdown date for every existing configuration. Check your tenant state.

Does RCD replace SharePoint permissions?

No. RCD limits broad discovery of selected sites and use in some Copilot responses, but it does not change the underlying permissions.

Should we apply RCD to every site outside the old allowlist?

No. It is a targeted temporary measure for risky sites. Blanket application can damage search and Copilot relevance.

What if a user must actually be denied access?

Correct membership and sharing, or apply an appropriate access control. Restricted Access Control can limit site access to defined groups.

Can RCD be applied to OneDrive?

Current RCD documentation supports SharePoint sites, not OneDrive sites. Do not infer its scope from other controls such as RAC.