Best practice for multideveloper automate - Sharing connection reference

(2) Share

Report

Posted on by Rohit4044041

286

We have a solution created and inside there is a power automate. This automate uses outlook, SharePoint connection reference which are created by account 1 (service account)

we do not want to share service account credential with developers.

we shared power automate with two developers who are to develop this further.

However, when they open the power automate shared with them they are asked to created their own connection reference. (Screenshot below)

What is the best practice followed?

If every developer creates their own connection reference, will solution be crowded with those many connections reference?

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

David_MA 12,982 Super User 2025 Season 2 on at

Like (1)

Report

What is the purpose of the service account if you do not share the login credentials with them? You basically have an account that doesn't get used. If you don't want the connection references to use the account information of the developers, you need to share the login information of the service account so they can login with that and use it to set up the connection references. Then, everything runs on the credentials of the service account. This is how we do it where I work and it works out just fine.

Was this reply helpful? Yes No
Rohit4044041 286 on at

Like (0)

Report

Thank you for your response.

I agree, while its convenient to share credentials, it's not secure. We can't know who really made change. It violates licensing agreement (Multiplexing) and Sharing password is already a problem. (I do understand orgs can still do it but i don't see our security team agreeing for this)

Primary reason to have service account is to run these flows in production under service account.

Even if say we keep service account aside. I am more concerned about how two/three/n number of developers can work on one power automate without having their own connection reference created.

Was this reply helpful? Yes No
Suggested answer

Rohit4044041 286 on at

Like (0)

Report

To close on this.

seems things are working as expected. devs were able to edit flow that was shared and had connection reference.

The euroka moment was when we realised that the power automates were turned off. the moment we turned on automate, other users were not getting connection reference error anymore.

We had kept it turned off during development to avoid accidental triggers.

Was this reply helpful? Yes No