Governing Agent identities and access
In brief
The overview now describes discovering overprivileged non-human agent identities in applications and links to detection and remediation guidance.
What Entra admins need to know
Administrators can use this guidance to identify and address excessive agent privileges. No required configuration change or deadline is stated.
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.
Governing Agent Identitiesidentities and access
Microsoft Entra allows you to ensure that the right people have the right access to the right apps and services at the right time. Microsoft Entra ID Governance features enable governing the identity and access lifecycle for employees and business guests. With the addition of the Microsoft agent identity platform, managing the access rights of agents in the same way is just as important in the governance lifecycle of your organization's identities. The Microsoft agent identity platform introduces the concept of Agent Identities (IDs). Agent identities are accounts within Microsoft Entra ID that provide unique identification, authentication and authorization capabilities for AI agents.
This allows agent identities to be governed with Microsoft Entra features in the same style as you would govern human identities. With Agent identities, you can govern and manage the identity and access lifecycle of agents, ensuring the agents have a responsible person providing oversight throughout the agent lifecyclelifecycle, and agent's access does not persist longer than it is needed. This article provides an overview of how Microsoft Entra can be utilized to govern agent identities and access.
In addition to agents that are using the Microsoft Entra agent ID platform, Microsoft Entra can also discover the agent non-human identities in an application that have excessive privileges. For more information, see Detection and remediation of overprivileged agent identities (Preview).
License requirements
Agent identities basics
Historically, AI agents would rely upon tools to interact with various applications and systems, andother resources. For an assistive agent, the tools might leverage the authenticated identity of the human user they were assisting. Alternatively, tools might each of those tools would have their own identities in those applications and systems. Some of those tools would useresources. For example, a tool might have historically used a service principalsprincipal to authenticate the agent to Microsoft services via Microsoft Graph or Microsoft Azure APIs.

Microsoft Entra Agent ID introduces support for identities for the agents themselves,themselves in Microsoft Entra and connected applications, with four new types of object: agent identity blueprint, agent identity blueprint principal, agent identity, and agent user. Through the agent identity blueprint, the agent can create one or more agent identities, and optionally an agent user for each agent identity, which it can use for authentication to Microsoft, third party and line of business applications. Each agent identity and agent user can have distinct access rights. The following diagram illustrates the relationship between the new objects in a Microsoft Entra tenant.

For a multitenant-capable agent, an agent identity blueprint principal created in one tenant can be brought into another tenant, the tenant with resources the agent needs to access, so itthe agent can create agent identities in that resource tenant, similar to how a multitenant application can have a service principal in each tenant. The following diagram illustrates the relationship of the Microsoft Entra ID objects when the agent blueprint is in a separate tenant than the resource.

The agent identity and the agent user allow AI agents to take on digital identities within Microsoft Entra. Once agent identities are created, these agent identities are able to be governed using lifecycle and access features. Sponsors can be assigned to agent identities after creation. Sponsors of agent identities are human users accountable for making decisions about its lifecycle and access. For more information about the role of a sponsor of agent identities, see: Administrative relationships for agent IDs. Agent users can also be provisioned to applications.
Agent identities in other Microsoft products and portals
To ensure the security and manageability of agent identities for Microsoft customers, Microsoft Entra Agent ID provides a default inactivity policy to all tenants. This policy identifies inactive agent identities, notifies relevant users, and then proceeds to disable the identity if no new activity is detected. For more information, see Microsoft Entra Agent ID default inactivity policy and Entra Agent ID lifecycle policies.
Dynamic permissions (preview)
In addition to agents that are using the Microsoft Entra agent ID platform, Microsoft Entra can also discover the agent non-human identities in an application that have excessive privileges. For more information, see Detection and remediation of overprivileged agent identities (Preview).
Related content
- Manage agent identities in your organization - Overview of agent identity management across the full lifecycle.
@@ -1,18 +1,20 @@ ----title: Governing Agent Identities+title: Governing Agent identities and access description: This article describes governing agent identities. ms.topic: concept-article #Required; leave this attribute/value as-is.-ms.date: 06/05/2026+ms.date: 11/16/2026 ai-usage: ai-assisted #Customer Intent: As an Identity Governance administrator, I want to learn how to use Microsoft Entra to manage lifecycle and access to resources for agent identities within my organization. --- -# Governing Agent Identities+# Governing Agent identities and access -Microsoft Entra allows you to ensure that the right people have the right access to the right apps and services at the right time. With the addition of the Microsoft agent identity platform, managing the access rights of agents in the same way is just as important in the governance lifecycle of your organization's identities. The Microsoft agent identity platform introduces the concept of Agent Identities (IDs). Agent identities are accounts within Microsoft Entra ID that provide unique identification, authentication and authorization capabilities for AI agents.+Microsoft Entra allows you to ensure that the right people have the right access to the right apps and services at the right time. Microsoft Entra ID Governance features enable governing the identity and access lifecycle for employees and business guests. With the addition of the Microsoft agent identity platform, managing the access rights of agents in the same way is just as important in the governance lifecycle of your organization's identities. The Microsoft agent identity platform introduces the concept of Agent Identities (IDs). Agent identities are accounts within Microsoft Entra ID that provide unique identification, authentication and authorization capabilities for AI agents. -This allows agent identities to be governed with Microsoft Entra features in the same style as you would govern human identities. With Agent identities, you can govern and manage the identity and access lifecycle of agents, ensuring the agents have a responsible person providing oversight throughout the agent lifecycle and agent's access does not persist longer than it is needed. This article provides an overview of how Microsoft Entra can be utilized to govern agent identities and access.+This allows agent identities to be governed with Microsoft Entra features in the same style as you would govern human identities. With Agent identities, you can govern and manage the identity and access lifecycle of agents, ensuring the agents have a responsible person providing oversight throughout the agent lifecycle, and agent's access does not persist longer than it is needed. This article provides an overview of how Microsoft Entra can be utilized to govern agent identities and access.++In addition to agents that are using the Microsoft Entra agent ID platform, Microsoft Entra can also discover the agent non-human identities in an application that have excessive privileges. For more information, see [Detection and remediation of overprivileged agent identities (Preview)](dynamic-permissions-overview.md). ## License requirements @@ -20,15 +22,19 @@ This allows agent identities to be governed with Microsoft Entra features in the ## Agent identities basics -Historically, AI agents would rely upon tools to interact with various applications and systems, and each of those tools would have their own identities in those applications and systems. Some of those tools would use service principals to authenticate to Microsoft services via Microsoft Graph or Microsoft Azure APIs. [Microsoft Entra Agent ID](../agent-id/what-are-agent-identities.md) introduces support for identities for the agents themselves, with four new types of object: agent identity blueprint, agent identity blueprint principal, agent identity, and agent user. Through the [agent identity blueprint](../agent-id/agent-blueprint.md), the agent can create one or more agent identities, and optionally an agent user for each agent identity, which it can use for authentication to Microsoft, third party and line of business applications. Each agent identity and agent user can have distinct access rights.+Historically, AI agents rely upon tools to interact with various applications and other resources. For an assistive agent, the tools might leverage the authenticated identity of the human user they were assisting. Alternatively, tools might each have their own identities in those applications and resources. For example, a tool might have historically used a service principal to authenticate the agent to Microsoft services via Microsoft Graph or Microsoft Azure APIs.++++[Microsoft Entra Agent ID](../agent-id/what-are-agent-identities.md) introduces support for identities for the agents themselves in Microsoft Entra and connected applications, with four new types of object: agent identity blueprint, agent identity blueprint principal, agent identity, and agent user. Through the [agent identity blueprint](../agent-id/agent-blueprint.md), the agent can create one or more agent identities, and optionally an agent user for each agent identity, which it can use for authentication to Microsoft, third party and line of business applications. Each agent identity and agent user can have distinct access rights. The following diagram illustrates the relationship between the new objects in a Microsoft Entra tenant.  -For a multitenant-capable agent, an agent identity blueprint principal can be brought into the tenant with resources so it can create agent identities in that tenant, similar to how a multitenant application can have a service principal in each tenant.+For a multitenant-capable agent, an agent identity blueprint principal created in one tenant can be brought into another tenant, the tenant with resources the agent needs to access, so the agent can create agent identities in that resource tenant, similar to how a multitenant application can have a service principal in each tenant. The following diagram illustrates the relationship of the Microsoft Entra ID objects when the agent blueprint is in a separate tenant than the resource.  -The agent identity and the agent user allow AI agents to take on digital identities within Microsoft Entra. Once agent identities are created, these agent identities are able to be governed using lifecycle and access features. Sponsors can be assigned to agent identities after creation. Sponsors of agent identities are human users accountable for making decisions about its lifecycle and access. For more information about the role of a sponsor of agent identities, see: [Administrative relationships for agent IDs](../agent-id/agent-owners-sponsors-managers.md).+The agent identity and the agent user allow AI agents to take on digital identities within Microsoft Entra. Once agent identities are created, these agent identities are able to be governed using lifecycle and access features. Sponsors can be assigned to agent identities after creation. Sponsors of agent identities are human users accountable for making decisions about its lifecycle and access. For more information about the role of a sponsor of agent identities, see: [Administrative relationships for agent IDs](../agent-id/agent-owners-sponsors-managers.md). Agent users can also be provisioned to applications. ### Agent identities in other Microsoft products and portals @@ -90,6 +96,10 @@ One of the most important parts of governing agent identities is making sure tha To ensure the security and manageability of agent identities for Microsoft customers, Microsoft Entra Agent ID provides a default inactivity policy to all tenants. This policy identifies inactive agent identities, notifies relevant users, and then proceeds to disable the identity if no new activity is detected. For more information, see [Microsoft Entra Agent ID default inactivity policy](agent-default-inactivity-policy.md) and [Entra Agent ID lifecycle policies](agent-lifecycle-policies.md). +## Dynamic permissions (preview)++In addition to agents that are using the Microsoft Entra agent ID platform, Microsoft Entra can also discover the agent non-human identities in an application that have excessive privileges. For more information, see [Detection and remediation of overprivileged agent identities (Preview)](dynamic-permissions-overview.md).+ ## Related content - [Manage agent identities in your organization](/entra/agent-id/manage-agent-identities-organization) - Overview of agent identity management across the full lifecycle. 