What is Microsoft 365 sprawl? The six kinds that matter
In short
Microsoft 365 sprawl is the access, objects and settings in a tenant that nobody owns or reviews. It comes in six kinds: sharing, identity, agent, workspace, permission and policy sprawl. Sprawl matters more with Copilot and agents, because they act with whatever access exists. Measure all six, then fix sharing first.
Most Microsoft 365 tenants weren't designed. They grew. Every team, share, guest invitation and app consent made sense on the day it happened. Years later, nobody remembers why half of it exists. Then Microsoft 365 Copilot arrives and can draw on any of it that a user is able to open.
This post defines Microsoft 365 sprawl, splits it into six kinds you can measure, and shows where to start.
What is Microsoft 365 sprawl?
Microsoft 365 sprawl is the accumulated access, objects and settings in a tenant that nobody owns or reviews. It includes:
- sharing links that outlived their purpose
- guests and accounts that no longer sign in
- teams and sites nobody uses
- agents whose maker has moved on
- permissions granted through side doors
- policies with gaps nobody has checked
Sprawl is not the same as size. A tenant with thousands of sites can be tidy if every site has an owner and a lifecycle. A 200-person tenant can be badly sprawled if nobody has reviewed sharing since the move to the cloud. The test is accountability: does someone own this, and has anyone looked at it lately?
Why does sprawl matter more once Copilot and agents arrive?
Copilot and agents act with whatever access already exists, so sprawl decides what they can reach. Microsoft states that Copilot only surfaces organizational data to which individual users have at least view permissions. That is the right design. It also means Copilot inherits every old decision in your permissions model.
Before Copilot, an overshared folder was protected by obscurity. You had to know it existed and where to look. Copilot removes that friction. A user asks a question, and the answer can draw on any file that user can open. That includes a salary spreadsheet in a site someone opened years ago to "Everyone except external users", a built-in group that includes everyone in your organization except guests. Controls such as Restricted Content Discovery and sensitivity labels can keep content out of Copilot's answers, but only once someone sets them up.
Agents raise the stakes in a second way. Each one is a new object with its own reach, built in Microsoft Copilot Studio, in Agent Builder or on a SharePoint site. Like a team or a site, an agent can outlive the person who made it. When nobody owns it, nobody is accountable for what it reaches or who uses it.
So sprawl does two things in an AI rollout. It widens what Copilot and agents can reach, and it hides who is accountable for that access.
What are the six kinds of Microsoft 365 sprawl?
The six kinds of Microsoft 365 sprawl are Sharing, Identity, Agent, Workspace, Permission and Policy Sprawl. Each answers one plain question, and splitting sprawl this way turns "clean up the tenant" into work you can measure, assign and track.
| Kind | The question it answers | Typical examples |
|---|---|---|
| Sharing Sprawl | Can Copilot reach what it shouldn't? | 'Anyone' (anonymous) links, content shared with 'Everyone', overshared sites, sites with no owner |
| Identity Sprawl | Who still has access they don't use? | Guests, accounts and admins that no longer sign in; app registrations nobody uses |
| Agent Sprawl | Which agents does nobody own? | Copilot Studio and Agent Builder agents, SharePoint agents and Power Platform resources nobody owns |
| Workspace Sprawl | Which workspaces has everyone forgotten? | Teams, groups and sites with no owner, no activity or no retention |
| Permission Sprawl | Who has access through a side door? | Nested groups, standing admin rights, app consent |
| Policy Sprawl | Where do your policies leave gaps? | Data loss prevention (DLP), sensitivity labels and Conditional Access, measured against CISA's SCuBA baseline |
The kinds overlap at the edges, and that is useful. An ownerless team is Workspace Sprawl, but if its site also has 'Anyone' links, it is Sharing Sprawl too. An object that shows up in two kinds is usually one to fix early.
A note on Policy Sprawl: SCuBA is CISA's Secure Cloud Business Applications project, which publishes security configuration baselines for Microsoft 365. It is CISA's baseline, not Microsoft's, and it gives you an outside yardstick for policy gaps.
How does sprawl build up?
Sprawl builds up from normal work, not one bad decision. The five common causes are self-service creation, projects ending, people leaving, defaults left as shipped, and consent granted once and never revisited.
- Self-service creation. People create teams, groups, sites, shares and agents when they need them. That is good for productivity, but creating is easy and cleaning up is nobody's job.
- Projects ending. The project finishes and the people move on. The team, its guests and its sharing links stay exactly as they were.
- People leaving. Microsoft notes that a team or group can become ownerless when an owner's account is deleted. The agents, app registrations and shared files that person created lose their owner too.
- Defaults left as shipped. Many settings start open so collaboration works on day one: who can create groups, how widely people can share, which apps users can consent to. Few tenants revisit them after setup.
- Consent granted once and never revisited. Tightening user consent settings later only affects future consent. Microsoft is explicit that existing consent grants remain unchanged, so old grants stay until someone reviews them.
None of these is a mistake on its own. Together, they mean sprawl grows by default and shrinks only by effort.
How do you measure Microsoft 365 sprawl?
Measure sprawl with an inventory of objects plus four signals for each one: owner, last activity, link type and assignment type. Counting objects alone misleads, because 500 active, owned teams are healthier than 50 forgotten ones.
| Signal | What it tells you | Where it applies |
|---|---|---|
| Owner | Is someone accountable? | Teams, groups, sites, agents, app registrations |
| Last activity | Is it still used? | Accounts, guests, admins, sites, teams, agents |
| Link type | How far does sharing reach? | Files and folders in SharePoint and OneDrive |
| Assignment type | How was access granted? | Directly, through a nested group (a group inside another group), an admin role held permanently (standing) or activated only when needed (eligible), or app consent |
For last activity on accounts, Microsoft Graph exposes a signInActivity property on each user that includes the last successful sign-in. Reading it requires Microsoft Entra ID P1 or P2, plus the User.Read.All and AuditLog.Read.All permissions. The last successful sign-in counts both interactive and non-interactive sign-ins. Microsoft's guidance is that in many organizations a reasonable window for inactive accounts is between 90 and 180 days.
GET https://graph.microsoft.com/v1.0/users?$select=displayName,userType,signInActivity
For link type, SharePoint and OneDrive offer 'Anyone with the link' (no sign-in needed), 'People in your organization', 'People with existing access' and 'Specific people'. 'Anyone' links are the widest external exposure: nobody has to sign in, and access can't be audited. For Copilot, the most direct exposure is content granted to everyone in the organization, such as sites, libraries or files shared with 'Everyone' or 'Everyone except external users'. Creating an 'Anyone' or 'People in your organization' link doesn't on its own make a file searchable or reachable through Copilot. Access extends only to people who redeem the link, which usually means opening it. A 'Specific people' link, by contrast, makes the file reachable through Copilot for everyone named on it.
Once you have the signals, turn them into a number you can track. Sprawlsight's Sprawl Score does this across the six kinds, on a scale of 0 to 100 where higher is tidier. Whatever you use, measure the same way each time so the trend means something.
Where should you start cleaning up?
Start with sharing, because it is the most direct Copilot exposure. Then move to identity, then workspace ownership. That order fixes what Copilot can reach today before what could cause trouble later.
- Sharing. Review sites and content opened to 'Everyone' or 'Everyone except external users', give every site an owner, and turn off or restrict 'Anyone' links, which reach people outside your organization without a sign-in. Sprawlsight's free snapshot checks the last of these as SPO-001, "'Anyone' links are turned off for SharePoint." Our guide to SharePoint oversharing covers the full cleanup.
- Identity. Remove guests who no longer sign in, turn off accounts nobody uses, and confirm that every admin still signs in.
- Workspace ownership. Give every team, group and site at least one owner, then archive or delete what nobody claims.
Agents, permissions and policy come next. They matter just as much, but fixing them usually needs decisions from more people, and that goes faster once sharing, identity and ownership are under control. Each has a field guide with a full cleanup playbook: agent sprawl, permission sprawl and policy sprawl.
Preparing for a rollout? Our post on Copilot readiness puts these steps into a full plan. The Copilot readiness checklist turns them into items you can tick off.
How do you keep sprawl down?
Keep sprawl down with four habits: owners on everything, lifecycle policies, access reviews and scheduled re-assessment. Cleanup without these habits just resets the clock.
- Owners. Aim for at least two owners on every group, team and site, so one departure doesn't orphan it. Turn on the ownerless group policy in the Microsoft 365 admin center (Settings > Org settings > Microsoft 365 Groups). When a group or team loses its last owner, it emails the most active members each week and asks them to take ownership. For sites without a group, use the site ownership policy described below.
- Lifecycle policies. A Microsoft 365 group expiration policy renews active groups automatically and asks owners to renew the rest. Groups nobody renews are deleted, with 30 days to restore them. It needs Microsoft Entra ID P1 or P2 licenses for the members of the groups it covers. For sites, SharePoint site lifecycle management in SharePoint Advanced Management adds site ownership, inactive site and site attestation policies. SharePoint Advanced Management is included when at least one user has a Microsoft 365 Copilot license, or with the SharePoint Advanced Management Plan 1 add-on.
- Access reviews. Access reviews in Microsoft Entra ID ask group owners or named reviewers to confirm who still needs access, including guests and people in admin roles. They need Microsoft Entra ID Governance or Microsoft Entra Suite licensing, though some capabilities work with Microsoft Entra ID P2.
- Scheduled re-assessment. Sprawl comes back as people create, share and leave. Re-measure on a schedule, at least quarterly, and after big changes such as a reorganization, a merger or a Copilot rollout. Compare each result with the last one, not with perfection.
Sprawl is never finished, but it can be kept small. Name the six kinds, measure them the same way every time, and give every object an owner who answers for it.
Frequently asked questions
Is tenant sprawl the same as Microsoft 365 sprawl?
People use tenant sprawl in two ways. Some mean running more Microsoft 365 tenants than you need, often after mergers or trials. More often it means sprawl inside one tenant: sharing, identities, agents, workspaces, permissions and policies that nobody owns. This post covers the second meaning, and the same six kinds apply in every tenant you run.
What is the difference between Teams sprawl and SharePoint sprawl?
Every team is backed by a Microsoft 365 group and a SharePoint site, so Teams sprawl always shows up as SharePoint sprawl too. Teams sprawl usually means teams and channels nobody uses or owns. SharePoint sprawl adds sites created outside Teams and the sharing links inside them. Both count as Workspace Sprawl, and the links count as Sharing Sprawl.
Does Microsoft 365 Copilot create new sprawl?
Copilot works within the permissions you already have. It only surfaces content the user can already view, so it doesn't widen access: mostly, it exposes the sprawl you already have. What people create with it is new, though: Copilot Pages and Copilot Notebooks are stored in a container each user owns, which needs an offboarding step just like OneDrive. Agents are different: each one is a new object that needs an owner and a review, and agents nobody owns are a new kind of sprawl.
How often should we measure Microsoft 365 sprawl?
At least quarterly, and after big changes such as a reorganization, a merger or a Copilot rollout. Sprawl returns as people create, share and leave, so a single cleanup doesn't last. Tenants that change quickly benefit from monthly or weekly checks, so new problems surface while they are still small.
Should we delete everything that looks inactive?
No. Inactive doesn't always mean unneeded: some sites hold records you must keep, and retention policies may apply. Confirm with an owner first, then archive, set to read-only or delete. Group expiration policies and SharePoint inactive site policies build that confirmation step in.