Hi all,
We’re currently working on some internal product development involving multiple developers.
As part of this, we all need to build Power Automate flows using specific connectors, such as Dataverse.
However, we’ve run into a limitation:
When I create a Power Automate flow under my named user account and assign a Connection Reference, that reference is not selectable by my colleagues. This is because the underlying connection is tied to my user account or to a service principal, but the ownership of the connection remains personal.
When trying to share the Dataverse connection, I can't find my colleagues in the sharing dialog, even though:
-
They are Members in AAD (not guests)
-
They have the appropriate Power Platform licenses
-
They have already logged in and are active users
-
They are working in the same tenant and environment
-
They can create their own Power Automate flows
I can only share the connection with "Azure APP Registrations" and not the AAD Users.
At this point, the only workaround seems to be that each developer creates their own connection reference using the same App Registration. However, this leads to clutter and complexity — especially when packaging solutions for the customer, as we then need to include multiple connection references and ensure each is configured upon import.
Is there a solution coming to support true shared or group-based connection references or is there a recommended best practice to handle this cleanly while still working with named user accounts?
Thanks in advance for any insights!
Best regards,
Frederic