Sharing Connection References in Power Platform

[svignesh]

Is there a way to share connection references that we create, across all solutions in an environment? or at least within the same solution? 

Assume that we create a connection reference and login with a service account "Dev_SP_Svc" and use it inside a Power Automate action, now when I share the Power Automate with others, they can use the same connection reference for newer actions that they are adding in the same flow, but it is not possible for them to use the same connection reference for actions in a new Flow. 

Is there a way to share this connection reference so that other users can use it in various Flows within the same solution or environment? 

[Mister_Shaik]

Hi @svignesh ,

What type of trigger are you using for your flow?

Because when it comes to Automated or Scheduled flows, they will always use the connection references that they are configured with. But when it comes to Instant flows, they always use the connections of the person who is triggering the flow, and all the actions inside the flow run with that user's connections.

I hope my assumption was right regarding the issue you're facing, or please provide additional details in case your issue is completely different.

Hope this helps 🙂

Kind Regards,

Shaik Sha
________________________________________________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

[svignesh]

Hello Shaik,

I am looking for a way to share connections references we create. Like for automated flows, assume its when an item is created in SharePoint list, I am creating an entry in dataverse and only service account has access to dataverse table. If we are to create multiple flows like this, I don't want developers to need the user ID and password of the service account, instead I am looking to see if there is a way where I can create the connection reference in the solution and share it with Developers so that they can use that connection reference to perform any CRUD operations on dataverse as required.

[Yocomd]

I'm guessing you haven't found a solution for this one?  Would be really nice to be able to do.

[HerrMueller]

Anything new on this topic? It would be really great to have the opportunity to share connection references for initial usage (creating new flows) because we don't want to have several connections for each and every developer. 

[RahulDubey]

Any Updates on this ?? Facing the same issue

[Anonymous]

This should be on the top of Microsoft's feature list. This is one scenario where a connection reference with admin credentials need to be shared across multiple flows if the admin credentials are not shared with developers working on flows.

[blipper123]

You can build out the flow using your own connection reference, then export as unmanaged and change the connectionreference schemaname to the SA one. When you open the flow again, it will not be editable until the person who owns the connection reference confirms it. Once that is done, the flow becomes editable, deployable etc etc.