--- title: "How to Exclude a SharePoint Site From Copilot: 3 Methods in 2026" description: "Restricted SharePoint Search: new activations blocked since July 31, 2026, full retirement in January 2027. Compare ways to exclude a site from Copilot." image: https://blog.idecsi.com/hubfs/exclure-site-sharepoint-copilot-3-methodes-2026-1.png --- [![Logo-Idecsi-Black-tagline](https://blog.idecsi.com/hs-fs/hubfs/LOGOS%20IDECSI/LOGOS%20OFFICIELS/Logo-Idecsi-Black-tagline.png?width=1010&height=319&name=Logo-Idecsi-Black-tagline.png)](https://www.idecsi.com/) - Solutions DETOX® pour M365 Audit, Remediation & ROI [Discover DETOX](https://info.idecsi.com/detox-m365?hsLang=en) ![Audit, Remediation & ROI](https://blog.idecsi.com/hubfs/ILLU-4.png) Solutions IDECSI gives security and IT teams full control over their data — across DSPM, Data Access Governance, Human Risk Management, and Data Volume Management. - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) M365 Data Security Platform](https://www.idecsi.com/solution/mydatasecurity/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Data storage optimization](https://www.idecsi.com/solution/mydatamanagement/) - Challenges M365 Checklist 15 Warning Signs Your M365 Data Is at Risk [Get the checklist](https://info.idecsi.com/checklist-15-warningsigns?hsLang=en) ![Checklist risques M365](https://blog.idecsi.com/hubfs/Frame-2147255341.png) Your 2026 Challenges Address your most critical data security and governance challenges - across your M365 environment - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Gain visibility accross M365](https://www.idecsi.com/challenges/visibility-microsoft-365) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Get Ready For Copilot M365](https://www.idecsi.com/challenges/m365-copilot/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Control external user access](https://www.idecsi.com/challenges/external-access-microsoft-365/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Prevent Sensitive Data Exposure](https://www.idecsi.com/challenges/sensitive-data-m365/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Gain visibility across Microsoft 365](https://www.idecsi.com/challenges/visibility-microsoft-365/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Ensure regulatory compliance](https://www.idecsi.com/challenges/compliance-m365/) - Resources Is Your Tenant Ready for Copilot? A Security & Governance Playbook [Download](https://info.idecsi.com/whitepapper_copilot?hsLang=en) ![Copilot guide](https://blog.idecsi.com/hubfs/Frame-2147255339.png) Our resources Check out our useful resources for improving data protection - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Blog](https://blog.idecsi.com) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Help Center](https://help.idecsi.com/) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) Ressources & News](https://blog.idecsi.com/resources?hsLang=en) - [![download\_done](https://blog.idecsi.com/hubfs/download_done.svg) About us](https://www.idecsi.com/about-us/) - [Customers](https://blog.idecsi.com/resources-customer?hsLang=en) - - [English](https://blog.idecsi.com/exclude-sharepoint-site-from-copilot-3-methods) - [Français](https://blog.idecsi.com/fr/exclure-site-sharepoint-copilot-3-methodes) Search [Request a demo](https://info.idecsi.com/demo-idecsi?hsLang=en) Microsoft 365 22 October 2026 # How to Exclude a SharePoint Site From Copilot: 3 Methods in 2026 ![SharePoint: How to exclude a site from Copilot](https://4272098.fs1.hubspotusercontent-na1.net/hubfs/4272098/exclure-site-sharepoint-copilot-3-methodes-2026-1.png) - [Home](https://www.idecsi.com/) - [Blog](https://blog.idecsi.com) - How to Exclude a SharePoint Site From Copilot: 3 Methods in 2026 If you need to exclude a SharePoint site from Copilot, the method most admins know can no longer be turned on. As of July 31, 2026, Microsoft blocks **any new activation of Restricted SharePoint Search**. According to Microsoft (Learn, July 2026), the feature is being retired, and organizations are pointed to Restricted Content Discovery instead. The timing matters. Copilot rollouts are accelerating, and the change forces a simple question back onto the table: which methods actually keep a SharePoint site out of Copilot, and which one fits your situation. ## Why a SharePoint Site Shows Up in Copilot Answers Microsoft 365 Copilot grants no new access. It runs on the permissions already in place in your tenant. If a user cannot open a file directly, Copilot will not surface it for them. The problem sits elsewhere. Copilot **turns theoretical access into effective access**. A poorly permissioned site stayed invisible as long as nobody went looking for it. It now becomes a plain-language answer, delivered in seconds. Microsoft uses a blunt example. A budgeting site holds sensitive business information, but its owner never set proper permissions or followed a data governance process. A marketing employee asks Copilot about the budget. Copilot returns content from that site, because the user technically holds permissions on that site. One nuance matters here. For a file shared through a “People in your organization” link, the content only enters Copilot's scope once the user has opened the link. A direct permission, site membership or an EEEU share is enough on its own: the user does not need to have opened the document before Copilot surfaces it. That shift changes the nature of the risk. Before Copilot, an overly broad permission created potential exposure. After Copilot, it creates immediate exposure, across every employee who knows how to ask a question. Our [enterprise guide to Microsoft 365 Copilot](https://blog.idecsi.com/m365-copilot-guide-entreprises?hsLang=en) covers the wider picture. One point deserves to be stated up front, because everything else depends on it: none of the methods below fixes a permission. According to Microsoft (Learn, 2026), Restricted SharePoint Search **is not a security boundary** and does not change site permissions. The same caveat applies to Restricted Content Discovery. In a Microsoft 365 tenant, excluding a site from Copilot reduces its visibility. It never reduces the number of users who can reach it. ## What Changed in 2026: Restricted SharePoint Search Is Retiring Restricted SharePoint Search ran on an allowed list. Admins declared the sites whose permissions they had validated. Only those sites fed organization-wide search and Copilot chat and agent experiences. According to Microsoft (Learn, updated July 6, 2026), the feature is being retired and new activation has been blocked since July 31, 2026. Full retirement is scheduled for **January 31, 2027** (Message Center MC1395311). Microsoft always framed it as a temporary measure, never as a long-term answer. Its limits explain the retirement: - **A hard cap of 100 sites on the allowed list.** A hub site counts as a single entry, and its associated sites are included without counting against the cap. - **A structural bypass.** Users still reach files they own, recently viewed, or received directly, even when those sites sit outside the allowed list. The total is capped at the last 2,000 entities. - **Organization-wide side effects.** The restriction degrades modern search for everyone, including users who never touch Copilot. - **Weaker answers.** Copilot has less content to ground on, which reduces the accuracy and completeness of its responses. The practical consequence runs two ways. Organizations that have not turned the feature on can no longer do so. Those already using it need to validate permissions and plan its removal before January 31, 2027. Microsoft has stated it will not automatically migrate existing configurations to Restricted Content Discovery: without action, content that was hidden **can become discoverable again**. An organization that discovers a SharePoint oversharing problem today no longer has Restricted SharePoint Search available as an emergency measure. ## Method 1: Exclude a SharePoint Site From Copilot With Restricted Content Discovery Restricted Content Discovery, or RCD, is the method Microsoft now recommends. It is a site-level setting, available for SharePoint sites only and not supported for OneDrive. ### What RCD Actually Does According to Microsoft (Learn, updated September 22, 2026), RCD limits discovery of a site's content in organization-wide search results and in Microsoft 365 Copilot responses. It also strips AI entry points from the site: the Copilot button, AI action menus, agent creation, and Create pages with AI. Microsoft documents three caveats. **RCD changes no existing permission**. RCD does not remove content from the Microsoft 365 search index. Users who already have access keep opening the content directly. The same page also says users can still find content they own or have recently interacted with, while stating elsewhere that recently interacted files are restricted. Test this behavior in your own tenant before relying on it. ### Prerequisites and Activation RCD requires a Microsoft 365 Copilot license and the SharePoint Advanced Management prerequisites. According to Microsoft (Learn, 2026), a single Copilot license assigned anywhere in the tenant is enough for SharePoint admins to receive the SAM capabilities that support your Copilot deployment. Some features, such as restricted site creation, still require the SAM Plan 1 add-on. You can turn it on from the SharePoint admin center, under *Sites \> Active sites*, on the site's *Settings* tab, using the *Restrict content from Microsoft Copilot* option. In PowerShell: Set-SPOSite -Identity "site-URL" -RestrictContentOrgWideSearch $true Delegation to site admins is enabled at tenant level: Set-SPOTenant -DelegateRestrictedContentDiscoverabilityManagement $true Once delegation is on, any change a site admin makes requires a justification, and the events are captured in the Microsoft Purview audit log. ### Propagation Delay, Routinely Underestimated RCD is a site property that has to propagate through the indexing systems. According to Microsoft (Learn, 2026), for a site holding more than 500,000 items, the update can take **more than a week** to fully reflect in search and Copilot. On a SharePoint site with more than 500,000 items, turning on RCD the day before a Copilot rollout produces no effect on launch day. ## Comparing the Ways to Exclude a SharePoint Site From Copilot RCD acts on discoverability. Two other approaches act on access itself, with very different results. Restricted Access Control reserves site access to members of a designated group. According to Microsoft (Learn, updated July 30, 2026), users outside that group cannot reach the site or its content, even if they held prior permissions or a sharing link. That is the difference in kind with RCD: the policy takes effect when the user tries to open the site or the file. Its scope is broad. The policy applies to Microsoft 365 group-connected sites, Teams-connected sites, sites not connected to a group, and OneDrive, using Microsoft 365 groups or Microsoft Entra security groups. Enable it at tenant level with `Set-SPOTenant -EnableRestrictedAccessControl $true`, then site by site with `Set-SPOSite -Identity "site-URL" -RestrictedAccessControl $true`, adding at least one allowed group with the `-AddRestrictedAccessControlGroups` parameter. For a group-connected site, the site's Microsoft 365 group serves as the default group. The policy does not change permissions: to reach the content, a user needs both the permission and membership in the designated group. Sensitivity labels move the control down to the file. According to Microsoft (Learn, June 2026), preventing selected files from being used by agents means pairing labels with Microsoft Purview Data Loss Prevention, through a custom DLP policy using the *Content contains* condition, then *Sensitivity labels*. For Copilot as a whole, the DLP policy must target the *Microsoft 365 Copilot and Copilot Chat* location, with the same condition. Our guide to [classifying and protecting sensitive data](https://blog.idecsi.com/classify-protect-sensitive-data?hsLang=en) with Microsoft Purview covers the labeling groundwork. Know the effect before you go this route. Identified items still appear as citations in the response, but their content is not used to generate it. Microsoft also notes that a sensitivity label cannot yet be applied directly to an `.agent` file, and recommends using a condition on the file extension instead. One recent announcement is easy to confuse with these controls. On September 24, 2026, [Microsoft announced general availability](https://www.microsoft.com/en-us/security/blog/2026/09/24/whats-new-in-microsoft-security-september-2026/) of a joint Microsoft Purview and Microsoft Entra Global Secure Access capability. It enforces Purview policies at the network layer: a sensitive document or text can be blocked before it reaches an unsanctioned AI tool, whether the upload comes from an employee or from an AI agent acting on their behalf. According to Microsoft (Message Center MC1419797), rollout is expected to complete by late October 2026. It requires Global Secure Access, TLS inspection, and pay-as-you-go billing. This capability addresses data leaving for unsanctioned AI, often called shadow AI. It **excludes no site from Copilot** and reduces no internal exposure: an overly broad share stays readable by Copilot and by agents inside the tenant. Blocking the exit protects the tenant's perimeter. Fixing permissions protects what sits inside it. A fourth option still dominates most English-language articles on this topic: the *Allow this site to appear in search results* checkbox, a classic SharePoint setting. It pulls the site out of organization-wide search, but out of site-level search too. User experience takes a heavy hit for a thin governance gain.   | **Method** | **Changes permissions** | **Effect on Copilot** | **Prerequisites** | **Scope** | | --- | --- | --- | --- | --- | | **Restricted Content Discovery** | No | Site not discoverable, AI entry points removed | Copilot license + SAM | SharePoint sites only | | **Restricted Access Control** | No, adds a group-membership condition | Content visible in Copilot to the allowed group only | SharePoint Advanced Management | SharePoint sites and OneDrive | | **Sensitivity labels + DLP** | No (unless the label applies encryption) | Item cited, content not used in the response | Microsoft Purview | File, including outside the site | | **Site search checkbox** | No | Also removes site-scoped search | None | Site or library |   One request recurs on Microsoft Q&A: admins want to block Copilot on a specific site while keeping that site fully searchable through standard Microsoft 365 search. There is **no supported way to do this**. Both Restricted Content Discovery and Restricted SharePoint Search remove content from organization-wide search and Copilot together, because Copilot grounds on the same index that search uses. If a site needs to stay searchable, the only real answer is fixing its permissions. The choice comes down to one question: do you want the content less visible, or do you want access restricted. RCD answers the first. Restricted Access Control answers the second. ## The Blind Spot: What Site-Level Controls Miss RCD applies to a whole site. Yet much of the exposure happens at file level, inside sites that will never be restricted. The Everyone except external users group, or EEEU, is the primary vector. According to Microsoft (Learn, 2026), EEEU represents the entire organization minus external guests, and shows up in two distinct scenarios. The first is a public site, where EEEU is part of site membership. The second is a public item, when a user picks EEEU in the people picker to share a specific file or folder. That second case is the hard one. The share is created by an employee, on a file, inside a site that is otherwise configured correctly. Restricting the site makes no sense, and the share escapes any site-level governance logic. Microsoft does provide a dedicated report, but its reach is bounded. Data access governance reports surface items shared with EEEU over the last 28 days, and the web view shows the top 100 sites involved. An EEEU share created six months ago **appears in none of these activity reports**. The permissions snapshot report does count it, but only as a per-site total: it shows neither which file is affected nor who created the share. One accounting detail deepens the blind spot. According to Microsoft (Learn, 2026), creating a sharing link or granting access to EEEU does not automatically increase the permissioned user count shown in the site permissions baseline report. Microsoft separates potential exposure from actual exposure, the latter materializing only when users reach the content. An admin dashboard showing a flat permissioned user count can therefore hide [massive potential exposure](https://blog.idecsi.com/microsoft-365-data-exposure?hsLang=en). ## Hiding Is Not Fixing: What to Do During the RCD Window Microsoft is explicit here. Restricted Content Discovery is designed as a temporary governance control, meant to buy time to review and right-size access while the Copilot deployment continues. Microsoft also warns against overuse. According to Microsoft (Learn, 2026), restricting too many sites reduces the content available and hurts the relevance of AI-generated answers across the whole tenant. RCD is not a comfortable fallback position. The longer the window stays open, the less value your Copilot deployment delivers. Another option shrinks the volume to deal with, without hiding a whole site. According to Microsoft (Learn, September 2026), [Microsoft Purview retention policies and labels](https://learn.microsoft.com/en-us/purview/retention-settings) can now include an archive action for SharePoint. Inactive files, based on when they were created or last modified, move to Microsoft 365 Archive. They stay subject to retention and legal holds and remain available to eDiscovery, but they **drop out of Microsoft 365 Copilot indexing**. The feature requires a Microsoft 365 E5 license and is off by default. Archiving targets dormant data, not shares. An active file shared with EEEU is untouched. And any user with read access can reactivate an archived file, at which point Copilot can use it again, with the same permissions as before. Archiving shrinks what Copilot can see. Like RCD, it fixes no permission. The real alternative to restricting is **reviewing access, permissions and shares** on a regular basis. Not once before the Copilot rollout, but every six months, as a habit each user builds around their own data. Microsoft points the same way. Its exit process for Restricted SharePoint Search lifts the restriction only once permissions are validated. Its site attestation policies ask owners to periodically confirm their sites' members, permissions and sharing settings. The remediation step is what sets the length of the window. An admin can turn RCD on across fifty sites in a day. Nobody can decide alone, at tenant scale, whether thousands of shares created by thousands of employees over several years are still legitimate. That reality shapes the method. IT orchestrates the campaign, defines the scope, and measures the results. Data owners decide on their own shares, because only they know the context of each document. According to IDECSI data (2026), a first DETOX campaign averages **7 remediations per user**, measured across more than 1 million users processed on the platform. That volume gives you the order of magnitude of the work RCD merely postpones. The [DETOX results from Abeille Assurances](https://blog.idecsi.com/m365-oversharing-remediation-detox-results-2026?hsLang=en) and Louis Dreyfus Company show that remediation step in practice. To prepare that step, our [technical checklist for getting your tenant ready](https://blog.idecsi.com/prepare-tenant-copilot?hsLang=en) for Microsoft 365 Copilot walks through the upstream controls. ## The Bottom Line Retiring Restricted SharePoint Search does not remove a capability. It removes an illusion. The 100-site allowed list gave a sense of a controlled perimeter, while letting through everything a user had already viewed or received as a share. Restricted Content Discovery is a more granular tool, but it does not close that bypass: according to Microsoft's documentation, users can still find content they own or have recently interacted with. Above all, understand what it does: **it buys time**. It reduces neither the number of people who can reach a piece of content, nor the number of shares created over the years. The clock runs while the restriction is on. So the question to ask before turning RCD on is not which sites to hide. It is how long it will take to stop needing to hide them. [A tenant checkup](https://info.idecsi.com/detox-m365?hsLang=en) maps your risky shares and puts a number on that timeline. [Assess the risk to your data](https://info.idecsi.com/fr/audit-picture?hsLang=en) · [Contact an IDECSI expert](https://info.idecsi.com/demo-idecsi?hsLang=en)   ## Q&A What is Restricted Content Discovery in SharePoint? Restricted Content Discovery is a SharePoint site-level setting that keeps a site's content out of organization-wide search results and Microsoft 365 Copilot responses. It also removes AI entry points from the site, including the Copilot button and agent creation. It does not change any permission, and users with existing access keep opening the content directly. How do I exclude a SharePoint site from Copilot? Turn on Restricted Content Discovery for that site, either from the SharePoint admin center under the site's Settings tab or with Set-SPOSite -Identity 'site-URL' -RestrictContentOrgWideSearch $true. The site stops appearing in Copilot responses and organization-wide search, although users can still find files they own or recently worked with. Expect propagation delays of more than a week on sites with over 500,000 items. What is the difference between Restricted Content Discovery and Restricted Access Control? Restricted Content Discovery acts on visibility, Restricted Access Control acts on access. RCD keeps a site out of Copilot and organization-wide search without touching permissions. Restricted Access Control limits who can open the site to a designated group, and it applies to OneDrive as well as SharePoint sites. Is Restricted SharePoint Search still available in 2026? Not for new activations. According to Microsoft, the feature is being retired and new activation has been blocked since July 31, 2026. Full retirement is scheduled for January 31, 2027, with no automatic migration to Restricted Content Discovery. Organizations already using it should validate permissions and plan its removal before that date. Is hiding a site from Copilot enough to secure the data? No. Microsoft positions Restricted Content Discovery as a temporary control while access is reviewed. The feature changes no permission and does not remove content from the search index. A user with overly broad access keeps that access until the permission itself is fixed. Recent articles [Microsoft 365 Oversharing Remediation: DETOX Results from Abeille Assurances and LDC](https://blog.idecsi.com/m365-oversharing-remediation-detox-results-2026?hsLang=en) [Microsoft Scout and M365 Security: Access Risks to Anticipate](https://blog.idecsi.com/microsoft-scout-security-data-access-m365?hsLang=en) [Sensitive Data in Microsoft 365: How to Identify Risks and Regain Control](https://blog.idecsi.com/fr/sensitive-data-microsoft-365?hsLang=en) Best practices to improve Microsoft Teams security [![Download the infographic ](https://no-cache.hubspot.com/cta/default/4272098/825ad7d1-e961-4a7a-a6b3-6e380b22285f.png)](https://cta-redirect.hubspot.com/cta/redirect/4272098/825ad7d1-e961-4a7a-a6b3-6e380b22285f) Share this article Subscribe to our newsletter and receive new contents every month Our articles These articles may interest you ![](https://4272098.fs1.hubspotusercontent-na1.net/hubfs/4272098/Co%C3%BBt%20du%20stockage%20Microsoft%20365%20en%202026.png) Microsoft 365 Microsoft 365 SharePoint Storage Costs in 2026: What's Changing [Lire l'article](https://blog.idecsi.com/microsoft-365-sharepoint-storage-costs-2026?hsLang=en) ![](https://4272098.fs1.hubspotusercontent-na1.net/hubfs/4272098/Microsoft%20Foundry%20_%20guide%20complet%20et%20enjeux%20pour%20la%20s%C3%A9curit%C3%A9%20%282026%29.png) Microsoft 365 Security Microsoft Foundry: Complete Guide and Data Security Implications (2026) [Lire l'article](https://blog.idecsi.com/microsoft-foundry-guide-security?hsLang=en) ![](https://4272098.fs1.hubspotusercontent-na1.net/hubfs/4272098/Illus-Blog-Supervision.png) Microsoft 365 Security Microsoft 365 Phishing: Why Oversharing Makes a Compromised Account Far More Dangerous [Lire l'article](https://blog.idecsi.com/fr/phishing-microsoft-365-risques-donnees-partagees-1?hsLang=en) ### Data protection, let's discuss your project?   [![Contact us](https://no-cache.hubspot.com/cta/default/4272098/bea4f372-c84f-4ec4-980c-ca663747fbfe.png)](https://cta-redirect.hubspot.com/cta/redirect/4272098/bea4f372-c84f-4ec4-980c-ca663747fbfe) ![video background](https://idecsi2a-dev-idecsi.pf27.wpserveur.net/wp-content/uploads/2022/02/video-background-idecsi-responsive-1.png) [![Logo-Idecsi-White-Ss-ES](https://blog.idecsi.com/hubfs/LOGOS%20IDECSI/LOGOS%20OFFICIELS/Logo-Idecsi-White-Ss-ES.svg)](https://www.idecsi.com/) +33 1 84 79 38 30 - - - - [Why choose IDECSI?](https://www.idecsi.com/user-security/) - [About us](https://www.idecsi.com/about-us/) - [Join the team](https://www.welcometothejungle.com/fr/companies/idecsi) - Solutions - [Visibility](https://www.idecsi.com/challenge-data-visibility/) - [Detection](https://www.idecsi.com/challenge-threat-detection/) - [User engagement](https://www.idecsi.com/challenge-involve-user/) - [Access review](https://www.idecsi.com/challenge-rights-review/) - [Remediation](https://www.idecsi.com/challenge-remediation/) - [Sensitive data](https://www.idecsi.com/challenge-sensitive-data/) - [Products](https://www.idecsi.com/solution/) - [MyDataSecurity](https://www.idecsi.com/solution/mydatasecurity/) - [Advanced Monitoring](https://www.idecsi.com/solution/advanced-monitoring/) - [MyDataManagement](https://www.idecsi.com/solution/mydatamanagement/) - Resources - [Resources & News](https://blog.idecsi.com/resources?hsLang=en) - [Blog](https://blog.idecsi.com) - [Customer success](https://blog.idecsi.com/resources-customer?hsLang=en) - [Extranet](https://extranet.idecsi.com?hsLang=en) © IDECSI ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Mona Piquet", "url" : "https://blog.idecsi.com/author/mona-piquet" }, "dateModified" : "2026-10-22T06:00:00.923Z", "datePublished" : "2026-10-22T06:00:00.000Z", "headline" : "How to Exclude a SharePoint Site From Copilot: 3 Methods in 2026", "image" : [ "https://blog.idecsi.com/hubfs/exclure-site-sharepoint-copilot-3-methodes-2026-1.png" ], "mainEntityOfPage" : { "@id" : "https://blog.idecsi.com/exclude-sharepoint-site-from-copilot-3-methods", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.idecsi.com/hubfs/Logo-Idecsi-Black-tagline.png" }, "name" : "IDECSI" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Restricted Content Discovery is a SharePoint site-level setting that keeps a site's content out of organization-wide search results and Microsoft 365 Copilot responses. It also removes AI entry points from the site, including the Copilot button and agent creation. It does not change any permission, and users with existing access keep opening the content directly." }, "name" : "What is Restricted Content Discovery in SharePoint?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Turn on Restricted Content Discovery for that site, either from the SharePoint admin center under the site's Settings tab or with Set-SPOSite -Identity 'site-URL' -RestrictContentOrgWideSearch $true. The site stops appearing in Copilot responses and organization-wide search, although users can still find files they own or recently worked with. Expect propagation delays of more than a week on sites with over 500,000 items." }, "name" : "How do I exclude a SharePoint site from Copilot?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Restricted Content Discovery acts on visibility, Restricted Access Control acts on access. RCD keeps a site out of Copilot and organization-wide search without touching permissions. Restricted Access Control limits who can open the site to a designated group, and it applies to OneDrive as well as SharePoint sites." }, "name" : "What is the difference between Restricted Content Discovery and Restricted Access Control?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Not for new activations. According to Microsoft, the feature is being retired and new activation has been blocked since July 31, 2026. Full retirement is scheduled for January 31, 2027, with no automatic migration to Restricted Content Discovery. Organizations already using it should validate permissions and plan its removal before that date." }, "name" : "Is Restricted SharePoint Search still available in 2026?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "No. Microsoft positions Restricted Content Discovery as a temporary control while access is reviewed. The feature changes no permission and does not remove content from the search index. A user with overly broad access keeps that access until the permission itself is fixed." }, "name" : "Is hiding a site from Copilot enough to secure the data?" } ] } ```