← Cocha Insights

Permission Creep Before You Turn On Copilot

Find Old Access First: a magnifying glass over a group icon with a clock, next to a locked folder in a filing cabinet, showing leftover SharePoint access to review before Copilot.

Permission creep is why a SharePoint tenant is usually more open than anyone at the firm believes. It builds over years of ordinary work, and it did little harm while people rarely went looking for what they didn’t know existed. Copilot removes that cushion. Microsoft says Copilot only surfaces organizational data a user already has at least view permission to, so every old grant turns into something a person can retrieve by asking a question.

Copilot doesn’t create new access. It makes existing access cheap to use. That changes how we’d sequence the cleanup: by audience size, widest grants first, instead of trying to review everything at once.

What permission creep is in a law firm SharePoint environment

Permission creep, sometimes called privilege creep, is access that grows slowly and still looks normal. There’s no single incident to point at. It comes from inheritance, group nesting, sharing links, and memberships nobody removed after people changed roles. Each step was reasonable on the day it happened.

Picture a litigation group that builds a Team for a matter. The matter closes, the Team stays, and the site behind it keeps every member. An attorney moves to the employment group and keeps the litigation memberships, because removing them was nobody’s job. A partner shares one exhibit with a colleague off the site, and that file now has its own permissions. None of it looks like a problem in daily work, which is why it survives.

The working definition we use: permission creep is the gap between the access people need today and the access they hold today.

Copilot will find the access nobody remembers granting

Copilot answers from whatever each user can already open, including old access no one has looked at in years. The free AI Readiness Snapshot reviews that access with you in a 60-minute working session. The request only needs your name, work email and firm.

Request the free Snapshot

How permission creep differs from oversharing

Oversharing is usually a visible, too-wide grant. An Anyone link. Everyone except external users on a site. A library open to the whole firm.

Permission creep is the quieter buildup. A practice group Team that kept adding members. A library with unique permissions nobody revisited. A security group nested inside another group, nested inside a third, until nobody can say offhand who is in it.

The two overlap, and they don’t share a fix. Oversharing reports tell you where access is wide. Creep forces a harder question: is this access still justified? Site owners and group owners have to answer that as much as IT does. For the oversharing reports themselves, see our guide to SharePoint oversharing before Copilot.

Where permission creep accumulates in SharePoint

Five places do most of the work.

Find the old sharing before Copilot does

Old groups, sharing links and site memberships are where creep piles up. The free Snapshot looks across your tenant without changing anything, then sends written findings and walks you through them in a 30-minute review.

Book the free Snapshot

Inheritance and unique permissions

By default a file or folder inherits permissions from the library or folder above it. Microsoft’s permission scope guidance says that sharing a file or folder breaks that inheritance and creates a new permission scope, and moving items into a folder later doesn’t consolidate those scopes. Every broken inheritance is a decision someone made once and nobody reviews. The site permissions report in the SharePoint admin center counts items with unique permissions for each site, which gives you somewhere to start.

Sharing links

Microsoft describes three primary link types: Anyone, People in your organization, and Specific people. People using an Anyone link don’t have to sign in, and their access can’t be audited.

The less obvious part is timing. Creating an Anyone link or a People in your organization link doesn’t by itself put the content into search or Copilot. Someone has to redeem the link by clicking it. Sending the link from SharePoint, OneDrive, Outlook, or a Teams chat redeems it automatically for up to 100 individual recipients. Specific people links work differently. They make the item appear in search and reachable through Copilot for everyone named on the link, from the day it’s created.

Group and Team membership

Microsoft’s access review planning guide notes that Teams uses Microsoft 365 Groups as the authorization model for the SharePoint content behind a team. A Team’s member list is a SharePoint permission list. Microsoft’s Entra groups guidance recommends periodic access reviews and at least two owners per group.

The site permissions report expands every group when it counts who can reach a site. That expanded number is the one to watch.

Everyone and Everyone except external users

Everyone except external users, usually shortened to EEEU, is a built-in SharePoint group that contains all internal users and excludes guests. Microsoft warns that sharing with it grants access to all current and future employees. It happens two ways. A site set to public adds EEEU to the site’s membership, or someone shares an individual file or folder with it directly.

Microsoft’s item-level report page calls unresolved EEEU permissions a top oversharing risk and says that content surfaces directly in Copilot search results.

Role changes, departures and outside accounts

This one is our judgment, not Microsoft documentation. A departed attorney whose account is disabled can’t sign in, so the person who left usually isn’t the live exposure. The attorney who is still here, three practice groups away from where they started, is. So is any guest or contractor account that outlived its engagement. Offboarding handles the first case. The second needs a membership review, or dynamic membership rules that add and remove people as job attributes change.

Why Copilot makes permission creep louder

Copilot can show or summarize content the signed-in user can already access. It doesn’t grant new SharePoint rights. Microsoft’s privacy and security page says the Semantic Index honors the user’s identity-based access boundary when it grounds a response. Microsoft is just as direct about the flip side. Its data protection page says that when content is already overshared, Copilot can surface it to anyone who has access.

Nothing about permissions changes on the day a seat is assigned. What changes is the cost of finding things. Before, a paralegal with read access to another matter’s library still had to know the library existed, browse to it, and open the right folder. That effort was a natural limit. A prompt now searches everything that person can read, including matters they were never meant to work on.

Copilot doesn’t read every file in the tenant, and it doesn’t bypass permissions. It retrieves what the user can reach and what fits the prompt. Your risk tracks the real audience of your content, so measure that audience.

Six cleanup steps for a midmarket firm

This is a suggested sequence for IT. It isn’t a Cocha package, a service level, or a timeline. It runs by audience size: fix the grants that reach the most people first, because those are the ones Copilot will surface most often.

A licensing note first. The snapshot reports below are SharePoint Advanced Management features. Microsoft says admins get them once one user in the organization has a Copilot license, or with the SharePoint Advanced Management Plan 1 add-on. Microsoft 365 E5 alone gets the activity reports, not the snapshots. So a firm can run this review with one pilot license assigned and the wider rollout on hold.

1. Find broadly shared sites and Everyone-style grants

Start with the site permissions report under Reports, then Data access governance, in the SharePoint admin center. For each site it shows permissioned users, guest, EEEU and Everyone permission counts, link counts, and items with unique permissions. Then run the sites and files shared via special SharePoint groups report, which lists the exact items shared with EEEU or Everyone. Our oversharing guide covers how to read them.

2. Review organization-wide and Anyone links

The site permissions report counts existing Anyone and People in your organization links for each site. The sharing links activity report only covers the last 28 days. Use it to catch new behavior, and use the snapshot counts to inventory old links.

3. Review group and Team membership

Look at the groups behind your highest-exposure sites, including nested groups and anyone who changed roles. Microsoft Entra access reviews can put group owners in charge of this on a schedule. Microsoft’s page says that requires Microsoft Entra ID Governance or Microsoft Entra Suite licenses. Without it, a membership export reviewed by each group owner does the same job more slowly. Site access review also lets an admin send review requests to the owners of up to 100 SharePoint sites at a time, straight from a data access governance report.

4. Review unique permissions on active matter libraries

Use the unique permission counts to pick libraries. Before you restore inheritance on any item, find out why it was unique. Restoring inheritance replaces the item’s own permissions with the parent’s. The exception may exist because of a client confidentiality restriction, and that’s a conversation with the responsible attorney before it’s a click. That caution is ours, not a Microsoft step.

5. Confirm site owners

Review requests go to site owners, so a site without one has no reviewer. Microsoft’s site ownership policy lets you set a minimum owner count, run it in simulation mode first, and notify sites that fall short.

6. Test a typical attorney’s results before adding seats

This is our suggested method, not a Microsoft procedure. Use a test account in a practice group with no role on a specific matter. Run prompts that name that matter’s subject, and record what comes back. A report tells you what’s possible. The test shows what’s findable.

Checks before you turn on Copilot seats

Four checks come before the next round of seats. Identity and group hygiene: strong sign-in requirements, and group membership someone has looked at recently. Site ownership: every high-exposure site has a named owner who will answer a review request. A small pilot group, which limits exposure while you find what you missed. And the step 6 test should pass before the pilot widens.

If a test fails and the fix will take time, Microsoft offers two interim controls. Restricted Content Discovery keeps a site’s content out of organization-wide search and Copilot discovery without changing permissions. Microsoft calls it temporary, and it doesn’t affect content a user already has open. On sites with more than 500,000 items, an update can take more than a week to apply.

Restricted access control goes further. It limits a site to a defined group, so the site’s content is visible in Copilot only to that group. Neither control replaces the cleanup.

For the wider path, see our Copilot readiness guide. For the ongoing practice after launch, see permissions management.

How this sits with labels, DLP and data security posture

Labels classify, and they can encrypt. Microsoft’s data protection page says that for encrypted content, the user needs both the VIEW and EXTRACT usage rights before Copilot will summarize or return it. That’s real protection for labeled content. It doesn’t remove anyone from a site, and unlabeled content gets none of it. Labels don’t replace an access review.

DLP restricts movement. The same page says a DLP policy for Copilot can keep Copilot from summarizing labeled files and emails, though Copilot can still return a link to the item. That governs what happens to content. It doesn’t shrink who holds a grant to it.

Permission creep is exactly what a data security posture review is hunting for, because overexposed data is where creep shows up. Microsoft Purview data risk assessments help identify SharePoint and OneDrive content that might be overshared and reachable by Copilot agents. For how a posture review fits together, see our guide to data security posture management.

Quick answers

What is permission creep?

Permission creep is access that builds slowly through inheritance, group membership, sharing links and role changes until people can reach far more than their current work requires. No single grant looks wrong. The result is a SharePoint environment where real access has drifted well beyond what anyone at the firm intended.

How is it different from oversharing?

Oversharing is usually a visible, too-wide grant, such as an Anyone link or a site open to the whole firm. Permission creep is the quieter buildup behind it: old group memberships, forgotten unique permissions, and access left over after role changes. Finding creep takes a membership and history review, beyond a report on broad sharing.

Why does Copilot make it louder?

Copilot doesn’t grant new rights. Microsoft says it surfaces only content a user can already view. What changes is discovery. Access nobody found by browsing can now come back from a single prompt, so old, broad permissions become easy to reach, including across matters a user was never meant to work on.

What is a practical cleanup order for a midmarket firm?

Start with the widest audiences. Find broadly shared sites and Everyone-style grants, review organization-wide and Anyone links, review group and Team membership, then check unique permissions on active matter libraries. Confirm every site has an owner. Before adding seats, test what a typical attorney can find about a matter they shouldn’t see.

How does the Snapshot help before more seats?

It’s a 60-minute working session followed by written findings and a 30-minute review. It makes no changes to your environment and installs no software. It ends with a findings report you can use to decide what to review first, before you assign more Copilot seats.

Start with a clear view of your own tenant

Permission creep is a sequencing problem more than a technology problem. The cleanup doesn’t need a new product. It needs the widest audiences found first, owners asked whether access is still justified, and a test before seats go out. If you’d like to see where your own tenant stands, start with the free AI Readiness Snapshot.

Primary sources

All pages read on November 11, 2026. Dates are each page’s on-page “Last updated” date.

Related articles

Have a question?

Talk with Cocha about your AI and data security priorities.

281-607-0616
info@cochatechnology.com

About the author

Steven R. Combs

Steven R. Combs

Co-Founder and Principal
Cocha Technology

Steven brings 30 years in IT and 15 years working with law firms. He helps organizations deploy Claude and Microsoft 365 Copilot with practical data protection, permissions, and ongoing governance.

Request your free AI Readiness Snapshot →

From guidance to action

See where your AI rollout needs attention.

The free AI Readiness Snapshot identifies selected priorities across permissions, data protection, monitoring, Shadow AI, and Secure Score. Deeper assessment and remediation are separately scoped.

Request your free Snapshot → Review the scope →

More guidance