SharePoint RSS Retirement: The Clock Is Ticking
SharePoint RSS retirement is happening whether you’re ready or not. By January 31, 2027, Restricted SharePoint Search (RSS) will be completely shut down. No extensions. No workarounds. If your organization relies on RSS for governance, the time to plan your SharePoint RSS retirement migration is now—not in December when panic sets in.
Here’s what’s at stake: RSS was designed to control what shows up in Microsoft Search and Microsoft 365 Copilot during governance reviews. It worked, but it was clunky, didn’t scale well, and definitely wasn’t built for modern Copilot scenarios. Microsoft realized this and created Restricted Content Discovery (RCD) as the replacement—and it’s objectively better.
But here’s the catch: Microsoft will not migrate your RSS settings automatically. That means auditing your tenant, identifying which sites have RSS enabled, understanding your current allowed-site lists, testing Restricted Content Discovery in your environment, and validating impact before you can turn off RSS. Six months sounds long. It isn’t.
What’s Happening: SharePoint RSS Retirement Timeline
The retirement of SharePoint RSS follows a specific, non-negotiable timeline:
| July 31, 2026 | New RSS enablement blocked—no new sites can be configured with RSS |
| January 31, 2027 | RSS service fully retires—all functionality stops (no extension possible) |
| February 28, 2027 | PowerShell cmdlets for RSS are removed |
That middle date is the hard deadline. Microsoft has stated clearly: there will be no exceptions and no grace period.
Why SharePoint RSS Retirement Matters Now
Three Reasons Admins Cannot Ignore SharePoint RSS Retirement
1. Copilot integration changes everything.
Restricted SharePoint Search never integrated with Copilot. It only controlled search visibility. Restricted Content Discovery does both—it controls what appears in Microsoft Search and what Copilot can access from restricted sites. If you’re rolling out enterprise Copilot (and you should be), RCD is not optional. It’s foundational to controlled AI adoption.
2. Your current setup will break on January 31.
If you’re using RSS and don’t migrate to RCD, your restricted content becomes fully discoverable on that date. Imagine a site you’ve been hiding from search suddenly appearing in every search result and every Copilot response. That’s a governance disaster.
3. The migration has hidden dependencies.
RSS used allow-list logic (this site is hidden, that site is allowed). RCD uses a different model. Your current configuration won’t map 1:1 to RCD. That means testing, validation, and potentially rethinking what “restricted” means for your org.
Who Needs to Act: SharePoint RSS Retirement Impact
This SharePoint RSS retirement affects:
- SharePoint and Microsoft 365 admins responsible for governance and compliance
- Organizations currently using RSS for search visibility control
- Teams planning Copilot rollouts who need content governance from day one
- Governance and security teams who rely on search/discovery controls
- Anyone with sensitive or confidential sites that need restricted access
The Action Plan: 5 Steps to Handle SharePoint RSS Retirement
Step 1: Audit Your Tenant (Week 1-2)
First, find out if you’re even using RSS. Many organizations have it enabled but don’t actively use it—and some don’t know they’re using it at all.
Run this Microsoft-provided audit script to check the current status of RSS in your tenant: Get the current mode of Restricted Search
This tells you:
- Is RSS enabled org-wide?
- If so, which sites are affected?
- What’s currently on your allowed-site list?
Time investment: 30 minutes to run. 1-2 hours to document findings.
Step 2: Identify Restricted Sites (Week 2-3)
Once you know RSS is enabled, use the discovery script to list all sites configured with RSS and their current allowed-site lists: Get the existing list of URLs in the allowed list
Create a spreadsheet tracking:
- Site URL
- Current RSS status (enabled/disabled)
- Business justification for restriction
- Owner (who approved this as restricted?)
- Migration target (will this use RCD, or a different control?)
Why this matters: You can’t migrate what you don’t understand. Document it now.
Step 3: Understand Restricted Content Discovery (RCD) (Week 3)
Before deploying RCD, understand how it differs from RSS:
- Scope: RCD works org-wide. You don’t allowlist individual sites—you mark content as restricted at the site level
- Access model: RCD prevents indexing of restricted content in both search and Copilot
- Governance: RCD integrates with Microsoft Purview and compliance tools
- Admin experience: RCD is managed in SharePoint admin center, not PowerShell alone
Read the official Microsoft documentation: Restricted Content Discovery Overview
Time investment: 2-3 hours reading + 1 hour lab testing.
Step 4: Test RCD in Staging (Week 4-6)
Do NOT pilot RCD in production. Set up a test environment:
- Create a staging site with sensitive test data
- Configure RCD on that site
- Run actual Microsoft Search and Copilot queries from a user account that should NOT have access to the restricted content
- Verify that:
- The site does NOT appear in search results
- Copilot cannot retrieve data from the restricted site
- A user WITH proper permissions CAN access and search the content normally
- Test with edge cases: shared documents, Teams channel content referencing the site, etc.
Critical: RCD + Copilot behavior can be different from RCD + Search alone. Test with actual Copilot prompts, not just search.
Time investment: 2-3 weeks of iterative testing.
Step 5: Deploy RCD and Decommission RSS (Week 7-8+)
Once testing is complete:
- Deploy RCD to production sites using the same business justification from your spreadsheet
- Verify each site is now governed by RCD, not RSS
- Disable RSS on those sites once RCD is confirmed working
- Run the disable script when ready: Enable or disable Restricted Search
- Update your internal documentation, runbooks, and support guides
- Train your support and governance teams on RCD troubleshooting
Common SharePoint RSS Retirement Mistakes to Avoid
Mistake 1: Orphaning Sites During Migration
The trap: You disable RSS on a site before RCD is fully configured.
The result: That site becomes fully discoverable—search indexes it, Copilot can access it, users see it.
The fix: Always bridge the gap. Have RCD ready before RSS is disabled. Test the handoff.
Mistake 2: Not Testing with Copilot
The trap: You test RCD with Microsoft Search only.
The result: Copilot behavior is different than search behavior. You deploy RCD, users complain that Copilot still surfaces restricted content, and you’re scrambling mid-deployment.
The fix: Test with actual Copilot queries. Use M365 Copilot or Teams Copilot on restricted sites. Verify the behavior matches your expectations.
Mistake 3: Forgetting About Shared Content
The trap: You restrict a site with RCD, but it’s linked in Teams channels, email, or shared with other sites.
The result: References leak. Copilot can still surface mentions of the restricted content, even if the site itself is hidden.
The fix: Map content dependencies before restricting. Understand what’s connected before you apply RCD.
Mistake 4: Waiting Until December
The trap: You wait until Q4 to plan SharePoint RSS retirement.
The result: Holiday freezes, implementation delays, 3-4 weeks lost to corporate schedules.
The fix: Start your audit in June or July. You have exactly 6 months of usable runway before administrative slowdown.
Restricted Content Discovery (RCD): The Governance Upgrade
Restricted Content Discovery isn’t just a replacement for RSS. It’s an upgrade to your governance posture:
- Better scoping: RCD lets you restrict content at the site level, with clear visibility into what’s restricted and why
- Copilot-aware: RCD is built for Copilot scenarios from day one. It controls both search and AI access
- Compliance integration: RCD works with Purview labels, retention policies, and audit trails
- Scalable: RCD doesn’t require allowlist management. Org-wide governance is cleaner and easier to maintain
Admin Tips: Streamline Your SharePoint RSS Retirement Approach
Tip 1: Use PowerShell for bulk operations.
If you have dozens of sites using RSS, PowerShell bulk scripts (provided by Microsoft) are faster than the UI.
Tip 2: Involve your security and compliance teams early.
They probably approved the original RSS restrictions. Loop them into the RCD planning so the migration doesn’t become a surprise.
Tip 3: Create an RCD deployment checklist.
Document each site’s migration: audit → RCD config → testing → decommission RSS → documentation. Reuse it for consistency.
Tip 4: Plan for communication.
Tell users why governance matters. Transparency about restricted content builds adoption faster than surprise policy changes.
Tip 5: Keep your allowed-site documentation updated.
Once RSS is gone, this documentation becomes your audit trail. Maintain it.
License Check: What You Need for Restricted Content Discovery
Restricted Content Discovery is included with SharePoint Online. No additional licensing required. If you have SharePoint Online, you have RCD.
The Paul-Take: Why SharePoint RSS Retirement Signals a Bigger Shift
Here’s what I’m seeing: Microsoft is moving governance away from negative controls (hide this, restrict that) toward positive, intentional controls. RSS was the old way—reactive, manual, site-by-site. RCD is the new way—proactive, integrated with Copilot, built for modern work.
RSS retirement isn’t a gotcha. It’s evolution. But it’s also a signal: if you’re not thinking about content governance as part of your Copilot rollout, you’re behind.
The admins who start their audit in June and test in staging by August will have a smooth migration. The ones who wait until January will be scrambling mid-deployment, dealing with frozen budgets and holiday schedules. The choice is yours.
The deadline is firm. No extensions. No negotiations. January 31, 2027 is when RSS stops working. Between now and then, you have the time to do this right. Use it.
Timing
According to Microsoft, SharePoint RSS retirement begins immediately. New enablement is blocked July 31, 2026. Full retirement and service shutdown is January 31, 2027. PowerShell cmdlets are retired February 28, 2027.
You have approximately 6 months from today. The audit phase must start now.
Resources
Microsoft Message Center: MC1395311 – Microsoft SharePoint Online: Retirement of Restricted SharePoint Search
Microsoft Learn Documentation:
Microsoft 365 Roadmap: View related updates on the Microsoft 365 Roadmap
Bottom line: SharePoint RSS retirement is a hard deadline. Start your audit today. Test RCD by August. Deploy by December. Your January 31 cutover will be smooth, not panicked. The governance posture you build now sets you up for controlled Copilot adoption down the line.