Power Automate Governance and Environments

Like (0) Share

Report

Posted on 5 Dec 2023 14:34:05 by DavidMullett

Hi,

We're very much beginning our journey into opening up the power platform for our users to start low-code automation developments. I've originally looked at having 3 environments, one Sandbox, one UAT and one Production. The idea being individuals would use the sandbox and then when ready pass the bundled solution to a central IT department to manage moving to UAT and then finally Production.

However I've come across a few articles suggesting I might want to have 1 environment per large scale development to keep it all tidy, this can then obviously lead to quite a few environments especially if for example I have a sandbox per department etc.

Does this still work as good governance? I'm happy to support managing more environments if it means keeping solutions separate and easier to update.

Any advice would be greatly appreciated

All responses (2)

Answers (0)

DavidMullett 51 on 06 Dec 2023 at 09:20:54

Like (0)

Report

Re: Power Automate Governance and Environments

Hi, thanks for your quick response. I think I'd want to go this route as our digital maturity is still quite low so having things isolated sounds like a way to go.

Another query though would be are there limitations to the amount of environments? I assume not all environments need to have dataverse spun up, certainly if it's mainly other data sources being used?
lbendlin 8,111 Super User 2025 Season 2 on 06 Dec 2023 at 02:45:42

Like (0)

Report
Re: Power Automate Governance and Environments

I've come across a few articles suggesting I might want to have 1 environment per large scale development

yes, you will want to follow that advice. There are drawbacks (like more complex sharing across environments) but these are outweighed by the benefits of isolation.