Microsoft Entra Agent ID
Authentication

Inheritable Permissions

In brief

Permission inheritance applies to multi-instance fleets using a blueprint and blueprint principal. Cloud and local single-instance agents lack a blueprint principal and receive permission grants directly, while still being able to declare required resource access.

What Entra admins need to know

Administrators should use the documented permission model that matches their agent architecture.

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.

Required resource access

Permission inheritance applies to fleets that use a multi-instance blueprint and blueprint principal. A cloud or local single-instance agent has no blueprint principal and receives permission grants directly. It can still declare required resource access, but those declarations alone don't grant access.

Required resource access is the agent identity blueprint's initial declaration of the APIs and permissions that the blueprint's child agent identities need to operate. It's expressed as a set of target resource applications and the specific delegated scopes and application roles the agent requests.

Required resource access serves as the agent's list of static consent permissions. When a tenant administrator reviews the agent for approval, this list makes the consent decision explicit and reviewable. It answers the question: "What does this agent need to function?"

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…