Copilot Managed Runtime has been generally available since the announcement made at Ignite on November 17, 2026, and it is starting to roll out to tenants. The Apps > Overview page of the Microsoft 365 admin center already shows an environment group created without any action on your part. This article explains what that group enforces, who can build and run apps, and what you need to configure before the first makers get started.
What Copilot Managed Runtime hosts, and where the rollout stands
Copilot Managed Runtime hosts Microsoft 365 business applications that inherit the organization's governance, security and compliance controls from the moment they are created. Whether an app is built in Copilot Cowork, Microsoft Copilot Studio (formerly Power Virtual Agents), Copilot Code or with the SDK, it runs in a Microsoft-hosted environment. It authenticates with Microsoft Entra ID and remains visible to administrators in the Microsoft 365 admin center.
The timeline deserves to be set out precisely. The Tech Community post states that the service had been in public preview since September 2026 and moves to general availability at Ignite.
September 2026
Public preview
Copilot Managed Runtime is available in public preview.
November 17, 2026
General availability announced
Microsoft announces general availability at Ignite, along with new previews: Microsoft Fabric integration, local creation of Copilot Studio agents and workflows, and Code Agents in early access.
Mid-November to mid-December 2026
Rollout to tenants
Message center post MC1558033 indicates a rollout starting in mid-November 2026 and expected to finish in mid-December 2026.
Documentation and behavior may diverge
Several Microsoft Learn pages still carry the "preview" label, notably the FAQ and the security and compliance page. During the rollout, what you see may differ from one tenant to another. In addition, Microsoft announces on November 17, 2026 that Copilot Code will become generally available "in the coming weeks", even though Managed Runtime already is.
The Apps > Overview page: reading each element
The Apps > Overview page is the admin entry point. Here is how to interpret what it displays when you open it.
- "App governance group created": this is the default environment group. Microsoft manages it, it cannot be deleted, and it is provisioned automatically when the first app is created or when an admin first visits the Managed Runtime experience. It corresponds to the "Environment groups configured: 1" indicator.
- Inventory 0 and Daily active users 0: no user has built a managed app yet. As soon as one does, Apps > All apps will list them, with a 15-minute display delay. The default columns are Name, Owner, Status, Location, Environment group and Created on.
- "Set up governance" / "Set up now": this option disappears once governance is configured. The default configuration is triggered only once, by whichever of two actions comes first: a maker creates their first app, or an admin selects the option. No prior action is therefore needed before makers start.
The page's four marketing bullets (ready-to-use rules, overview of key apps, security-oriented environments, health alerts) do not match any term in the Microsoft Learn documentation consulted. The most plausible reading, which remains an interpretation, links them to the default group's rules, the Usage tab, personal managed environments and the alert rules of the Monitor tab.
That Monitor tab, in an app's detail panel, exposes the open success rate, the number of sessions, the time to interactive and data request metrics. Alert rules are in preview there, with review periods of 1 hour or 24 hours.
Who sees what in All apps
The Global Administrator and Power Platform Administrator roles have full access: view, delete, block. The AI Administrator, AI Reader and Global Reader roles are read-only. For tier-1 support or an auditor, a read-only role is enough, which respects least privilege. The Microsoft Learn page Understand roles and responsibilities details the recommendations.
What the default environment group enforces
The default group applies a restrictive policy with no configuration. It covers four areas.
19
First-party connectors allowed (Entra ID authentication only)
Microsoft Learn
12
First-party MCP servers allowed
Microsoft Learn
| Area | Default behavior |
|---|---|
| Routing | Each maker gets their own personal environment |
| Connectors | Allow list curated by Microsoft; free-form HTTP requests, Excel Run script and arbitrary calls to Dataverse Custom APIs blocked |
| Sharing | Sharing with the whole organization enabled, sharing with guests disabled |
| Content security policy | Enforced and restrictive |
To change these rules, open Apps > Settings > Environment groups and edit the relevant rule. The page Review default governance settings for apps also details the allow list of connectors and MCP servers, as well as the Fabric option.
Taking full control of the connector policy stops Microsoft updates
If you take full control of the connector policy, Microsoft stops updating it automatically. New connectors or MCP servers added to the curated list will no longer arrive on their own: plan for an owner and a periodic review.
Who can create apps from day one
Four authoring tools coexist, with very different default settings. The most open is Copilot Cowork, which makes it the first decision point.
| Authoring tool | Default | Control |
|---|---|---|
| Copilot Cowork | Enabled | Build apps in Copilot setting: disable or limit to users or groups |
| Copilot Code | Restricted | Reserved for users in a Copilot Code spending policy |
| Copilot Studio | Enabled | Disable or limit to security groups via Power Platform CLI |
| CLI / SDK | Disabled | Environment group settings |
An organization with several hundred seats could, for example, limit Cowork to a pilot group of ten volunteer makers. It then observes the inventory and consumption before widening access. This approach avoids discovering the bill and the usage after the fact. For the no-code side, see our article on Copilot Cowork and building apps without code.
Licensing and costs: building and running are not paid the same way
The model relies on consumption-based billing in Copilot Credits, with a clear separation between building and running. The Microsoft Learn licensing FAQ sets out the rules.
| Need | What is required |
|---|---|
| Build with Cowork or Copilot Code | Microsoft Copilot license, plus Copilot Credits billed through a spending policy |
| Build with Copilot Studio | Billing through the environment |
| Build, create and deploy with the CLI | No license required |
| Run an app | Power Apps Premium, or a spending policy that includes Copilot Managed Runtime |
Three clarifications avoid unpleasant surprises on the runtime side. A Microsoft 365 Copilot license is not enough. The Power Apps rights included in Microsoft 365 and Dynamics 365 (E3, E5) do not cover these apps. A user who has both Premium and a spending policy consumes their license first: there is no need to exclude Premium holders from the policy.
The runtime cost is 0.1 Copilot Credit per API call. The message center suggests a modest per-user limit, for example 100 Copilot Credits (about 1 US dollar). The spending policy is created under Copilot > Cost management.
What happens without coverage during the preview
An uncovered user first sees a warning. Their access is then blocked after 20 operations or 5 minutes of use. They can use Request more, and the admin processes requests in Cost management. Per-user limits are reset on the 1st of each month.
0.1
Copilot Credit consumed per API call
Microsoft Learn
20
Operations before an uncovered user is blocked (preview)
Microsoft Learn
Routing: the pitfall that blocks makers
A maker who matches no routing rule can neither get a personal environment nor create an app. The apps FAQ offers three remedies: add the maker to a targeted group, modify an existing rule, or add an "Everyone" rule.
An apparent contradiction clouds the reading. At general availability, environment routing is enabled, and a tenant with no rules sends users to personal environments in the default group. Yet existing rules do not change. Probable reading, to verify in your tenant: with no rules, the default applies; with pre-existing rules, only the users they cover are routed.
Check routing coverage before opening up creation
If your tenant already has routing rules, test with a representative maker account. A user outside the rules will have their creation blocked, which looks like a licensing failure when it is actually a routing failure.
Frequently asked questions
Does a Microsoft 365 Copilot license allow running a managed app?
No. Running requires Power Apps Premium or a spending policy that includes Copilot Managed Runtime. The Power Apps rights included in Microsoft 365 and Dynamics 365 (E3, E5) do not cover these apps either.
Should Power Apps Premium users be excluded from the spending policy?
No. A user who has both Premium and a policy consumes the license first. Exclusion is therefore not necessary.
Where do end users open their apps, and where do admins find them?
End users go through the managedapps.cloud.microsoft portal. The CLI and SDK are separate from this portal. On the admin side, the inventory is in Apps > All apps, and the environment hosting an app can be found in the Power Platform admin center (Manage > Inventory, item type Copilot Managed Runtime).
Does the CLI require a license to create and deploy?
No. According to the Microsoft Learn licensing FAQ, the CLI requires no license to create, build and deploy. It is, however, disabled by default in the environment group.
Three decisions to make before the first apps
The default group already exists: the challenge is to decide who builds, who runs and who pays. For broader agent governance, our article on the three-zone model provides a complementary framework.
Next actions
- Open Apps > Settings > Environment groups and review the default group's rules
- Decide whether creation via Cowork stays open to everyone or is limited to a pilot group
- Create a spending policy under Copilot > Cost management so that makers and users are neither blocked nor surprised by the bill
- Test routing with a real maker account if rules already exist
- Assign read-only roles (AI Reader, Global Reader) to profiles that only need to view the inventory
If your organization wants to limit financial risk, start with a pilot group and a low per-user limit. If it favors fast adoption, leave Cowork open, but monitor Apps > All apps during the rollout, which should finish in mid-December 2026. Our overview of Copilot Managed Runtime gives the runtime context.
Going further
- Copilot Managed Runtime overview for admins: default governance, authoring options, licensing and billing.
- Copilot Managed Runtime licensing FAQ: licenses required to build and run, recommended spending policy.
- General availability announcement: details of the new previews (Fabric, agents).
- Review default governance settings for apps: default environment group, allow list, Fabric option.
- Understand roles and responsibilities: read and management roles and least privilege.



