Entra Agent User — Agent Skill by GitHub

From the author

Create Agent Users in Microsoft Entra ID from Agent Identities, enabling AI agents to act as digital workers with user identity capabilities in Microsoft 365 and Azure environments.

— the description by fizamusthafa

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a guide for creating Agent Users in Microsoft Entra ID. By linking an agent identity to a specialized user object, AI agents can obtain user-level identity tokens (idtyp=user), allowing them to interact with Microsoft 365 services like Teams, Exchange, and org charts that typically require a user identity. The guide covers the full lifecycle, including verification of agent identities, creation of the agent user, and optional configuration such as manager assignment and license provisioning.

What it does

Verifies existing agent identities for compatibility.
Creates agent user objects in Microsoft Entra ID.
Assigns managers to agent users for organizational hierarchy visibility.
Configures usage locations and assigns licenses for M365 service access.
Provides troubleshooting steps for common provisioning and configuration errors.

When to use it

When an AI agent needs to access Microsoft 365 services that require a user-level identity.
When you need an agent to participate in Teams chats or appear in organizational charts.
When you need to assign specific licenses to an agent to enable mailbox or SharePoint features.
When managing digital worker identities within an enterprise Microsoft Entra environment.

Advantages

Enables agents to function as digital workers with standard user capabilities.
Maintains security boundaries by using specialized agent user identities.
Provides a clear 1:1 relationship between agent identities and agent users.
Supports standard Microsoft Graph API workflows for identity management.

Usage examples

“How do I create an agent user for my existing agent identity?”: The agent provides the specific POST request structure for the Microsoft Graph API, including the required identityParentId and user properties.
“Why is my agent user not appearing in the org chart?”: The agent explains the steps to assign a manager using the PUT method on the manager/$ref endpoint and notes the 24-48 hour propagation time.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/entra-agent-user/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip entra-agent-user.zip -d .agents/skills

Documentation by fizamusthafa

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.

Prerequisites

A Microsoft Entra tenant with Agent ID capabilities
An agent identity (service principal of type ServiceIdentity) created from an agent identity blueprint
One of the following permissions:
- AgentIdUser.ReadWrite.IdentityParentedBy (least privileged)
- AgentIdUser.ReadWrite.All
- User.ReadWrite.All
The caller must have at minimum the Agent ID Administrator role (in delegated scenarios)

Important: The identityParentId must reference a true agent identity (created via an agent identity blueprint), NOT a regular application service principal. You can verify by checking that the service principal has @odata.type: #microsoft.graph.agentIdentity and servicePrincipalType: ServiceIdentity.

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 <token>

Verify the response contains:

{
  "@odata.type": "#microsoft.graph.agentIdentity",
  "servicePrincipalType": "ServiceIdentity",
  "agentIdentityBlueprintId": "<blueprint-id>"
}

PowerShell

Connect-MgGraph -Scopes "Application.Read.All" -TenantId "<tenant>" -UseDeviceCode -NoWelcome
Invoke-MgGraphRequest -Method GET `
  -Uri "https://graph.microsoft.com/beta/servicePrincipals/<agent-identity-id>" | 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 <token>

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

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 "<tenant>" -UseDeviceCode -NoWelcome

$body = @{
  accountEnabled    = $true
  displayName       = "My Agent User"
  mailNickname      = "my-agent-user"
  userPrincipalName = "[email protected]"
  identityParentId  = "<agent-identity-object-id>"
} | 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 <token>

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

PowerShell

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

Step 4: Set Usage Location and Assign Licenses (Optional)

A license is needed for the agent user to have a mailbox, Teams presence, etc. Usage location must be set first.

Set Usage Location

PATCH https://graph.microsoft.com/beta/users/{agent-user-id}
Content-Type: application/json
Authorization: Bearer <token>

{
  "usageLocation": "US"
}

List Available Licenses

GET https://graph.microsoft.com/beta/subscribedSkus?$select=skuPartNumber,skuId,consumedUnits,prepaidUnits
Authorization: Bearer <token>

Requires Organization.Read.All permission.

Assign a License

POST https://graph.microsoft.com/beta/users/{agent-user-id}/assignLicense
Content-Type: application/json
Authorization: Bearer <token>

{
  "addLicenses": [
    { "skuId": "<sku-id>" }
  ],
  "removeLicenses": []
}

PowerShell (all in one)

Connect-MgGraph -Scopes "User.ReadWrite.All","Organization.Read.All" -TenantId "<tenant>" -NoWelcome

# Set usage location
Invoke-MgGraphRequest -Method PATCH `
  -Uri "https://graph.microsoft.com/beta/users/<agent-user-id>" `
  -Body '{"usageLocation":"US"}' -ContentType "application/json"

# Assign license
$licenseBody = '{"addLicenses":[{"skuId":"<sku-id>"}],"removeLicenses":[]}'
Invoke-MgGraphRequest -Method POST `
  -Uri "https://graph.microsoft.com/beta/users/<agent-user-id>/assignLicense" `
  -Body $licenseBody -ContentType "application/json"

Tip: You can also assign licenses via the Entra admin center under Identity → Users → All users → select the agent user → Licenses and apps.

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

Troubleshooting

Error	Cause	Fix
`Agent user IdentityParent does not exist`	`identityParentId` points to a non-existent or non-agent-identity object	Verify the ID is an `agentIdentity` service principal, not a regular app
`400 Bad Request` (identityParentId already linked)	The agent identity already has an agent user	Each agent identity supports only one agent user
`409 Conflict` on UPN	The `userPrincipalName` is already taken	Use a unique UPN
License assignment fails	Usage location not set	Set `usageLocation` before assigning licenses

References

Files

ATTRIBUTION.mdAdded by AutoGineer945 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md9.1 KiB

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Auth Implementation Patterns
Seth Hobson· Community
Master industry-standard authentication and authorization patterns for secure, scalable access control.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Iam Helper For Privileged Access Management
GoogleOfficial
Manage Google Cloud Privileged Access Manager (PAM) entitlements and access grants.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0Low riskHas scriptsGitHub stars of the source repository23.2k
Iam Helper For Policy Management
GoogleOfficial
Manage Google Cloud IAM allow and deny policies with a structured, safety-first workflow.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository23.2k
Dpop Adoption
GoogleOfficial
Implement OAuth 2.0 DPoP (RFC 9449) for secure, sender-constrained token exchanges with Google's OAuth platform.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0Low riskGitHub stars of the source repository23.2k
Entra Agent Id
MicrosoftOfficial
Manage OAuth2-capable AI agent identities using the Microsoft Entra Agent ID preview via Microsoft Graph.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository3.2k
Entra Agent Id
MicrosoftOfficial
Manage Microsoft Entra Agent Identity blueprints and per-instance identities for AI agents using Microsoft Graph.
SecurityClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository3.2k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download entra-agent-user.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by fizamusthafa

SKILL: Creating Agent Users in Microsoft Entra Agent ID

Overview

Prerequisites

Architecture

Step 1: Verify the Agent Identity Exists

PowerShell

Step 2: Create the Agent User

HTTP Request

Required Properties

PowerShell

Key Notes

Step 3: Assign a Manager (Optional)

PowerShell

Step 4: Set Usage Location and Assign Licenses (Optional)

Set Usage Location

List Available Licenses

Assign a License

PowerShell (all in one)

Provisioning Times

Agent User Capabilities

Agent User Security Constraints

Troubleshooting

References

Files

Requirements and compatibility

Security

Attribution and licence

Related skills

Auth Implementation Patterns

Iam Helper For Privileged Access Management

Iam Helper For Policy Management

Dpop Adoption

Entra Agent Id

Entra Agent Id

Download ZIP