Power Platform ALM: solutions, environments and pipelines for Power Automate flows
Diesen Beitrag auf Deutsch lesen
Step-by-step guide to moving Power Automate flows from dev to test and production with solutions, connection references, environment variables and Pipelines.
TL;DR
Flows should be built in a solution with a dedicated publisher and moved through separate dev, test and production environments. Connections never travel; connection references get a connection per environment, and environment-specific values like SharePoint sites belong in environment variables. Test and production receive managed solutions via Pipelines, which require Managed Environments.
Original by Anders Jensen, on andersjensen.org. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Build flows in a solution with your own publisher and use connection references plus environment variables, because the Default Solution cannot be exported and hardcoded values break on import.
- Admins/CoE: Provide dev, test and production environments with Dataverse, enable Managed Environments for Pipelines, and plan for unmanaged developer environments being retired from November 2026.
- Security/Compliance: Remove current dev values from solutions before export and use Secret variables backed by Azure Key Vault for credentials.
- Leadership/Business: Support separate dev and test environments, since fixing live flows where colleagues work puts operations at risk.
Frequently asked questions
How do I move a Power Automate flow from dev to production using a solution?
Build the flow in a solution in dev, export it as managed, and import it into test and production via Pipelines. Connections and environment values must already exist in each target.
Why does a Power Platform solution ask for connections again after import?
Because a connection is a personal sign-in and is never part of the solution. The connection reference points to it, and you choose a connection for each environment at import.
Do Power Platform Pipelines require Managed Environments as targets?
Yes, Pipelines deploy managed solutions and require the target environments to be Managed Environments. Enable managed on test and production before deploying.