Copilot Code and Managed Runtime: Anyone in Your Firm Can Build an App Now. Who Owns It?

Of the three things Microsoft announced on 25 September, Code is the one that changes who in a firm can build things. Picture the tax team hearing that you can describe a tracker and get one. Someone tries it, it works and they share it with the team. That is the point of the product, and it is also the reason to read past the demo.

This post covers what Code is, the hosting underneath it that matters more than Code itself, where Copilot Studio and Power Apps still fit and what it costs. For the whole announcement, see the new Copilot explained.

What Code is

Microsoft’s framing is that the unit of knowledge work has been the file: the document, the spreadsheet and the deck. Code adds a fourth, small purpose-built solutions that anyone can create.

You describe an app, tracker, dashboard, automation or workflow and Copilot chooses an approach and builds it. That might be a persistent desktop widget for quick reference, an interactive dashboard or a cloud-hosted internal app you share with the team.

It uses the same underlying technology as GitHub Copilot. It runs in a sandbox and can be hosted securely in your tenant, meaning your organisation’s own Microsoft 365 environment. It is grounded in the context of your work through Microsoft IQ, Microsoft’s context platform. Plugins sync automatically. Developers keep using GitHub Copilot for their day-to-day work.

Code is rolling out to the Frontier programme at the end of September. Frontier is Microsoft’s opt-in early-access programme: an admin switches it on in the Microsoft 365 admin centre, it is off by default and everything in it is preview. Broad availability is promised “in the coming weeks”, with a preview for Microsoft 365 Premium and Pro subscribers, which are individual plans, later this year. Fabric IQ integration with Code, which brings in the Power BI models behind your reports, is coming through Frontier “soon”.

Managed Runtime, the bit that matters more than Code

Copilot Managed Runtime is Microsoft’s hosting for Microsoft 365 line-of-business apps, the internal tools a firm runs its work on. Those apps inherit the organisation’s governance, security and compliance controls from the moment they are created. Whatever built the app, it runs in a Microsoft-hosted environment, uses Entra sign-in (Microsoft’s identity service), follows tenant governance policies and is visible to admins in the Microsoft 365 admin centre.

Microsoft Learn documents three ways to create an app today:

• From a Cowork session, using the App builder skill. This needs Frontier.
• In Copilot Studio, under Apps in the navigation, in preview. You describe the app, Copilot Studio proposes a plan and drafts it, you refine it in a live preview and then publish and share.
• Code-first, with the ms command line tool and SDK, for developers.

The announcement adds Code as the way in for everyone. All the routes produce the same kind of thing: an app that inherits the tenant’s default governance policy (approved connectors, sharing rules and content security policy) and appears in the admin inventory. Users find and open apps in one place, the Managed Runtime portal at managedapps.cloud.microsoft, which is separate from the build tools and the admin centre.

Under the hood it is Git. There is a platform-managed repository, builds come from real commits, preview is automatic and going live is a deliberate step. Nobody in your firm needs to know Git, but it means every app has a history and a version that is live. Microsoft’s developer quickstart also states that the preview runs under the same enterprise governance as production: Entra ID, Conditional Access (the rules on who can sign in and under what conditions) and data loss prevention.

Microsoft is opening Managed Runtime to third-party and pro-code developers, and it will be reachable inside Code. That is in preview now. We looked at the same platform before it had a public name in apps in Copilot Cowork and Copilot Studio.

Code vs Copilot Studio vs Power Apps

This is the question prospects will ask: if Copilot builds apps itself, what is Copilot Studio for?

This is not either/or. Managed Runtime hosts Copilot Studio apps too, and Copilot Studio agents join Agent 365 cost management in October, so the platform is converging rather than replacing anything. The older questions still apply at the edges: Agent Builder or Copilot Studio for agents, and Copilot Studio or Power Automate for workflows.

What it costs

Code runs on usage-based billing in Copilot Credits, on top of the Copilot licence. A Copilot Credit is Microsoft’s usage currency for AI work the per-user licence does not cover. Microsoft has not published rates for Code.

What is published is how apps built in Cowork are billed. They draw Copilot Credits, and consumption varies with the model used, the complexity of the app and how much generation and iteration happens. It is reasonable to expect Code to work the same way, but that is an expectation, not a published rate.

Cost management in Agent 365, Microsoft’s admin and governance layer for agents, is expanding to cover Code and Managed Runtime. And usage-based services stay off until an admin sets a spending policy. Our Copilot Credits explainer covers the existing workloads, and three numbers to check before your first agent goes live applies to a first Code app just as well.

The shadow app problem

Here is the honest risk for a firm. The tax team builds six trackers in a month. One of them pulls client data from a SharePoint site that half the firm can see. Nobody knows which app is the live one.

Some of the platform helps. The admin inventory shows what exists, the approved-connector policy limits what an app can reach and the single portal gives people one place to look.

What does not help by itself is an inventory nobody reads. Every Code app needs the same three things as an agent: an owner, a line on what data it reads and a date when it gets reviewed or retired. We made the case for agents in why every agent needs an owner, and for flows in automation maintenance for Microsoft 365. Apps are the same argument. So is Autopilot, which gets its own account and its own manager.

What a firm should do

1. Do not enrol everyone in Frontier to try Code. Pick one person who already builds things (usually the Excel person) and let them learn it first.
2. Set the spending policy before they start. Give it a cap and alerts.
3. Add Code apps to the same owner list as agents and flows. One register, not three.
4. Keep the Copilot Studio work going. The agents you are building now are the ones that will run on this platform.

The bottom line

Code removes the excuse that building is hard. It does not remove the need to decide what is worth building and who looks after it. For teams that want to learn to build properly, Enable is where our agent workshops sit. For firms still working out what is worth building at all, Discover is the fixed first step.

Sources checked

Last checked: 26 September 2026.

• Microsoft Official Blog, “Introducing the new Copilot with Home, Code and Autopilot”, 25 September 2026
• Microsoft Tech Community, “Evolution of the Copilot pricing model”, 24 September 2026
• Microsoft Learn, “What is Copilot Managed Runtime (preview)”
• Microsoft Learn, “Quickstart: Build a Microsoft Copilot Managed Runtime app with GitHub Copilot (preview)”
• Microsoft Learn, “Quickstart: Create an app with natural language in Microsoft Copilot Studio (preview)”
• Microsoft, Copilot Credits Guide, September 2026

Want help deciding which apps and agents are worth building in your firm, and who should own them? That is the work FiveForward does. Book a free consultation and we will start from the trackers and spreadsheets you already rely on.