Microsoft AI-first Development Weekly: Copilot Managed Runtime audit gap and new app workflows
Microsoft AI-first Development Weekly covers Copilot Code, Power Apps Code Apps, Microsoft Copilot Managed Runtime and Power Platform skills and plugins for AI-first development: using artificial intelligence to help build and change apps.
Copilot Managed Runtime: an important audit limit
Microsoft confirmed that sending Copilot Managed Runtime app audit events to Microsoft Purview is not currently an officially supported capability. Purview's audit log records activities that organisations may need to investigate or demonstrate compliance. The app operations raised in the report are not expected to appear there as runtime-specific events.
This matters when deciding whether the public preview meets an organisation's requirements. Microsoft has not given a confirmed availability date. This is a specific limit on Purview audit events, rather than a statement that all runtime monitoring is unavailable. Read Microsoft's response.
Copilot Code: planned European processing for Claude models
Microsoft plans to process Claude AI model requests from Copilot Code within its EU Data Boundary for eligible organisations in the European Union and the European Free Trade Association. Claude is a family of AI models that helps Copilot Code build and change software. The boundary is Microsoft's commitment to keep covered data storage and processing within those regions.
This is an announced future change, not confirmation that processing has moved. Existing users will move automatically when it becomes available. Claude remains disabled by default in these regions and requires an administrator to enable it. Copilot Code remains a Frontier preview, Microsoft's early-access programme. Read Microsoft's announcement.
Copilot Managed Runtime: a simpler route from App Builder
Microsoft has started making a one-click route available for moving App Builder apps into Copilot Cowork as Copilot Managed Runtime apps. App Builder is retiring. The new route avoids downloading source files and writing a migration prompt, although it may not yet appear for everyone.
The move creates a separate app. SharePoint data stays in the same lists, and connections are reconnected automatically. Existing app links and sharing permissions do not carry over: the new app still needs review, publication and sharing.
Copilot Cowork requires a Microsoft 365 Copilot licence, access enabled by the organisation, participation in Microsoft's Frontier early-access programme, and Copilot Credits for usage-based charges. App creation in the user's personal developer environment must also be allowed. A manual migration route remains available. Read the migration guide.
Power Apps Code Apps: earlier checks for blocked data connections
Power Apps Code Apps command-line tool version 1.4.0 adds checks against an organisation's connector policies when adding a data source. A connector is the link an app uses to work with another service, such as SharePoint. The tool can reject a blocked connector before adding it and stop when every operation in that connector is blocked.
There is an important limit: some sign-in or policy-lookup failures produce a warning and allow the command to continue without this check. This is an earlier development check, not proof that every policy will be enforced in every situation. Inspect the published tool.
Power Apps Code Apps: fix for silently lost connection settings
Microsoft says Power Apps Code Apps command-line tool version 1.4.1 fixes a refresh problem that could remove a saved connection reference and a flow's dependency on it while reporting success. A connection reference tells an app which saved service connection to use. Losing it can leave a previously working automation unable to run.
Microsoft asks affected users to update and verify the result. The fix has not been independently retested for this roundup. Read the fix confirmation.
Copilot Managed Runtime: Microsoft reports a policy-delay fix
Microsoft reported a fix for the gap between creating a developer environment and applying its environment-group rules. An environment is a separate space for apps and data; an environment group applies common rules to several spaces. During that delay, the command-line route could create and publish an app before the blocking rules arrived.
Microsoft closed the report and said the fix was expected to reach all locations. This roundup has not verified the completed deployment or retested an affected organisation. The report concerns that specific timing gap. Read Microsoft's follow-up.
Copilot Managed Runtime: new home and an upgrade change
Microsoft moved current Copilot Managed Runtime templates, tools and issue reporting to a new repository. Existing open reports will be transferred with their discussion history, so people do not need to submit them again.
The new packages are @microsoft/cmr-apps, @microsoft/cmr-cli and @microsoft/cmr-apps-vite-plugin. They provide app code helpers, terminal commands and integration with Vite, the tool that builds and serves an app during development. The terminal command remains ms.
The Vite plugin's version 0.5.0 removes the old managedApps function. Existing projects upgrading to it need to change the import and call to copilotManagedRuntime, with corresponding type-name changes for TypeScript projects. The new coding-agent plugin is a separate installation from the old one. Copilot Managed Runtime remains in public preview. See the new repository and the Vite upgrade note.
Power Apps model-driven apps: keep more app parts in step with a saved plan
The Power Platform Model Apps plugin can now use an optional declared configuration to keep more model-driven app parts in step with a saved app description. Model-driven apps arrange screens around structured business data. Developers can describe forms, dashboards, views, charts and supporting files, then rebuild supported parts from that description.
The workflow requires approval before taking over existing components. Business rules check or change data, while business process flows guide users through steps. Both support creation or adoption of existing items, rather than unrestricted editing. Rules may still need separate publication. The plugin's documented checks have limits, including some differences between saved and published labels. Read the Model Apps changes.
Power Apps model-driven apps: describe settings and field protection
The Power Platform Model Apps plugin also lets an app description include environment variables, saved connection references, custom operations and duplicate-detection rules. These describe settings that vary between installations, connections to services, extra actions an app can call, and checks for repeated records.
The same update adds column-security settings, profiles controlling who can read or change particular fields, and date-and-time behaviour. This lets developers include important data-handling choices in a repeatable build. Destructive changes require explicit approval. An optional app-theme setting is in preview; these additions do not remove the organisation's normal permissions or platform requirements. See the configuration reference.
Power Apps model-driven apps: safer recovery after interrupted creation
The Power Platform Model Apps plugin adds optional stable identities for newly created views, charts and configuration items. In everyday terms, it reserves the identity of an item before creating it, so a lost answer does not lead to blindly creating another copy.
Configuration protection includes environment variables, connection references, custom operations and duplicate-detection rules. Existing rows are not automatically moved into this new arrangement. Taking over an uncertain result needs the approvals named by the tool, and some unsupported edits stop for manual handling. Dashboard recovery also avoids a second creation when the first creation was durably recorded. Read the recovery changes and limits.
Power Apps Code Apps: reuse saved Dataverse views
Power Apps Code Apps code library version 1.6.0 adds a way to retrieve records through a saved Dataverse query, including fetching further pages of results. Dataverse stores business records; a saved query is a reusable selection of those records, such as open customer cases.
Developers can use the new library method to reuse that selection instead of rebuilding its query in app code. The command-line tool also adds generated service support for saved queries. These are published code changes, rather than a claim that an existing app gains a new screen automatically. Inspect the Code Apps library.
Power Apps Code Apps and Copilot Managed Runtime: broader coding-agent packaging
The Power Apps Code Apps plugin and Copilot Managed Runtime plugin now include packaging intended for more coding-agent clients. A coding-agent plugin supplies reusable instructions for an AI assistant to build and change an app. Code Apps adds a Codex catalogue entry and documents loading in other compatible clients; the runtime plugin also adds portable discovery information.
Both retain important compatibility qualifications. A package file does not prove that every client can run every agent or hook. The runtime plugin records incomplete client tests and does not supply Codex-specific hooks or an architect agent. Its shared skills now inherit the model selected in the client, which can affect results, speed and cost. Both plugins remain in preview. Read the Code Apps package notes and runtime compatibility notes.
Copilot Managed Runtime: three working sample starting points
Microsoft added three Copilot Managed Runtime samples: CodeFlow for reviewing proposed GitHub code changes, Task Manager for an Azure DevOps work board, and Learning Hub for organising learning sessions and topic votes.
They demonstrate real service connections alongside app-owned information. That app-owned information stays in the browser by default. Shared storage needs additional setup through SharePoint, Dataverse or another service. The samples require setup in the user's own environment and remain part of the runtime's public preview. Explore CodeFlow, Task Manager and Learning Hub.
Power Apps model-driven apps: inspect a move before changing an environment
The Power Platform Model Apps plugin adds a read-only promotion planner. It examines the source environment, target environment and app package, then reports whether a move appears ready, should be refused, or cannot be established from the evidence.
This helps developers inspect a proposed move from development to another installation without importing the app. It is a planning tool: it does not perform the move or turn an uncertain result into approval. Inspect the promotion planner.
Power Apps model-driven apps: review and apply bulk data repairs
The Power Platform Model Apps plugin adds a workflow for repairing existing Dataverse records in bulk. It first prepares a read-only plan, then requires approval of that exact plan before applying changes. It can resume records that were not attempted and offers a checked reversal workflow.
Partial, conflicting or uncertain results are reported as failures rather than success. Reversal is not guaranteed for every write, and the tool keeps private before-and-after evidence locally. This is a data-changing operation, not just a change to an app's screens. Inspect the data-repair tool.
Power Apps model-driven apps: prepare page changes before publication
The Power Platform Model Apps plugin adds draft page uploads and draft navigation changes, plus an optional identifier for recovering the same upload after a lost answer. Developers can prepare changes to generated pages, which are screens built from code, before completing their publication workflow.
This gives page editing a more explicit preparation and recovery path. It does not make replacing an entire page tree an all-or-nothing operation: the plugin still documents that limitation. Read the page-workflow changes.
Power Apps model-driven apps: more complete downloads
The Power Platform Model Apps plugin improves downloading components it manages. It can preserve a form's required script library as an external resource and recover a flow's associated personas when their roles provide sufficient evidence. A persona describes a group of app users and their access.
The download replaces its output only after restoration and validation succeed. Some blocked components are saved separately for review, and the documented download gaps remain. This improves recovery of an app description without claiming a complete copy of every app component. Read the download changes.
Copilot Managed Runtime: further reports of apps failing to open
A second reporter described a Copilot Managed Runtime app that previewed successfully but returned a missing-route error from its published play link. Microsoft requested network evidence and is investigating.
These are corroborated user reports, not a confirmed platform-wide outage. They show why a successful build or deployment message alone does not establish that affected users can open the resulting app. No confirmed fix appears in the checked thread. Read the reports and investigation.
Keep up with AI first development with Power Squared on YouTube.
Comments