TLDRocket
Sign in

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

The New Stack Amanda Caswell ● Covered by 3 sources

Microsoft gave Copilot agents their own email, calendar, and Teams access. That makes them act more like workers inside a company, and harder to move out.

Based on reporting by The New Stack, Amanda Caswell — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Microsoft says Friday’s Copilot update is its biggest yet, and Satya Nadella is pitching the whole thing as “a new OS for work.” The flashy part is the assistant layer. The more interesting part is what’s underneath it: Microsoft is folding agent infrastructure into Microsoft 365 so developers don’t have to stitch together identity, state, permissions, and execution boundaries themselves.

The update splits into four pieces, with Autopilot at the top of the list. Microsoft describes Autopilot as a proactive, long-running enterprise agent. It takes a role and a goal, then keeps going in the background without asking for a fresh prompt every time. Home now merges Chat and Cowork in the Copilot app, while Code can generate apps, dashboards, and workflows from natural language.

For developers, the biggest shift is identity. Autopilot agents in Microsoft Foundry get a full Entra Agent ID user account with a productivity license, which gives them their own email, calendar, OneDrive storage, Teams access, and a place in the org chart. Microsoft says that lets an agent act as itself rather than piggybacking on a human account or a shared service credential. A developer builds an Autopilot blueprint from a Foundry-hosted agent, and once an administrator approves it, employees can hire instances of that agent in Teams.

Microsoft is also pushing AI-generated apps into its own managed runtime. Code runs on Microsoft Copilot Managed Runtime, which is in public preview and keeps apps inside the customer’s Microsoft 365 tenant boundary under IT governance. The runtime accepts apps built in Copilot Studio and Cowork, and Microsoft is opening it to outside tools and developers through an SDK and command-line tooling. Lovable is already on board, and Microsoft says its apps can run inside a tenant with the same sign-in, policies, and app inventory as everything else.

The money side changes too. Cowork, Code, Autopilot, and other agentic features are billed through Copilot Credits, and the same applies to frontier models such as Fable and Astra. Microsoft is extending cost management in Agent 365 to Code and Copilot Managed Runtime, with support for Copilot Studio agents planned for October. That matters because once an agent can work for hours or days, usage, access, and governance stop being separate problems.

There’s a catch, of course. The more Microsoft handles for you, the more Microsoft sits in the middle if you ever want to move. The company says the models themselves are not locked in, and Copilot currently runs on OpenAI and Anthropic models, with more labs and open-weight models coming. But identity, permissions, and context are sticky things, and Microsoft knows it.

My take — AI-written commentary, not fact-checked reporting

This is classic Microsoft: make the enterprise feel safe, then quietly make it dependent. The company is not selling agents so much as renting the plumbing around them, and that’s the real moat. Nice if you like convenience; less cute if you like escape hatches.

Read more about this at: The New Stack

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.