Hi,
Not sure if it is even possible at all, but here is my problem:
I have a solution with a bunch of Power Automate Flows and a couple of Connection References. The Connection References are bonded to Connections that I've created myself, one to the Azure Service Bus, and the other to the Dataverse.
Now, when someone else tries to run these Flows, they cannot, because they don't have access to these Connections.
The logical solution as I see is to share those Connections with my team members, and there is an option as well to do it. But when I try to share, I'm simply not able to find any of my team members. I'm able to hit some accounts that are apparently service accounts or App accounts, but none of the actual human accounts are searchable.
Please if someone can share a solution or insights to better understand the problem.
Thanks much & Regards,
Haris Munawar
Completely madding. I can't find a solution anywhere - and have the same issue... It's like these connections that are created after solution import aren't linked to the same tenant/directory.
any update on this . Even i am facing same issue
OK, well after some confusion this article helped me: https://learn.microsoft.com/en-us/power-automate/service-principal-support
I was trying to share the connection with a regular user but you have to share it with the Application User and then set the flow owner to the Application User
Regular Developer "isn't in your organization's directory"...
I'm having the exact same issue.
I can share Flows with users but I'm not able to share Connections (Custom Connections seem to work) with others.
Hi @FloMarks,
No, still no improvement, everyone in the team has to create connections of their own to edit a flow.
@HarisM Is there an update here? I have the same problem. My guess is that it is due to the Developer Plan.
Okay, but as the owner of the connection, I even cannot share it with anyone on the team. So, should I be the Environment Maker/Admin as well? besides being the owner of the connection.
Yes, there is a specific permission required to share a connection in Power Platform. By default, only the owner of the connection can share it with others. To allow other users to share the connection, the environment admin must grant them the "Environment Maker" or "Environment Admin" role.
To grant these roles, the environment admin can follow these steps:
Go to the Power Platform admin center (https://admin.powerplatform.microsoft.com)
Select the environment that contains the connection
Click on "Security" in the left-hand navigation menu
Click on "Users" in the sub-menu
Select the user(s) that need the role
Click on "Edit roles" in the command bar at the top
Select either "Environment Maker" or "Environment Admin" from the dropdown list
Click "Save"
Once the user has the appropriate role, they should be able to share the connection with others.
Hi rswain,
Thank you for the reply. The team members have access to the same environment and can create connections for themselves as well, and can also edit or run the Power Automate flows in the solution, created by others.
So they have access to the environment, and tenant, but cannot share the connections. Do you know if there is any special kind of permission one should have to share a connection?
Regards,
Haris Munawar
It sounds like you may not have the correct permissions to share the connections with your team members. You will need to have the appropriate permissions to share connections in Power Automate.
To share connections with your team members, follow these steps:
Go to the Connections tab in Power Automate.
Find the connection you want to share and click on the ellipsis (...) next to it.
Select "Share connection" from the dropdown menu.
In the "Share connection" dialog box, search for the name of the person or group you want to share the connection with.
Select the appropriate permissions for the connection (e.g., "Can use" or "Can edit").
Click "Share" to share the connection with the selected person or group.
If you are not able to find your team members in the search, it's possible that they do not have access to the same environment or tenant as you. In that case, you may need to work with your IT administrator to ensure that your team members have the appropriate permissions to access the environment and tenant.
MS.Ragavendar
20
BCBuizer
10
Super User 2025 Season 1
LC-26081402-0
10