Microsoft Moves Copilot Agent Identity and Runtime Into Microsoft 365

Microsoft Moves Copilot Agent Identity and Runtime Into Microsoft 365

AI-generated editorial illustration; not a documentary photograph.

Microsoft’s latest Copilot update moves key infrastructure for long-running enterprise agents into Microsoft 365, giving agents persistent identity, state, execution boundaries and organizational context. The change reduces the platform work developers must assemble around an AI model, according to The New Stack’s report on Microsoft’s announcement.

Persistent agent identities

The most consequential change for developers is Autopilot, which Microsoft describes as a background worker that can continue pursuing an assigned role and goal without a new prompt at every step. Each Autopilot receives a governed Entra identity and agent user account, separating its permissions and activity from those of the employee who created it.

For agents built with Microsoft Foundry, that account can include email, calendar, OneDrive storage, Teams access and a place in the organization chart through an Entra Agent ID user account with a productivity license. Administrators approve agent blueprints in the Agent 365 registry and continue to control the resources and data available to each instance.

A managed home for generated apps

Microsoft is also placing Code-generated apps on Copilot Managed Runtime, now in public preview. The runtime hosts code inside the customer’s Microsoft 365 tenant boundary and applies the tenant’s existing identity and governance controls. It supports apps from Copilot Studio and Cowork, while an SDK and command-line tooling are intended to let outside tools and professional developers use the platform. Git tracks source and versions, and Microsoft says new versions can be tested and deployed without taking the current release offline.

Home and Code are initially rolling out through Microsoft’s Frontier early-access program. Autopilot is expanding to a private preview at the end of September 2026, while Autopilot agents in Foundry have been in public preview since June, according to the report.

Governance and portability costs

Long-running work introduces an operational cost alongside access-control concerns. Standard Copilot subscriptions cover the assistant, but Cowork, Code, Autopilot and other agentic features use Copilot Credits billed by usage. Microsoft is extending Agent 365 cost management to Code and Copilot Managed Runtime, and plans to support agents built in Copilot Studio in October.

The infrastructure can support models from OpenAI and Anthropic, with Microsoft saying more labs and open-weight models are coming. However, model flexibility does not remove platform dependence: agents that rely on Microsoft 365 for identity, permissions and organizational context may be harder to move to another environment.

Source: Microsoft’s new Copilot agents get their own email, calendar — and a place in the org chart

Share this article
FacebookThreadsLinkedInX

Leave a Reply

Your email address will not be published. Required fields are marked *