Fix SharePoint oversharing before Microsoft 365 Copilot
In short
Copilot only shows people content they can already open, so SharePoint and OneDrive oversharing surfaces as soon as Copilot rolls out. Fix it in order: tighten tenant sharing defaults, find broad access with data access governance reports, remove 'Everyone except external users' access and 'Anyone' links site by site, and contain sensitive sites while cleanup runs.
Microsoft 365 Copilot doesn't create new access, but it's very good at finding what each person can already open. That makes oversharing in SharePoint and OneDrive the first thing to fix before a wider rollout. This guide works through it in order, using Microsoft's built-in tools.
What is oversharing in SharePoint and OneDrive?
Oversharing is content that more people can reach than the owner intended. Think of a salary spreadsheet in a site everyone can open. Or a contract shared with an "Anyone" link two years ago, or a project folder shared with the whole company for one meeting. Each one is overshared.
Sharing sprawl is the accumulated version of the same problem: years of links, broad grants, public sites and one-off permissions that nobody remembers creating or reviews. For how sprawl builds up across a tenant, see what Microsoft 365 sprawl is and why it matters.
Why does Copilot make oversharing more visible?
Copilot makes oversharing visible because it finds and summarizes anything a person can already open, so files that were hidden only by obscurity start appearing in answers. Microsoft states that Copilot presents only data that each individual can access.
Before Copilot, an overshared file stayed out of sight unless someone knew where to look. Now a plain question can surface it. For the wider readiness picture, see how to check whether your Microsoft 365 tenant is ready for Copilot.
Where does oversharing come from?
Most oversharing comes from a few sources:
- "Anyone" links. Anyone who has the link can open the file without signing in, and you can't track who has accessed it.
- "People in your organization" links. A forwarded link works for anyone in the organization, though access starts only when someone uses it. They're less exposed than site-wide grants but still travel through email and chat.
- "Everyone except external users" (EEEU). A built-in group of every internal user. Granting it on a site, folder or file opens that content to the whole organization.
- Public teams and Microsoft 365 groups. When a site is public, EEEU is part of its membership, so everyone in the organization can see its content.
- Broken inheritance. Folders and files with unique permissions drift away from the site's intended audience and rarely get reviewed.
- Broadly shared OneDrive folders. Personal storage quietly becomes a team share.
- Guests resharing. A guest who can reshare can pass content to people you never invited.
How do you find overshared sites and files?
Use the data access governance reports in the SharePoint admin center to find sites with the broadest access, then add Microsoft Purview data risk assessments for a view by content. Fix the worst sites first.
Data access governance reports
Data access governance reports are part of SharePoint Advanced Management, a set of SharePoint governance and oversharing controls. It comes with Microsoft 365 Copilot (once at least one user is licensed) or the SharePoint Advanced Management Plan 1 add-on. In the SharePoint admin center, go to Reports > Data access governance.
- Site permissions across your organization is a snapshot of permissions on every SharePoint and OneDrive site. Use it to find sites with thousands of users, guests or EEEU access.
- Sharing links shows sites where people created the most "Anyone", organization and external "Specific people" links in the last 28 days.
- Shared with 'Everyone except external users' shows sites where content was shared with the whole organization in the last 28 days.
Microsoft Purview data risk assessments
If you have Microsoft 365 E5 or Microsoft Purview Suite, Data Security Posture Management (DSPM) data risk assessments add a content view. A default assessment runs weekly on your 100 most-used SharePoint sites, counting items shared with anyone, the whole organization or externally, and sensitive data found. Custom assessments cover other sites.
Which tenant sharing settings should you tighten first?
Tighten "Anyone" links, the default link type, external sharing domains and guest resharing first, so new sharing stops adding to the problem during cleanup. Most of these settings live in the SharePoint admin center under Policies > Sharing (see Microsoft's guide to sharing settings). Guest sign-in is now governed by Microsoft Entra, as explained below the table. The Test ID column shows which check in Sprawlsight's free snapshot covers each one.
| Setting | Recommended value | Test ID |
|---|---|---|
| "Anyone" links | Off: set external sharing to "New and existing guests" or stricter. If you must keep them, require expiration and view-only | SPO-001 |
| Default link type | "Specific people" | Not a snapshot test |
| External sharing by domain | Limited to an allow list of approved partner domains | SPO-002 |
| Guests sharing items they don't own | Not allowed | SPO-003 |
| Guest sign-in | Governed by Microsoft Entra B2B redemption; the older SharePoint setting is deprecated, so review your Entra external collaboration settings | SPO-004 |
The same settings in SharePoint Online PowerShell, plus one that hides EEEU from the people picker:
Set-SPOTenant -SharingCapability ExternalUserSharingOnly # new and existing guests, no 'Anyone' links
Set-SPOTenant -DefaultSharingLinkType Direct # default to 'Specific people'
Set-SPOTenant -SharingDomainRestrictionMode AllowList -SharingAllowedDomainList "fabrikam.com northwindtraders.com"
Set-SPOTenant -PreventExternalUsersFromResharing $true
Set-SPOTenant -ShowEveryoneExceptExternalUsersClaim $false # hide EEEU in the people picker
For guest sign-in, Microsoft turned on Microsoft Entra B2B integration for new SharePoint and OneDrive external sharing in commercial tenants from May to July 2026. It can't be turned off. Each invited person gets a guest account in your directory, so Microsoft Entra policies such as multifactor authentication apply to them. Guests now sign in under Microsoft Entra B2B redemption rules, which is why Microsoft deprecated the older SharePoint setting that required the invited account (RequireAcceptingAccountMatchInvitedAccount). Review your Microsoft Entra external collaboration settings alongside SharePoint, because the stricter setting wins.
Two cautions: turning off "Anyone" links, or making them view-only, also turns off file requests, and guests typically lose access within an hour of a sharing restriction. Tell site owners first.
How do you fix 'Anyone' links and 'Everyone except external users' access?
Tenant settings stop new links but don't remove existing grants. Work site by site, broadest exposure first:
- Rank sites. Use the site permissions report to list sites with EEEU access, guests or very large audiences. Put sites with sensitive content at the top.
- Make sites private. Change public teams and groups that shouldn't be open to everyone to private, which removes EEEU from the site's Members group.
- Remove EEEU from site groups and items. Remove "Everyone except external users" from each site's SharePoint groups, and from files and folders through Manage access.
- Delete or replace "Anyone" links. Remove links on sensitive items and reshare with specific people where access is still needed.
- Ask owners to confirm audiences. Start a site access review from a data access governance report. Owners get an email pointing to the issue, fix permissions and mark the review complete. You can start reviews for up to 100 sites from the report page, or use PowerShell for more.
- Fix broken inheritance. Where a folder no longer needs unique permissions, restore inheritance so the site's membership governs it again.
If a site has no owner, assign one before you send the review; see how to find and fix ownerless teams and sites.
What can you do while a cleanup is still in progress?
Use Restricted Content Discovery to hide sensitive sites from Copilot and organization-wide search, and Restricted Access Control to limit a site to named groups. Both are SharePoint Advanced Management controls that limit exposure during a cleanup.
Restricted Content Discovery isn't a security boundary: it doesn't change permissions, and people with access can still open files directly. Turn it on from the site's Settings tab under Active sites, or with Set-SPOSite -Identity <site-url> -RestrictContentOrgWideSearch $true. Use it selectively, because hiding too much weakens Copilot's answers, and remove it once a site is fixed.
Restricted Access Control suits genuinely sensitive sites such as HR, finance or legal. It limits a site to members of up to 10 Microsoft 365 groups or Microsoft Entra security groups. People outside those groups can't open the site or its files, even with existing permissions or a link, and Copilot and search honor the policy. Allow it once for the tenant under Policies > Access control, then apply it site by site. It doesn't carry over to a team's private or shared channel sites, so apply it to each one separately.
If you use Restricted SharePoint Search, plan to replace it. Microsoft blocks new enablement from July 31, 2026, and retires it fully on January 31, 2027. Its allow list isn't migrated, so apply Restricted Content Discovery or Restricted Access Control to sensitive sites before then.
How do you handle OneDrive oversharing?
Handle OneDrive oversharing by keeping its sharing level strict, limiting sync to managed devices, keeping departed users' files long enough to review, and cleaning up links. Site access reviews and Restricted Content Discovery don't cover OneDrive.
- Keep OneDrive at least as strict as SharePoint. Its external sharing level can be stricter than SharePoint's, never looser.
- Limit sync to managed devices. Under Settings > Sync in the SharePoint admin center, you can allow syncing only on computers joined to specific Active Directory domains. For devices that are only Microsoft Entra joined, use Conditional Access instead.
- Keep departed users' files long enough to recover. A deleted user's OneDrive is kept for 30 days by default, and you can set 30 to 3,650 days under Settings > Retention. It counts as unlicensed, though, so it becomes read-only after 60 days and is archived after 93 days, even with a longer retention period. Reopening an archived account requires billing for unlicensed OneDrive accounts. Have the manager review what the person shared and move what the business needs to a team site within that window.
- Clean up links. The site permissions report covers OneDrive too, so use it to find accounts with broad sharing and ask owners to remove links they no longer need.
How do you stop oversharing from coming back?
Cleanup only holds if defaults, owners and reviews stay in place.
- Keep defaults tight. Recheck the sharing settings above after migrations, new admins or tenant changes.
- Give every site and group an owner, ideally two. Owners answer access reviews.
- Schedule reviews. Microsoft suggests running the site permissions report quarterly and the activity reports monthly. Send site access reviews for anything that grew.
- Remove guests who no longer sign in. Stale guests keep access to whatever was shared with them; see how to clean up inactive guests and accounts.
- Label teams and sites. Sensitivity labels on teams and sites can set privacy and external sharing, so new workspaces start in the right state.
- Recheck on a schedule. Sprawlsight's free snapshot checks the sharing settings above (SPO-001 to SPO-004), OneDrive sync and retention (ODB-001 and ODB-002), guest invitations (ENTRA-032) and inactive guests (SPR-001). It gives a score and the top 5 fixes, and it can run again every 30 days.
For the full ten-step clean-up playbook and a printable checklist mapped to the free snapshot's test IDs, see the Sharing Sprawl field guide.
Frequently asked questions
Do 'People in your organization' links expose files to Copilot?
Not on their own. Creating a 'People in your organization' or 'Anyone' link doesn't make a file show up in search or Copilot for everyone, because access extends only to people who redeem the link, usually by opening it. Content shared with 'Everyone except external users' is different: every internal user can already reach it, so it can appear in anyone's Copilot answers.
What does 'Everyone except external users' mean in SharePoint?
It's a built-in group that includes every internal user in your organization but no guests. Granting it on a site, folder or file opens that content to the whole organization, and public sites include it in their membership. Remove it wherever the content is meant for a smaller audience.
Is Restricted Content Discovery enough to protect sensitive sites?
No. Restricted Content Discovery hides a site from organization-wide search and Copilot discovery, but it doesn't change permissions, so people with access can still open files directly. Use it as a stopgap while owners fix access, and use Restricted Access Control when only a defined group should be able to open a site.
Do I need SharePoint Advanced Management to find oversharing?
Not strictly, but it helps a lot: data access governance reports, site access reviews, Restricted Content Discovery and Restricted Access Control are all SharePoint Advanced Management features. It comes with Microsoft 365 Copilot (once one user is licensed) or with the SharePoint Advanced Management Plan 1 add-on. Without it, you can still tighten sharing settings in the SharePoint admin center and PowerShell. Microsoft 365 E5 tenants can also turn on data collection for the activity reports, but they don't get the site permissions snapshot.
Should I turn off 'Anyone' links completely?
For most organizations, yes: anyone with the link can open the file without signing in, and you can't see who did. If a team genuinely needs them, allow them only on the sites that need them, require an expiration and limit them to view-only. Note that file requests need 'Anyone' links with upload permission, so they stop working when 'Anyone' links are off or view-only.