Microsoft's new Copilot adds an always on Autopilot agent and moves agent work to usage based billing

Microsoft rebuilt Copilot around three tabs, and the pricing change matters as much as the features.

What happened

On September 25, Microsoft introduced a new Copilot app with three parts. Home combines Chat and Cowork, with Word, Excel and PowerPoint built in. Code lets anyone describe an app, tracker, dashboard or automation in natural language and have Copilot build it, powered by the same technology as GitHub Copilot and hosted inside the company's tenant. Autopilot, previously called Scout, is a persistent agent with its own identity, memory, computer and workspace that can watch channels, follow up on threads and run recurring work while you are offline, with permissions, audit and governance behind it.

The billing shift: Microsoft says a user subscription license covers Copilot Chat and Copilot in Word, Excel, PowerPoint, Outlook and Teams, with an Auto model router. Cowork, Code, Autopilot and frontier models like Astra and Fable run on usage based billing. Microsoft also announced FinOps for AI tools that let admins set spending policies, route credit requests into approval workflows and choose which model families each group can use. Home and Code roll out through the Frontier program in the coming weeks, and Autopilot goes to private preview at the end of the month, according to Microsoft and The Verge.

My take

Two things stand out for anyone building automations for Microsoft 365 shops.

First, "describe an automation and Copilot builds it" will put a lot of small internal tools in the hands of non developers. That is useful, and it also means sprawl. Someone still needs to decide which of those become supported systems with owners.

Second, usage based billing turns agent design into a cost question. An always on agent that watches channels is only cheap if it acts on narrow triggers. My default for clients:

1. Use fixed workflows for predictable steps and reserve the agent for judgment calls.
2. Set spend limits per group before rollout, not after the first invoice.
3. Track cost per completed task, not cost per seat.

If you are on Microsoft 365, this is a good month to list which recurring tasks deserve an agent and which just need a scheduled flow.