Copilot Managed Runtime enters public preview

This weekly series covers Microsoft Copilot Managed Runtime (a.k.a. Managed Apps), Power Apps Code Apps and agent plugins.

Managed Apps: Copilot Managed Runtime enters public preview

Microsoft announced Copilot Managed Runtime. It provides Microsoft-hosted infrastructure for internal apps, with Microsoft Entra sign-in, tenant governance and central administration. Makers can build through Copilot Cowork or Copilot Studio, while developers can use a software development kit and command-line tool with a Git-based development workflow.

The preview documentation describes availability for eligible commercial-cloud tenants. Cowork requires Frontier enrolment and Copilot Studio uses its preview experience. This is a preview, subject to supplemental terms, rather than general availability. It is a distinct product from Power Apps Code Apps.

The developer overview says app users need Power Apps Premium or Managed Application Copilot Credits, including developers running apps locally. Premium covers app operations without consuming those credits. Connector access remains subject to tenant policies: the default governance settings allow a curated set of connectors and block some actions, so access to the wider connector catalogue does not mean every connector is enabled by default.

Power Apps Code Apps

More documented ways to license users

Microsoft changed the Code Apps overview. Previously it said end users needed Power Apps Premium. It now also lists pay-as-you-go, an App Pass and auto-claim.

That broadens the documented options for planning user access. Auto-claim assigns an available Premium licence from the tenant; it is not a separate licence type or licence-free access. The source change establishes when the guidance changed, not when each option first became available.

Solution-export failures returned in reports

A controlled comparison reported export failures for Code Apps published on Dataverse build 9.2.26091.144, while an older build worked. Multiple users corroborated export problems in the earlier thread. Export was reported as working again, followed by a new failure report for more recently published Code Apps.

The later report describes missing package containers and 404 errors. Solution export underpins pipelines and other solution-based release workflows, so the reported failure can block moving an app between environments. The newer issue remains unresolved in the cited report. These are community reports, without a Microsoft-confirmed service-wide incident or published root cause.

Power Platform Skills agent plugins

Power Pages can create sites from curated templates

The Power Pages plugin update adds a complete template-based route to /create-site. It selects and pins a curated single-page application template, imports supporting solutions, applies optional sample data, builds and activates the site. This gives makers a reusable starting point alongside the existing from-scratch route. The workflow retains approval and environment checks and includes recovery steps when provisioning fails.

Power Automate makes separate sign-in accounts manageable

The Power Automate plugin update adds account listing and switching, identity comparison and token-cache reset tools. Connection management uses a separate sign-in session from the Azure command-line tool; changing one does not automatically change the other. The new tools expose that mismatch when diagnosing failed connection operations.

The update also adds cloud-specific connectivity endpoints. DoD configuration still requires an operator-verified token audience, and tenant authorisation requirements remain. Tooling changes do not establish blanket availability in every government tenant.

Model Apps protects existing forms and concurrent edits

The Model Apps update changes form-layout verification to check deployed widths and spans against the same rules used to build them. It preserves existing row-spanning layouts when a requested rearrangement cannot safely fit. Related form-topology work checks where tabs, sections and fields actually appear.

Business process flow creation also uses the token returned by each write, refusing a conflicting concurrent edit instead of overwriting it. These changes affect correctness when editing existing apps, rather than adding a new app-building surface.

Canvas Apps checks requirements before declaring completion

The Canvas Apps authoring update adds an evidence-based acceptance workflow and a static validator. Requirements, actions and record fields must remain traceable through the plan and generated app. A final successful compile must follow the last app change, so an earlier compile cannot certify later edits.

Further validation changes cover viewport containment and time ordering. A simple-edit extension also permits one new leaf control without rebuilding a whole hierarchy. Static acceptance evidence does not prove that every live connector or user interaction has been tested.

---

Keep up with AI first development with Power Squared on YouTube.