Microsoft Entra Agent ID
Architecture

Agent Id Design Patterns

In brief

The article now uses updated links and clarifies blueprint principals, single- and multi-instance modes, permission inheritance, and delegated versus application access guidance.

What Entra admins need to know

Administrators get clearer guidance for understanding Agent ID deployments and assigning permissions; no configuration change is required.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Key concepts

The following components are the foundation of Microsoft Entra Agent ID. If you're new to them, start with Microsoft Entra Agent ID key conceptsMicrosoft Entra Agent ID key concepts before continuing with this article.

Identity constructs

The following identity constructs are used throughout the patterns described in this article:

Permissions models

Blueprint-level permissions and agent identity-level permissions serve different purposes:

  • BlueprintFleet blueprint permissions represent the minimum permissions shared across all agent identities created from the blueprint. Use inheritable permissions on the blueprint when you want all agent identities to start withcan provide a common baseline.baseline through explicitly configured inheritance and consent. Single-instance agents don't have a blueprint principal and receive permissions directly.
  • Agent identity permissions represent differentiated permissions for a specific agent. Use these permissions when different agents in the same system need different access to downstream resources.

For more information, see Configure inheritable permissions for blueprints and Authorization in Microsoft Entra Agent ID.

Structure: One blueprint → one agent identity

This deployment pattern doesn't by itself select the blueprint's instance mode. A single-instance blueprint and a multi-instance blueprint with one child identity both have one Agent ID, but their client IDs, token acquisition, and permission inheritance differ.

Although a blueprint with a single agent identity might seem redundant, the blueprint gives the agent consistent Conditional Access policies, monitoring, governance, and audit entries — the same infrastructure you need for multi-agent systems, with minimal setup.

Permissions: Grant permissions directly on the agent identity. The blueprint's inheritable permissions aren't typically needed for singleton cases.

Example: An AI sales representative with a real mailbox, listed in the Global Address List, that responds to email and is assigned a human manager in the org chart.

Permissions: Grant the agent's user account the specific Exchange, Teams, and OneDrive permissions it needs. Grant the agent identity application-level permissions for systems that don't require a user object. For more information,delegated access, see Request consent for delegated permissions. For application access, see Permissions and consent in the Microsoft identity platform.

Agent's user account: Required. Create one agent's user account per digital worker agent identity.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…