Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
All tenants have routing for Copilot Managed Runtime selected by default. Admins must manually enable routing for other products.
This article explains what environment routing for Copilot Managed Runtime means for your tenant and makers, and how it works with existing environment routing rules you set up.
Environment routing rules
Review the following routing behavior and requirements for tenants that use Copilot Managed Runtime.
Environment routing for Copilot Managed Runtime is automatically enabled in all tenants. You can't change this setting.
- Admins must enable routing for other products manually.
- When Copilot Managed Runtime is the only product enabled for routing, makers using Power Apps, Power Automate, or Copilot Studio aren't routed to their personal developer environments. They can continue to build in the default environment or any other environment where they have maker permissions.
When there are no routing rules configured in the tenant, a new routing rule is created automatically that routes Everyone in the tenant to their own personal developer environments.
- A new default environment group is also created automatically, and rules specific to Copilot Managed Runtime are applied to this group.
- If the tenant already has routing rules, no changes are made to them. In this case, only makers who are part of the security groups used in routing rules can build apps hosted on Copilot Managed Runtime. All other makers are blocked until admins of these tenants create a new Everyone routing rule or add makers to security groups used in routing rules.
- Admins can't delete routing rule that routes Everyone to an environment group.
- Routing rule targeting Everyone must be the last rule in the priority. Any tenants with routing rule configuration that placed a routing rule targeting Everyone above a security group must adjust the priority before making any further changes.
- New routing rules can't be created without selecting an environment group.
Personal developer environments created for Copilot Managed Runtime are managed environments by default.
- Auto claim isn't applicable for makers who use these environments only to create apps hosted on Copilot Managed Runtime. No premium licenses are required in this case.
- Auto claim is applicable if makers create Power Apps, Power Automate, or Copilot Studio in their personal developer environment created for Copilot Managed Runtime. Premium licenses might be required for the maker in this case.
- Environments created for Copilot Managed Runtime don't have Dataverse. Makers or admins can manually add Dataverse to these environments from the Power Platform Admin Center.
- Dataverse is automatically added to the personal developer environments when the maker is routed to this environment from Power Apps, Power Automate, or Copilot Studio maker portals due to their routing configuration.
Frequently asked questions
Is automatic environment creation expected?
Yes. Provisioning personal developer environments is part of the documented Copilot Managed Runtime experience. Creation that appears inconsistent with your configured access controls requires further investigation.
Will the Environment Creation: Developer tenant setting block automatic environment creation?
No. That tenant setting only impacts manual creation of developer environments. Environment routing is unaffected by this setting.
Can I control where the Copilot Managed Runtime apps are created?
Yes. You can manage this setting from the Microsoft 365 admin center as a Global Administrator or Power Platform Administrator.
- Sign in to the Microsoft 365 admin center as a Global Administrator or Power Platform Administrator.
- Go to Apps > Overview > Set up app creation spaces.
- Review Copilot Studio app-creation access. You can turn off this creation path or restrict access to selected Microsoft Entra security groups, as described in the administrator guide.
- Review Copilot Cowork separately. Its app-building availability is governed through Frontier onboarding and Cowork access, not the Copilot Studio setting.
- Refresh open Copilot Studio pages after changing settings. Existing tabs can cache settings for up to 15 minutes.
These controls manage app-creation access; they don't delete existing environments or turn off Copilot Managed Runtime routing itself.
Do these environments contain Dataverse?
Not initially. Environments created for Copilot Managed Runtime don't include Dataverse by default. You can add Dataverse later, including through other maker experiences under applicable routing configurations.
Should I delete the environments?
Review ownership, apps, and dependencies before deleting an environment. Don't assume it's unused solely because its creation was unexpected.
What if environments continue appearing after I change access settings?
Contact Microsoft Support with the tenant ID, affected environment IDs, UTC creation times, originating app-building experience, and the settings you applied.
Will routing move Personal Environments from one environment group to another.
If a personal environment is in a group, it stays there. However, if the personal environment is not in any group, it will be added to the environment group matching the environment routing rule.