Control 1.3: Restricted SharePoint Search and Restricted Content Discovery — Troubleshooting
Common issues and resolution steps for Restricted SharePoint Search (RSS) and Restricted Content Discovery (RCD) configuration.
Common Issues
Issue 1: RSS or RCD Not Available in SharePoint Admin Center
- Symptoms: The Restricted SharePoint Search option does not appear under Settings > Search, or
Set-SPOSite -RestrictContentOrgWideSearchreturns "unrecognized parameter" or "property not found" - Root Cause: RCD requires the SharePoint Advanced Management capabilities Microsoft documents for Copilot deployment scenarios. Verify the tenant has a Microsoft 365 Copilot license and that current SharePoint Advanced Management prerequisites are satisfied. Older versions of the SPO Management Shell may not include RCD or RSS cmdlets. Note: RSS new enablement is blocked from July 31, 2026 — if the RSS toggle is unavailable for enablement after that date, this is expected behavior.
- Resolution:
- Verify SharePoint Advanced Management is licensed and activated in the tenant (check Microsoft 365 Admin Center > Billing > Licenses)
- Update the SharePoint Online Management Shell to the latest version:
Update-Module Microsoft.Online.SharePoint.PowerShell - If Copilot licensing and prerequisites are satisfied but RCD features are still not visible, check your tenant's release ring and service rollout status before concluding the feature is unavailable
- For RSS: if trying to enable RSS after July 31, 2026, this is expected — use RCD instead
- Contact Microsoft support if RCD remains unavailable after licensing and module updates
Issue 1b: RCD-Enabled Site Content Still Appearing in Copilot
- Symptoms: After enabling
RestrictContentOrgWideSearchon a site, Copilot still surfaces content from that site - Root Cause: RCD configuration changes require time to propagate through Microsoft 365 indexing systems, and large sites can take significantly longer than small sites. Additionally, content may be cached in Copilot's retrieval layer.
- Resolution:
- Allow time for propagation before testing; Microsoft notes that large sites can require extended processing time and sites with more than 500,000 items can take more than a week to reflect the change fully
- Verify the setting was saved:
(Get-SPOSite -Identity <url>).RestrictContentOrgWideSearchshould returnTrue - Clear the user's browser cache and sign out/in to Microsoft 365 before retesting
- Note: RCD does not affect content already in Copilot's active context window — test with a fresh Copilot session
- If RCD is not working after the documented propagation window for the site's size, check service health for search indexing delays
Issue 2: Allowed List Changes Not Reflected in Search Results
- Symptoms: After adding or removing sites from the allowed list, search results do not immediately reflect the changes
- Root Cause: RSS allowed list changes require time to propagate through the search index. Microsoft documents RSS itself as taking effect within about one hour after it is enabled, but it doesn't publish a fixed propagation window for later allow-list edits.
- Resolution:
- Allow time for the change to propagate before testing; use the RSS enablement timing only as a general indicator rather than as a guaranteed SLA for allow-list edits
- Verify the change was saved by running
Get-SPOTenantRestrictedSearchAllowedList - Clear the user's browser cache and sign out/in to Microsoft 365
- If changes still aren't reflected after allowing reasonable propagation time, check service health for search indexing delays
Issue 3: 100-Site Allowed List Limit Reached
- Symptoms: Attempting to add a site to the allowed list fails with a limit error, or the
Add-SPOTenantRestrictedSearchAllowedListcmdlet returns an error about maximum capacity - Root Cause: RSS supports a maximum of 100 sites in the allowed list. Organizations with more than 100 sites that need Copilot access will hit this limit.
- Resolution:
- Review the current allowed list and remove sites that are no longer needed
- Consolidate content into fewer sites where feasible
- Prioritize sites based on business need and governance risk assessment
- Check Microsoft documentation for updated limits as this cap may increase
- Consider using DSPM for AI and granular permissions instead of RSS if the limit is too restrictive
Issue 4: Users Report Missing Search Results from Allowed Sites
- Symptoms: Users cannot find content from sites that are on the allowed list
- Root Cause: RSS controls search scope at the tenant level, but individual user permissions still apply. Users without access to an allowed site will not see its content in search results.
- Resolution:
- Verify the user has at least read access to the site in question
- Check that the content has been indexed by searching directly within the site
- Verify the site URL in the allowed list matches exactly (no trailing slashes or variations)
- Request a re-index of the site if content was recently added using PnP PowerShell (
Request-PnPReindexWeb) or the SharePoint site settings UI under Search and Offline Availability
Issue 5: RSS Accidentally Disabled (Existing Configurations Only)
RSS is retiring
If RSS was never enabled in your tenant, or you are deploying Copilot for the first time after July 31, 2026, use RCD instead — do not attempt to enable RSS.
- Symptoms: (Existing RSS configurations only) Users suddenly report seeing search results from sites that were previously restricted
- Root Cause: An administrator may have toggled RSS off via the admin center or PowerShell, or a service update may have reset the setting.
- Resolution:
- Evaluate whether the RSS disable was intentional as part of migration to RCD — if RCD is already covering the required sites, disabling RSS may be expected
- If RSS should remain active during ongoing migration, re-enable it:
Set-SPOTenantRestrictedSearchMode -Mode Enabled - Verify the allowed list is intact:
Get-SPOTenantRestrictedSearchAllowedList - Review the audit log for who changed the setting:
Search-UnifiedAuditLog -Operations "Set-SPOTenantRestrictedSearchMode" - Implement alerting on RSS configuration changes to detect future unauthorized modifications
- Accelerate migration to RCD so the RSS dependency can be formally retired
Diagnostic Steps
Current (RCD):
- Check RCD state on a site:
(Get-SPOSite -Identity <url>).RestrictContentOrgWideSearchshould returnTruefor RCD-excluded sites - Review RCD report: Run
Start-SPORestrictedContentDiscoverabilityReport/Get-SPORestrictedContentDiscoverabilityReportand confirm the site list matches the governance log - Test as specific user: Use a non-admin account with no prior interaction history to test Copilot discovery behavior
- Review audit logs: Search Microsoft Purview audit logs for RCD enablement, disablement, and justification changes
- Check search health: Verify the SharePoint search service is healthy in the admin dashboard
Legacy (existing RSS configurations only):
- Check RSS mode:
Get-SPOTenantRestrictedSearchModereturns the documented state (Enabledwhile an existing configuration remains in use during migration to RCD) - Verify allowed list:
Get-SPOTenantRestrictedSearchAllowedListreturns expected sites - Review audit logs: Search for RSS-related admin operations in the unified audit log
Escalation
| Severity | Condition | Escalation Path |
|---|---|---|
| Low | Propagation delay on allowed list changes | Monitor, verify the saved allow list, and retest after allowing propagation time |
| Medium | Site limit reached, blocking approved additions | Governance committee for prioritization |
| High | RSS found disabled without authorization | Security Operations for investigation |
| Critical | Copilot returning content from non-allowed sites | Security Operations and CISO immediately |
Related Resources
- Portal Walkthrough — Configuration reference
- PowerShell Setup — Allowed list management scripts
- Verification & Testing — Validation procedures
- Control 1.3: Restricted SharePoint Search — Parent control