Governance

Associate group environments with a default pipeline

The environment group rule associates developer and sandbox environments with a selected Power Platform pipeline.

Click image to enlarge

The Default deployment pipeline rule for environment groups associates a selected pipeline with development environments in the group. In this context, ā€œdevelopmentā€ means developer or sandbox environments; the rule doesn’t turn production environments into development environments.

Requirements

You need to be a tenant administrator to configure environment group rules. Install the Power Platform Pipelines package, configure a pipelines host, and create at least one pipeline. Environments used by the pipelines need Dataverse, and target environments must be Managed Environments. Source and target environments used in default pipelines are automatically enabled as Managed Environments.

Users also need access to the selected pipelines host. The default pipeline rule shares the pipeline with users on the host environment’s default team, so check that the intended makers are included.

Configure and publish the rule

  1. In the Power Platform admin center, open the environment group and select Rules.
  2. Select Default deployment pipeline.
  3. Choose the Pipeline Host, then the Pipeline to associate with the group’s development environments.
  4. Select Save, then Publish rules.
  5. Allow up to ten minutes for the rule to apply, then verify the association from a developer or sandbox environment.

The rule associates development environments with a pipeline; it doesn’t define the pipeline’s target environments. Configure the targets separately and confirm that users can access them. A successful association is only one part of a usable deployment path.

Use it as part of an ALM design

This rule is useful when administrators want a consistent pipeline association for developer and sandbox environments in an environment group. Before applying it broadly, check that the pipeline’s target stages, permissions, solution dependencies, and deployment settings match the group’s purpose. Pilot with one group and verify that a solution can move through the intended stages.

If environment routing is also part of your setup, verify how new developer environments are assigned to groups and when group rules take effect. Don’t assume that creating a rule alone provisions an environment, configures its targets, or grants every maker the necessary permissions.

Sources

Share this tip

Did this tip help you?

Vote once and classify what made this tip valuable.

Try this now

Quick checklist to apply this tip immediately.

šŸ’¬ Comments & Suggestions

Share your thoughts, tips, or drop a useful link below.