Control 1.3: Restricted SharePoint Search Configuration
Control ID: 1.3 Pillar: Readiness & Assessment Regulatory Reference: GLBA §501(b), FFIEC IT Handbook (Information Security Booklet), Data Minimization Principles Last Verified: 2026-09-29 Governance Levels: Baseline / Recommended / Regulated
RSS Retirement — New Enablement Blocked from July 31, 2026
Restricted SharePoint Search (RSS) is retiring. Microsoft has blocked new enablement of RSS starting July 31, 2026 (Microsoft Learn — Restricted SharePoint Search, verified August 2026). Organizations that enabled RSS before that date may continue using it during a transition period, but should plan migration to current controls.
For new Copilot deployments, use Restricted Content Discovery (RCD) as the primary discoverability control. RCD is a per-site opt-out mechanism that removes specific SharePoint sites from organization-wide search and Copilot grounding without requiring a tenant-wide allow-list. See Restricted Content Discovery below and Microsoft Learn — Restrict discovery of SharePoint sites and content.
Objective
Govern the scope of SharePoint content that Microsoft 365 Copilot can discover and use for grounding responses, using Restricted Content Discovery (RCD) as the current per-site discoverability control and, where applicable for existing deployments, Restricted SharePoint Search (RSS) as a legacy transitional allow-list posture. RSS is retiring — new enablement is blocked from July 31, 2026 — and RCD is the Microsoft-recommended replacement. This control supports compliance with data minimization principles and helps prevent Copilot from accessing content on sites that have not been reviewed for data hygiene and appropriate permissions.
Why This Matters for FSI
- GLBA §501(b): Data minimization is a core principle of information security programs required under GLBA. Restricting Copilot's search scope to vetted sites reduces the surface area for potential unauthorized disclosure of customer financial information. Per GLBA §501(b), least-privilege data access for AI tools directly supports the safeguard requirements for customer information — both RSS and RCD give institutions mechanisms to limit what Copilot can discover.
- FFIEC IT Handbook (Information Security): The principle of least privilege extends to AI tools. RSS and RCD together implement least privilege at the search scope level, limiting Copilot to only the content it needs to function effectively.
- SEC Regulation S-P: Limiting the scope of AI-accessible data supports technical safeguards for consumer financial information by reducing the number of data sources Copilot can query.
- Data Minimization (NIST Privacy Framework): RSS directly implements data minimization by constraining the universe of content available to Copilot, aligning with NIST Privacy Framework Function: Data Processing, Category: Data Minimization. RCD provides complementary site-level data minimization without requiring a tenant-wide allow-list posture.
- Information Barrier Support: For institutions with regulatory information barriers (e.g., between investment banking and research), RSS and RCD provide complementary control layers beyond user-level permissions. RSS excludes entire site categories from Copilot; RCD surgically excludes specific high-risk sites.
Control Description
What Is Restricted SharePoint Search? (Legacy — Retiring)
RSS is retiring
Microsoft has blocked new enablement of RSS from July 31, 2026. This section is retained for organizations managing existing RSS configurations and planning migration to RCD.
Restricted SharePoint Search (RSS) is a tenant-level setting in SharePoint Online that changes Copilot's default behavior from searching all SharePoint sites a user can access to searching only sites on an approved allow-list.
| Aspect | Full Tenant Search (Default) | Restricted SharePoint Search |
|---|---|---|
| Copilot search scope | All SharePoint sites the user has permission to access | Only sites on the curated allow-list (up to 100 sites) |
| Default behavior | Opt-out (all sites included unless specifically excluded) | Opt-in (sites must be added to allow-list; however, recently accessed, shared, or owned content may still appear) |
| Management model | Must identify and exclude problematic sites | Must identify and include approved sites |
| Risk profile | Higher -- unknown content may be surfaced | Lower -- primarily reviewed content is in scope, but exceptions exist for recent interactions |
| Site limit | No limit | 100 sites maximum on the allow-list |
| User direct access | Unchanged -- users can still navigate to any site they have permission for | Unchanged -- RSS only affects Copilot search, not direct access |
Key Architectural Detail
Important: Neither RSS nor RCD is a security boundary, and neither changes SharePoint permissions. Microsoft explicitly states that users may still see content from excluded sources if they recently accessed the site, had it shared with them via Teams or Outlook, frequently visit the site, or own/previously interacted with the content. For RSS specifically, this recent-activity exception (frequently visited sites, directly shared files, and content the user viewed, edited, or created) is limited to the last 2,000 entities; RCD's recent-interaction exception is not defined by this numeric cap. Organizations should not rely on RSS or RCD as the sole access control mechanism. RSS is additionally retiring — new enablement is blocked from July 31, 2026.
RSS affects organization-wide search experiences and Copilot grounding. When enabled, RSS impacts:
- Microsoft 365 Copilot chat and agentic experiences
- Organization-wide search (SharePoint home, Office.com, modern search)
- Enterprise search-backed experiences in Teams, Outlook, Office apps, and other M365 products
RSS does not affect:
- User permissions (users can still directly access any site they have permission for)
- Site-scoped searches (searching within a specific SharePoint site)
- OneDrive content accessibility
- Microsoft Purview features (eDiscovery, auto-labeling)
RSS is designed as a short-term deployment aid for Copilot onboarding and is now retiring. Microsoft has blocked new enablement from July 31, 2026 and recommends transitioning to Restricted Content Discovery (RCD), SharePoint Advanced Management, and Microsoft Purview. Organizations that enabled RSS before the retirement date should plan migration to RCD and comprehensive permissions governance.
The 100-Site Governance Limit
RSS supports a hard maximum of 100 SharePoint sites on the allow-list — this is an enforced cap, not advisory guidance, and Microsoft positions RSS as a short-term measure that does not scale as Copilot and agentic operations grow. The 100-site limit counts Hub sites but not their sub-sites: when a Hub site is added to the allow-list, the sub-sites under that Hub site are included in the allow-list (and become searchable) but do not count toward the 100-site cap — so confirm every child site under an added Hub site has appropriate permissions before adding it. This creates a governance decision:
| Organization Size | Approach | Considerations |
|---|---|---|
| Small (<100 active sites) | Add all reviewed sites to RSS allow-list | May be able to include all relevant sites within the limit |
| Medium (100-500 active sites) | Prioritize high-value, low-risk sites | Must make governance decisions about which sites to include |
| Large (500+ active sites) | Use RSS as transitional control only | Plan migration to site-level controls and full tenant search as remediation progresses |
Organizations managing existing RSS configurations should verify the current cap against Restricted SharePoint Search and Curate the allowed list for Restricted SharePoint Search. (Note: RSS is retiring — new enablement blocked from July 31, 2026, per Microsoft Learn.)
What Is Restricted Content Discovery (RCD)?
Restricted Content Discovery (RCD) is the current Microsoft-recommended per-site discoverability control for Microsoft 365 Copilot governance. RCD is a site-level setting that excludes specific SharePoint sites from organization-wide search results and Copilot grounding while leaving permissions and direct user access unchanged. Microsoft describes RCD as a temporary governance control that gives organizations time to review and right-size access during Copilot deployment rather than as a permanent security boundary.
Key capabilities of RCD:
- Excludes targeted SharePoint sites from Copilot grounding and organization-wide search (SharePoint home, Office.com, Bing) without a tenant-wide allow-list
- Removes AI-powered entry points from restricted sites — users do not see the Copilot button, AI actions menus, or Create pages with AI on sites under RCD
- Site-admin delegation is supported (
Set-SPOTenant -DelegateRestrictedContentDiscoverabilityManagement $true) - Tenant-wide monitoring reports are available via
Start-SPORestrictedContentDiscoverabilityReport/Get-SPORestrictedContentDiscoverabilityReport - Audit events are captured in Microsoft Purview audit logs for enablement, disablement, and justification changes
RCD does not:
- Change existing site permissions — users with access can still navigate to and open content directly
- Remove content from the Microsoft 365 search index — Microsoft Purview eDiscovery and auto-labeling continue to function
- Apply to OneDrive sites — organizations should use sensitivity labels or DLP policies for OneDrive content
Propagation timing: RCD changes propagate through search indexing systems. For sites with more than 500,000 items, full propagation can take more than a week. Organizations should verify effectiveness after allowing adequate propagation time.
| Aspect | Details |
|---|---|
| Configuration | Set-SPOSite -Identity <url> -RestrictContentOrgWideSearch $true per site |
| Portal | SharePoint Admin Center > Sites > Active sites > [site] > Settings > Restrict content from Microsoft Copilot |
| Verification | Get-SPOSite -Identity <url> | Select RestrictContentOrgWideSearch |
| Monitoring | Start-SPORestrictedContentDiscoverabilityReport |
| Licensing | Microsoft 365 Copilot license, which includes the SharePoint Advanced Management capabilities RCD depends on |
(Source: Microsoft Learn — Restrict discovery of SharePoint sites and content, verified August 2026.)
RSS and Restricted Content Discovery: Current Status and Comparison
Restricted SharePoint Search (RSS) is a legacy tenant-level control that is retiring (new enablement blocked from July 31, 2026). Restricted Content Discovery (RCD) is the current per-site discoverability control. Organizations already using RSS should plan migration; organizations deploying Copilot for the first time should use RCD. Both tools address Copilot scope governance but differ in approach.
| Feature | RSS (Restricted SharePoint Search) — Legacy/Retiring | RCD (Restricted Content Discovery) — Current |
|---|---|---|
| Status | Retiring — new enablement blocked from July 31, 2026 | Current — Microsoft-recommended replacement |
| Scope | Tenant-wide allow-list of sites visible to Copilot | Per-site opt-out from Copilot content discovery (SharePoint sites only; cannot be applied to OneDrive sites) |
| Configuration | Set-SPOTenantRestrictedSearchMode -Mode Enabled + allow-list |
Set-SPOSite -RestrictContentOrgWideSearch $true per site |
| Use case | Strict positive-list: only approved sites are searchable by Copilot (existing deployments only) | Surgical exclusion: remove specific sensitive sites from Copilot discovery |
| User impact | Only allow-listed sites appear in Copilot results | Excluded sites invisible to Copilot; AI entry points hidden; direct user access unchanged |
| Admin effort | Higher (must maintain allow-list as sites are created) | Lower (opt-out specific sites as needed) |
| Recommended for | Existing deployments during transition to RCD | All new Copilot deployments; targeted exclusion for any tier |
Organizations may use both tools simultaneously — RSS to establish a tenant-wide positive-list of Copilot-eligible sites, and RCD to surgically exclude specific sites within that list that contain sensitive content not yet fully remediated.
Copilot in SharePoint Availability Transition
Starting September 30, 2026, Copilot in SharePoint begins rolling out to general availability. Microsoft states that two governance details change at GA:
- Preview-era PowerShell availability controls retire. Existing
KnowledgeAgentScope,KnowledgeAgentSelectedSitesList, andKnowledgeAgentSelectedSitesListOperationsettings continue to be honored only until November 1, 2026. - Site AI settings become the availability surface. After the retirement date, site owners manage Copilot in SharePoint behavior for their sites from Settings > Site AI. Microsoft documents owner capabilities such as choosing which agent opens from the site header, hiding the Copilot button for site visitors, and enabling advanced document processing. This is not a tenant-admin allow/deny equivalent to the retiring
Set-SPOTenant -KnowledgeAgent*controls, so continue to use RCD for sites that must not appear in Copilot or organization-wide discovery.
Microsoft also documents that RCD is respected regardless of other Copilot in SharePoint availability settings: if RCD is enabled on a site, Copilot in SharePoint and AI actions do not appear on that site.
SAM Licensing Note
For Microsoft Copilot deployment scenarios, verify the tenant has a Microsoft 365 Copilot license so the SharePoint Advanced Management capabilities RCD depends on are available. RSS new enablement is blocked from July 31, 2026 and is not a viable option for new Copilot deployments; Microsoft recommends RCD, SAM, and Microsoft Purview as the current and comprehensive governance solutions.
When to Use RSS vs. RCD
RSS is retiring
RSS cannot be newly enabled after July 31, 2026. The table below documents both tools for organizations managing existing RSS configurations. For new Copilot deployments, use RCD.
| Scenario | Recommended Approach |
|---|---|
| New Copilot deployment, data hygiene not yet complete | RCD — apply to known high-risk sites; RSS cannot be newly enabled |
| Existing RSS deployment, data hygiene maturing | Migrate to RCD — transition RSS allow-list posture to per-site RCD exclusions |
| Ongoing operations with mature data hygiene | RCD — use per-site opt-out to exclude specific sensitive sites from Copilot |
| Very large tenants (1000+ sites) | RCD — RSS 100-site limit is insufficient for coverage at scale |
| Regulatory requirement for explicit allow-listing | RCD + SAM — RCD provides per-site surgical exclusion; use SAM Restricted Access Control for site-level access restriction |
| Phased rollout by department | RCD per phase — apply RCD to departments not yet onboarded; remove as each phase deploys |
| Sites with known sensitive content that can't yet be remediated | RCD — surgically exclude those sites from Copilot without disrupting access |
| Defense-in-depth for regulated data | RCD + SAM RAC — use RCD for discovery control with Restricted Access Control for access-level enforcement |
RSS Migration Planning
Organizations with existing RSS configurations should plan migration to RCD. RSS new enablement is blocked from July 31, 2026; Microsoft recommends completing the RSS-to-RCD transition as part of broader Copilot governance maturation.
Phase 1: Inventory (Immediate)
├── Export current RSS allowed list (Script 3 in PowerShell Setup playbook)
├── Identify sites with sensitive content that should be RCD-excluded
└── Classify allow-listed sites by risk profile
Phase 2: Parallel RCD Deployment (Weeks 1-4)
├── Enable RCD on identified sensitive sites
├── Communicate changes to affected user populations
└── Validate Copilot behavior with RCD in place
Phase 3: RSS Disable (After RCD Validated)
├── Confirm RCD covers all sites requiring discovery restriction
├── Disable RSS: Set-SPOTenantRestrictedSearchMode -Mode Disabled
├── Verify Copilot behavior with full tenant search + RCD
└── Update governance documentation and examination file
Phase 4: Steady-State Governance
├── Maintain RCD log: sites, justification, review dates
├── Monthly: audit RCD site list; remove restrictions as remediation completes
└── Ongoing: use DSPM for AI and SAM reports to identify new candidate sites
Copilot Surface Coverage
The table below shows surfaces affected by RSS (legacy) and RCD (current). RSS affects Copilot discovery based on a tenant-wide allowed list; RCD applies per-site and also removes AI entry points (Copilot button, AI action menus) from restricted SharePoint sites.
| Copilot Surface | Affected by RSS (Legacy) | Affected by RCD (Current) | Notes |
|---|---|---|---|
| Microsoft Copilot Chat | Yes | Yes | Both restrict SharePoint content in Copilot Chat grounding |
| SharePoint Copilot | Yes | Yes | RCD removes Copilot entry points from restricted sites |
| Word / Excel / PowerPoint | Partially | Partially | Both affect "Reference" and "Draft from" features pulling from SharePoint |
| Teams Copilot | Partially | Partially | Affects SharePoint-backed file content in Teams channels |
| Outlook Copilot | No | No | Neither affects Exchange content |
| OneDrive Copilot | No | No | Neither affects OneDrive content; RCD cannot be applied to OneDrive sites |
| Copilot Pages | Partially | Partially | Both affect SharePoint content used to generate Pages |
| Copilot Notebooks | Partially | Partially | Both affect SharePoint content used to generate Notebooks |
| Loop Copilot | Partially | Partially | Both affect SharePoint content referenced in Loop components |
| Viva Copilot | Partially | Partially | Both affect SharePoint content used in Viva surfaces |
Governance Levels
| Level | Requirement | Rationale |
|---|---|---|
| Baseline | Enable RCD on known high-risk sites to surgically exclude them from Copilot discovery. If an existing RSS configuration is in place from before July 31, 2026, maintain its allowed list during transition and plan migration to RCD. Document RCD-excluded sites with business justification. | RCD provides targeted exclusion with lower administrative overhead and is the current Microsoft-recommended control. New RSS enablement is not available. |
| Recommended | Enable RCD for targeted exclusion of high-risk and unvetted sites. If migrating from RSS, complete the transition to RCD: inventory allowed-list sites, apply RCD to those still requiring restriction, then disable RSS. Establish a site nomination and review process for RCD. Review RCD-excluded sites monthly. | RCD surgical exclusion is more scalable than RSS allow-lists and remains available for all tenants with Microsoft 365 Copilot or SAM licensing. |
| Regulated | Apply RCD to all sites with sensitive content that have not passed data hygiene review. Maintain a formal RCD log: each excluded site must have documented justification, review date, and compliance sign-off. RCD configuration changes follow documented change control. Review bi-weekly. If migrating from RSS, complete migration with formal compliance sign-off and update the examination file to reflect the transition. Establish formal criteria for removing RCD from a site after remediation is complete. | Provides examination-ready governance of Copilot discovery scope with documented per-site control records, supporting GLBA and FFIEC least-privilege expectations. |
Setup & Configuration
Step 1: Enable Restricted Content Discovery (RCD) for Specific Sites (Current Path)
RCD is the current discoverability control. Apply RCD to sites that should be excluded from Copilot grounding and organization-wide search while data hygiene review is in progress:
Portal: SharePoint Admin Center > Sites > Active sites > [select site] > Settings > Restrict content from Microsoft Copilot
# Enable RCD on a site (see Playbook 1.3.2 for full walkthrough):
# Set-SPOSite -Identity "https://contoso.sharepoint.com/sites/sensitive-site" -RestrictContentOrgWideSearch $true
# Monitor RCD status across tenant:
# Start-SPORestrictedContentDiscoverabilityReport
# Get-SPORestrictedContentDiscoverabilityReport
RCD does not affect direct user access — users with permissions can still navigate to and use the site. Only Copilot discovery and organization-wide search of the site's content is restricted. RCD also removes AI entry points (Copilot button, AI action menus) from the affected site.
OneDrive limitation: RCD cannot be applied to OneDrive sites. Organizations should verify that plans to restrict Copilot access to sensitive content rely on alternative controls (such as sensitivity labels or DLP policies) for OneDrive locations.
Step 1b: Manage Existing Restricted SharePoint Search (RSS) Configuration (Legacy Transition)
RSS retirement
RSS new enablement is blocked from July 31, 2026. These steps apply only to organizations that enabled RSS before that date and are managing existing configurations during migration to RCD.
If RSS was enabled before July 31, 2026, navigate to SharePoint admin center > Settings > Search > Restricted SharePoint Search or use PowerShell to manage or disable the existing configuration:
# PowerShell reference (see Playbook 1.3.2 for full walkthrough):
# Check current RSS status:
# Get-SPOTenantRestrictedSearchMode
# Disable RSS (after confirming RCD covers required exclusions):
# Set-SPOTenantRestrictedSearchMode -Mode Disabled
Step 2: Manage RSS Allow-List (Legacy — Existing Configurations Only)
RSS is retiring
Step 2 applies only to organizations managing an existing RSS configuration enabled before July 31, 2026. For new deployments, skip to Step 3 (RCD site selection criteria).
For organizations with existing RSS, manage the allowed list via SharePoint admin center or PowerShell:
# PowerShell reference:
# Add-SPOTenantRestrictedSearchAllowedList -SitesList @("https://contoso.sharepoint.com/sites/approved-site")
# Get-SPOTenantRestrictedSearchAllowedList
Step 3: Define Site Selection Criteria for RCD
Establish criteria for which sites should have RCD applied (discovery restriction):
| Criterion | Applies RCD? | Verification Method |
|---|---|---|
| Permission review incomplete — broad access not yet remediated | Yes | SharePoint DAG report |
| Sensitivity labels not yet applied | Yes | DSPM label coverage report |
| Stale or unclassified content posing risk | Yes | Site analytics and content review |
| Site owner not identified or inactive | Yes | Site collection admin check |
| Content fully reviewed, permissions right-sized, labels applied | Remove RCD | Post-remediation sign-off |
Step 4: Establish Change Management Process for RCD
Document a process for adding/removing sites from RCD:
- Site owner or IT identifies site requiring discovery restriction
- IT/compliance reviews site against selection criteria
- Approval documented with justification (required if site admin delegation is enabled)
- RCD enabled on site
- Verification that site is excluded from Copilot discovery
- Change logged in RCD governance log (date, site, justification, owner)
- Periodic review: confirm ongoing need; remove RCD when site remediation is complete
Step 5: Plan RSS Migration (Existing Deployments)
For organizations with existing RSS, document criteria for migration to RCD:
- Inventory of RSS allowed-list sites and their current RCD status
- Identification of sites still requiring discovery restriction (RCD candidates)
- RCD deployment timeline per site or site group
- User communication plan for Copilot behavior changes post-RSS disable
- Compliance sign-off requirements for RSS disable event
Financial Sector Considerations
- Information Barriers: RCD provides an additional control layer for institutions with Chinese wall requirements. Sites containing MNPI (material non-public information) can have RCD applied to exclude them from Copilot discovery, providing defense-in-depth beyond user-level information barriers. Organizations with existing RSS configurations should migrate MNPI-site controls to RCD.
- Departmental Phasing: Many financial institutions deploy Copilot by department (e.g., operations first, then wealth management, then compliance). RCD supports this by allowing per-site exclusion to be removed as each department's sites are vetted and remediated.
- Regulatory Examination Posture: A documented RCD log demonstrating per-site data minimization decisions is a strong governance indicator. Organizations should maintain a governance log (site, justification, review date) that can be presented in regulatory examinations. Organizations migrating from RSS should retain historical RSS governance records as part of the examination file.
- Trading Floor Considerations: Sites containing trading algorithms, position data, or market-sensitive information should have RCD applied during initial deployment phases and until permissions and labels are fully validated.
- Client-Facing Sites: Sites used for client portal content or external collaboration should have RCD applied until content classification and permissions are confirmed appropriate for Copilot grounding.
- RSS-to-RCD Migration Risk: For institutions with existing RSS, disabling RSS is a significant governance change. Treat it as a change management event with appropriate risk assessment, user communication, testing, and rollback planning. Ensure RCD is fully deployed on all sites requiring discovery restriction before disabling RSS.
Verification Criteria
- RCD configuration state is documented and aligns with the organization's intended governance posture; a governance log exists with site URL, justification, review date, and owner for each RCD-excluded site
- For organizations with existing RSS configurations (enabled before July 31, 2026): RSS configuration state is documented, the allowed list is current, and a migration plan to RCD is in place
- Each RCD-excluded site has documented evidence of the reason for restriction (permission review pending, labels not applied, sensitive content not yet remediated)
- RCD configuration changes follow a documented change control process; where site admin delegation is enabled, justification records are retained in Purview audit logs
- A site nomination and review process is documented and being followed for adding or removing sites from RCD
- For existing RSS configurations: the allowed list is reviewed at the specified cadence (monthly / bi-weekly per governance level) and a change log documents all additions and removals with dates and rationale
- A plan documents criteria for removing RCD from a site (post-remediation sign-off, permissions validation, label coverage threshold)
- For existing RSS configurations: a migration plan to RCD is documented with completion criteria and compliance sign-off requirements
- Users are aware that Copilot discovery is restricted for specific sites (communication to affected user populations)
- RCD monitoring reports (
Start-SPORestrictedContentDiscoverabilityReport) are run periodically and reviewed for accuracy - For RCD-configured sites, testing confirms that Copilot does not surface content from excluded sites for users with no prior interaction history (users who recently accessed the site or own content on it may still see results due to documented exceptions)
- For existing RSS configurations, testing confirms Copilot is respecting RSS restrictions (test queries from accounts with no prior SharePoint interaction history against non-listed sites return no results; note that recently accessed, shared, or owned content may still appear due to documented RSS exceptions)
- RCD and (where applicable) RSS configurations are included in the organization's Copilot governance documentation and regulatory examination file
Additional Resources
- Microsoft Learn: Restricted Content Discovery (current control — verified August 2026)
- Microsoft Learn: Restricted SharePoint Search (legacy/retiring — new enablement blocked from July 31, 2026)
- Microsoft Learn: Manage Copilot data access with SharePoint
- Microsoft Learn: SharePoint admin center search settings
- NIST Privacy Framework: Data Minimization
- Related Controls: 1.2 SharePoint Oversharing Detection, 1.4 Semantic Index Governance, 1.7 SharePoint Advanced Management, 3.1 Copilot Audit Logging, 4.1 Admin Settings & Feature Management
- Playbooks: Portal Walkthrough, PowerShell Setup, Verification & Testing, Troubleshooting
FSI Copilot Governance Framework v1.8.0 - July 2026