Best Practice - Setting up flow for multiple users

[bjarvis]

Hi all,

I've been setting up a couple of automated flows for our Dynamics 365 instance. 

However, i've been setting these up under my own account, and so each of the connections are in my account.

This got me thinking, is there a better way of doing this when creating flows that will be used company wide?

For instance, the last flow i created was a simple update record on creation of a new record - this flow is automated and so runs in the background for all dynamics users. But it's running under my connection to Dynamics.

Should i be using a 'central' account for Flows like this?

How is everyone else handling this?

[ScottShearer · Accepted solution]

@bjarvis 

Since the action that does the update uses a connection with your credentials, the item will show as being updated by you.

As you have suggested, many Flow developers are using a "service account" so that updates, etc. do not show as being made by them.  The downside is that licenses must be assigned to the service account.  You might even create the Flow while connected as the service account and then add other Flow developers as owners.

[bjarvis]

Thanks @ScottShearer, i thought that would be the case, but just wanted to make sure there wasn't something i was missing.