Configure Development And Target Environments

Imported reference from Matthew Devaney's blog for learning purposes. Original: https://www.matthewdevaney.com/the-complete-power-platform-pipelines-alm-setup-guide/configure-development-and-target-environments/. Author: Matthew Devaney.

Configure Development And Target Environments

Power Platform Pipelines must be connected to a development environment and one or more target environments. A development environment is where makers develop solutions. Target environments are where solutions get deployed to. For example, the test and production environments. Before creating the pipeline we will add environments to the pipeline configuration app. Table of Contents

“>Open The Deployment Pipeline Configuration App

Add The Development Environment To The Pipelines App

Get The Environment ID From Developer Resources

Setup The Test Environment As A Target Environment

Configure The Prod Environment As A Target Environment

Open The Deployment Pipeline Configuration App

Go to the Power Platform Pipelines host environment and open the Deployment Pipelines Configuration app.

Add The Development Environment To The Pipelines App

First, we will add a development environment . Go to the Environments page and press the New button.

Fill-in the environment details then press the save button. The validation status will switch to pending. Name – ALM Tutorial (Dev) Owner – set to your own user account

Environment Type – Development Environment

Environment ID – the environment ID from the environment’s developer resources menu.

After a few moments pass press the refresh button. The validation status will be updated to success.

Get The Environment ID From Developer Resources

The environment id is necessary to setup the developer and target environments in Power Platform Pipelines. Go to any environment, press the settings button and select developer resources.

The unique identifier of the environment is shown as Environment ID.

Setup The Test Environment As A Target Environment

Continue on with adding the Test Environment as a target environment. Target environments are environments where managed solutions are deployed to.

Add the environment details then press the save button. Wait for the environment to pass validation. Name – ALM Tutorial (Test) Owner – set to your own user account Environment Type – Target Environment

Environment ID – the environment ID from the environment’s developer resources menu.

Configure The Prod Environment As A Target Environment

Add a new environment one more time. Supply the Production environment details then press the save button. Wait for the environment to pass validation. Name – ALM Tutorial (Prod) Owner – set to your own user account Environment Type – Target Environment

Environment ID – the environment ID from the environment’s developer resources menu.

All environments have now been added to the Deployment Pipeline Configuration app. The Developer environment is included as development environment. And the Test & Production environments are target environments. Next Steps

Continue to the next steps in the Power Platform Pipelines & ALM Setup Guide.

Next: Create A Power Platform Pipeline >> Did You Enjoy This Article? 😺

Subscribe to get new Copilot Studio articles sent to your inbox each week for FREE Enter your email address Sign Me Up Questions?

If you have any questions about Configure Development And Target Environments please leave a message in the comments section below. You can post using your email address and are not required to create an account to join the discussion.