Skip to content

Control 2.5: Data Minimization and Grounding Scope

Control ID: 2.5 Pillar: Security & Protection Regulatory Reference: GLBA §501(b), Data Minimization Principles Last Verified: 2026-09-29 Governance Levels: Baseline / Recommended / Regulated


Objective

Control and limit the scope of data that Microsoft 365 Copilot can access for grounding responses. By combining Restricted Content Discovery (RCD), Microsoft Purview, SharePoint Advanced Management (SAM), sensitivity labels, role-based access control (RBAC), and DLP, organizations can support least-privilege AI interactions. Restricted SharePoint Search (RSS) is retiring: Microsoft blocks new enablement starting July 31, 2026, and directs organizations to RCD for content discoverability, so RSS is relevant only to tenants where it is already enabled. RCD and RSS are scope-limiting controls: they do not change user permissions, provide complete exclusion, or replace labels, RBAC, or DLP. This control helps reduce oversharing amplification, where Copilot surfaces content that users have technical permissions to access but should not practically encounter in AI-generated responses.


Why This Matters for FSI

  • GLBA §501(b) requires that safeguards be reasonably designed to protect customer information — limiting the data Copilot can access reduces the surface area for potential customer information exposure
  • Data minimization principles (embedded in GLBA, state privacy laws, and prudential guidance) require that data processing be limited to what is necessary for the stated purpose — Copilot should only access data relevant to the user's legitimate business needs
  • FFIEC IT Examination Handbook expects access controls that follow least privilege — Copilot's default behavior of searching all content a user can access may exceed least-privilege standards
  • SR 11-7 / OCC Bulletin 2011-12 (Model Risk Management) expects controls over model inputs — limiting grounding scope controls what data feeds into Copilot's AI model for response generation
  • SEC Reg S-P requires protection of customer nonpublic personal information (NPI) — restricting Copilot's grounding scope helps prevent NPI from appearing in AI-generated responses outside its intended context

Control Description

Microsoft 365 Copilot grounds its responses by searching content across the Microsoft 365 tenant using the Microsoft Graph. By default, Copilot can access any content the authenticated user has permission to view. For financial institutions, this default scope is often too broad.

Grounding Scope Control Mechanisms

Mechanism Description Scope Control
Restricted Content Discovery (RCD) Site-level setting for high-risk SharePoint sites Hides sites from organization-wide discovery experiences such as SharePoint home, Office.com, and Bing, and from Microsoft 365 Copilot discovery scenarios; also removes AI entry points (Copilot button, AI actions menus including agent creation, and Create pages with AI) on the site. Direct access and content already in use by the user, such as summarizing an open document, are unaffected
Restricted SharePoint Search (RSS) Retiring tenant-wide allow-list for SharePoint sites; new enablement blocked starting July 31, 2026 Where already enabled, limits Copilot and SharePoint search primarily to up to 100 allowed sites; owned, recently accessed, or Teams/Outlook-shared content can still appear
Restricted Access Control (RAC) Site-level policy restricting site access to members of specified Microsoft Entra security groups or Microsoft 365 groups Honored in organization-wide search and Microsoft 365 Copilot experiences; users outside the control group cannot view the content even with direct item permissions
Data Access Governance (SharePoint admin center) SAM reports providing visibility into overshared sites and files Monitoring: Identify and remediate oversharing
SharePoint Advanced Management (SAM) Restricted access controls, lifecycle management, and data access governance reports Management: Control site-level permissions at scale
Microsoft Graph Permissions User-level graph permissions that Copilot inherits Foundation: Copilot can only access what user can access

Restricted Content Discovery (RCD)

RCD is the mechanism Microsoft directs organizations to for limiting content discoverability during Copilot readiness work. It is a site-level setting that Microsoft describes as a temporary governance control while permissions, ownership, and governance controls are reviewed. RCD does not change permissions and does not remove content from the Microsoft 365 search index, so Microsoft Purview capabilities such as eDiscovery and auto-labeling continue to function. Microsoft cautions against excessive use, because over-application reduces the content available to organization-wide search and Copilot experiences.

Eligibility requires SharePoint Advanced Management availability and a Microsoft 365 Copilot license. Because the setting must propagate across indexing systems, changes take time to become fully effective; Microsoft notes that sites with more than 500,000 items can take more than a week to fully process.

Restricted SharePoint Search (RSS)

RSS is a transitional tenant-wide scoping mechanism for Copilot onboarding while SharePoint permissions are audited. Microsoft positions RSS as a short-term approach that is not intended or scalable for long-term use, and it is not a security boundary. RSS is retiring. Microsoft blocks new enablement starting July 31, 2026 and directs organizations to comprehensive data controls such as RCD for content discoverability. The guidance below therefore applies to tenants where RSS is already enabled and is being wound down.

Mode Behavior Use Case
Disabled (Default) Copilot can ground on SharePoint sites the user can access Target state once permissions, labels, DLP, and SAM controls are validated
Enabled — Allow List Copilot and SharePoint search are scoped primarily to allowed sites, but Microsoft notes owned, recently accessed, or Teams/Outlook-shared content can still appear Applies only where RSS was enabled before new enablement was blocked — document exceptions while winding down
Transitioning to Disabled Move from RSS to RCD plus long-term Purview, SAM, RBAC, DLP, and sensitivity-label governance Required direction of travel given the RSS retirement

RSS Configuration Flow (tenants where RSS is already enabled)

RSS already enabled
(new enablement blocked
 from July 31, 2026)
        │
        ▼
  Define Allowed Sites
  (curated, clean list; ≤100 sites)
        │
        ▼
  ┌──────────────────────────────────────────┐
  │  Copilot / SharePoint tenant search      │
  │                                          │
  │  ✓ Allowed Site A                        │
  │  ✓ Allowed Site B                        │
  │  ✓ Allowed Site C                        │
  │  ⚠ Non-allowed content may still appear  │
  │    when owned, recently accessed, or     │
  │    Teams/Outlook-shared; direct          │
  │    SharePoint access is unchanged        │
  └──────────────────────────────────────────┘
        │
        ▼
   Monitor via Data Access
   Governance reports
        │
        ▼
   Transition to RCD, Purview,
   SAM, labels, RBAC, and DLP

Data Access Governance Reports

SharePoint Advanced Management Data Access Governance reports are generated in the SharePoint admin center. Microsoft currently publishes the following reports:

Report Type Description FSI Action
Site permissions across your organization Snapshot Permission structure across all SharePoint and OneDrive sites, highlighting the broadest access such as "Everyone except external users" Remediate before broadening Copilot grounding scope
Site permissions for users Snapshot All sites a specified user can access, directly or through groups Validate least privilege for high-risk roles
Sites and files shared via special SharePoint groups Snapshot Sites, folders, and files made effectively public through the "Everyone except external users" or "Everyone" groups Item-level remediation and scripted cleanup
Sensitivity labels for files Snapshot Sites containing files with specific sensitivity labels applied Verify label accuracy before Copilot access
Sharing links Activity (last 28 days) Sites where users recently created the most sharing links Investigate emerging oversharing
Shared with 'Everyone except external users' Activity (last 28 days) Sites where content was recently shared with all internal users Investigate broad internal exposure

Microsoft notes that administrators with Microsoft 365 E5 licensing can access Data Access Governance reporting but cannot use the other SharePoint Advanced Management features; in that configuration snapshot reports and remedial actions are unavailable, and activity reports return up to 10,000 sites. Organizations should verify which reports their licensing makes available.

Site Exclusion Strategy for FSI

Site Category Default Action Justification
Executive/Board sites Exclude Board materials too sensitive for general Copilot access
HR/Compensation sites Exclude Employee PII and compensation data
Legal/Litigation hold sites Exclude Privileged information
Compliance/Regulatory sites Exclude SAR, examination correspondence
M&A deal rooms Exclude MNPI and deal-specific information
Archived client sites Exclude Stale permissions, historical data
Departmental collaboration Include (curated) Standard business content after hygiene review
Project sites (active) Include (curated) Active work product after permission review
Intranet/communication sites Include Generally safe, broadly shared by design

Copilot Surface Coverage

RSS values below apply only to tenants where RSS is already enabled, because Microsoft blocks new RSS enablement starting July 31, 2026.

M365 Application RSS Applies Site Exclusion Data Access Governance Notes
Microsoft Copilot Chat Yes Yes Yes Primary grounding scope concern
Word Partial Yes Yes Grounding from SharePoint/OneDrive
Excel Partial Yes Yes Data analysis from linked files
PowerPoint Partial Yes Yes Content suggestions from SharePoint
Outlook Partial No Limited Email grounding uses Exchange, not SharePoint; Microsoft notes RSS affects any product where Enterprise Search could return SharePoint content or files
Teams Partial Yes Yes Teams-linked SharePoint sites
OneNote Partial Yes Yes Notebook sites in SharePoint
Loop Partial Yes Yes Loop workspaces in SharePoint
Copilot Pages Yes Yes Yes Pages grounding follows RSS
SharePoint (Agents) Yes Yes Yes Agent scope limited by RSS and site access

Governance Levels

Level Requirement Rationale
Baseline Apply RCD to executive, HR, legal, and compliance sites where organization-wide discovery should be suppressed; where RSS is already enabled, maintain a curated allow-list of 10-50 sites while planning its retirement; run Data Access Governance reports monthly Reduces grounding scope during onboarding while documenting that direct access remains governed by permissions
Recommended Retire RSS in line with Microsoft's July 31, 2026 enablement block; implement RCD for sensitive site categories; use SharePoint Advanced Management for at-scale permission reviews; quarterly grounding scope reviews; document site inclusion, exclusion, and exception rationale Balanced approach that expands Copilot utility while moving toward durable data boundary controls
Regulated Manage RCD and any remaining RSS changes through formal change control; require data hygiene certification before broadening grounding scope; monitor grounding scope changes; integrate DSPM for AI to track sensitive data access patterns; conduct annual grounding scope audit by compliance Stronger governance for firms with highest regulatory scrutiny while long-term Purview, SAM, RBAC, label, and DLP controls mature

Setup & Configuration

Step 1: Apply Restricted Content Discovery to High-Risk Sites

Portal: SharePoint admin center > Sites > Active sites > [select site] > Settings > Restrict content from Microsoft Copilot > Save

RCD is the mechanism Microsoft directs organizations to for limiting content discoverability. Confirm SharePoint Advanced Management prerequisites and a Microsoft 365 Copilot license before configuring. Changes propagate through the search index over time, and large sites take longer to reflect.

# Connect to SharePoint Online
Connect-SPOService -Url "https://contoso-admin.sharepoint.com"

# Restrict content discovery for a high-risk site
Set-SPOSite -Identity "https://contoso.sharepoint.com/sites/LegalHold" `
  -RestrictContentOrgWideSearch $true

# Check the current setting for a site
Get-SPOSite -Identity "https://contoso.sharepoint.com/sites/LegalHold" |
  Select RestrictContentOrgWideSearch

# Generate and review a tenant-wide RCD report
Start-SPORestrictedContentDiscoverabilityReport
Get-SPORestrictedContentDiscoverabilityReport

Step 2: Manage Restricted SharePoint Search Where Already Enabled

Microsoft blocks new RSS enablement starting July 31, 2026. Tenants that already have RSS enabled manage it with PowerShell, which is the enablement and management method Microsoft documents. Learn documents the one-hour figure only for RSS enablement; verify the propagation of allow-list edits in the tenant. RSS does not change user permissions and does not provide complete exclusion — document known exceptions for owned, recently accessed, or Teams/Outlook-shared content, and plan the transition to RCD.

# Connect to SharePoint Online
Connect-SPOService -Url "https://contoso-admin.sharepoint.com"

# Verify current RSS mode (returns Enabled or Disabled)
Get-SPOTenantRestrictedSearchMode

# Set the RSS mode (Enabled or Disabled)
Set-SPOTenantRestrictedSearchMode -Mode Enabled

# Add sites to the RSS allowed list
Add-SPOTenantRestrictedSearchAllowedList -SitesList @("https://contoso.sharepoint.com/sites/Department-A")
Add-SPOTenantRestrictedSearchAllowedList -SitesList @("https://contoso.sharepoint.com/sites/Project-B")

# Bulk-load the allowed list from a CSV of site URLs
Add-SPOTenantRestrictedSearchAllowedList -SitesListFileUrl "C:\Users\admin\Downloads\UrlList.csv"

# View current allowed list
Get-SPOTenantRestrictedSearchAllowedList

# Remove a site from the allowed list
Remove-SPOTenantRestrictedSearchAllowedList -SitesList @("https://contoso.sharepoint.com/sites/OldSite")

Step 3: Configure Restricted Access Control for Sensitive Sites

Restricted Access Control (also called restricted site access) limits a site to members of specified Microsoft Entra security groups or Microsoft 365 groups, and is honored in organization-wide search and Microsoft 365 Copilot experiences. Enable it for the organization before applying it to a site.

Portal: SharePoint admin center > Policies > Access control > Site-level access restriction > Allow access restriction > Save

# Enable site-level access restriction for the organization (may take up to one hour)
Set-SPOTenant -EnableRestrictedAccessControl $true

# Restricted Access Control — limits site access to specified groups only
Set-SPOSite -Identity "https://contoso.sharepoint.com/sites/BoardMaterials" `
  -RestrictedAccessControl $true

# Specify the control groups (up to 10 group GUIDs per site)
Set-SPOSite -Identity "https://contoso.sharepoint.com/sites/BoardMaterials" `
  -AddRestrictedAccessControlGroups "<group-guid>"

Step 4: Run Data Access Governance Reports

Portal: SharePoint admin center > Reports > Data access governance

  1. Generate the "Site permissions across your organization" snapshot report
  2. Generate the "Sites and files shared via special SharePoint groups" snapshot report to find item-level exposure through "Everyone except external users" or "Everyone"
  3. Review the "Shared with 'Everyone except external users'" and "Sharing links" activity reports, which cover the last 28 days
  4. Review results and remediate before broadening Copilot grounding scope
  5. Schedule monthly activity report review and quarterly snapshot reports

Step 5: Monitor and Expand

  1. Review Copilot usage analytics to identify user requests that hit grounding scope boundaries
  2. Evaluate requested sites for data hygiene readiness
  3. Remove RCD, or add sites to a remaining RSS allow list, through a documented change control process
  4. Track expansion progress against target state

Financial Sector Considerations

  • Oversharing Amplification Risk: Financial firms often have years of SharePoint content with broad permissions established before data classification programs were mature. Copilot can amplify this risk by surfacing content users did not know they could access. RCD is the scope limiter Microsoft now directs organizations to while permissions, labels, DLP, and SAM controls mature.
  • M&A Deal Room Protection: Deal rooms should be evaluated for RCD where organization-wide discovery should be suppressed, and kept out of any remaining RSS allow list. Information barriers, RBAC, sensitivity labels, and DLP remain the durable controls.
  • Regulatory Correspondence Sites: Sites containing examination correspondence, regulatory filings, and supervisory letters should be evaluated for RCD and permission remediation to reduce the chance of inadvertent disclosure through AI-generated responses.
  • Client Data Repositories: Sites containing client account information, portfolio data, and transaction records require careful permission review before inclusion in Copilot's grounding scope. Stale permissions from departed employees or reorganized teams are common in financial firms.
  • RSS Retirement Planning: Microsoft blocks new RSS enablement starting July 31, 2026. Firms that have not enabled RSS should plan around RCD, SAM, and Purview rather than RSS. Firms already using RSS should document RCD/RSS exceptions and retire the allow list methodically as data hygiene improves. Most firms require 3-6 months to clean SharePoint permissions sufficiently for broader Copilot grounding.
  • SAM Licensing: SharePoint Advanced Management (SAM) provides data access governance reports, Restricted Access Control, and lifecycle management capabilities that support long-term governance. Microsoft makes SAM capabilities that support Copilot deployment available when at least one user is assigned a Microsoft 365 Copilot license, and also offers a SharePoint Advanced Management Plan 1 add-on; some features require the add-on. Organizations should verify licensing requirements for Regulated-level implementations.
  • Documentation for Examiners: Maintain a log of RCD and RSS allow-list changes (date, site added/removed, approver, hygiene certification status, and known exceptions). Microsoft Purview audit log activities record RCD enable, disable, and justification events. This demonstrates proactive data governance to regulators examining AI deployment practices.

Verification Criteria

  1. RCD Status: Confirm high-risk sites have RestrictContentOrgWideSearch = True via Get-SPOSite -Identity <site-url> | Select RestrictContentOrgWideSearch, and validate organization-wide search and Copilot discovery behavior after index propagation. For sites with more than 500,000 items, Microsoft notes propagation can take more than a week
  2. RCD Coverage Reporting: Confirm a tenant-wide RCD report has been generated with Start-SPORestrictedContentDiscoverabilityReport and reviewed against the approved list of restricted sites
  3. RSS Status: Where RSS is already enabled, confirm Get-SPOTenantRestrictedSearchMode returns Enabled. Microsoft blocks new RSS enablement starting July 31, 2026, so tenants without RSS should evidence RCD coverage instead
  4. Allow List Accuracy: Verify any RSS allow list contains only sites that have passed data hygiene review and remains within the 100-site limit. Hub sites count as one entry and their associated sites do not count toward the limit, so confirm associated-site permissions separately
  5. Scope Exception Testing: Query Copilot Chat with test users who do not own, recently access, or receive Teams/Outlook shares for restricted or non-allowed sites; document any exceptions that still appear
  6. Allowed Site Testing: Query Copilot Chat for content on an in-scope site and confirm results are returned normally for users with appropriate permissions
  7. Data Access Governance Reports: Confirm reports are generated and reviewed on the documented cadence, with remediation actions tracked
  8. Sensitive Site Review: Verify that executive, HR, legal, compliance, and M&A sites are either remediated, covered by RCD, or excluded from any RSS allow list with documented rationale
  9. Change Control Process: Confirm a documented change control process exists for RCD and RSS allow-list modifications, and that RCD justification and audit events are retained
  10. User Communication: Verify that users understand Copilot's data access scope, RCD/RSS limitations, and the fact that direct SharePoint access is still governed by permissions
  11. Permission Hygiene: Run the "Site permissions across your organization" report and confirm that no in-scope grounding sites appear as overshared
  12. Transition Tracking: Confirm a documented plan exists for retiring any remaining RSS allow list and for expanding grounding scope over time, with milestones and hygiene criteria

Additional Resources