Power Apps vs. Copilot Managed Runtime apps

Key insights

• Copilot Managed Runtime apps are code-based web apps hosted on a Microsoft-managed runtime.
• The source describes Copilot Managed Runtime as a preview; Power Apps is the established platform.
• Users need Power Apps Premium or Copilot Credits to run a Managed Runtime app.
• Microsoft 365-included Power Apps rights do not cover Managed Runtime apps, according to the source.
• Power Apps supports visual canvas and model-driven development; Managed Runtime apps use Git-based code workflows.

Power Apps and Copilot Managed Runtime apps offer different ways to build and run business applications, with different governance, source-control, and licensing implications. The choice matters to Power Platform administrators, app makers, and development teams deciding whether to keep an app in Power Apps or pilot a code-based alternative. Suparna Banerjee compares the two approaches and describes the runtime, licensing, and administration trade-offs.

What's new

Copilot Managed Runtime is a Microsoft-hosted runtime for code-based line-of-business web apps. Apps use JavaScript or TypeScript and inherit organizational governance and security controls, according to the source material. This is a separate app model, not a new version of Power Apps.

Power Apps remains the better-defined choice for visual canvas apps and Dataverse-centered model-driven apps. The source also distinguishes Power Apps code apps, which let developers build React or Vue apps that remain part of the Power Apps platform, from Managed Runtime apps, which have their own runtime and administration model.

That means this is not a simple replacement decision. Managed Runtime is presented as a route for quickly creating custom web apps and working with code in Git. Power Apps remains a fit for solutions built around Dataverse, formal release pipelines, and existing Power Apps licensing and practices.

Who it is for and what you need

The comparison is relevant to Power Platform teams, citizen developers, and professional developers. The source describes several creation routes for Managed Runtime apps: Copilot Cowork, Copilot Studio, Copilot Code, and a command-line tool and developer kit. Cowork is described as requiring a Microsoft 365 Copilot license, usage-based billing, and the Frontier program during preview; the command-line route is off by default.

The source identifies Copilot Managed Runtime as being in preview and cautions that its documentation is prerelease. It does not establish availability by region or provide a complete list of eligible tenants or plans, so organizations should check Microsoft’s current documentation before planning a rollout.

Licensing is a key distinction. The source says users need Power Apps Premium or Copilot Credits to run a Managed Runtime app, and Microsoft 365-included Power Apps rights do not cover these apps—even when they use standard connectors. It also says users do not need a Microsoft 365 Copilot license merely to run an app. Building may incur Copilot Credits in Cowork, Copilot Code, and Copilot Studio; the command-line route is listed as not using credits.

For comparison, the source says canvas apps using standard connectors can run under Microsoft 365 Power Apps rights, while Premium connectors or Dataverse can require different licensing. Check the relevant Managed Runtime licensing FAQ and Power Apps licensing FAQ for current terms.

How it works

Managed Runtime apps can start from a natural-language description or from code, depending on the creation route. The source says apps are created by default in the maker’s personal developer environment, which is a Managed Environment; Dataverse is not included unless added. It describes app code as stored in Git and apps as opened from managedapps.cloud.microsoft.

1. Choose a creation route: Cowork, Copilot Studio, Copilot Code, or the command-line tool and developer kit. Availability and prerequisites vary by route.
2. Create or refine the app using natural language or code. The source describes JavaScript and TypeScript as the code-based approach and says apps can connect to more than 1,500 connectors.
3. Share the app with users, then confirm each person has Power Apps Premium or access to Copilot Credits to run it. Sharing alone does not provide the right to run the app.
4. Review and manage the app in the Microsoft 365 admin center, and manage its environment through the Power Platform admin center. The source says the two admin surfaces have different roles.

Power Apps follows a different development path. Makers can use visual designers and Power Fx; model-driven apps center on Dataverse, while canvas apps provide a flexible interface. For a Power Apps code app, developers work with web frameworks such as React or Vue while the app remains within the Power Apps family. The Power Apps code apps overview provides the product-specific documentation.

Microsoft lists Copilot Managed Runtime documentation and guidance for building apps in Copilot Cowork. These are useful starting points for teams checking the runtime and creation options; the preview status means details may change.

Limitations and open questions

The source recommends adding Managed Runtime to an app portfolio rather than replacing Power Apps wholesale. It points to Power Apps for long-lived, business-critical apps, formal development-to-production pipelines, Dataverse-centered designs, and users who have only Microsoft 365-included rights. These are practical selection criteria, not a claim that every organization should follow one architecture.

Managed Runtime may suit a pilot where speed, a custom web interface, Microsoft 365 content, or Git-based developer ownership matters. The source says Premium users can run these apps without credits, but building can still use credits; other users may need credits to run them. It also describes a separate deployment step before an app goes live, rather than treating every build as a production release.

Governance requires attention across two places: the Microsoft 365 admin center for the apps and the Power Platform admin center for environments. The material does not provide a complete operational runbook, a full breakdown of spending-policy configuration, or region-by-region availability. Because the feature is in preview, confirm current documentation and licensing before committing to a production design.

Sources

• Copilot Managed Runtime documentation
• Build apps in Copilot Cowork
• Copilot Managed Runtime overview for admins
• Copilot Managed Runtime licensing FAQ
• Power Apps code apps overview
• Power Apps licensing FAQs
• Suparna Banerjee’s Power Apps and Managed Runtime comparison

Frequently asked questions

Do users need Microsoft 365 Copilot to run a Copilot Managed Runtime app?

No Microsoft 365 Copilot license is stated as necessary just to run the app. The source says users need Power Apps Premium or Copilot Credits.

Do Microsoft 365-included Power Apps rights cover Managed Runtime apps?

No. The source says those included rights do not cover these apps, even when they use standard connectors.

Is Copilot Managed Runtime generally available?

The source describes it as in preview and its documentation as prerelease. It does not state region-by-region availability.

Where are Copilot Managed Runtime apps administered?

The source describes the Microsoft 365 admin center as the place to manage the apps, and the Power Platform admin center as the place to manage their environments.