Every new maker seems to land in Default and start building agents next to production apps. Can we automatically send them to personal developer environments — and what does that cost us in Managed Environments / licences?

Environment routing, managed developer environments, sharing limits — Steady before Default becomes the agent landfill.

Should we route Copilot Studio makers out of the Default environment?

You’re right to worry about Default. It’s the shared kitchen where everyone cooks — fine for experiments until someone’s agent shares connectors with last year’s unmanaged flow.

Here’s what’s going on. Environment routing in the Power Platform admin centre (Manage → Tenant settings → Environment routing) is a premium governance feature that can automatically send makers to their own personal developer environment when they open Copilot Studio (also Power Apps / Power Automate). You turn routing on per product portal, then define rules for Everyone or selected security groups, each pointing at an environment group so new developer environments inherit group rules. Routed environments are managed by default, with preconfigured sharing limits (no security-group sharing; share with up to five individuals), Solution Checker on Warn, and usage insights on. Makers become admins of their personal environment and can still switch to Default or other environments. If provisioning fails, they fall back to Default. Developer environments don’t consume tenant Dataverse capacity quota; running assets in a managed developer environment still needs the usual premium licensing story — create/preview is lighter than run. Multi-rule routing lets different cohorts land in different groups.

This is Steady before scale for maker sprawl: Pane 04/05 (Security / GRC) own where agents are born before Pane 07 Cost argues about credits. Default stays a controlled shared space — not the only door.

Options that actually work:

Route Copilot Studio makers to a governed environment group. Enable routing for Copilot Studio, rule for the maker security group, group rules for DLP, AI features, and ALM. Best Steady posture for most organisations.
Route Everyone, leave Default locked down. Simple; watch licence and sharing-limit friction when someone tries to co-build. Pair with maker welcome content explaining the personal sandbox.
Leave routing off; police Default with DLP alone. Possible; still leaves name collisions and shared Dataverse risk. Weaker for agent programmes.
Assume routing deletes Default risk. It doesn’t — makers can switch back. Keep Default policies tight.

12 Panes action / comms: Tell makers: your first Copilot Studio landing is a personal sandbox — production agents still promote through the approved environment path. Leadership: routing is how we stop Default becoming the agent landfill without banning makers.

Benefits / risks: Personal sandboxes reduce collision and inherit group DLP; managed-developer run paths need premium clarity, sharing limits frustrate pair-building, and failed routing silently returns people to Default. Non-managed developer environments you already own are unaffected — inventory those separately.

I’d suggest this week: pick the maker cohort security group, create or choose an environment group with your Studio DLP baseline, enable Environment routing for Copilot Studio only, and pilot before “Everyone.” You’ll have a calmer Default when new agents start life in a named, managed space.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer