Power Platform Community Forum Thread Details

Is there a good strategy for dealing with desktop flows, and the machine/environment they run on, when deploying solutions across environments?

I have cloud flows that call desktop flows, which run on a specific VM in attended mode. When working in my Dev environment I use Power Automate Machine Runtime on the VM to allocate the machine to the Dev environment.

When I want to deploy to the Test environment or Prod using a pipeline, after a lot of experimentation I find I have to, in this order,

Re-allocate the machine to the Test environment
Edit the Desktop Flow Connection on the machine to remake it (it's a username/password authentication)
Run the pipeline, but take the option to re-verify the Desktop Flow connection when invited

If I don't do this, in this order, I get failures when the desktop flows are called.

Then to move on to Prod or go back to Dev I have to this over again. Meanwhile nobody can use the app in Prod because the machine is re-allocated to Dev.

Is this the best/most economic/only way to do things, short of paying for separate machines for DEV, TEST and PROD?

Categories:

Power Automate Desktop