Power Platform Community Forum Thread Details

I am looking for real experiences regarding Copilot Studio Governance.

I understand the idea of providing PDE to all my users - but how do you manage the billing of those environments? The provisioning is done through environment routing but how do you allocate COpilot Credit capacity if users are publishing and using agents (even just for themselves ?)
how do you manage 20K Personal Dev Environments at scale ?

I you create managed env for Copilot studio, how do you restrict the users which can create agents (with the env maker role) to also create Preimum Power Automate FLows and Power Apps ?

thank you very much for any feedback on Advanced copilot studio REX

Categories:

General topics

For PDE billing, we don’t try to manage environments individually. Environment groups are used for organization, but actual Copilot usage is handled at the tenant level or via Azure PAYG. All usage flows into a single subscription, and we rely on Azure Cost Management for tracking/showback, since there’s no native way to allocate capacity per environment or group.

For managing PDEs, we treat them as low-governance environments. We use auto-cleanup (e.g., 90 days) and the CoE Starter Kit for visibility and monitoring rather than strict control.

On restricting makers, this is a known limitation — Environment Maker can’t be scoped to Copilot only. The practical approach is: