Answered

Environments on Power Automate

(1) Share

Report

Posted on by asynadinou

Hello,

Can you please share best practices how to set-up environments on Power Automate, so that you can distinguish between Prod and Dev/Test? Can they both be of type Production, but serve as Production (the first one) and Dev/Test (the second one)? Is it easy then to promote the flows from dev environment to the test one? What should the access rights be for production, so that no flows are accidentally edited or deleted?

Best regards,

Katerina

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report

ignore... I posted to the wrong question.

Was this reply helpful? Yes No
Verified answer

abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi

Environments

While creating the development and testing environments you can set the environment type as Sandbox. For production instance it will be Production.

When you configure or edit an environment, you can change the environment from:

Production to sandbox
Sandbox to production

Production instance you can't reset which make sense.
Sandbox instance you can reset and default to factory default settings.

Power Platform environments overview - Power Platform | Microsoft Learn

Solutions & Deployment

To move the solutions from dev to test or production you can deploy as managed solution. This way you can restrict people to edit. But if someone edits the flow in production it will create an unmanaged layer. With the right admin permissions you can delete the unmanaged changes.

Solution concepts - Power Platform | Microsoft Learn

Import solutions - Power Apps | Microsoft Learn

Best practices for ALM in Dynamics 365 applications - Dynamics 365 | Microsoft Learn

Thanks

Was this reply helpful? Yes No