What is considered best practice for creating Flows for a service?

[AH2O]

Hi Power Automate Community

Power Automate appears to be designed for an individual user in mind first and foremost, where they will create Flows to help them solve problems for themselves or the area they work in.

What is the best practice for when you need to create Flows for the business overall, not linked to an individual as a creator but more of a central supported function? Would a service account with the sufficient licenses and limited access to resources it needs be a suitable recommendation?

Concerns I have of using an individuals account and shared Flows for this use case are:

• The creator leaving the business and their flows going with them
• The creator having greater access to data and resources than the Flows need is a risk should the flow be compromised
• The creator has to grant wide permissions for certain connectors, such as email, and if the Flow is shared with other owners they could change the Flow to exploit this permission
• Shared Flows with other owners can then share further without the original creator having control

[Hardesh15 · Accepted solution]

@AH2O Welcome to Power automate community.

For license: its depend on organization size and uses of automation in your organization. I would recommend you to raise one support ticket to Microsoft and take their recommendations.

1. Do not allow individual to create flow. Its better use one service account so that your flow works flawlessly.

2.Flow creator need Member access it does not require owner access of data source.

Rest of queries are covered in these points.

Please 'Thumbs Up' the posts that helped you and 'Mark as Solution' if my post answered your question.

@Hardesh

[AH2O]

Thanks. A 'service-type account' is working well. It only has access to what it needs to and the workflows this creates can be shared with other IT administrators that need to support the flow.