An object in Microsoft Entra Agent ID that serves as a template for creating agent identities and holds the credentials used to obtain tokens on their behalf. Disabling a blueprint stops all agent identities created from it from signing in.
An agent identity blueprint is an object in Microsoft Entra ID, within Microsoft Entra Agent ID, that acts as a template for agent identities and defines how agents are created, authenticated and managed. It works as a container: many agent identities of one kind can be administered centrally, while each agent identity keeps its own identity, credentials and permissions. The concept addresses a common problem with non-human identities, which is the lack of a repeatable and consistent way to create, manage and retire them.
The blueprint holds the properties that agent identities of one kind share. According to Microsoft Learn, these include a description, app roles, the verified publisher and authentication protocol settings such as optional claims. Credentials used to request access tokens are configured on the blueprint, so agent identities created from it can obtain tokens on that basis. OAuth permissions granted to the blueprint apply to every identity created from it. Required resource access and inheritable permissions on a blueprint are only declarations, so administrators must still give consent before they take effect. Blueprints can be single-tenant or multitenant, and the documentation reviewed here names no licensing requirements.
A blueprint is also an identity in its own right, with exactly one allowed operation: provisioning or deprovisioning agent identities. For that purpose it needs an OAuth client ID, credentials and the Microsoft Graph permission AgentIdentity.CreateAsManager. Blueprints are created through Microsoft Graph.
The blueprint is also a central control point. Conditional Access policies applied to a blueprint reach all of its agent identities. Disabling a blueprint stops authentication for every agent identity created from it, which gives administrators a single action to stop a whole group of agents from signing in. This is relevant for incident response, retirement of a class of agents, or policy enforcement across many similar agents without editing each identity separately.
The M365.FM episode "AI Agent Identity Security: Beyond Service Accounts" (2026-06-26) discusses the blueprint as a repeatable, secure way to create, manage and retire agent identities. The episode says it ensures every agent follows the same rules and security controls, and presents it as a way to avoid unmanaged non-human identity sprawl. It breaks a strong blueprint into components: a template that records shared characteristics for consistent configuration across agent identities; an identity that acts as a special identity type able to provision or deprovision agent identities; a credential container that holds the credentials used for authentication so that agent identities can request access tokens; and a management container.
In practice, the decision around a blueprint is about granularity. Because credentials, OAuth permissions and Conditional Access policies set on the blueprint apply to all agent identities created from it, the choice of what belongs in one blueprint determines the shared blast radius, and the extent of central control, for those agents. Its broader context is Microsoft Entra Agent ID, the area of Microsoft Entra that deals with identities for AI agents.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
AI agents are often managed like traditional service accounts—but that mindset creates serious security and governance risks. This episode explains why AI agents should be treated as autonomous digital identities with their own lifecycle, permissions, and…
Shadow IT didn’t disappear, it evolved into AI agents quietly moving your data faster than your controls can see. In this episode, we break down how AI agents, Copilot Studio bots, and Power Automate flows are becoming the new Shadow IT inside Microsoft 365.…
Timeline of episodes about Agent identity blueprint
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is an agent identity blueprint? (AI)
It is an object in Microsoft Entra Agent ID that acts as a template for agent identities. It holds shared properties and the credentials used to request access tokens, and it defines how agents are created, authenticated and managed.
What happens when an agent identity blueprint is disabled? (AI)
Disabling a blueprint stops authentication for all agent identities created from it, so none of them can sign in.
How is an agent identity blueprint created and what can it do itself? (AI)
It is created through Microsoft Graph. As an identity itself, it has one allowed operation, provisioning or deprovisioning agent identities, and for this it needs an OAuth client ID, credentials and the Graph permission AgentIdentity.CreateAsManager.
Related topics in brief
Topics linked to Agent identity blueprint, each briefly explained:
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Experts on related topics
Experts on topics related to Agent identity blueprint, each with the topic that connects them: