entrabot: Skill for Claude Code

Implementing Microsoft Entra Agent ID

Read these repository sources before changing identity or token code:

• docs/platform-docs/agent-id-blueprints-and-users.md
• docs/platform-docs/entra-agent-users.md
• docs/platform-docs/delegated-auth.md
• docs/reference/token-flows.md
• engineering-history/research/hard-won-learnings.md

Microsoft Entra Agent ID and Microsoft Agent 365 reached GA on 2026-05-01, but not every related API is on Microsoft Graph v1.0. Use the endpoint version documented for each object rather than treating the whole surface as beta or stable.

Object model

Agent Identity Blueprint (application)
  └─ AgentIdentityBlueprintPrincipal (service principal; create explicitly)
      ├─ Agent Identity (service principal)
      └─ Agent Identity (service principal)
           └─ Agent User (user; linked through user_fic)

An Agent Identity is a service principal, not a user. Do not create a password-backed fake user to represent an agent.

Non-negotiable constraints

Use a dedicated provisioner identity

Azure CLI user tokens contain Directory.AccessAsUser.All; Agent Identity APIs reject those tokens with a hard 403. Use Azure CLI only to bootstrap the dedicated provisioner app and identify the signed-in sponsor.

The provisioner authenticates with a certificate credential. Keep the private key in the OS credential store and purge legacy password credentials. Entrabot implements this in:

• scripts/entra_provisioning.py
• scripts/create_entra_agent_ids.py

Do not add a client secret fallback.

Parse Azure CLI output as JSON

CLI warnings can corrupt TSV output. Request JSON and parse the id field:

result = subprocess.run(
    ["az", "ad", "signed-in-user", "show", "-o", "json"],
    check=True,
    capture_output=True,
    text=True,
)
user_id = json.loads(result.stdout)["id"]

Sponsors are user references

Blueprint and Agent Identity creation require at least one sponsor. Bind a Microsoft Graph v1.0 user reference: