Microsoft MVP (Business Application & Data Platform) | Microsoft Certified Trainer (MCT) | Microsoft SharePoint & Power Platform Practice Lead | Power BI Specialist | Blogger | YouTuber | Trainer
Copilot Studio’s Apps preview lets makers create, test, publish and share business applications that run on Copilot Managed Runtime. It is aimed at makers building internal apps around business data, as well as admins responsible for their governance. Dhruvin Shah [MVP] demonstrates the workflow by creating a student enrollment app connected to a SharePoint list.
Copilot Managed Runtime is the Microsoft-hosted environment in which these apps run. The creation experience is separate from the runtime: makers can start in Copilot Studio, while the demonstration also identifies Microsoft 365 Copilot Code, Copilot Cowork and a command-line interface as other ways to create apps for the same managed runtime.
The runtime uses Microsoft Entra ID authentication and applies organizational governance, security and compliance controls. In the demonstrated app, Copilot Studio generates an application from a natural-language description and a data source. The maker can test the result, refine it with another prompt, preview it on different device sizes, publish it and share access with individuals or a security group.
This is an app-building experience, not just a way to configure a conversational agent. In the example, the app lists student records, supports creating and editing records, and searches by name, email or phone number. Those are features of the requested sample app, not a fixed set of functions every generated app receives.
The Apps experience is marked preview in the demonstration. It is relevant to makers who want to build an internal business app from a prompt and connect it to data, and to administrators who need to inspect published apps and their governance. The maker starts in Copilot Studio, but a newly created app is placed in a Personal Development Environment (PDE), not necessarily in the environment currently open in Copilot Studio.
Building and running have separate credit and licensing requirements. The description specifies Copilot credits to build an app. To run one, users need Power Apps Premium or Copilot credits enabled on the environment. These are distinct requirements: having a way to run the app does not remove the stated credit requirement for building it. For related app-building and licensing topics, see Power Apps.
Prepare the data connection as part of the build. In the example, the SharePoint list already exists before the maker submits the prompt, and the app requests permission to connect to it during testing. The demonstration also notes that Dataverse can create a table through the same interface, while a missing SharePoint list or library may need to be created before building can continue.
The Microsoft 365 admin center is the key management location described for these apps; the demonstration distinguishes it from Power Platform admin center as the place to manage the published Copilot Managed Runtime apps. Power Platform environment groups and rules still feature in the governance model, including connector policies, but the app inventory and settings are surfaced through the Microsoft 365 admin center.
The main operational constraint highlighted is the lack of solution-based ALM for these apps. The demonstration describes no separate development, test and production environments with a solution move between them. Instead, when the maker updates and publishes, the update goes live. Teams that rely on staged releases should account for this before using the experience for an app with formal release controls.
Keep the app’s storage location and management location distinct when planning ownership. Apps are created in the maker’s Personal Development Environment, while admins review and govern them through the Microsoft 365 admin center. A SharePoint-based build also depends on the relevant list being available and connector access being approved. Before publishing, test the data operations and verify that the intended users have both access to the app and a supported way to run it.
New apps created through the Apps experience are placed in the maker’s Personal Development Environment, not necessarily the environment currently open in Copilot Studio.
Building requires Copilot credits. Running an app requires Power Apps Premium or Copilot credits enabled on the environment.
Admins can view the published app inventory and app settings in the Apps area of the Microsoft 365 admin center. Governance includes environment groups and policies such as connector controls.
The described Apps experience does not support solution-based ALM across separate development and production environments. Publishing an update makes it live.