Microsoft has introduced a new Copilot experience built around Home, Code and Autopilot.
There have been plenty of Copilot updates over the last few years, but this one caught my attention because it shows how quickly Copilot is moving beyond simply answering questions, summarizing information or creating content.
Home brings Copilot Chat and Cowork together, with Word, Excel and PowerPoint creation also becoming part of the experience. It gives users a more unified place to work with Copilot rather than moving between different AI experiences.
Code is another interesting addition. Users can describe what they want to build in natural language and Copilot can help turn that idea into an application. It doesn't replace traditional development, but it certainly makes building applications more accessible to people who understand the business problem but may not be developers themselves.
For me, Autopilot is probably the most interesting part.
Instead of waiting for us to provide the next prompt, Autopilot is designed for ongoing work that can continue in the background. This is where the shift from AI assistants to agents becomes much more visible. We are not just asking AI for help anymore; we are gradually starting to delegate work to it.
Microsoft is also introducing Microsoft IQ, providing the enterprise context that Copilot and agents need to better understand the people, relationships and information around the work they are performing.
There is another part of this announcement that shouldn't be overlooked: FinOps for AI.
As Copilot moves towards more agentic and usage-based workloads, understanding AI consumption and cost becomes increasingly important. Microsoft is introducing new FinOps capabilities to provide better visibility and control over AI spending.
This connects closely with what I recently wrote about in FinOps for AI: Understanding Tokens, Copilot Credits and the Real Cost of AI. AI adoption is no longer just about licenses; organizations increasingly need to understand consumption, cost and the value being delivered.
This announcement also follows Microsoft's recent discussion around building the system for AI at work, and the direction is becoming clearer.
Copilot is gradually becoming much more than an AI assistant sitting alongside our Microsoft 365 applications. It is becoming a place where we can work with AI, build with AI and increasingly delegate work to AI.
We are still early in this journey, and enterprises will need to get security, identity, governance, cost and human oversight right as these capabilities mature.
But Home, Code and Autopilot give us a good indication of where Microsoft believes the next phase of Copilot is heading.
Read below to know more
Microsoft — Introducing the new Copilot with Home, Code and Autopilot
Microsoft — Building the system for AI at work
Update (September 25, 2026): Microsoft Copilot Managed Runtime
The same day as the Home, Code and Autopilot announcement, Microsoft also introduced Copilot Managed Runtime into public preview — the enterprise hosting layer underneath apps built in Copilot Cowork, Copilot Code and Copilot Studio.
Functioning code was never the hard part. Provisioning, identity, policy and deployment were — and every app-building tool meant a separate governance stack. Managed Runtime fixes that with one shared foundation: Microsoft Entra identity, governed data access, and a single app inventory in the Microsoft 365 admin center, regardless of where the app was built.
Microsoft is also opening this to third-party tools via an SDK, so the goal looks less like "make Copilot Code production-ready" and more like "one governance model no matter where the app comes from."
Reference
Build apps in Copilot Cowork and Copilot Studio