23.2 Implement Microsoft 365 Workload Controls for AI

23.2 Implement Microsoft 365 Workload Controls for AI

Quick Answer: Copilot can ground only on content the user can already access, so oversharing in SharePoint and OneDrive is the workload problem. Restricted Content Discovery (RCD) hides selected SharePoint sites from organization-wide search and Microsoft 365 Copilot (PowerShell: Set-SPOSite -RestrictContentOrgWideSearch $true) without changing ACLs. Restricted SharePoint Search (RSS) is a temporary tenant allow list of up to 100 sites; it is not a security boundary, and new enablement is blocked starting July 31, 2026. Fix Anyone links and membership, enable labels for SharePoint and OneDrive, then disable RSS after validation.

Purview labels and the Copilot DLP location decide whether Copilot may extract protected items. Microsoft 365 productivity workload controls decide which sites and files are even discoverable through Microsoft Search and Copilot chat. Microsoft's Copilot data-protection architecture groups those workload levers as search and discovery settings, sharing and membership controls, governance and lifecycle policies, and information protection policies. This section is the first three, plus how Copilot in Word, Excel, PowerPoint, Outlook, and SharePoint consumes whatever those workloads still expose.

Copilot does not grant new permissions. If a budgeting site is shared with the whole company, Copilot will answer “summarize this year's bonuses” for anyone in that access control list. The exam failure mode is treating Copilot as a new leak path you can switch off independently of SharePoint. You cannot. You either shrink who can access the content, shrink what is discoverable, or stop extract with labels and DLP.

Oversharing is amplified, not created, by Copilot

Before Copilot, a user had to know a site existed, browse it, and open files. After Copilot, the same user can ask natural-language questions across Graph-grounded content they already can read. Microsoft therefore treats Copilot readiness as SharePoint governance: Data Access Governance reports, sharing-link reports, Anyone (anonymous) links, overly broad Microsoft 365 group membership, and stale libraries full of unlabeled drafts.

Restricted Access Control (RAC) for SharePoint sites (SharePoint Advanced Management) is a true access control: it can limit who is allowed into a site. RCD and RSS are discovery controls: they change what appears in organization-wide search and Copilot, not who can open a known URL. If the exam stem says “users must still open the files in the browser, but Copilot must not surface the site,” that is RCD (or RSS while it remains enabled), not RAC. If the stem says “those users must not open the site at all,” that is permissions or RAC.

SharePoint Advanced Management reports help you pick sites. Typical Copilot-readiness loop: identify high-risk sites (Anyone links, too many sharing links, everyone except external users), right-size membership, apply default library labels and auto-labeling, then use RCD only on sites still under review. Lifecycle policies that delete or retain stale content matter because leftover overshared drafts become high-speed Copilot answers; you configured retention earlier—here the point is stale overshared content is an AI grounding problem.

Restricted SharePoint Search: temporary allow list, now retiring

RSS lets a SharePoint administrator or other Microsoft 365 administrator maintain an allow list of SharePoint sites that may be used in organization-wide search. As a temporary measure it also applies to Copilot chat and agentic experiences. It is off by default and the allow list starts empty. Microsoft is explicit: RSS is not intended or scalable for long-term use, it is not a security boundary, and it does not change permissions.

Restricted SharePoint Search is retiring. Starting July 31, 2026, new enablement is blocked. Microsoft tells customers to use comprehensive controls such as Restricted Content Discovery, SharePoint Advanced Management, and Purview. If a practice item still describes turning RSS on as the long-term Copilot architecture, it is outdated.

When RSS is on, users can still interact with content they own or previously accessed. Organization-wide search and Copilot chat can surface:

• Sites on the curated allow list (up to 100 SharePoint sites), honoring existing site permissions
• The user's OneDrive files, chats, emails, and calendars they can access
• Files from frequently visited SharePoint sites
• Files shared directly with the user
• Files the user viewed, edited, or created

The last three file categories together are limited to the last 2,000 entities. Hub sites on the allow list include associated sites; those associated sites do not count toward the 100, but they must have proper permissions. Site-scoped search is not affected. RSS can take effect within an hour. You enable, disable, and curate the list with PowerShell (see Microsoft's Restricted Search admin scripts; disable with Disable-SPORestrictedSearch after validation).

RSS is not a deny list. You cannot use it to name 400 “blocked” sites. Sites not on the allow list can still appear if the user recently accessed them or they were shared in Teams or Outlook. RSS also hits any product where enterprise search can return SharePoint files, including users who never open Copilot, which is why Microsoft wants it off after you fix ACLs. It does not affect Purview or SharePoint Advanced Management features that depend on the Microsoft 365 index.

Turning off Allow this site to appear in Search results on a site is a different switch: it hides the site from both organization-wide search and site-specific search. Do not use that as a Copilot-only control.

Microsoft's Contoso-style story is the exam scenario: Alex can see a budgeting site that never had ACL hygiene. Copilot answers budgeting questions from that site. After RSS, the site is left off the allow list, so Copilot chat no longer grounds on it unless Alex owns, recently visited, or was directly shared those files. The durable fix is still SAM + Purview, then disable RSS and tell Copilot agent owners that answers will change.

Restricted Content Discovery: per-site hide from Copilot and org-wide search

RCD is the current control for organizations that need time to review SharePoint sites during a Copilot rollout. Applied to a site, it limits discovery of that site's content—including recently interacted files—in organization-wide search (SharePoint home, Office.com, Bing) and Microsoft 365 Copilot responses. It also removes in-site AI entry points: the Copilot button, AI actions menus (including creating agents), and Create pages with AI. The site shows a Restricted tag. Copilot in SharePoint respects RCD: those AI surfaces do not appear on a restricted site regardless of tenant Copilot-in-SharePoint availability settings.

RCD does not change existing permissions. Users who already have access can still open content directly. It applies only to SharePoint sites, not OneDrive. It does not affect searches that originate from site context, Microsoft 365 Feed, or Recommendations. It does not remove content from the Microsoft 365 search index, so eDiscovery and auto-labeling keep working. It does not block experiences on content already in use, such as summarizing an open document in Word.

Prerequisites Microsoft documents: SharePoint Advanced Management (including the SharePoint Online PowerShell module and RBAC) and a Microsoft 365 Copilot license. RCD is intended for Copilot deployment and governance, not as a general search feature for tenants that never licensed Copilot.

Enable it in the SharePoint admin center: Sites > Active sites, select the site, Settings, turn on Restrict content from Microsoft 365 Copilot. PowerShell:

Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true

Set the same property to $false to remove RCD. Check status with Get-SPOSite -Identity <site-url> | Select RestrictContentOrgWideSearch. Tenant-wide reporting uses Start-SPORestrictedContentDiscoverabilityReport, Get-SPORestrictedContentDiscoverabilityReport, and download by ReportId.

By default only SharePoint administrators can manage RCD. Delegate to site administrators with Set-SPOTenant -DelegateRestrictedContentDiscoverabilityManagement $true. Site admins who change the setting must provide a justification. Purview audit events cover enable, disable, and those justifications.

Propagation is a site-level property that must flow through search systems. Microsoft does not publish a single SLA for every site. Time depends on site size and how many sites you update at once. For sites with more than 500,000 items, an update could take more than a week. If a restricted site still appears in search, wait for index propagation and check item count—do not assume the cmdlet failed.

Use RCD selectively. Overuse starves organization-wide search and Copilot of grounding material. Typical use: Finance or Human Resources sites during a permissions review, then remove the restriction.

Labels, Office apps, and putting the layers together

Workload discovery controls do not replace Purview. Enable sensitivity labels for SharePoint and OneDrive so at-rest Office files participate in Copilot's encryption and inheritance behavior. In Copilot Chat, returned data can show the highest-priority label among references, and new content inherits that label when supported. User-defined permissions can block Copilot from extracting file content. Default library labels reduce the unlabeled corpus that Copilot would otherwise summarize freely for anyone with access.

Do not expect RCD or RSS to hide a file the user already has open. Data in use is a different path: the Office app already loaded the bytes. Endpoint DLP and the Copilot DLP location (previous section) cover extract and paste; workload controls cover discovery.

After you validate permissions, Microsoft's RSS guidance is to disable Restricted SharePoint Search, keep SAM and Purview in place, and warn agent owners that Copilot answers will widen to ordinary permission-based grounding. RCD stays on only for sites still under review.

Exam traps

• RSS is an allow list, not a deny list, and it is retiring.
• RCD does not revoke access and does not apply to OneDrive.
• RCD does not make Purview blind: the index remains, so eDiscovery still finds the files.
• Sites over 500,000 items can need more than a week after an RCD change.
• Copilot will still summarize an open Word document on an RCD site.
• DSPM data risk assessments can recommend RCD or Copilot DLP; configuring DSPM itself is the next chapter.