Power Automate Governance

(1) Share

Report

Posted on by aaroh_bits

416

Hi All,

I have stakeholders who are C levels and have an E3 License. The number of users is 10,000 with locations within across Europe and Asia. Governance is of the utmost importance for this organization.

Requirement 1: All the end user can have Power Automate license but cant create any random flows and selected only specified set for flows that approved by the organization.
Requirement 2: The approved flows can be used for each region. Approvers should be dynamic depending in the region.
Example: A Purchase Order Approval flow used in Paris can be used in Perth as well. Approvers should come from dynamically based on master configuration.
Question for Requirement 1: Is it possible restrict users to use flows and they can select only set for flow set by the organization? Something like a Template Gallery shared in this article. https://www.serverlessnotes.com/docs/building-a-power-automate-template-gallery
Question for Requirement 2: Regional HQ Power Automate flow and push down to other countries. Does the concept of Child flow be used for this requirement?
https://learn.microsoft.com/en-us/power-automate/create-child-flows

Please advice.

Thanks in advance.
@trice602 , @Agnius , @ManishSolanki , @wskinnermctc , @SudeepGhatakNZ , @Chriddle

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

sandeepstw 312 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi There,

As per your requirements here are possible work around.
>> Is it possible to restrict users to use flows and they can select only a set for the flow set by the organization?
Yes. Use Data Loss Prevention (DLP) policies in the Power Platform admin center to limit the connectors users can employ. Additionally, you can guide users towards an organizational Power Automate Template Gallery, as suggested in the provided article. By doing so, users can only utilize pre-approved templates, ensuring governance.
>> Can the concept of Child flow be used for regional Power Automate flow distribution?
Answer: Yes. Child flows are suitable for this requirement. Centralize the core logic in the Parent flow, while Child flows can handle regional specifics, like dynamic approvers. Utilize SharePoint or Dataverse to maintain a master configuration of approvers by region. Child flows can then reference this data to determine the appropriate approvers dynamically.

Please give kudos and mark as solution if it helps.

Thanks,
Sandeep Mishra

Was this reply helpful? Yes No
aaroh_bits 416 on at

Like (0)

Report
Copy link

Link copied!

Thanks a lot for your valuable insights @sandeepstw

Was this reply helpful? Yes No
Verified answer

SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

I think you are looking at a combination of Power platform environments and DLP policies.

Everyone in the organisation can build flows in the Default environment, you can't prevent it

However, a solution is to establish additional environments and assign the Environment Maker security role to individuals authorized to create apps and flows. This approach allows for greater control over app and flow development while maintaining a default environment open to all.

Was this reply helpful? Yes No
aaroh_bits 416 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your advice @SudeepGhatakNZ

Was this reply helpful? Yes No