Unanswered

Deploy Power Automate using Azure DevOps

(1) Share

Report

Posted on by Lars_Martin

I'm referring to this article:

We use exactly this approach for deploying Power Automate Flows.

There is only one missing piece we additionally use: We use a PowerShell script after importing the solution to enable all cloud flows in the solution. Otherwise they stay disabled.

Is this step missing in the mentioned article or is there a way to avoid the PowerShell script?

All responses (2)

Answers (0)

Lars_Martin on at

Like (0)

Report

Deploy Power Automate using Azure DevOps

We use a Service principal for deploying the solution to the other environments.

The Cloud Flows use connection references and during solution import we use a deployment settings file for mapping the connection references in the solution to the connections in the target environment.

However, after importing the solution we have a Powershell script in place which activates all Cloud Flows contained in the solution using an impersonation user as a Service principal is not able to activate Cloud Flows. This impersonation user is the one who owns the connections in the target environment we mapped to the connection references. Otherwise activating would fail.
tmms on at

Like (0)

Report

Deploy Power Automate using Azure DevOps

What user are you deploying the solutions under? Do you use connection references? A common scenario where flows are deployed in disabled state is relate to connection/user problems.
This article explains how to avoid this:

Connection references and disabled flows – what’s the connection? – It Ain't Boring (itaintboring.com)

HTH