Microsoft Entra Agent ID
Authentication

Microsoft Entra security for AI overview

In brief

The documentation now distinguishes the Agent identity platform’s authentication and authorization role from the Agent 365 registry’s inventory role. It also limits Entra logging guidance to identity activity and states that permission inheritance for fleets requires consent and explicit configuration.

What Entra admins need to know

Administrators managing agent fleets must provide consent and configure permission inheritance; application and downstream-service activity must be monitored separately.

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.

  • Register and manage agents: Create and manage agent identity blueprints as templates and agent identities as individual instances with parent-child relationships, enabling centralized metadata management and automatic organization into security collections.

  • Assign secure, scalable identities: The Microsoft Entra Agent identity platform enables you to assign identities to agents, autodiscover them across your organization, and manage all agent metadata in one place including capabilities, tasks, and protocols. ItMicrosoft Entra Agent identity platform provides agent-to-agent discoverythe authentication and authorization based on standard protocols such as Model Context Protocol (MCP)foundation for agents. The Microsoft Agent 365 registry provides the broader agent inventory and agent-to-agent (A2A).metadata experience.

  • Log and monitor agentidentity activity: AllUse Microsoft Entra sign-in and directory audit logs to investigate authentication and identity-management operations. Instrument the agent and its downstream services separately to observe application actions performed by agents are logged in Microsoft Entra ID and viewable through the Microsoft Entra admin center for compliance and audit purposes.results. See Sign-in and audit logs for agents.

For more information about agent identities as identity constructs, including how they differ from application and user identities, see What are agent identities?What are agent identities?.

Control AI access with Zero Trust

  • Govern agent identities at scale, from deployment to expiration.
  • Ensure sponsors and owners are assigned and maintained for each agent identity, preventing orphaned agent identities.
  • Enforce that agent access to resources is intentional, auditable, and time-bound through access packages.
  • Apply Conditional Access rules, permissions,supported policy and governance controls at the blueprint level so all currentblueprint level. API permission inheritance is separate: fleets require consent and future agent instances inherit them automatically, with the ability to disable an entire class ofexplicit inheritance configuration, while single-instance agents in a single operation.receive grants directly.
  • Maintain a complete inventory of all agent identities through centralized discovery and management in the Microsoft Entra admin center and Microsoft Graph, preventing shadow AI and enabling organizations to track agents across the full lifecycle — from registration and credential management through deactivation and decommissioning.

For more information, see Identity governance for agents.

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…