Complete ALM: ship Power Platform from dev to prod

The big picture

A reliable Power Platform delivery has four moving parts: environments (dev / test / prod), the app schema (in solutions), the automation (Power Automate flows) and the data (reference vs transactional). Get the boundaries right and releases stop being scary.

Golden rule: author only in dev, promote through test, and never edit production by hand.

The three steps, in order

1. 11) Set up the deployment pipeline — package the app in a solution and promote dev → test → prod with Power Platform Pipelines (see the deployment-pipeline guide).
2. 22) Make flows portable — use connection references and environment variables so flows survive the move, then turn them on in the target (see the flows-across-environments guide).
3. 33) Move the right data — migrate reference/config data with the Configuration Migration Tool or Dataflows, and never copy transactional data (see the data-transfer guide).

Before every production release

1. 1Take a manual backup of the target environment.
2. 2Deploy the solution as managed, then validate in test/UAT.
3. 3Map connection references and environment variables for the target.
4. 4Run reference-data migration if the schema changed, then turn flows on and smoke-test.