September 26, 2026, (Inside AI) — Microsoft has begun assigning AI agents their own corporate identities, complete with email addresses, calendars, and file storage inside Microsoft 365. The company unveiled the update on September 25, calling it its largest Copilot overhaul to date. CEO Satya Nadella described the assistant as "a new OS for work" that spans every model and task.
The move pushes agent operations into the enterprise infrastructure layer. Persistent identity, execution boundaries, and organizational context now sit directly inside Microsoft 365 rather than in separate systems developers must stitch together. Autopilot agents receive their own Entra identity and user account. Each one gains email, calendar, OneDrive storage, and Teams access. Agents appear on the organizational chart as themselves, not as shared service accounts or borrowed user credentials.
Four Pillars Reshape Workplace Agents
Microsoft organized the release around four components. Home merges Chat and Cowork inside the Copilot app. Code generates apps, dashboards, and workflows from natural language descriptions. Autopilot turns agents into persistent background workers that keep running without fresh prompts for each task.
Home and Code reach users first through the company's Frontier early-access program. Autopilot enters private preview by the end of September. Code-generated applications run on Copilot Managed Runtime, now in public preview. That platform hosts apps inside each customer's Microsoft 365 tenant under IT governance. Apps execute within existing identity and governance frameworks while Microsoft manages the underlying runtime. Developers can push new versions without taking current releases offline.
Lovable, an app-building platform, joined the initiative immediately. Apps built on Lovable can now run inside Microsoft tenants the same way other software does. The integration signals that Microsoft wants third-party builders inside its governance perimeter rather than competing with them.
The financial model changes for long-running agents. Standard Copilot subscriptions still cover the assistant itself. But Cowork, Code, Autopilot, and frontier models incur usage-based charges through Copilot Credits. Teams must now govern agent compute alongside what each agent can access. Microsoft is extending cost management in Agent 365 to cover Code and Copilot Managed Runtime operations.
The trade-offs are real. The more agents depend on Microsoft 365 for identity, permissions, and context, the harder they become to move elsewhere. Agents lock into Microsoft's infrastructure more deeply with each capability they adopt. Model portability survives because Microsoft runs Copilot on models from both OpenAI and Anthropic. The Agent 365 SDK adds governed Model Context Protocol access. Yet the underlying identity and permission layers remain tightly integrated with Microsoft 365.
That integration cuts both ways. Enterprises gain audit trails, access controls, and a single pane of glass for every agent. They also accept that switching costs rise with every agent they deploy. Rivals including Google and Salesforce have pushed their own agent platforms, but none has matched Microsoft's decision to give agents first-class directory accounts. Treating an agent like an employee is a governance breakthrough and a lock-in strategy at the same time.
Read: Enterprise AI Agents Fail Without Employee Trust, Wharton Blueprint Finds
Microsoft has not disclosed pricing for Copilot Credits or a general availability date for Autopilot. The company also has not said whether agents will appear in billing systems as distinct line items or as extensions of their human owners. Those details will determine how quickly IT departments embrace persistent agents. For now, the message is clear. Agents are no longer tools that live inside apps. They are coworkers with logins, mailboxes, and a place on the org chart.
