Environment Groups is a feature to let you club the environments of your choice together in order to govern them commonly and easily with Rules for the environments.
The Rules as of now which you can govern commonly for the grouped Environments are –
- Sharing controls for Canvas Apps
- Usage Insights
- Maker welcome content
- Solution checker enforcement
- Backup retention
- Enable AI-generated descriptions (preview)
Let’s see how you can do this!
Environment Groups
Here’s how you can use Environment Groups in Power Platform Admin Center given that you have the correct Dynamics 365 Admin privileges –
- You’ll see in the Power Platform Admin Center that Environment Groups is its own section.

- Here, can you can click on Create a group as the button suggests and It’ll let you create a Group.

- Next obvious step is to simply give it a Name and Description.

- Once done, you’ll be able to select Environments to be added to the Group you just created.

- Then, select the ones which are relevant to be added to this group. Once done selecting, click on Add environments.

- Next, you’ll need to turn on the Managed Environment Modes for the selected environments. If all selected already have Managed Environments feature turned on, then they’ll simply be added further. In order to understand Managed Environments feature, you can refer to this post – Enable Managed Environments in Power Platform Admin Center

- It takes a few moments to turn on Managed Environments, then you can finally click on Add Environments to add them to the Group.
As you see in the notification area, it takes a few moments to add the environments.
- Once the processing has been completed on the backend, the environments will be added.

Rules for Environment Groups
Now, let’s see how you can commonly set Rules for the environments in the Environment Group –
- You’ll see the tab called as Rules. Once your environments are added, you can go to this tab to look at the Rules you can change and apply.

- You’ll see that by default, the rules remain as is and are not commonly applied. Let’s modify Backup Retention rule at first.
Once you select a Rule, you’ll get to Edit it.
- Once you Edit, for example, Backup Retention – you’ll see the default values which you can change in order to commonly apply to the environments in the Environment Group.

- Now, I’ll change it to 21 Days, as an example. Then, click Save.

- Let me change another rule.

- Now, you’ll see that the changed Rules will have star mark on it and are marked as bold.

- Now, when you click Publish, it takes a few moments for the Rules to be published and you’ll see the last published rules once applied.

And here’s the latest status once changed.
In order to fully understand the capabilities and limitations of the Environment Groups, follow this Microsoft article on the same – https://learn.microsoft.com/en-us/power-platform/admin/environment-groups?WT.mc_id=DX-MVP-5003911
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!