Microsoft gives each Copilot Autopilot agent its own Entra user account

Satya Nadella said Copilot is "a new OS for work." ^[2] The New Stack's reading of the release is more specific. In its account, Microsoft is building persistent identity, state, execution boundaries and organizational context into Microsoft 365 ^[12]. Teams building production agents, it says, no longer have to assemble those pieces around a model on their own ^[12].

Identity is the best documented of the four. Every Foundry agent already carries an agent identity. The Autopilot user account sits on top of it, so the agent acts as itself and not on behalf of whoever set it up ^[7]. Its permissions and activity stay separate from its creator's ^[5]. That removes the two workarounds the report names: shared service accounts and borrowed user credentials ^[7]. AuthZed CEO Jake Moshenko has said that pattern reflects a common misconception about how agents should be deployed, according to The New Stack ^[8].

Access control reuses the employee model. The blueprint fixes what the agent is designed to do. Administrators still decide which resources and data each instance can reach, under the same policies used for employees ^[10]. An agent with its own calendar will, sooner or later, get invited to a meeting. For a team that wrote its own permission layer for agents on Microsoft 365, I think this is the first piece to hand over once it leaves preview. Foundry Autopilot agents have been in public preview since June ^[6].

State is thinner. Nadella said Autopilot is a "proactive and long-running agent built for the enterprise" ^[3]. Long-running is the property that needs failure semantics. The report does not describe how an Autopilot run checkpoints, retries or resumes when a worker dies partway through a task. A team whose current stack already survives that failure should see Autopilot survive it too before removing its own layer. Durable recovery is a product category in its own right: Diagrid, for example, adds it to LangGraph and other agent frameworks ^[11].

Execution boundaries are concrete on the app side. Microsoft manages the runtime under Code's apps and provides a path to test and deploy a new version without taking the current release offline ^[14]. Outside tools and professional developers get an SDK and command-line tooling, with Git tracking source and versions ^[15]. The runtime also takes apps built in Copilot Studio and Cowork ^[15]. Code itself is built on the same technology as GitHub Copilot ^[13], and Lovable is already on board ^[16].

Adoption cost sits in hosting and licensing. The registry path in the report starts from a Foundry-hosted agent ^[9]. An agent on a self-hosted framework would have to move to Foundry to get an Entra user account this way. Each of those accounts also carries a productivity license ^[6]. In a tenant where agents already run in Foundry, I'd move identity to Entra now and keep my own durable-execution layer until Microsoft documents how Autopilot recovers.