3.2.1. Agent Identities and Lifecycle Workflows with Microsoft Entra Agent ID
💡 First Principle: An agent identity should have a lifecycle tied to a person, just as an employee's account is tied to HR records. When the accountable person moves or leaves, the agent's accountability must move with them — otherwise the tenant fills with powerful, ownerless actors.
The object model. Microsoft Entra Agent ID adds four directory object types:
- An agent identity blueprint is the template. It creates agent identities (and their optional agent users) but can't access resources itself.
- An agent identity is the actor that performs the agent's tasks. One blueprint can create many.
- An agent user is an optional user account paired one-to-one with an agent identity, for agents that must appear and operate as a user — for example, with a mailbox.
- A blueprint principal represents a multitenant agent's blueprint in each tenant, like a multitenant app's service principal.
Find them in the Microsoft Entra admin center under Entra ID > Agents > Agent identities and Agent blueprints. Disabling a blueprint stops new identities being created from it and blocks the existing ones. Since May 2026, Copilot Studio creates an Entra Agent ID for every new agent automatically, with no opt-out, and deleting a Copilot Studio agent deletes its Agent ID. Microsoft Foundry creates a blueprint and agent identity per project and per published agent.
Sponsors and succession. Every agent identity and blueprint needs at least one sponsor. In delegated creation, the person creating the agent becomes its sponsor if none is specified. Sponsors can be users or certain groups — dynamic-membership groups and assigned Microsoft 365 groups, but not role-assignable groups or assigned security groups — up to 100 sponsors (no more than 5 of them groups). Even with no workflow configured, when a sponsor leaves the organization, their agents' sponsorship transfers automatically to the sponsor's manager.
Lifecycle Workflows (Entra admin center > ID Governance > Lifecycle workflows, as a Lifecycle Workflows Administrator) add explicit, auditable handling. The agent sponsor tasks — emailing the manager about sponsorship changes, emailing co-sponsors about sponsor changes, and transferring the user's agent sponsorships to their manager (which needs the manager attribute populated) — are available only in mover and leaver workflow templates, not joiner. You build the workflow from a mover or leaver template: basics and trigger, scope, tasks, review, create.
Licensing: ID Governance for agent identities needs Microsoft 365 E7, or a Microsoft Agent 365 license together with at least Microsoft Entra ID P1 or Microsoft 365 E3.
⚠️ Exam Trap: If a question asks how to make sure a departing employee's agents notify and transfer to their manager, the answer is a leaver (or mover) Lifecycle Workflow with the sponsor tasks — a joiner workflow can't use them. And don't pick "assign the agent to the departing user's manager as owner": owners are optional; it's sponsorship that must transfer.
Reflection Question: A team lead who sponsors 40 agents is promoted to another department. Which workflow type handles this, what does the transfer task do, and what directory attribute must be correct for it to work?