Skip to content

Copilot Managed Runtime Explained: Run Copilot Apps Securely

With Cowork, Code, or Copilot Studio, almost anyone can build a small app today. The question is where it runs afterwards. Microsoft's answer is Copilot Managed Runtime, generally available since Ignite 2026. Here's what it is, who it's for, and where to find the official links.

By Dual Microsoft MVP for Copilot and Copilot Studio Published

A man holds up a card with a question mark and points a remote at a laptop that reads “WOW!”; behind him is a sketched Golden Gate Bridge with “Ignite 2026”.
AI-generated image

A dashboard from Cowork, a form from Copilot Code, a small app from Copilot Studio: building apps with Copilot has become easy. The hard part comes next. Where does the app run? Who can open it? Which data can it read? And does IT even know it exists?

That’s what Copilot Managed Runtime is for. Microsoft announced it as generally available at Ignite 2026 on November 17, and it’s rolling out to tenants step by step.

What is Copilot Managed Runtime?

Copilot Managed Runtime is where your app runs, inside your own Microsoft 365 tenant, operated by Microsoft. Microsoft describes it as an IT-governed platform for running code in your tenant, with built-in sharing, live data connections, and easy access to apps.

Put simply: you build the app, Microsoft takes care of the server. You don’t set up a cloud service, book hosting, or code a sign-in. The app gets all of that out of the box:

  • Sign-in with Microsoft Entra: only people signed in to your organization can open it.
  • Sharing like any other Microsoft 365 content.
  • Approved data connections, for example to SharePoint or Dataverse, following your organization’s rules.
  • Code in Git: every app usually has a platform-managed repository with versions. If you use GitHub Enterprise Cloud, you can connect your own repository.
  • A start page for users: at managedapps.cloud.microsoft, they find every app shared with them.

Where do the apps come from?

According to Microsoft Learn, there are four ways to build an app for Managed Runtime:

Path Who it’s for Status
Cowork people with a Copilot license and a spending policy for Cowork Frontier (app builder) according to Learn; generally available and rolling out in November according to the Copilot Studio blog
Copilot Code people who want apps from a description, in the cloud or locally Frontier, generally available in December according to the Book of News
Copilot Studio makers who already build agents in Copilot Studio generally available, rolling out in November (Copilot Studio blog); Learn still lists it as preview
SDK and CLI developers with their own editor, including GitHub Copilot or Claude Code preview according to the Learn quickstart

For developers, Microsoft ships a command-line package (@microsoft/cmr-cli, command ms) and an SDK for the app itself. The GitHub repository includes a React and Vite template and a plugin with skills for coding agents.

What’s new since Ignite 2026?

According to the Tech Community blog announcement from November 17, 2026:

Update Status according to Microsoft
Copilot Managed Runtime itself generally available, rolling out to tenants
Microsoft Fabric as data storage for apps public preview in the Frontier program
Build Copilot Studio agents and workflows locally and publish from the command line public preview
Code Agents early-access preview with sign-up, “coming soon”

Managed Runtime had been in public preview since September. The main change is that apps can get persistent storage with Fabric. Until now, apps used connections such as SharePoint and Dataverse; Fabric adds to them.

What does IT control?

For admins, this is the real win. Instead of individual apps scattered across the web, there’s one overview:

  • App inventory: all apps show up in the Microsoft 365 admin center under Apps > All apps. Admins see their health there and manage security and compliance.
  • Policies: the organization decides which connectors, data, and endpoints an app may use. Connectors that aren’t approved are blocked.

So no shadow IT appears just because someone built a dashboard in Cowork.

How is Copilot Managed Runtime billed?

Billing is consumption-based through Copilot Credits. Microsoft Learn separates building from running:

  • Building: in Cowork and Copilot Code, you need a Microsoft 365 Copilot license plus credits. In Copilot Studio, credits go through the environment’s billing. With the command line, you don’t need a license to build and publish.
  • Running: anyone who uses an app needs a Power Apps Premium license or Copilot Credits through a spending policy that includes Managed Runtime. A Copilot license alone doesn’t cover it, and neither do the Power Apps rights included with Microsoft 365.

Admins create spending policies with a monthly limit per user in the admin center under Copilot > Cost management. How credits work in general is explained in our article on the 2026 Copilot pricing model.

Who is it for?

  • Teams that already build apps in Cowork or Code: the app no longer gets passed around as a file but runs in one place, with sign-in.
  • IT that wants to know which apps exist and which data they access.
  • Developers who work in their own editor but don’t want to host anything themselves.

Before you start, settle two things: who should use the apps, and how will those users be licensed? That decides whether the app runs for everyone day to day or stays blocked for some of them. If you want to sort that out for your IT, that’s a topic for coaching for IT and admins. Whether your agent idea is feasible with these building blocks is what the free pre-check at Agent-Architekt tells you.

Microsoft published these short links for Ignite:

Sources

As of November 18, 2026.