Agent sprawl in Microsoft 365: find agents nobody owns
In short
Agent sprawl is the build-up of Copilot Studio, Agent Builder and SharePoint agents, and the Power Platform resources behind them, that nobody owns or reviews. To control it, build one inventory from the Microsoft 365, Power Platform, Microsoft Entra and SharePoint admin centers, give every agent an accountable sponsor, and block, then retire, agents nobody uses.
Agents are easy to make. A maker builds one in Microsoft Copilot Studio over lunch. A colleague creates another with Agent Builder, and a site owner adds a SharePoint agent to a project site. Each one can reach data and outlive the person who made it.
What is agent sprawl?
Agent sprawl is the build-up of agents in a Microsoft 365 tenant that nobody owns, uses or reviews. It covers Copilot Studio and Agent Builder agents, SharePoint agents, and the Power Platform resources they depend on. It is one of the six kinds of Microsoft 365 sprawl, and it answers one question: which agents does nobody own?
Ownership matters more for agents than for most objects. An agent can draw on knowledge sources, call connectors and act for the people who use it. When its maker leaves, nobody decides whether it should still exist or what it should reach. It is the same problem as ownerless teams and sites, but the object can act.
Where do agents come from in Microsoft 365?
Agents come from four places: Microsoft Copilot Studio, Agent Builder in Microsoft 365 Copilot, SharePoint sites and the Agent Store. Each keeps its own list.
- Microsoft Copilot Studio. Makers build agents in Power Platform environments, often the default one, on top of connections, connectors and agent flows. New agents automatically get an agent identity in Microsoft Entra Agent ID (the agent's own sign-in identity in your tenant). Agents created before May 2026, when this began, keep app registrations until admins migrate them (in preview) or Microsoft does.
- Agent Builder in Microsoft 365 Copilot. People describe an agent in plain language and share it with colleagues. These agents don't currently use Entra agent identities, so the Entra agent identity list doesn't show them.
- SharePoint agents. People create agents grounded in a site's content. Each one is saved as an .agent file on the site.
- The Agent Store. People can install agents built by Microsoft, your organization or external publishers, depending on what you allow.
How do you inventory the agents in your tenant?
Build one list from four admin views (the Microsoft 365, Power Platform, Microsoft Entra and SharePoint admin centers), then reconcile it. Expect overlaps.
- Microsoft 365 admin center. The agent registry lists agents across platforms and publishers. It counts agents without owners, filters to them in one click and exports to CSV. By design, one Copilot Studio agent can appear twice, under two publisher types.
- Power Platform admin center. Power Platform inventory lists agents built in Copilot Studio and Agent Builder alongside apps, flows and environments. Filter by owner and environment type, then export to CSV.
- Microsoft Entra admin center. The agent identity list shows agent identities and agents that use a plain service principal (an app's sign-in identity), with status, permissions, owners and sponsors.
- SharePoint admin center. The Agent Insights report uses audit data to show which sites and OneDrive accounts hold the most agents created in the last 1, 7, 14 or 28 days, so treat it as a recent-activity view, not a full list. Without SharePoint Advanced Management, you turn on data collection, generate reports a day later and see only agents created since. For older agents, check the Microsoft 365 admin center registry, which includes SharePoint agents used in Copilot Chat.
For scripts, Microsoft Graph lists agent identities, but not plain service principals or app registrations, with the AgentIdentity.Read.All permission. A signed-in admin also needs a role such as Agent ID Administrator:
GET https://graph.microsoft.com/v1.0/servicePrincipals/microsoft.graph.agentIdentity?$select=displayName,accountEnabled,disabledByMicrosoftStatus
Then compare the lists. An agent that has an owner in one view and none in another is where ownership has drifted.
Who should own or sponsor an agent?
Every agent needs a sponsor who answers for why it exists and an owner who keeps it running. Microsoft Entra Agent ID makes this split explicit in its guide to owners, sponsors and managers.
- Sponsors are business representatives accountable for an agent's purpose and lifecycle. Each agent identity needs at least one. They can disable or soft-delete it and change its sponsors, but not its technical settings.
- Owners are technical administrators. They manage configuration and credentials, and they can re-enable or restore what a sponsor disabled. Owners are optional.
Only agents with an Entra agent identity have a sponsor field. For the rest, such as Agent Builder and SharePoint agents, record the accountable business person in your inventory.
Two cautions apply. First, "owner" means different things in different tools. In Copilot Studio, the owner is the maker who created or was assigned the agent, and editors can change it but not delete it. In Agent Builder, everyone with edit rights is an owner. On an Entra agent identity, the owner is a technical administrator. Copilot Studio makes the agent's owner the sponsor of its agent identity, though some preexisting agents might not have one yet.
Second, a sponsor set at creation doesn't stay current as people move and leave. Assign a group where you can: Microsoft 365 groups and dynamic membership groups can be sponsors (up to five groups per agent identity), but assigned-membership security groups and any role-assignable group can't. Sprawlsight's free snapshot checks this as AGT-001, "Every agent identity has a sponsor."
What should you do about agents Microsoft disabled for abuse?
Investigate them and remove their permissions. Microsoft has blocked new token requests, but existing access tokens stay valid until they expire, and granted permissions remain. When Microsoft confirms that an app breaks its terms, Microsoft Entra ID disables it. Agent identities carry the same disabledByMicrosoftStatus property, set to DisabledDueToViolationOfServicesAgreement.
Microsoft notes that these objects can't be deleted, so clean up around them:
- Check audit and sign-in logs for what the agent did and which users signed in to it or consented to it.
- Review the delegated and application permissions it was granted, and remove them.
- Block or remove the agent wherever it is listed or deployed, and tell its sponsor.
The free snapshot flags any agent identity in this state as AGT-002, "No agents that Microsoft disabled for abuse remain." Because you can't delete the identity, treat the finding as a prompt to finish the steps above.
How should you set up environments and sharing?
Treat the default environment as personal productivity space, not a home for shared agents. Every employee has access to it, so whatever you allow there, you allow for everyone.
- Route makers away from the default environment. Environment routing sends makers who open Copilot Studio, Power Apps or Power Automate to personal developer environments. These are managed environments, and people need premium licenses to run what they build there.
- Apply data policies. Power Platform data policies, also called data loss prevention (DLP) policies, sort connectors into business, non-business and blocked groups. In Copilot Studio, they can also require user authentication and block knowledge sources, connectors, HTTP requests and publishing channels. In the default environment, Microsoft recommends making Blocked the default group, so new connectors stay unusable until reviewed.
- Limit sharing. In managed environments, sharing limits control whether makers can share Copilot Studio agents with editors, viewers or security groups, and can cap viewers when sharing is limited to individuals. They apply only to agents that require authentication, another reason to require it through data policies. For Agent Builder agents, the sharing setting in the Microsoft 365 admin center decides who can share with the whole organization.
- Decide which store agents people can install. The same settings allow or block agents built by Microsoft, your organization and external publishers.
Sharing rules don't remove existing access, so also review what is already shared.
What should happen to agents nobody uses?
Block them first, confirm with the sponsor or owner, then delete. Blocking is reversible, so a quiet user can speak up first.
- Unused agents. Start with agents that have no owner and no recent use. An agent management rule in the Microsoft 365 admin center can block them in bulk.
- Makers who leave. Shared agents become ownerless when the creator's account is deleted. Admins can then assign a new owner to Agent Builder and Copilot Studio agents. Better, add a second owner to each shared Agent Builder agent before anyone leaves. Copilot Studio agents have a single owner, so give each a co-author and make reassignment part of the leaver process that cleans up inactive guests and accounts.
- Sponsor handover. When a sponsor leaves, Microsoft Entra moves their sponsorships to their manager. Microsoft Entra ID Governance lifecycle workflows can also email the manager and co-sponsors, and transfer sponsorships when someone moves or leaves. They need extra licensing. Either way, confirm the new sponsor as part of your leaver checklist.
- Review cadence. Review every agent at least quarterly, and after reorganizations. Ask each sponsor three questions: is it still needed, who uses it, and does it reach more than it should?
Agents reach whatever their identities and users can reach, so include them in your Microsoft 365 permissions audit.
Which controls apply to each agent type?
Each agent type has its own main control: data policies and sharing limits for Copilot Studio, the sharing setting for Agent Builder, site permissions for SharePoint agents, publisher rules for store agents and sponsors for agent identities.
| Agent type | Where to inventory it | Owner signal | Control |
|---|---|---|---|
| Copilot Studio agents | Power Platform inventory; Microsoft 365 admin center registry; Entra agent identities (newer or migrated agents) | Owner in Copilot Studio; sponsor on the Entra agent identity | Data policies, sharing limits, environment routing, reassign or block |
| Agent Builder agents | Microsoft 365 admin center registry; Power Platform inventory | Owners (people with edit rights) | Org-wide sharing setting, add or assign owners, block |
| SharePoint agents | Agent insights report (recent agents); Microsoft 365 admin center registry | The site that stores the .agent file, and its owners | Site permissions, Restricted Content Discovery, block in Copilot Chat |
| Agent Store agents | Microsoft 365 admin center registry, filtered by publisher type | Publisher, plus the admin who installed or approved it | Allow by publisher type, install, block |
| Agent identities | Microsoft Entra admin center agent identity list | Sponsors and owners | Disable, Conditional Access, sponsor lifecycle workflows |
| Power Platform apps and flows | Power Platform inventory | Owner column (for flows, the creator) | Data policies, environment strategy |
Sprawlsight's Sprawl Score measures all of this as Agent Sprawl. For the full clean-up playbook and a checklist, get the agent sprawl field guide.
Agents will keep multiplying, and that is fine. The goal is that every one has a named sponsor, a reason to exist and a date for its next review.
Frequently asked questions
Do Agent Builder agents get a Microsoft Entra agent identity?
Not currently. Microsoft's Copilot Studio documentation says Agent Builder agents don't use app registrations or Entra agent identities, so they won't appear in the Entra agent identity list. Inventory them in the Microsoft 365 admin center or in Power Platform inventory instead.
What happens to an agent when its maker leaves the organization?
The agent doesn't disappear. Once the maker's account is deleted, a shared agent can become ownerless, and the Microsoft 365 admin center counts and filters these agents for you. Admins can assign a new owner to Agent Builder and Copilot Studio agents, and adding a second owner to Agent Builder agents before people leave avoids the gap. Copilot Studio agents have a single owner, so reassign them as part of your leaver process.
What is the difference between an agent owner and an agent sponsor?
In Microsoft Entra Agent ID, a sponsor is the business person accountable for why an agent exists and whether it should continue. An owner is a technical administrator who manages its configuration. Every agent identity needs at least one sponsor, while owners are optional.
Can we stop people from creating agents?
You can narrow who creates and shares agents rather than switch agents off everywhere. Withhold Copilot Studio user licenses and block self-service trials, but note that people with a Microsoft 365 Copilot license can still build in Copilot Studio. Use environment security roles outside the default environment, route makers away from it, apply data policies, and limit who can share Agent Builder agents with the whole organization. A practical middle ground is to allow personal agents and add a review before an agent is shared widely.
How often should we review agents?
At least quarterly, and whenever a sponsor or owner changes roles or leaves. Each review should confirm the agent is still needed, still used and still has a current sponsor. Block agents that fail the review before you delete them, so anyone who still relies on one can speak up.