Copilot Studio app creation and governance walkthrough

Key insights

• The video demonstrates app creation in Copilot Studio's new experience.
• The walkthrough describes the app experience as part of Copilot Managed Runtime.
• The demonstration covers governance in Power Platform Admin Center.
• The video includes environment routing and environment groups.
• It shows how the app appears in Microsoft 365 Apps and how to disable the Copilot Studio experience.

Daniel Christian [MVP] recently published a 21-minute walkthrough of app creation using the GitHub Copilot harness in Copilot Studio. The video follows a build demonstration and then turns to administration, including controls in Power Platform Admin Center (PPAC) and how environment groups appear in Microsoft 365 Apps. Its practical takeaway is that app creation is only one part of the experience: administrators also need to understand the access and environment controls shown in the walkthrough.

What's new

The video focuses on an Apps feature in what the description calls Copilot Studio's new experience, using the GitHub Copilot harness. Christian says the demonstration explains how this is part of the Copilot Managed Runtime service. The material provided does not describe the harness architecture in detail or specify the app's technical components.

The session moves from entering a prompt to viewing the resulting app, then covers administration. Its chapter outline identifies app building at 01:09, adding the prompt at 03:41, viewing the app in Microsoft 365 Apps at 11:08, and governance in PPAC from 14:53. It also lists environment routing and environment groups as topics.

Why it matters

For makers, the walkthrough offers a view of the described prompt-led app-building process rather than a purely administrative overview. It can help a practitioner see the sequence presented by the publisher: start an app, provide a prompt, and inspect the resulting experience. The description does not provide enough detail to assess what kinds of apps it supports or how much editing a generated app requires.

For administrators, the notable point is that the video pairs app creation with governance. It explicitly shows controls in PPAC and discusses environment routing, as well as disabling the experience in Copilot Studio. These topics may be relevant to teams deciding who can create apps and how app activity is managed, but the description does not state the exact configuration or policy choices shown.

For end users, the chapter about viewing an app in Microsoft 365 Apps signals that the demonstration considers how the app is surfaced beyond the build interface. The provided material does not explain what users can do there, how sharing works, or whether additional licensing is required. No rollout stage or tenant availability is stated in the video description.

How it works

The chapter list suggests a practical sequence, though it is not a detailed transcript of every action or screen. Christian begins with app building, adds a prompt, and later shows the app in Microsoft 365 Apps. He then turns to the admin experience and environment controls.

1. Start building an app in the Copilot Studio experience.
2. Add a prompt as part of the creation demonstration.
3. View the resulting app in Microsoft 365 Apps.
4. Review governance in PPAC, including environment routing and environment groups.
5. See the option to disable the experience in Copilot Studio.

The description says the session explains the relationship to Copilot Managed Runtime and demonstrates governance through PPAC. It does not provide step-by-step configuration values, so readers should treat this as an overview rather than a complete deployment procedure. The documentation links below are the appropriate place to check the administrative details referenced by the publisher.

Limitations and open questions

The available source material is a video description with chapter headings, not a full transcript of the demonstration. As a result, it identifies the features and administration subjects covered but does not establish exactly what prompt Christian used, what app was generated, or how the screens behaved. It also does not confirm whether the functionality is generally available, preview-only, or limited by a particular license.

The description names Copilot Managed Runtime, PPAC, environment routing, and environment groups, but it does not spell out the respective settings or their effects. Nor does it explain any restrictions, dependencies, or prerequisites. Readers should verify current controls and eligibility in Microsoft's documentation before applying the approach in a tenant.

Sources

• Daniel Christian's app-building and governance walkthrough
• Microsoft documentation on managing apps
• Microsoft documentation on what's new in Copilot Cowork
• Microsoft documentation on scoping access to Copilot Studio app creation

Frequently asked questions

What does the video demonstrate?

It demonstrates creating an app in Copilot Studio's new experience using the GitHub Copilot harness, then reviews the app and related governance topics.

Which admin controls are covered?

The chapter list names governance in Power Platform Admin Center, environment routing, environment groups, and disabling the experience in Copilot Studio.

Does the video confirm availability or licensing?

The provided description does not state a rollout stage, availability conditions, or licensing requirements.