Share
ReportHi everyone,
Please let me know if you have an answer to the below:
We have a Power Platform solution containing all the components, including Power Automate flows and their connection references.
We have pipeline releases, and the flows use connection references, and the connections to those connection references on QA/UAT/PROD are updated through deployment settings file in your Azure DevOps YAML pipeline.
Normally, when the managed solution is released from Dev to QA/Prod, the flows remain turned on automatically as expected.
The problem starts when:
- A flow was originally created by Developer A.
- Developer B later edits/updates that same flow with minor changes in Dev.
- Developer B does not create any new connection reference and does not intentionally change the connection setup.
- The flow is still on in Dev and is published.
- The managed solution is deployed via pipeline to QA/UAT/Prod.
- From that release onward, the updated flow is turned off after every deployment. We can manually turn the flow back in targeted env on click turn on button.
- However, on every subsequent deployment, the same flow is turned off again, even though the Deployment Settings and connection references appear to be correct.
I would like to make sure flows remain turned on after deployment regardless of which developer updates them in Dev.
Any suggestions would be much appreciated. Thanks.
All responses (
Answers (
79
