Learn about the agent's user account in Microsoft Entra Agent ID
In brief
The article now explains when an agent needs an optional user account, clarifies its relationship to the parent agent identity, and distinguishes it from the human who signs in. It also updates credential guidance for blueprints and agent users.
What Entra admins need to know
Administrators can use the revised guidance to choose between an agent user account and delegated access, and to avoid assigning credentials directly to the agent user.
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.
title: Learn about the agent's user account in Microsoft Entra Agent ID
description: This article explains the concept of theLearn when an agent's needs its own user account, how it functions within Microsoft Entra ID,the account relates to its parent agent identity, and its relationship with agent identities.which authentication and access restrictions apply.
titleSuffix: Microsoft Entra Agent ID
ms.date: 11/04/202506/2026
ai-usage: ai-assisted
ms.topic: concept-article
#customer intent: As a developer or IT administrator, I want to understand the agent's user account and its capabilities so that I can determine when to create it and how to manage agents that need to act as digital workers in my organization.
The agent's user account in Microsoft Entra Agent ID
TheCreate an agent's user account isonly when the agent needs its own user identity to access a specialized identity type designedresource. This optional account belongs to bridgea parent agent identity; it isn't the gap between agents and human user capabilities. Thewho signs in to an agent. If your agent's user account enables AI-powered applications to interact with systems and services that require user identities, while maintaining appropriate security boundaries and management controls. It allows organizations to manage the agent's access using similar capabilities as they do for human users. instead calls an API on behalf of a signed-in human, use user-delegated access.
Example of agent's user account scenarios
Sometimes it's not enough for an agent to perform tasks on behalf of a user or operate as an autonomous application. In certain scenarios, an agent needs to act as a user, functioning essentially as a digital worker. The following are example scenarios where the agent's user account would be applicable:
- The organization needs long-term digital employees that function as team members with mailboxes, chat access, and inclusion in HR systems.
- The agent needs to access APIs or resources that are only available to user
identitiesidentities. - The agent needs to participate in collaborative workflows as a team
membermember.
For these reasons, the agent's user account is created. The agent's user account is optional and should only be created for interactions where the agent needs to act as a user or access resources restricted to user accounts.
The authentication model for the agent's user account differs significantly from human-user accounts:
Federated identityBlueprint credentials:Authentication happensThe blueprint authenticates with its configured credential, such as a federated identity credential. The associated agent identity then obtains tokens for its dedicated agent user throughcredentials assignedtheir parent relationship. Don't assign a federated credential, password, or certificate directly to the agent's user account.In production systems, use Federated Identity Credentials (FIC). These credentials are used for authenticating bothFor theagent identity blueprint and the agent identity. The credential assigned to the user is used for authenticating across the agent ecosystem.exchange, see Agent user OAuth flow.Restricted credential model: The agent's user account doesn't have regular credentials like passwords. Instead, it's restricted to using the credentials provided through its parent relationship. This restriction on credentials, along with restrictions on interactive sign-in, ensures that the agent's user account can't be used like a standard user account.
@@ -1,8 +1,9 @@ --- title: Learn about the agent's user account in Microsoft Entra Agent ID-description: This article explains the concept of the agent's user account, how it functions within Microsoft Entra ID, and its relationship with agent identities.+description: Learn when an agent needs its own user account, how the account relates to its parent agent identity, and which authentication and access restrictions apply. titleSuffix: Microsoft Entra Agent ID-ms.date: 11/04/2025+ms.date: 11/06/2026+ai-usage: ai-assisted ms.topic: concept-article #customer intent: As a developer or IT administrator, I want to understand the agent's user account and its capabilities so that I can determine when to create it and how to manage agents that need to act as digital workers in my organization.@@ -11,15 +12,15 @@ ms.reviewer: yukarppa # The agent's user account in Microsoft Entra Agent ID -The agent's user account is a specialized identity type designed to bridge the gap between agents and human user capabilities. The agent's user account enables AI-powered applications to interact with systems and services that require user identities, while maintaining appropriate security boundaries and management controls. It allows organizations to manage the agent's access using similar capabilities as they do for human users.+Create an agent's user account only when the agent needs its own user identity to access a resource. This optional account belongs to a parent agent identity; it isn't the human user who signs in to an agent. If your agent instead calls an API on behalf of a signed-in human, use [user-delegated access](aspnet-core-call-custom-api-as-user.md). ## Example of agent's user account scenarios Sometimes it's not enough for an agent to perform tasks on behalf of a user or operate as an autonomous application. In certain scenarios, an agent needs to act as a user, functioning essentially as a digital worker. The following are example scenarios where the agent's user account would be applicable: -- The organization needs long-term digital employees that function as team members with mailboxes, chat access, and inclusion in HR systems.-- The agent needs to access APIs or resources that are only available to user identities-- The agent needs to participate in collaborative workflows as a team member+- The organization needs long-term digital employees that function as team members with mailboxes, chat access, and inclusion in HR systems.+- The agent needs to access APIs or resources that are only available to user identities.+- The agent needs to participate in collaborative workflows as a team member. For these reasons, the agent's user account is created. The agent's user account is optional and should only be created for interactions where the agent needs to act as a user or access resources restricted to user accounts. @@ -50,7 +51,7 @@ Admins manage the lifecycle of an agent's user account. An admin user can delete The authentication model for the agent's user account differs significantly from human-user accounts: -- **Federated identity credentials**: Authentication happens through credentials assigned to the agent's user account. In production systems, use Federated Identity Credentials (FIC). These credentials are used for authenticating both the agent identity blueprint and the agent identity. The credential assigned to the user is used for authenticating across the agent ecosystem.+- **Blueprint credentials**: The blueprint authenticates with its configured credential, such as a federated identity credential. The associated agent identity then obtains tokens for its dedicated agent user through their parent relationship. Don't assign a federated credential, password, or certificate directly to the agent's user account. For the exchange, see [Agent user OAuth flow](agent-user-oauth-flow.md). - **Restricted credential model**: The agent's user account doesn't have regular credentials like passwords. Instead, it's restricted to using the credentials provided through its parent relationship. This restriction on credentials, along with restrictions on interactive sign-in, ensures that the agent's user account can't be used like a standard user account. 