What to do with virtual machine when move a solution that contains PAD flow from Dev to Production environment?

(0) Share

Report

Posted on by VMK

Hi all,

I have a solution with PAD flow in my development environment.

This PAD flow is triggered by a Business Process Flow in a Model-Driven App.

I now need to move the solution to production environment but I see that my virtual machine can only work in one environment. So when I move the solution my cloud flow will lose connection to the virtual machine.

I need that machine to stay in development environment because it is used for other projects. Should I create additional VM in Production environment and then manually change the cloud flows in Production environment?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (1)

Sort by

VishnuReddy1997 2,666 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @VMK

For each machine, We can have multiple environments. On the same machine, Please the change the environment to production in make.powerautomate.com and import the flow into solutions.

If you dont know how to create environment in Power automate ,Please find the below information

Sign in: Access the Power Platform admin center at https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation.
Navigate: In the left navigation pane, select "Environments" and then click "New."
Provide Details: Enter the following information for your environment:
Name: Choose a descriptive name for your environment.
Region: Select a region where your environment's data will be stored.
Type: Choose the environment type based on your needs:
Production: Use for critical business processes and production data.
Trial: Ideal for testing and development purposes (limited functionality and duration).
Development: Suitable for development and testing (may have limitations compared to production).
Sandbox: Excellent for experimenting and training without affecting other environments.
Description: (Optional) Provide a brief description of your environment's purpose.
Database: Select "Yes" to create a Dataverse database associated with the environment (optional, additional costs may apply).
Azure subscription: If using Dataverse or other services requiring payment, link your Azure subscription for billing.
Language and Organization: Choose the default language and your organization name.
Review and Create: Review the details and click "Save" to create your new Power Platform environment.

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards
Vishnu Reddy

Was this reply helpful? Yes No
Verified answer

CU16071609-1 6,255 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

@VMK

Indeed, you've grasped it correctly. Registering our VM in a single environment is the norm. Attempting to switch it to another environment results in losing connectivity to the previous environment, necessitating a new connection to the new environment.

Should you decide to alter the VM's environment connection, it will impact other processes, particularly cloud flows utilizing the machine for desktop flow.

Following best practices, it's advisable to maintain separate machines for production. Once your solution moved to production, simply update the connection to point to the production environment or establish a new connection using production VDI details.

I hope this clarifies matters!

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
VMK 28 on at

Like
a
(1)

Report
Copy link

Link copied!

ok, thank you for your answer! I will create a second VM for Production then.

Was this reply helpful? Yes No