Why you can run it but others cannot?
This happens because the flow inside your Solution uses a connection reference that belongs to you. When you run the app, the flow uses your fixed connection, so everything works.
But when another user presses the same button:
Power Apps calls the flow as the app user (the invoker)
The flow requires a connection reference owned by you
Power Apps refuses to pass that connection
You get:
“Connection reference … cannot be given by invoker.”
This is expected behavior when using:
Solution-aware flows
Power Apps V2 trigger
Shared connection references
Multiple Fix Options:
1. Configure “Run‑Only Users”
This is often the most correct and simplest fix.
Open the flow inside the Solution
Go to Run‑only users → Edit
For each connection used in the flow, set:
Use this connection (your@domain.com) (NOT “Provided by run-only user”)
Result:
Every user who triggers the flow uses your pre-selected connection, not their own. This completely avoids the “cannot be given by invoker” error.
2. Use a Service Account (Best practice for enterprise apps)
This avoids future failures if your password changes or you leave the team.
Create a service account (e.g., svc_powerplatform@domain.com)
Create the SharePoint and Dataverse connections under that account
Assign proper permissions in SharePoint & environment
In the flow’s Run‑only users settings, choose:
Use this connection (service account)
Now all users trigger the flow using the same stable connection.
3. Refresh the Flow in Power Apps
Sometimes Power Apps caches an outdated version of the flow’s connection reference.
To refresh it:
Go to Power Apps Studio
Remove the flow from Data → Flows
Save the app
Add the flow back again
Save & publish
This forces Power Apps to re-register the corrected connection reference.
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.
