跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 entra-agent-user

Entra Agent User

从代理身份(Agent Identities)中创建出Microsoft Entra ID中的代理用户,使AI代理能够在Microsoft 365和Azure环境中担任具有用户身份能力的数字工人.

8667 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

从代理身份(Agent Identities)中创建出Microsoft Entra ID中的代理用户,使AI代理能够在Microsoft 365和Azure环境中担任具有用户身份能力的数字工人.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:SKILL: Creating Agent Users in Microsoft Entra Agent ID、Overview、Prerequisites、Architecture、Step 1: Verify the Agent Identity Exists、PowerShell。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

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.

SKILL: Creating Agent Users in Microsoft Entra Agent IDOverviewPrerequisitesArchitectureStep 1: Verify the Agent Identity ExistsPowerShellStep 2: Create the Agent UserHTTP RequestRequired PropertiesPowerShellKey NotesStep 3: Assign a Manager (Optional)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
entra-agent-user
description
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.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「entra-agent-user」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-dd3fe542ea0c7421-Entra-%E4%BB%A3%E7%90%86%E7%94%A8%E6%88%B7.html
请存为 .cursor/skills/entra-agent-user/SKILL.md 或 .claude/skills/entra-agent-user/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/github/awesome-copilot' --list

npx skills add 'https://github.com/github/awesome-copilot' --skill 'entra-agent-user'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: entra-agent-user description: '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.' --- # 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: ```http GET https://graph.microsoft.com/beta/servicePrincipals/{agent-identity-id} Authorization: Bearer ``` Verify the response contains: ```json { "@odata.type": "#microsoft.graph.agentIdentity", "servicePrincipalType": "ServiceIdentity", "agentIdentityBlueprintId": "" } ``` ### PowerShell ```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 ```http 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 ```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). ```http 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 ```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" ``` --- ## 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 ```http PATCH https://graph.microsoft.com/beta/users/{agent-user-id} Content-Type: application/json Authorization: Bearer { "usageLocation": "US" } ``` ### List Available Licenses ```http GET https://graph.microsoft.com/beta/subscribedSkus?$select=skuPartNumber,skuId,consumedUnits,prepaidUnits Authorization: Bearer ``` Requires `Organization.Read.All` permission. ### Assign a License ```http POST https://graph.microsoft.com/beta/users/{agent-user-id}/assignLicense Content-Type: application/json Authorization: Bearer { "addLicenses": [ { "skuId": "" } ], "removeLicenses": [] } ``` ### PowerShell (all in one) ```powershell Connect-MgGraph -Scopes "User.ReadWrite.All","Organization.Read.All" -TenantId "" -NoWelcome # Set usage location Invoke-MgGraphRequest -Method PATCH ` -Uri "https://graph.microsoft.com/beta/users/" ` -Body '{"usageLocation":"US"}' -ContentType "application/json" # Assign license $licenseBody = '{"addLicenses":[{"skuId":""}],"removeLicenses":[]}' Invoke-MgGraphRequest -Method POST ` -Uri "https://graph.microsoft.com/beta/users//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 - [Agent identities](https://learn.microsoft.com/en-us/entra/agent-id/identity-platform/agent-identities) - [Agent users](https://learn.microsoft.com/en-us/entra/agent-id/identity-platform/agent-users) - [Agent service principals](https://learn.microsoft.com/en-us/entra/agent-id/identity-platform/agent-service-principals) - [Create agent identity blueprint](https://learn.microsoft.com/en-us/entra/agent-id/identity-platform/create-blueprint) - [Create agent identities](https://learn.microsoft.com/en-us/entra/agent-id/identity-platform/create-delete-agent-identities) - [agentUser resource type (Graph API)](https://learn.microsoft.com/en-us/graph/api/resources/agentuser?view=graph-rest-beta) - [Create agentUser (Graph API)](https://learn.microsoft.com/en-us/graph/api/agentuser-post?view=graph-rest-beta)

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…