Best Practices Connections

(0) Share

Report

Posted on by A Wennerwik

144

Hi,

Is there a best practices way of handling connections when setting up Flows?

Example: I'm the main person for creating Flows for Dynamics 365 and PowerApps at my company. So each new Flow or App uses or creates a connection with my details (firstname.lastname@mycompany.co.uk).

What will happen when I leave the company? Does my account need to be kept "alive" or does the next admin have to sign over Flows and Apps to someone else?

Is the best practice to create one admin connection for each of Flow, Common Data Service, Office 365 etc and use those when creating Flows and Apps?

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (1)

Community Power Pla... on at

Like (1)

Report

@McMontyYu can always have multiple people added as owners of the flows. Called team flows. That way, even when a person leaves the organization, the flows can still be operational.

Please accept this as a solution and give kudos if you find this handy.

Was this reply helpful? Yes No
Verified answer

Jcook 7,781 Most Valuable Professional on at

Like (3)

Report

Hello @McMonty

The best practice would be to have a service account / an account specific for flows or even specific to the project. Depending on how your organization would want to do this.

For example you could have an account setup:
D365.flow@Companyname.co.uk

This way if you do leave the company the flows and connections won’t be broken by an off boarding process.

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

1 people found this reply helpful.

Was this reply helpful? Yes No
EMKody 147 on at

Like (0)

Report

Going to blow some dust of this thread. @Jcook is there a 365 license that would work best for this type of solution, or would you just have to create a service account on something like an E3 that also includes a premium automate license if using premium connectors?

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Hi @EMKody

E3 or equivalent would be good.

And yes a Power Automate premium license for that account would be required if premium connectors are used.

Was this reply helpful? Yes No
RobinCarlsson365 5 on at

Like (0)

Report

Disagree on this one, usage of service accounts should be treated as an anti-pattern / bad practice, considering it may cause a pooled connection (multiplexing) which violate product terms.

Instead, add multiple owners like the 'Anonymous' user explain. For the connections, use explicit authentication as the prefered option where user's own license and credentials are used. As secondary option for connections, use implicit authentication for service principles only when service-to-service authentication is required.
If service principles are not supported for some specific connection where background service-to-service is intended, as a last resort (third option) is to use implicit authentication with a service account.

Was this reply helpful? Yes No