Many organizations start building agents in Microsoft Copilot Studio inside the Default environment. This can quickly create governance and management challenges.

In this video, I explain why makers should avoid developing in the Default environment and how administrators can configure environment routing in Power Platform Admin Center to guide makers into a better setup.

You will see how admins can enable environment routing so that when makers open Copilot Studio, they are automatically directed to their personal developer environment. If a maker does not already have one, the platform provisions a new developer environment for them.

I also demonstrate how administrators can select an environment group during the routing configuration. This allows newly created environments to be automatically placed in that group and inherit its governance rules.

This setup helps organizations establish a cleaner development structure, prevents makers from building agents in the Default environment, and supports better application lifecycle management practices for Copilot Studio solutions.