managed environments

Environment Routing in Power Platform Admin Center

priyeshwagh777 Power Platform, Power Platform Admin Center , ,

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 –

  1. 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.

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

  3. 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.


  4. 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 –

  1. 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 –

  2. 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.

  3. 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 –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Environment Groups in Power Platform Admin Center

priyeshwagh777 Power Platform Admin Center , ,

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 –

  1. Sharing controls for Canvas Apps
  2. Usage Insights
  3. Maker welcome content
  4. Solution checker enforcement
  5. Backup retention
  6. 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 –

  1. You’ll see in the Power Platform Admin Center that Environment Groups is its own section.

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

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

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

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

  6. 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


  7. 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.

  8. 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 –

  1. 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.

  2. 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.

  3. 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.

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

  5. Let me change another rule.

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

  7. 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 –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Setup Power Platform Pipelines

priyeshwagh777 Power Platform, Power Platform Admin Center , , , , , , ,

Given that you need to setup Power Platform Pipelines, here’s a post for you!
This post will walk you through on how you can setup Power Platform Pipelines.

Pre-Requisites

Here’s what you need to setup in order to enable Power Platform Pipelines –

  1. You need to enable Managed Environments for the environments which need to participate in Power Platform Pipelines. Here’s a post on Managed Environment which I’ve written in the past – Enable Managed Environments in Power Platform Admin Center

    Given that all participating environments have been enabled with Managed Environments, select an Environment which is supposed to a “Host” environment where all the Pipelines master data will house and then go to it’s Dynamics 365 Apps section from Resources to install Power Platform Pipelines into that environment.

  2. Once you are in, click on Install app and then search for Power Platform Pipelines.

  3. Confirm that you are about to install this Solution.

  4. Once installed, go to Power Apps Maker Portal (https://make.powerapps.com/) and then select the Host environment in which you have installed Power Platform Pipelines on.
    Then go to Apps and you’ll see Deployment Pipeline Configuration app. Play that app!



    Let’s see how you can set the environments up first!

Setting up Environments

Here’s how you can setup your Environments in the –

  1. Once you are in the Deployment Pipeline Configuration App, go to Environments and create a New record.

  2. Then, enter all the details. Also, mention if the Environment type is Development Environment or Target Environment.

  3. Once you save the record, this the configuration will be validated.


  4. In case you are wondering how to you find the Environment ID, here’s where you’ll find the Environment ID in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments), select the environment and you’ll see the details as below –

  5. Once all the Environments are set in the Deployment Manager, here’s how it should look


Configure Deployment Pipelines

Now that your environments are set, let’s also configure the Deployment Pipelines –

  1. Go to Pipelines and create a New record.

  2. Now, fill in all the relevant information and save the record.

  3. Now, link your Managed Environments in the Linked Deployment Environment grid below. Then click on Add Existing Environments button.

  4. And once you add, they’ll appear like this while selecting them in lookups. Then click Add.

  5. Once added the Development Environments, go ahead and create new Pipeline Stages too.

  6. In the new Deployment Stage, I’ll simply tag the Production Environment and save the record to keep this example simple.

    At this point, your Pipeline is all set to Run.

    Shortly, I’ll share another post on how you can Run a Pipeline in Power Platform!

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Enable Managed Environments in Power Platform Admin Center

priyeshwagh777 Power Platform Admin Center , ,

Here’s what Managed Environments do! They provide more control on how you administer the Environments i.e. by limiting App Sharing, applying Data Policies on the environment and even how Solution Checker should allow to import solutions upon detecting critical issues (Solution Checker feature for Managed Environments is in Preview at the time of writing this post!).

Below is the snipped from Microsoft Learn Document highlighting the capabilities of Managed Environments



Further, as I explore these features more, I’ll update and add links to the posts explaining each of the features in details.

Enable Managed Environments in Power Platform Admin Center

Given that you have appropriate permissions to take administrative actions on Power Platform environments, you can navigate to Power Platform Admin Center and then in Environments (https://admin.powerplatform.microsoft.com/environments) –

  1. Select an Environment and click on the ellipses on the menu.

  2. Once you select the same, review the License implications as highlighted below –
    Here’s the Microsoft Documentation on the same – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-licensing?WT.mc_id=ppac_inproduct_env%3FWT.mc_id%3DDX-MVP-5003911

  3. Once you review the below preferences on how you want this environment to be managed, you can select the same and click on Enable as seen below –
    These will send insights in email. I’ll cover in a separate post and link here.


  4. Once everything looks good, you can Enable.

Editing Managed Environments / Disabling

Here’s how you can edit or disable Managed Environments –

  1. If you are seeing Edit Managed Environments, it means that Managed Environment is enabled for that environment.

  2. And you can disable Management Environment control using PowerShell. You can check this post which highlights how you can do so – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell?WT.mc_id=DX-MVP-5003911
    Snapshot of the document below –

Here’s Microsoft Learn documentation on Managed Environments – https://learn.microsoft.com/en-gb/power-platform/admin/managed-environment-overview?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!