In case you already have created Environment Groups, you can set some rules to divert how environments are created to Environment Groups.
If not, you might want to first take a look at a post on Environment Groups in Power Platform Admin Center!
Environment Routing is feature to redirect existing/new Makers to their own Developer environment when logging into the Maker Portal (https://make.powerapps.com/)
Routing in Environment Groups
Here’s how you can set Routing rules in Environment Groups in Power Platform Admin Center –
- Given that you have the correct Dynamics 365 Administrator privileges, you should be able to see the Environment Groups section and also see button to set the Environment Routing.

- In Environment Routing, you can choose to enable to Create personal developer environments for makers option.

- When you turn it on, you can choose to enable it either for All makers or for new makers only. I’ll enable it for All makers for this example.

- Now, I’ll select the Environment Group where the routing should happen to – for this, I’ve created a CFT Developers Environment Group.

And Save.
Routing to Developer Environments
Let’s consider this example to demonstrate how Routing will work –
- When a developer logs into the Maker Portal (https://make.powerapps.com/), a setup will load for a few moments the user, let’s say, Amit Prajapati in this example, will be redirected to his own Portal –

- And if you look at the list of the Environments in the Group you selected for Routing, you’ll see that Amit’s Environment is now created.

- Now, another User Ethan Rebello also logs into the Maker Portal. He too will be redirected to his own environment.
And the same will be added to the Group as well.
Every developer will have access to only their own Developer environments and other’s won’t be able to access them.
Hope this was useful!
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate
Thank you!