entra-agent-user

by github

Create Agent Users in Microsoft Entra ID to enable AI agents to act as digital workers with user identity access. Provisions specialized user identities ( idtyp=user tokens) linked to agent identities, allowing agents to access user-only APIs like Exchange mailboxes, Teams, and org charts Requires a parent agent identity created from an agent identity blueprint; supports 1:1 relationship with optional manager assignment and license provisioning Includes step-by-step HTTP and PowerShell... npx skills add https://github.com/github/awesome-copilot --skill entra-agent-user Download ZIPGitHub36.2k

SKILL: Creating Agent Users in Microsoft Entra Agent ID

Overview

An agent user is a specialized user identity in Microsoft Entra ID that enables AI agents to act as digital workers. It allows agents to access APIs and services that strictly require user identities (e.g., Exchange mailboxes, Teams, org charts), while maintaining appropriate security boundaries.

Agent users receive tokens with idtyp=user, unlike regular agent identities which receive idtyp=app.

Architecture

Agent Identity Blueprint (application template)
 │
 ├── Agent Identity (service principal - ServiceIdentity)
 │ │
 │ └── Agent User (user - agentUser) ← 1:1 relationship
 │
 └── Agent Identity Blueprint Principal (service principal in tenant)

Component Type Token Claim Purpose Agent Identity Service Principal idtyp=app Backend/API operations Agent User User (agentUser) idtyp=user Act as a digital worker in M365

Step 1: Verify the Agent Identity Exists

Before creating an agent user, confirm the agent identity is a proper agentIdentity type:

GET https://graph.microsoft.com/beta/servicePrincipals/{agent-identity-id}
Authorization: Bearer 

Verify the response contains:

{
 "@odata.type": "#microsoft.graph.agentIdentity",
 "servicePrincipalType": "ServiceIdentity",
 "agentIdentityBlueprintId": " "
}

PowerShell

Connect-MgGraph -Scopes "Application.Read.All" -TenantId " " -UseDeviceCode -NoWelcome
Invoke-MgGraphRequest -Method GET `
 -Uri "https://graph.microsoft.com/beta/servicePrincipals/ " | ConvertTo-Json -Depth 3

Common mistake: Using an app registration's appId or a regular application service principal's id will fail. Only agent identities created from blueprints work.

Step 2: Create the Agent User

HTTP Request

POST https://graph.microsoft.com/beta/users/microsoft.graph.agentUser
Content-Type: application/json
Authorization: Bearer 

{
 "accountEnabled": true,
 "displayName": "My Agent User",
 "mailNickname": "my-agent-user",
 "userPrincipalName": "[email protected]",
 "identityParentId": " "
}

Required Properties

Property Type Description accountEnabled Boolean true to enable the account displayName String Human-friendly name mailNickname String Mail alias (no spaces/special chars) userPrincipalName String UPN — must be unique in the tenant (alias@verified-domain) identityParentId String Object ID of the parent agent identity

PowerShell

Connect-MgGraph -Scopes "User.ReadWrite.All" -TenantId " " -UseDeviceCode -NoWelcome

$body = @{
 accountEnabled = $true
 displayName = "My Agent User"
 mailNickname = "my-agent-user"
 userPrincipalName = "[email protected]"
 identityParentId = " "
} | ConvertTo-Json

Invoke-MgGraphRequest -Method POST `
 -Uri "https://graph.microsoft.com/beta/users/microsoft.graph.agentUser" `
 -Body $body -ContentType "application/json" | ConvertTo-Json -Depth 3

Key Notes

• No password — agent users cannot have passwords. They authenticate via their parent agent identity's credentials.

• 1:1 relationship — each agent identity can have at most one agent user. Attempting to create a second returns 400 Bad Request.

• The userPrincipalName must be unique. Don't reuse an existing user's UPN.

Step 3: Assign a Manager (Optional)

Assigning a manager allows the agent user to appear in org charts (e.g., Teams).

PUT https://graph.microsoft.com/beta/users/{agent-user-id}/manager/$ref
Content-Type: application/json
Authorization: Bearer 

{
 "@odata.id": "https://graph.microsoft.com/beta/users/{manager-user-id}"
}

PowerShell

$managerBody = '{"@odata.id":"https://graph.microsoft.com/beta/users/ "}'
Invoke-MgGraphRequest -Method PUT `
 -Uri "https://graph.microsoft.com/beta/users/ /manager/`$ref" `
 -Body $managerBody -ContentType "application/json"

Provisioning Times

Service Estimated Time Exchange mailbox 5–30 minutes Teams availability 15 min – 24 hours Org chart / People search Up to 24–48 hours SharePoint / OneDrive 5–30 minutes Global Address List Up to 24 hours

Agent User Capabilities

• ✅ Added to Microsoft Entra groups (including dynamic groups)

• ✅ Access user-only APIs (idtyp=user tokens)

• ✅ Own a mailbox, calendar, and contacts

• ✅ Participate in Teams chats and channels

• ✅ Appear in org charts and People search

• ✅ Added to administrative units

• ✅ Assigned licenses

Agent User Security Constraints

• ❌ Cannot have passwords, passkeys, or interactive sign-in

• ❌ Cannot be assigned privileged admin roles

• ❌ Cannot be added to role-assignable groups

• ❌ Permissions similar to guest users by default

• ❌ Custom role assignment not available

References

• Agent identities

• Agent users

• Agent service principals

• Create agent identity blueprint

• Create agent identities

• agentUser resource type (Graph API)

• Create agentUser (Graph API)