Playbooks · Teams
Audit agent blueprint creation in Entra
Written November 15, 2026
Since November 4, default users in Entra can create agent identity blueprints. Where the setting sits, how to inventory what exists, and the 403 catch.
A creation right most admins never granted
In a default Microsoft Entra tenant, ordinary users can create agent identity blueprints — the templates from which agent identities are made. Microsoft's guide to delegating application and agent management permissions states it directly: "By default, users in your organization can create agent identity blueprints." The blueprint creation guide names the switch behind it: if the organization-wide setting "Users can create agent blueprints" is set to Yes, "any user within the tenant can create an agent identity blueprint and its agent identity blueprint principal." Creators are automatically set as owners of both the blueprint and its principal, and owners can create agent identities for that blueprint without holding an Agent ID role. Nothing in that chain requires an admin to have approved anything first.
Where the setting sits
The toggle is a user setting, not an Agent ID setting. The delegation guide gives the path: sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator, browse to Entra ID, then Users, then User settings, and set "Users can create agent blueprints" to No. Doing so "will disable the default ability for users to create new agents within Entra" and, in the guide's words, restricts creation to administrators and users assigned the Agent ID Developer role. One inconsistency is worth knowing before you rely on any single page: the creation guide's prerequisites still lead with the Agent ID Developer and Agent ID Administrator roles and present the setting second — follow the user-settings pages for the toggle itself.
Inventory what already exists
Turning the setting off stops new blueprints; it says nothing about the ones already in the tenant. Microsoft's guide to managing agent identity blueprints gives the inventory route: in the Entra admin center, browse to Entra ID, then Agents, then Agent blueprints, where you can view all agent identity blueprint principals in the tenant and search, filter, and sort them — including a filter by Blueprint App ID. Each blueprint carries an accountable sponsor and an owner, the administrative relationships the creation guide asks for at setup, so an inventory can name a person for every template it finds. For creation activity rather than current state, Microsoft's guide to how agent identities are created points admins at the audit logs — subscribe to audit events filtered on agent identity creation operations — and at Microsoft Graph queries over agent identity objects for a full inventory.
Governing what you find
Blueprints are the control point because identities inherit from them. The blueprint overview notes that administrators can apply Conditional Access policies to an agent identity blueprint that target all agent identities created from it, and that disabling a blueprint prevents all of its agent identities from authenticating. Credentials and OAuth permissions granted to a blueprint are likewise granted to every identity created from it, which is why a blueprint created casually by a default user deserves the same review as one created deliberately by an admin.
The CreateAsManager catch
The companion change concerns how identities get created from blueprints. A blueprint creates identities through a special Microsoft Graph permission, AgentIdentity.CreateAsManager, and Microsoft's creation-channels guide says that permission "is automatically granted to any agent identity blueprint principal in the tenant" and "can't be revoked" — to stop a principal creating identities, you disable it or remove it from the tenant. Against that standing behaviour, a November 2026 change (Message Center MC1506728) tightens consent for agents created outside Microsoft-managed platforms. As a Microsoft employee put it in the Microsoft Q&A thread on MC1506728, "Microsoft-managed platforms like Copilot and Foundry will continue to work as needed without explicit consent," while agents created in your organization, other organizations, or third-party platforms "will need explicit consent." A child identity that used to appear automatically can therefore stall at creation time — not because the blueprint broke, but because the consent it relied on is no longer automatic.
What to do
Inventory first, while creation is still visible in the audit logs. Then decide the setting deliberately: No, if blueprint creation should be an assigned role in your tenant; Yes, only if you are comfortable with any user standing up a template that can mint agent identities. Either way, review the blueprints that already exist — their owners, sponsors, credentials, and Conditional Access coverage — because the default gave them a path into your tenant without an admin decision.
Related playbooks
- Copilot CLI signs in with Microsoft Entra
- Baseten Grid routes coding-agent traffic
- Copilot Agent Merge: watch a PR and fix its blockers
- Currents Sessions: one link per agent task
Sources
- Delegate application and agent management administrator permissions — Microsoft Learn
- Create an agent identity blueprint — Microsoft Learn
- Manage agent identity blueprints — Microsoft Learn
- Agent identity blueprints in Microsoft Entra Agent ID — Microsoft Learn
- How are agent identities created? — Microsoft Entra Agent ID, Microsoft Learn
- MC1506728 – Clarification on AgentIdentity.CreateAsManager for Copilot Studio agent identity blueprint — Microsoft Q&A
Back to: Teams playbooks hub · Also: Zalando's broker hands agents OAuth safely · Microsoft 365 Copilot connectors can now write · Also: Set a spending policy before Copilot billing does