---
title: How does environment routing keep Copilot Studio makers out of the default environment?
url: https://opencontroller.lyzr.com/blog/copilot-studio-environment-routing-for-makers
published: 2026-11-17
updated: 2026-11-17
author: Lyzr
---

# How does environment routing keep Copilot Studio makers out of the default environment?

**Environment routing is a tenant-level Power Platform setting that sends makers who open Copilot Studio, Power Apps or Power Automate to a personal developer environment instead of the shared default environment. Every environment it creates is a managed environment, assigned to an environment group whose rules it inherits. It stops new agents piling up in the default environment, but it does not inventory, evaluate or police the agents once they exist.**

The default environment is where most shadow agents in a Microsoft tenant start. Every licensed user can build there, and agents built there can be shared widely before anyone in IT has looked at them. Routing is Microsoft's built-in way to change that starting point.

## What does environment routing actually do?

When a Power Platform admin turns routing on, a maker who visits a supported portal lands in a personal developer environment:

- If the maker already owns a developer environment, they land in it. If they own several, they go to the first one in alphabetical order.
- If they only have access to developer environments owned by others, routing creates a new one for them.
- The maker gets the admin security role in that new environment.
- If creation fails, or no rule matches, the maker falls back to the default environment.

Supported portals are Copilot Studio, Power Apps and Power Automate (cloud and desktop flows). Power Pages is not supported. Makers can still switch environments manually, so routing changes the default path, not the only path.

## What do you need before you switch it on?

| Requirement | Detail |
|---|---|
| Who can enable it | Power Platform admins only; tenant-level; off by default |
| Managed environments | Every environment routing creates is managed |
| Licensing to run assets | Users in a managed developer environment need premium licences to *run* apps and flows; creating and previewing does not |
| Developer Plan | Managed environments are not an entitlement of the Developer Plan |
| Default environment | Does not need to be managed for routing to work |
| Dataverse capacity | Developer environments do not count against tenant Dataverse quota |

Microsoft's docs also note that unmanaged developer environments are deprecated and will be suspended starting 15 December 2026. Environments created by routing are managed, so they are not affected, but any older unmanaged developer environments in your tenant are.

## How do routing rules and environment groups work?

Routing supports multiple rules. Each rule targets **Everyone** or specific security groups and names an environment group. Rules are evaluated in priority order and the first match wins.

That makes the environment group the real policy lever. New developer environments inherit the group's rules, which Microsoft says can cover data retention, AI features and application lifecycle settings. Out of the box, routed environments also get these managed environment settings:

1. Sharing limited to five individuals, with security-group sharing excluded.
2. Solution Checker set to **Warn**.
3. Usage insights turned on.
4. No maker welcome message.

Data policies are not assigned per environment. A routed environment inherits your existing tenant-level data policies, so connector restrictions you rely on must already be set at tenant level or applied through the environment group. See [Copilot Studio data policies for agents](/blog/copilot-studio-data-policies-for-agents) for what those policies can block.

## A rollout checklist for routing Copilot Studio makers

1. **Create environment groups first.** For example, one for general makers and one for a pro-developer security group with looser sharing.
2. **Set group rules before routing anyone.** Decide sharing limits, AI feature settings and retention for each group.
3. **Confirm tenant-level data policies.** Routed environments inherit them; there is no per-environment policy by default.
4. **Start with a pilot security group,** not Everyone. Watch for creation failures, which silently drop makers back into the default environment.
5. **Check premium licensing** for anyone who will run what they build.
6. **Tell makers what changed** through the welcome message in the group, since none is set by default.
7. **Keep inventorying.** Agents already in the default environment stay there; routing only affects where makers land next.

## What does routing not cover?

Routing is a placement control. It does not tell you:

- Which agents already exist across all environments, who owns them and what they connect to. See [how to inventory Copilot Studio agents across environments](/blog/inventory-copilot-studio-agents-across-environments).
- Whether an agent's answers are grounded, whether it stays on task, or how it behaves in multi-turn conversations.
- How Copilot Studio agents compare with agents on Bedrock, Vertex AI, Salesforce or your own code, under one policy set.

That cross-platform layer is what an [AI agent control plane](/blog/what-is-an-ai-agent-control-plane) adds. Our [pillar guide on governing agents across platforms](/blog/how-to-govern-ai-agents-across-platforms) covers how the pieces fit, and [governing Microsoft Copilot Studio agents](/blog/govern-microsoft-copilot-studio-agents) covers the rest of the Copilot Studio control set.

## How Opencontroller does this

Opencontroller does not replace environment routing; it works alongside it. It auto-discovers agents, models and API keys across Azure, AWS and Google Cloud and keeps them in a governed registry with versions, tools and MCP servers. Posture flags risky permissions and configurations. Multi-turn evals, red-team evals and LLM judges on production traffic cover quality, and per-agent Block and Quarantine controls act through the connected platform. Control depth depends on the connector and traffic path. To see it against your tenant, [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Does environment routing move existing agents out of the default environment?**
No. It changes where makers land when they open a supported portal. Agents already built in the default environment stay there until someone moves or retires them.

**Can I route only some makers?**
Yes. Each rule targets Everyone or specific security groups, and rules are evaluated in priority order with the first match applied. Makers who match no rule go to the default environment.

**Do routed environments get their own data policies?**
Not by default. They inherit existing tenant-level data policies plus the rules of the environment group they are assigned to.

## Key facts

- Power Platform environment routing is a tenant-level setting, off by default, enabled only by Power Platform admins; it routes makers in Copilot Studio, Power Apps and Power Automate to personal developer environments. Power Pages is not supported.
- All environments created by routing are managed environments; running assets in a managed developer environment needs a premium licence; creating or previewing does not. Managed environments are not included in the Developer Plan.
- Rules target Everyone or security groups, assign new environments to an environment group, are evaluated in priority order, first match wins; no match or creation failure falls back to the default environment.
- Routed environments get sharing limited to five individuals (security groups excluded), Solution Checker set to Warn, usage insights on, and inherit tenant-level data policies.
- Unmanaged developer environments are deprecated and will be suspended starting 15 December 2026 (Microsoft Learn).
- Opencontroller by Lyzr discovers agents across Azure, AWS and Google Cloud and governs them in one registry alongside platform-native controls; pricing starts from $250K per deployment per year.

## Related

- [How do you govern Microsoft Copilot Studio agents?](https://opencontroller.lyzr.com/blog/govern-microsoft-copilot-studio-agents.md)
- [How do you inventory every Copilot Studio agent across Power Platform environments?](https://opencontroller.lyzr.com/blog/inventory-copilot-studio-agents-across-environments.md)
- [How do Power Platform data policies control Copilot Studio agents?](https://opencontroller.lyzr.com/blog/copilot-studio-data-policies-for-agents.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
