Microsoft Entra Agent ID
Conditional Access

Manage Agent Identities Admin

In brief

The documentation now explains permission inheritance prerequisites, distinguishes requested access from granted consent, links to current limitations, and clarifies that the Graph example returns only service principal sign-in events.

What Entra admins need to know

Administrators get clearer guidance for configuring inherited permissions and interpreting agent sign-in data.

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.

#customer intent: As an IT administrator, I want a unified guide for managing agent identities in my organization so that I can efficiently view, govern, monitor, and secure agents across the full management lifecycle.

Configure inheritable permissions for blueprints

Inheritable permissions letcan make permissions granted to a blueprint principal available to its agent identities automatically inherit OAuth 2.0identities. The current Microsoft Graph beta reference documents delegated scope inheritance through inheritableScopes. The broader Agent ID permission scopes from their parent blueprint. When you configuremodel also describes application-role inheritance, but the public Graph reference doesn't define an application-role property or payload. Confirm Graph support before relying on application-role inheritance.

Inheritance requires both a resource app to be configured as inheritable and the permission to be granted to the blueprint principal. Required resource access declares requested permissions on a blueprint, newly created agent identities receive a base set of scopes without requiring interactive user or adminfor consent prompts.review; it doesn't grant access by itself. For static consent, include the permission in required resource access. For dynamic consent, explicitly request the permission. For details, see Inheritable permissions and required resource access and the Microsoft Graph inheritablePermission resource.

Two inheritance patterns are supported per resource app:

Start with enumerated scopes using only essential permissions, then expand as needed. This approach follows the principle of least privilege and makes it easier to audit which permissions agents actually use.

Key limits:

  • Maximum of 10 resource apps per blueprint.
  • For enumerated scopes, maximum of 40 scopes per resource app.
  • Some high-privilege scopes are blocked bycurrent API constraints and platform policy and can't be inherited.
restrictions, see Inheritable permissions limitations.

Inheritable permissions are configured via the inheritablePermissions navigation property on the agentIdentityBlueprint application resource using Microsoft Graph. For step-by-step API examples (add, update, delete), see Configure inheritable permissions for agent identity blueprints.

  • Agent type: Choose from Agent ID user, Agent Identity, Agent Identity Blueprint, or Not Agentic.
  • Is Agent: Choose from No or Yes.

You can also retrieve agentThis Microsoft Graph example retrieves only service principal sign-in events using Microsoft Graph:for agent identities. It doesn't return every sign-in type associated with agents; see Microsoft Entra Agent ID logs for the other log types and filtering options.

GET https://graph.microsoft.com/beta/auditLogs/signIns?$filter=signInEventTypes/any(t: t eq 'servicePrincipal') and agent/agentType eq 'AgentIdentity'
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…