A woman reviews a collaboration and security dashboard on a large monitor in a modern office.
Microsoft 365 Copilot does not break your permissions. It uses them as they are. If those permissions are years out of date, Copilot will find the problems quickly. A new admin checklist from explainx.ai describes Copilot readiness as a cleanup project rather than a licensing decision, and Microsoft's own documentation supports that view. Prompts run in the security context of the user who submits them. A user has to be able to open an item before it can appear in a response.

So the risk is not that Copilot invents new access. The risk is the old access nobody remembers granting. That includes "Everyone except external users" (EEEU) permissions, anonymous links, and finance spreadsheets that someone shared broadly years ago. None of this mattered much while the files were hard to find. Copilot makes them easy to find.

The checklist is useful, but parts of the guidance have hard deadlines. Below is the readiness sequence, checked against Microsoft Learn, with the timing limits and gaps that admins need to plan around.

A woman reviews a collaboration and security dashboard on a large monitor in a modern office. The Readiness Order at a Glance​

The explainx.ai guide sets out seven steps. Each one maps to a tool Microsoft documents:

StepTaskPrimary tool
1Find overshared sites and filesSharePoint Advanced Management (SAM) data access governance reports
2Hide the riskiest sites during reviewRestricted Content Discovery (RCD)
3Fix permissions and ownershipSite access reviews, ownership policy, restricted access control
4Label sensitive contentPurview sensitivity labels
5Add guardrails on prompts and groundingPurview DLP for Copilot
6Govern agents, audit and retentionAdmin center agent settings, Purview
7Pilot, then widen in wavesYour rollout plan

Microsoft's "Secure and govern Microsoft Copilot" foundational deployment blueprint was last updated November 13, 2026. It groups the same work into three pillars: remediate oversharing, set up guardrails, and meet regulations. It also says SharePoint Advanced Management is included with a Microsoft Copilot license, which removes the usual "we'd need another SKU for that" objection.

Section summary: Find the exposure, hide it temporarily, fix it permanently, then add Purview controls on top. The order matters.

Step 1: Measure Your Oversharing Baseline​

Data access governance (DAG) reports are in the SharePoint admin center under Reports > Data access governance. Microsoft currently lists:

  • Snapshot reports: site permissions across your organization (the recommended starting point), site permissions for users or groups, and sensitivity labels applied to files.
  • Activity reports: sharing links, and content shared with "Everyone except external users," both covering the last 28 days.

The timing matters for your rollout plan. Microsoft's documentation says:

  • The first organization-wide permissions report can take up to five days, regardless of tenant size.
  • Later reports finish within 24 hours.
  • Report data can be up to 48 hours old when the report is generated.
  • You can rerun the report every 30 days.
  • Archived sites and sites in a NoAccess lock state are excluded.

You cannot run this report on a Monday and start a pilot on Tuesday. Start it early.

The report also distinguishes two kinds of exposure. Adding users directly or through Entra groups raises the "Total permissioned users" count right away. EEEU grants and sharing links do not raise that count. Microsoft calls them potential exposure, which becomes actual exposure only when someone uses them. A site with a modest user count can therefore still be a serious risk if it is full of organization-wide links. Check the EEEU and link columns in the CSV export, which covers up to a million sites, as well as the headline figure.

Microsoft also recommends a review cadence: run snapshot reports quarterly and activity reports monthly. The explainx.ai checklist suggests monthly sharing-link and EEEU reviews and quarterly site attestations, which fits that pattern closely. Its pilot size of 20 to 50 users and its "top 20 overshared sites" target are the publisher's own suggestions, not Microsoft requirements.

Two caveats from Microsoft's documentation:

  • Tenants with Microsoft 365 E5 but without SAM get only partial access. There are no snapshot reports or remedial actions, and activity reports return at most 10,000 sites.
  • DAG reports may not work if the tenant shows real (non-pseudonymized) user, group and site names in reports. A Global Administrator can fix this by clearing Display concealed user, group, and site names in all reports in the Microsoft 365 admin center's Reports setting.

Section summary: Start the organization-wide permissions report now. The first run can take five days, and it is the baseline for everything that follows.

Step 2: Restricted Content Discovery as a Temporary Measure​

Restricted Content Discovery (RCD) is a site-level setting. It keeps a SharePoint site's content, including recently used files, out of organization-wide search results and Copilot responses. It also removes AI entry points on that site, such as the Copilot button, AI actions menus (including agent creation) and "Create pages with AI."

To enable it in the SharePoint admin center:

  1. Expand Sites and select Active sites.
  2. Select the site.
  3. On the Settings tab, turn on Restrict content from Microsoft Copilot.
  4. Select Save.

Or use SharePoint Online PowerShell:

Code:
# Enable
Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true

# Verify
Get-SPOSite -Identity <site-url> | Select RestrictContentOrgWideSearch

# Remove once permissions are fixed
Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $false

Only SharePoint administrators can manage RCD by default. Running Set-SPOTenant -DelegateRestrictedContentDiscoverabilityManagement $true lets site administrators manage it, but they must give a justification for every change. Purview audit records each enable, disable and justification. For a tenant-wide view, Start-SPORestrictedContentDiscoverabilityReport generates a report of restricted sites, and Get-SPORestrictedContentDiscoverabilityReport checks its status and downloads it.

What RCD does not do:

  • It does not change permissions. Anyone with access can still open the content directly.
  • It does not work on OneDrive.
  • It does not affect searches made from within the site, or Microsoft 365 Feed and Recommendations.
  • It does not stop Copilot from working on content the user already has open, such as summarizing an open document.
  • It does not remove content from the search index. eDiscovery and auto-labeling keep working.

The change also takes time to spread through the search index. For sites with more than 500,000 items, Microsoft says an update can take more than a week to show up fully in search and Copilot. If a restricted site still appears in results, check its item count before you log a support ticket.

Microsoft also warns against applying RCD to too many sites. Each restricted site reduces what search and Copilot can use. Restrict every site and you have paid for a Copilot that cannot see much of anything.

The Retiring Feature: Restricted SharePoint Search​

RCD replaces Restricted SharePoint Search (RSS), and the retirement now has firm dates. Microsoft's documentation states that Restricted SharePoint Search is retiring. Starting July 31, 2026, new enablement is blocked. Use comprehensive data controls such as Restricted Content Discovery (RCD) for content discoverability.

The explainx.ai guide covers the enablement block. It does not mention the final shutdown date. According to Message Center post MC1395311, starting from July 31, 2026, you won't be able to set up new RSS configurations, and by January 31, 2027, RSS will stop working entirely. The retirement covers organizations currently using Restricted SharePoint Search (RSS) in Worldwide, GCC, GCC High and DoD. That gives tenants still using RSS about ten weeks from today.

There is no automatic migration. ABT, a Microsoft partner, notes that Message Center post MC1395311, published on June 18, 2026, sets the schedule and that Microsoft has stated in MC1395311 that it will not automatically migrate Restricted SharePoint Search configurations to Restricted Content Discovery. ABT also reports that the related PowerShell cmdlets will be discontinued on February 28, 2027. Scripts that call them will need updating.

The two features also work in opposite directions. RSS was a tenant-wide allow list of up to 100 sites: everything else was hidden. RCD is a per-site block list: everything is visible except the sites you restrict. You cannot simply copy your RSS list into RCD. When RSS turns off, any site not on that list of 100 becomes visible to search and Copilot again under its normal permissions. Microsoft's documentation also says RSS was never a security boundary. Recently accessed sites, and content shared through Teams or Outlook, could appear even if they were not on the list.

Microsoft's recommended exit has four parts:

  1. Remediate oversharing with SAM.
  2. Apply Purview labels, DLP and auditing.
  3. Disable RSS.
  4. Tell Copilot agent owners and IT teams that results will again follow normal SharePoint permissions.

Step 3: Fix the Permissions​

RCD gives you time. Fixing permissions resolves the problem. Site access reviews let administrators hand DAG findings to the people who know each site best. Microsoft's reasoning is that site owners are best placed to judge access, and compliance rules can prevent IT staff from seeing item-level details.

To start a site access review:

  1. In the SharePoint admin center, go to Reports > Data access governance.
  2. Open a supported report: sharing links, EEEU, or the permissions-based oversharing baseline.
  3. Select the sites to review, then select Initiate site access review.
  4. Customize the email so it does not look like phishing, then select Send.

Know the limits before you plan around this. You can start reviews for up to 100 sites at a time from the web view, and PowerShell handles larger batches. The organization-wide permissions report allows up to 1,000 reviews per calendar month. Reviews cover SharePoint sites only, not OneDrive, and are not supported in Microsoft 365 operated by 21Vianet. You can track progress on the My review requests tab. A review fails if the site owner's email address is invalid, which also tells you that site's ownership needs fixing.

SAM's other cleanup tools include:

  • Site ownership policies: set minimum owner counts and send notifications when sites fall short.
  • Inactive site detection and site attestations: ask owners to confirm a site is still needed and its membership is correct.
  • Restricted access control: limit a site to specific groups.
  • Block-download policies: cover sensitive sites and Teams meeting recordings.
  • Site policy comparison: compare a baseline site against up to 10,000 target sites.

The explainx.ai guide suggests this order: remove EEEU and broad groups from sensitive sites, assign two owners per site, archive dead sites, then restrict the sites that must stay limited. That is a reasonable approach, but it is the publisher's recommendation. Microsoft's own guidance asks you to weigh how sensitive the content is, how much is exposed, and how much disruption a change will cause.

Steps 4 and 5: Labels and Purview DLP​

Sensitivity labels give DLP rules something to target. Microsoft's example taxonomy uses five labels: Highly Confidential, Confidential, Internal, Public and Personal. Treat this as a reasonable starting point, not a requirement.

Purview DLP for Copilot uses the Microsoft Copilot, Copilot Chat, and Copilot Cowork policy location, available through the Custom policy template. It offers four controls:

ControlStatusEffect
Block external web search when a prompt contains sensitive information typesAvailableCopilot answers from permitted internal sources only
Block processing of prompts containing sensitive information typesPreview, rolling outCopilot does not respond or search
Block files and emails with sensitivity labelsAvailableContent is not used in the response but can still appear in citations
Block external email as grounding dataPreview; not yet supported for CoworkExcludes mail from senders outside accepted domains, based on sender domain only

Watch for these gaps:

  • DLP checks only the text typed into a prompt. It cannot scan files uploaded directly into the prompt.
  • In Word, Excel and PowerPoint, the policy is evaluated when a file opens. A label applied mid-session takes effect the next time the file is opened.
  • Policy changes can take up to four hours to reach Copilot.
  • Calendar invites are not supported, and labeled email is covered only if it was sent on or after January 1, 2025.
  • During the preview, Word, Excel and PowerPoint may not clearly tell users that a prompt was blocked by policy. Expect help desk calls about Copilot "ignoring" requests.

Two features help with operations. DLP policies for Copilot can be scoped to Entra administrative units. Scoping follows the user who submits the prompt, not the owner of the file. You can also replace the default "Learn about access restrictions" link in the block message with your own internal policy page. Run new policies in simulation mode before enforcing them.

The external-email control is a defense against prompt injection. Mail from outside your organization is untrusted input, and this setting keeps it out of Copilot's reasoning entirely.

Step 6: Agents, Retention and Remaining Settings​

The explainx.ai guide also covers agent governance, Copilot activity-history retention, connected experiences, and the option for admins to allow Anthropic and OpenAI models as subprocessors. It notes, citing Microsoft, that Anthropic models are currently outside the EU Data Boundary.

Those claims were not independently verified here, so check them against current Microsoft Learn pages before relying on them. The principle behind them holds regardless: agents inherit the permissions of the user running them. Every oversharing problem above affects agents too, and they may surface it at scale.

The Bottom Line​

The explainx.ai guide is a solid outline and matches Microsoft's documentation on the important points. It leaves out the deadline that matters most: Restricted SharePoint Search stops working entirely on January 31, 2027, and its settings will not carry over to Restricted Content Discovery.

If your tenant still uses RSS, this week's tasks are:

  1. Export the RSS allow list.
  2. Run the organization-wide DAG permissions report now, since the first run can take five days.
  3. Decide which sensitive sites need RCD before January 31.
  4. Allow time for RCD to propagate on large sites, which can exceed a week.

Copilot is only as safe as the permissions it reads. Fixing them is slow work, but it has to happen before a broad rollout.

 

References

  1. Copilot Readiness Checklist: Oversharing, Purview (2026) - explainx.ai explainx.ai 2026-11-19T00:00:00+00:00
  2. Secure & Governed Data Foundation for Microsoft Copilot - Foundational Deployment Guidance | Microsoft Learn learn.microsoft.com
  3. Microsoft Purview DLP for Microsoft 365 Copilot and Cowork | Microsoft Learn learn.microsoft.com