Microsoft's biggest Copilot change yet is not a feature drop — it is a re-founding. Announced on 25 September, the assistant is now one app with three modes, and the company is openly framing it as the next Office: the surface where knowledge work happens, rather than a panel bolted onto someone else's document.
Home is the new front door. Chat handles quick questions and drafts; Cowork takes delegated, multi-step jobs — an RFP response, a launch kit, a financial close package — and returns a finished result. Underneath both, "Office in Copilot" puts real, editable Word, Excel and PowerPoint files inside the conversation, so a deck stays in sync with the chat that produced it and teammates can be @-mentioned into a live document.
Code is the more consequential bet. Describe a tracker, dashboard, automation or internal app in natural language and Copilot picks an approach and builds it, running in a sandbox and hostable inside your own tenant. Microsoft says it runs on the same underlying technology as GitHub Copilot; the company's pitch is that building small, purpose-made tools is becoming as ordinary as writing a memo. A new Copilot Managed Runtime provides the governed hosting, and a plugin registry with central IT approval is meant to keep the sprawl in check.
Autopilot — previously Scout — is the piece that changes the working day. Give it a name, a role and a goal and it watches channels, follows up on threads, runs recurring work and picks a project back up days later without a prompt. It is cloud-hosted with its own identity, memory, computer and workspace, lives inside Teams, Outlook and documents, and answers to @-mentions with permissions, audit and governance behind it. Home and Code arrive through the Frontier programme in the coming weeks; Autopilot moves to private preview at the end of the month.
The pricing is where the strategy shows. Everyday chat and document work sits on a fixed user subscription licence with an "Auto" router picking a model per request. Long-running agentic work — Cowork, Code, Autopilot, and frontier models such as Astra and Fable — moves to usage-based billing, with new FinOps-for-AI controls so administrators can set budgets, restrict model families and see which delegated tasks actually pay off.
That split is the real announcement. Microsoft is betting that the unit of knowledge work is shifting from the file to the small, purpose-built solution and the always-on agent — and that customers will accept a metered bill for the second half. Whether enterprises agree will be decided by the question that now haunts every agent deployment: what happens when the Autopilot is wrong, and who is accountable when it is.
