[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADHH3M4AQ2DM2NDMXEG97T":3,"skill-same:01M6ADHH3M4AQ2DM2NDMXEG97T":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6ADHH3M4AQ2DM2NDMXEG97T","entra-agent-user",null,"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.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fentra-agent-user\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"entra agent user","user","environments","ai agents","with","users","id","as","act","workers","capabilities","create","azure","entra id","identity","create agent","microsoft","2026-11-10 10:12:30",false,"---\nname: entra-agent-user\ndescription: '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.'\n---\n\n# SKILL: Creating Agent Users in Microsoft Entra Agent ID\n\n## Overview\n\nAn **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.\n\nAgent users receive tokens with `idtyp=user`, unlike regular agent identities which receive `idtyp=app`.\n\n---\n\n## Prerequisites\n\n- A **Microsoft Entra tenant** with Agent ID capabilities\n- An **agent identity** (service principal of type `ServiceIdentity`) created from an **agent identity blueprint**\n- One of the following **permissions**:\n  - `AgentIdUser.ReadWrite.IdentityParentedBy` (least privileged)\n  - `AgentIdUser.ReadWrite.All`\n  - `User.ReadWrite.All`\n- The caller must have at minimum the **Agent ID Administrator** role (in delegated scenarios)\n\n> **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`.\n\n---\n\n## Architecture\n\n```\nAgent Identity Blueprint (application template)\n    │\n    ├── Agent Identity (service principal - ServiceIdentity)\n    │       │\n    │       └── Agent User (user - agentUser) ← 1:1 relationship\n    │\n    └── Agent Identity Blueprint Principal (service principal in tenant)\n```\n\n| Component | Type | Token Claim | Purpose |\n|---|---|---|---|\n| Agent Identity | Service Principal | `idtyp=app` | Backend\u002FAPI operations |\n| Agent User | User (`agentUser`) | `idtyp=user` | Act as a digital worker in M365 |\n\n---\n\n## Step 1: Verify the Agent Identity Exists\n\nBefore creating an agent user, confirm the agent identity is a proper `agentIdentity` type:\n\n```http\nGET https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FservicePrincipals\u002F{agent-identity-id}\nAuthorization: Bearer \u003Ctoken>\n```\n\nVerify the response contains:\n```json\n{\n  \"@odata.type\": \"#microsoft.graph.agentIdentity\",\n  \"servicePrincipalType\": \"ServiceIdentity\",\n  \"agentIdentityBlueprintId\": \"\u003Cblueprint-id>\"\n}\n```\n\n### PowerShell\n\n```powershell\nConnect-MgGraph -Scopes \"Application.Read.All\" -TenantId \"\u003Ctenant>\" -UseDeviceCode -NoWelcome\nInvoke-MgGraphRequest -Method GET `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FservicePrincipals\u002F\u003Cagent-identity-id>\" | ConvertTo-Json -Depth 3\n```\n\n> **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.\n\n---\n\n## Step 2: Create the Agent User\n\n### HTTP Request\n\n```http\nPOST https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002Fmicrosoft.graph.agentUser\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"accountEnabled\": true,\n  \"displayName\": \"My Agent User\",\n  \"mailNickname\": \"my-agent-user\",\n  \"userPrincipalName\": \"my-agent-user@yourtenant.onmicrosoft.com\",\n  \"identityParentId\": \"\u003Cagent-identity-object-id>\"\n}\n```\n\n### Required Properties\n\n| Property | Type | Description |\n|---|---|---|\n| `accountEnabled` | Boolean | `true` to enable the account |\n| `displayName` | String | Human-friendly name |\n| `mailNickname` | String | Mail alias (no spaces\u002Fspecial chars) |\n| `userPrincipalName` | String | UPN — must be unique in the tenant (`alias@verified-domain`) |\n| `identityParentId` | String | Object ID of the parent agent identity |\n\n### PowerShell\n\n```powershell\nConnect-MgGraph -Scopes \"User.ReadWrite.All\" -TenantId \"\u003Ctenant>\" -UseDeviceCode -NoWelcome\n\n$body = @{\n  accountEnabled    = $true\n  displayName       = \"My Agent User\"\n  mailNickname      = \"my-agent-user\"\n  userPrincipalName = \"my-agent-user@yourtenant.onmicrosoft.com\"\n  identityParentId  = \"\u003Cagent-identity-object-id>\"\n} | ConvertTo-Json\n\nInvoke-MgGraphRequest -Method POST `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002Fmicrosoft.graph.agentUser\" `\n  -Body $body -ContentType \"application\u002Fjson\" | ConvertTo-Json -Depth 3\n```\n\n### Key Notes\n\n- **No password** — agent users cannot have passwords. They authenticate via their parent agent identity's credentials.\n- **1:1 relationship** — each agent identity can have at most one agent user. Attempting to create a second returns `400 Bad Request`.\n- The `userPrincipalName` must be unique. Don't reuse an existing user's UPN.\n\n---\n\n## Step 3: Assign a Manager (Optional)\n\nAssigning a manager allows the agent user to appear in org charts (e.g., Teams).\n\n```http\nPUT https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\u002Fmanager\u002F$ref\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"@odata.id\": \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{manager-user-id}\"\n}\n```\n\n### PowerShell\n\n```powershell\n$managerBody = '{\"@odata.id\":\"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cmanager-user-id>\"}'\nInvoke-MgGraphRequest -Method PUT `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\u002Fmanager\u002F`$ref\" `\n  -Body $managerBody -ContentType \"application\u002Fjson\"\n```\n\n---\n\n## Step 4: Set Usage Location and Assign Licenses (Optional)\n\nA license is needed for the agent user to have a mailbox, Teams presence, etc. Usage location must be set first.\n\n### Set Usage Location\n\n```http\nPATCH https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"usageLocation\": \"US\"\n}\n```\n\n### List Available Licenses\n\n```http\nGET https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FsubscribedSkus?$select=skuPartNumber,skuId,consumedUnits,prepaidUnits\nAuthorization: Bearer \u003Ctoken>\n```\n\nRequires `Organization.Read.All` permission.\n\n### Assign a License\n\n```http\nPOST https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\u002FassignLicense\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"addLicenses\": [\n    { \"skuId\": \"\u003Csku-id>\" }\n  ],\n  \"removeLicenses\": []\n}\n```\n\n### PowerShell (all in one)\n\n```powershell\nConnect-MgGraph -Scopes \"User.ReadWrite.All\",\"Organization.Read.All\" -TenantId \"\u003Ctenant>\" -NoWelcome\n\n# Set usage location\nInvoke-MgGraphRequest -Method PATCH `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\" `\n  -Body '{\"usageLocation\":\"US\"}' -ContentType \"application\u002Fjson\"\n\n# Assign license\n$licenseBody = '{\"addLicenses\":[{\"skuId\":\"\u003Csku-id>\"}],\"removeLicenses\":[]}'\nInvoke-MgGraphRequest -Method POST `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\u002FassignLicense\" `\n  -Body $licenseBody -ContentType \"application\u002Fjson\"\n```\n\n> **Tip:** You can also assign licenses via the **Entra admin center** under Identity → Users → All users → select the agent user → Licenses and apps.\n\n---\n\n## Provisioning Times\n\n| Service | Estimated Time |\n|---|---|\n| Exchange mailbox | 5–30 minutes |\n| Teams availability | 15 min – 24 hours |\n| Org chart \u002F People search | Up to 24–48 hours |\n| SharePoint \u002F OneDrive | 5–30 minutes |\n| Global Address List | Up to 24 hours |\n\n---\n\n## Agent User Capabilities\n\n- ✅ Added to Microsoft Entra groups (including dynamic groups)\n- ✅ Access user-only APIs (`idtyp=user` tokens)\n- ✅ Own a mailbox, calendar, and contacts\n- ✅ Participate in Teams chats and channels\n- ✅ Appear in org charts and People search\n- ✅ Added to administrative units\n- ✅ Assigned licenses\n\n## Agent User Security Constraints\n\n- ❌ Cannot have passwords, passkeys, or interactive sign-in\n- ❌ Cannot be assigned privileged admin roles\n- ❌ Cannot be added to role-assignable groups\n- ❌ Permissions similar to guest users by default\n- ❌ Custom role assignment not available\n\n---\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `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 |\n| `400 Bad Request` (identityParentId already linked) | The agent identity already has an agent user | Each agent identity supports only one agent user |\n| `409 Conflict` on UPN | The `userPrincipalName` is already taken | Use a unique UPN |\n| License assignment fails | Usage location not set | Set `usageLocation` before assigning licenses |\n\n---\n\n## References\n\n- [Agent identities](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-identities)\n- [Agent users](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-users)\n- [Agent service principals](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-service-principals)\n- [Create agent identity blueprint](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fcreate-blueprint)\n- [Create agent identities](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fcreate-delete-agent-identities)\n- [agentUser resource type (Graph API)](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fagentuser?view=graph-rest-beta)\n- [Create agentUser (Graph API)](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fagentuser-post?view=graph-rest-beta)\n","# SKILL: Creating Agent Users in Microsoft Entra Agent ID\n\n## Overview\n\nAn **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.\n\nAgent users receive tokens with `idtyp=user`, unlike regular agent identities which receive `idtyp=app`.\n\n---\n\n## Prerequisites\n\n- A **Microsoft Entra tenant** with Agent ID capabilities\n- An **agent identity** (service principal of type `ServiceIdentity`) created from an **agent identity blueprint**\n- One of the following **permissions**:\n  - `AgentIdUser.ReadWrite.IdentityParentedBy` (least privileged)\n  - `AgentIdUser.ReadWrite.All`\n  - `User.ReadWrite.All`\n- The caller must have at minimum the **Agent ID Administrator** role (in delegated scenarios)\n\n> **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`.\n\n---\n\n## Architecture\n\n```\nAgent Identity Blueprint (application template)\n    │\n    ├── Agent Identity (service principal - ServiceIdentity)\n    │       │\n    │       └── Agent User (user - agentUser) ← 1:1 relationship\n    │\n    └── Agent Identity Blueprint Principal (service principal in tenant)\n```\n\n| Component | Type | Token Claim | Purpose |\n|---|---|---|---|\n| Agent Identity | Service Principal | `idtyp=app` | Backend\u002FAPI operations |\n| Agent User | User (`agentUser`) | `idtyp=user` | Act as a digital worker in M365 |\n\n---\n\n## Step 1: Verify the Agent Identity Exists\n\nBefore creating an agent user, confirm the agent identity is a proper `agentIdentity` type:\n\n```http\nGET https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FservicePrincipals\u002F{agent-identity-id}\nAuthorization: Bearer \u003Ctoken>\n```\n\nVerify the response contains:\n```json\n{\n  \"@odata.type\": \"#microsoft.graph.agentIdentity\",\n  \"servicePrincipalType\": \"ServiceIdentity\",\n  \"agentIdentityBlueprintId\": \"\u003Cblueprint-id>\"\n}\n```\n\n### PowerShell\n\n```powershell\nConnect-MgGraph -Scopes \"Application.Read.All\" -TenantId \"\u003Ctenant>\" -UseDeviceCode -NoWelcome\nInvoke-MgGraphRequest -Method GET `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FservicePrincipals\u002F\u003Cagent-identity-id>\" | ConvertTo-Json -Depth 3\n```\n\n> **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.\n\n---\n\n## Step 2: Create the Agent User\n\n### HTTP Request\n\n```http\nPOST https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002Fmicrosoft.graph.agentUser\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"accountEnabled\": true,\n  \"displayName\": \"My Agent User\",\n  \"mailNickname\": \"my-agent-user\",\n  \"userPrincipalName\": \"my-agent-user@yourtenant.onmicrosoft.com\",\n  \"identityParentId\": \"\u003Cagent-identity-object-id>\"\n}\n```\n\n### Required Properties\n\n| Property | Type | Description |\n|---|---|---|\n| `accountEnabled` | Boolean | `true` to enable the account |\n| `displayName` | String | Human-friendly name |\n| `mailNickname` | String | Mail alias (no spaces\u002Fspecial chars) |\n| `userPrincipalName` | String | UPN — must be unique in the tenant (`alias@verified-domain`) |\n| `identityParentId` | String | Object ID of the parent agent identity |\n\n### PowerShell\n\n```powershell\nConnect-MgGraph -Scopes \"User.ReadWrite.All\" -TenantId \"\u003Ctenant>\" -UseDeviceCode -NoWelcome\n\n$body = @{\n  accountEnabled    = $true\n  displayName       = \"My Agent User\"\n  mailNickname      = \"my-agent-user\"\n  userPrincipalName = \"my-agent-user@yourtenant.onmicrosoft.com\"\n  identityParentId  = \"\u003Cagent-identity-object-id>\"\n} | ConvertTo-Json\n\nInvoke-MgGraphRequest -Method POST `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002Fmicrosoft.graph.agentUser\" `\n  -Body $body -ContentType \"application\u002Fjson\" | ConvertTo-Json -Depth 3\n```\n\n### Key Notes\n\n- **No password** — agent users cannot have passwords. They authenticate via their parent agent identity's credentials.\n- **1:1 relationship** — each agent identity can have at most one agent user. Attempting to create a second returns `400 Bad Request`.\n- The `userPrincipalName` must be unique. Don't reuse an existing user's UPN.\n\n---\n\n## Step 3: Assign a Manager (Optional)\n\nAssigning a manager allows the agent user to appear in org charts (e.g., Teams).\n\n```http\nPUT https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\u002Fmanager\u002F$ref\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"@odata.id\": \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{manager-user-id}\"\n}\n```\n\n### PowerShell\n\n```powershell\n$managerBody = '{\"@odata.id\":\"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cmanager-user-id>\"}'\nInvoke-MgGraphRequest -Method PUT `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\u002Fmanager\u002F`$ref\" `\n  -Body $managerBody -ContentType \"application\u002Fjson\"\n```\n\n---\n\n## Step 4: Set Usage Location and Assign Licenses (Optional)\n\nA license is needed for the agent user to have a mailbox, Teams presence, etc. Usage location must be set first.\n\n### Set Usage Location\n\n```http\nPATCH https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"usageLocation\": \"US\"\n}\n```\n\n### List Available Licenses\n\n```http\nGET https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002FsubscribedSkus?$select=skuPartNumber,skuId,consumedUnits,prepaidUnits\nAuthorization: Bearer \u003Ctoken>\n```\n\nRequires `Organization.Read.All` permission.\n\n### Assign a License\n\n```http\nPOST https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F{agent-user-id}\u002FassignLicense\nContent-Type: application\u002Fjson\nAuthorization: Bearer \u003Ctoken>\n\n{\n  \"addLicenses\": [\n    { \"skuId\": \"\u003Csku-id>\" }\n  ],\n  \"removeLicenses\": []\n}\n```\n\n### PowerShell (all in one)\n\n```powershell\nConnect-MgGraph -Scopes \"User.ReadWrite.All\",\"Organization.Read.All\" -TenantId \"\u003Ctenant>\" -NoWelcome\n\n# Set usage location\nInvoke-MgGraphRequest -Method PATCH `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\" `\n  -Body '{\"usageLocation\":\"US\"}' -ContentType \"application\u002Fjson\"\n\n# Assign license\n$licenseBody = '{\"addLicenses\":[{\"skuId\":\"\u003Csku-id>\"}],\"removeLicenses\":[]}'\nInvoke-MgGraphRequest -Method POST `\n  -Uri \"https:\u002F\u002Fgraph.microsoft.com\u002Fbeta\u002Fusers\u002F\u003Cagent-user-id>\u002FassignLicense\" `\n  -Body $licenseBody -ContentType \"application\u002Fjson\"\n```\n\n> **Tip:** You can also assign licenses via the **Entra admin center** under Identity → Users → All users → select the agent user → Licenses and apps.\n\n---\n\n## Provisioning Times\n\n| Service | Estimated Time |\n|---|---|\n| Exchange mailbox | 5–30 minutes |\n| Teams availability | 15 min – 24 hours |\n| Org chart \u002F People search | Up to 24–48 hours |\n| SharePoint \u002F OneDrive | 5–30 minutes |\n| Global Address List | Up to 24 hours |\n\n---\n\n## Agent User Capabilities\n\n- ✅ Added to Microsoft Entra groups (including dynamic groups)\n- ✅ Access user-only APIs (`idtyp=user` tokens)\n- ✅ Own a mailbox, calendar, and contacts\n- ✅ Participate in Teams chats and channels\n- ✅ Appear in org charts and People search\n- ✅ Added to administrative units\n- ✅ Assigned licenses\n\n## Agent User Security Constraints\n\n- ❌ Cannot have passwords, passkeys, or interactive sign-in\n- ❌ Cannot be assigned privileged admin roles\n- ❌ Cannot be added to role-assignable groups\n- ❌ Permissions similar to guest users by default\n- ❌ Custom role assignment not available\n\n---\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `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 |\n| `400 Bad Request` (identityParentId already linked) | The agent identity already has an agent user | Each agent identity supports only one agent user |\n| `409 Conflict` on UPN | The `userPrincipalName` is already taken | Use a unique UPN |\n| License assignment fails | Usage location not set | Set `usageLocation` before assigning licenses |\n\n---\n\n## References\n\n- [Agent identities](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-identities)\n- [Agent users](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-users)\n- [Agent service principals](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fagent-service-principals)\n- [Create agent identity blueprint](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fcreate-blueprint)\n- [Create agent identities](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fagent-id\u002Fidentity-platform\u002Fcreate-delete-agent-identities)\n- [agentUser resource type (Graph API)](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fagentuser?view=graph-rest-beta)\n- [Create agentUser (Graph API)](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fagentuser-post?view=graph-rest-beta)\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fentra-agent-user",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add github\u002Fawesome-copilot --skill entra-agent-user",{"tool":62,"command":63},"bunx","bunx skills add github\u002Fawesome-copilot --skill entra-agent-user",{"tool":65,"command":66},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill entra-agent-user","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fentra-agent-user\u002FSKILL.md",true,[],[71,99,127,156,189,205],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":81,"publishedAt":41},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87,88,89,90,91,92,93,94,31,95,96,97,29,98,28],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","tests","prove","use","functions",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":41},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[105],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":139,"publishedAt":41},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[140,141,142,143,144,145,113,86,146,147,148,36,149,150,151,97,152,153,154,155],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":167,"publishedAt":41},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[163,166],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},[168,169,170,171,172,173,174,175,176,177,178,34,179,180,181,87,182,183,184,185,186,113,187,188],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":202,"publishedAt":41},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[197,198,201],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[203,110,177,204,38],"resemble detect","https",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":193,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":41},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[217,218,219,220,141,88,9,109,221,222,204,223,224,225,226,227,228,229,230,231,232,233,95,234,235,236,237],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]