AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

entra-agent-id

Microsoft Entra Agent ID (preview) for creating OAuth2-capable AI agent identities via Microsoft Graph beta API. Covers Agent Identity Blueprints, BlueprintPrincipals, Agent Identities, required permissions, sponsors, and Workload Identity Federation. Includes Microsoft Entra SDK for AgentID (containerized sidecar) for polyglot agent authentication (Docker/Kubernetes), 3P agent integration, autonomous and interactive agent patterns. Triggers: "agent identity", "agent id", "Agent Identity Blueprint", "BlueprintPrincipal", "entra agent", "agent identity provisioning", "Graph agent identity", "entra sidecar", "agent id sidecar", "auth sidecar", "3P agent", "third-party agent identity", "polyglot agent auth".

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--entra-agent-id-2 at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 4

references/known-limitations.md

Known Limitations (Preview)

Source: Microsoft Entra Agent ID preview: Known issues and gaps

API & Object Model

  1. Preview API only — all endpoints are under /beta, not /v1.0
  2. Sponsors must be Users — ServicePrincipals and Groups are not accepted as sponsors
  3. BlueprintPrincipal not auto-created — requires explicit POST /servicePrincipals after Blueprint creation
  4. Agent Identities cannot have password credentials — credentials belong on the Blueprint only (PropertyNotCompatibleWithAgentIdentity error)
  5. Agent Identities have no backing application object — they are service-principal-only entities
  6. Blueprint needs explicit identifierUris — not set by default, required for OAuth2 scope resolution (api://{app-id}/.default)
  7. No Graph relationship filtering for Agent IDs — /ownedObjects, /deletedItems, /owners etc. return all types; must client-side filter by odata.type
  8. Orphaned agent users after deletion — deleting a blueprint or identity does NOT auto-delete its agent users; clean up manually via admin center or Graph API

Roles & Permissions

  1. Directory.AccessAsUser.All hard rejection — if present on the client, all other Agent ID delegated permissions are ignored → 403 Forbidden
  2. No viable delegated permission for creating agent identities — must use application permissions
  3. No quick-start permission bundle — must discover and grant 18+ individual Agent Identity permissions
  4. Permission propagation delay — 30–120+ seconds after admin consent before tokens include new claims; use delegated permissions where possible and add retry with exponential backoff
  5. Global Reader cannot list agent identities — GET /servicePrincipals/graph.agentIdentity returns 403; use GET /servicePrincipals instead
  6. Custom roles cannot include Agent ID actions — use built-in roles (Agent ID Administrator, Agent ID Developer)
  7. Administrative units not supported — cannot add agent identities, blueprints, or blueprint principals to admin units; use owners property instead
  8. Agent ID Admin cannot update agent user photos — use User Administrator role

Admin Center & Management

  1. No blueprint management in Entra admin center — must use Microsoft Graph APIs / PowerShell to create and edit blueprints
  2. /me endpoint unavailable in client_credentials flow — use az ad signed-in-user show or Graph delegated permissions for user context

Authentication & Consent

  1. No SSO to web apps — Agent IDs cannot sign in via Microsoft Entra ID sign-in pages (no OpenID Connect or SAML); use web APIs instead
  2. Admin consent workflow (ACW) broken — does not work properly for permissions requested by Agent IDs; contact tenant admin directly
  3. Cannot grant app permissions to blueprint principals — grant application permissions to individual agent identities instead
  4. Cannot assign app roles where target resource is an agent identity — use blueprint principal as the target resource
  5. Risk-based step-up blocks consent silently — no "risky" indication in the UX

Groups, Logs & Monitoring

  1. No dynamic group membership — agent identities and agent users cannot be added to dynamic groups; use security groups with fixed membership
  2. Audit logs do not distinguish Agent IDs — operations on blueprints/identities logged as ApplicationManagement, agent users as User Management; cross-reference object IDs via Graph to determine entity type
  3. Graph activity logs do not distinguish Agent IDs — agent identity requests logged as applications, agent user requests as users; join with sign-in logs

Performance & Scale

  1. Sequential creation requests may fail — creating multiple entities in quick succession (e.g., blueprint → principal → identity) can return 400 Bad Request: Object with id {id} not found; especially with application permissions. Use delegated permissions where possible and add exponential backoff retry.

Product Integrations

  1. Copilot Studio — only custom engine agents are supported; Agent IDs are used for channel auth only (not connectors or tools)
  2. MSAL complexity — Agent ID scenarios require managing Federated Identity Credentials manually. For .NET use Microsoft.Identity.Web.AgentIdentities. For other languages use the Microsoft Entra SDK for Agent ID.

Reporting Issues

Report unlisted issues via aka.ms/agentidfeedback.