Restricted SharePoint Search Retiring: Next Steps
Share on LinkedIn!
| #SimpleSharepoint #SharePoint #Microsoft365Copilot #MicrosoftSearch #DataGovernance #CopilotReadiness #Oversharing #SharePointOnline #ITGovernance #M365Admins |
| If you switched on Restricted SharePoint Search to keep sensitive sites out of Copilot, that guardrail now has an expiration date. Microsoft is retiring Restricted SharePoint Search (RSS), the control many organizations enabled as a stopgap to limit which SharePoint content Microsoft 365 Copilot and Microsoft Search could surface during permissions reviews. New RSS enablement is blocked after July 31, 2026; RSS stops working entirely on January 31, 2027; and the PowerShell cmdlets retire February 28, 2027. The Catch: Microsoft won’t migrate your configuration for you. If RSS is the only thing holding sensitive sites back from Copilot, those sites become discoverable again the moment RSS stops working — unless a successor control is already in place. The Migration Path: the replacement is Restricted Content Discovery (RCD), which applies discovery limits per site and is built for Copilot scenarios rather than as a temporary cap. Moving over is a project, not a switch — you need to know which sites RSS protects, and why, before you can reproduce that in RCD. Action Items for M365 Admins • Check whether RSS is enabled and export the allowed-site list while the cmdlets still work. • Map each restricted site to a Restricted Content Discovery configuration or another control. • Validate that Copilot and Microsoft Search surface only what you intend, before the January 2027 cutoff. The organizations treating this as a serious Copilot-governance project, rather than a last-minute cmdlet swap, won’t be surprised by what AI can see next year. We help organizations move from legacy RSS to a discovery model that actually holds up. |
