On 25 September 2026 Microsoft rebuilt its work Copilot app around three tabs: Home, Code and Autopilot. Code is the one developers should pay attention to, because it is built for people who are not developers, and the things it produces will still end up running inside your company.
I went through Microsoft's announcement, the Copilot pricing post and the related Microsoft 365 message center notice. Everything below comes from those sources. Where something is still preview or private preview, I say so.
TL;DR
- Code turns a plain-language description into an app, tracker, dashboard, automation or workflow. Microsoft says it is powered by the same underlying technology as GitHub Copilot.
- It runs in a sandboxed environment and can be hosted inside your Microsoft 365 tenant.
- Hosting comes from Copilot Managed Runtime, which is in preview and which Microsoft says it is opening up to third-party and pro-code developers.
- Autopilot (previously called Scout) is a cloud-hosted agent with its own identity, memory, computer and workspace in your tenant. It is in private preview.
- Cowork, Code and Autopilot run on usage-based billing with Copilot Credits. In enterprise tenants they stay off until an admin creates a spending policy.
- Microsoft says developers keep using GitHub Copilot for their day-to-day work.
What Code actually is
Microsoft frames Code as a new unit of knowledge work, next to the document, the spreadsheet and the deck. You describe what you want and Copilot "chooses an approach and builds it". The examples Microsoft gives fall into three shapes:
- Persistent desktop widgets for quick reference.
- Interactive dashboards for exploring data and testing outcomes.
- Cloud-hosted internal apps you can share with your team.
The announcement says Code is grounded in Microsoft IQ, so what you build can use the context of your work, and that plugins sync automatically. Fabric IQ, which brings in data such as Power BI semantic models, is generally available in Chat and Cowork, with Code integration "coming through the Frontier program soon".
On timing, Microsoft said Code would roll out to its Frontier early access program at the end of September, with broad availability in the following weeks, and a preview for Microsoft 365 Premium and Pro subscribers later in 2026.
Copilot Managed Runtime is the part that matters to devs
The prompt box gets the attention, but the hosting layer is the real platform move. Microsoft describes Copilot Managed Runtime as "hosting infrastructure that lets code run safely right inside your company's Microsoft 365 environment". It is governed by IT, while users can share an app with teammates, connect it to live data and open it from anywhere.
Three details from the announcement stand out:
- The same runtime backs apps built in Cowork, Code and Copilot Studio.
- Microsoft says it is opening it up to third-party and pro-code developers.
- It is in preview now and will also be reachable inside Code.
Microsoft has not published, in these posts, what languages, frameworks, deployment model or limits the runtime supports for pro-code use. I could not confirm any of that, so I am not guessing. If you are on a platform team, this is the thing to watch at Ignite (17 to 20 November 2026, San Francisco and online), where Microsoft says more Copilot news is coming.
Autopilot: an agent with its own identity
Autopilot is the always-on piece. You give it a name, a role and a goal, and it watches channels, follows up on threads, runs recurring work and picks projects back up days later without a prompt. Microsoft says it lives in your tenant with "its own identity, memory, computer and workspace", shows up in Teams, Outlook, chats, channels and documents, and works with "permissions, audit and governance behind it".
For anyone who has built integrations, that sentence raises the obvious questions: what scopes does that identity get, who owns it, and how do you review what it did? The announcement does not answer those in detail. Autopilot is in private preview, so this is the moment to ask your Microsoft 365 admins how they plan to handle it, before it becomes another service account nobody remembers creating.
The billing model, in developer terms
Microsoft split Copilot pricing into two parts:
| What it covers | How it is billed | |
|---|---|---|
| User subscription license (USL) | Chat, Copilot in Word, Excel, PowerPoint, Outlook and Teams, model selection, and Auto | Per user, per month, with fair use limits |
| Usage-based billing (UBB) | Cowork, Code, Autopilot, long-running agent work, and frontier models | Copilot Credits, on top of the USL |
Auto weighs accuracy, speed and cost on each request and routes it to a suitable model. Heavy USL users get a warning first, then a choice to switch to Auto at no extra cost or move to credits.
The guardrail that matters most: Microsoft says that for enterprise customers, UBB services stay off until an admin creates a spending policy in the Microsoft 365 admin center, and nothing is billed before that. Policies can set tenant and group budgets, per-user caps inside group policies and alert thresholds. Microsoft also says spending policies can be managed programmatically through the Microsoft Graph API, and that usage can be mapped to Azure subscriptions or resource groups. The message center notice says UBB begins rolling out in Copilot in Q4 2026.
If you already think in FinOps terms for Azure, this will feel familiar. The new part is that the people generating the spend may be in finance or sales, not engineering.
What I would do as a developer or platform team
None of this needs a migration today. These are low-cost steps that save pain later:
- Find out if your tenant is in Frontier, Microsoft's early access program. If it is, Code may already be visible to colleagues.
- Talk to IT about the spending policy before it exists. Ask for a pilot group, a per-user cap and alerts rather than a tenant-wide default.
- Decide where "citizen-built" apps live. If a Code dashboard becomes business-critical, who owns it, who fixes it, and does it ever move to a real repo?
- Treat Autopilot identities like service principals. Ask for least privilege, an owner and an audit trail from day one.
- Watch Managed Runtime for pro-code support. If it opens up the way Microsoft suggests, it could become another hosting target inside Microsoft 365, next to the Azure services you already use.
The honest take
Most of this is preview or private preview, and the developer story for Managed Runtime is still thin on details. But the direction is clear. Microsoft wants small internal tools to be built by the people who need them, in Copilot, and run inside the tenant. GitHub Copilot stays the tool for developers, and Code is aimed at everyone else.
For developers, that can be a relief, because fewer tickets come in asking for a quick dashboard. It can also be a headache, because more unreviewed apps end up touching live company data.
Your turn
If your colleagues can describe a dashboard and get a working, shareable app in your Microsoft 365 tenant, does that take load off your team, or create a new pile of shadow IT you will end up maintaining? And if you are in the Frontier program, what has Code built for you so far?
Originally published on WindowsMode.
