I built a Power Apps that triggers a Power Automate Flow, which uses the Azure Automation Connector to trigger a runbook in Azure.
I specified the Connector's Connection to use a Service Account with the appropiate permissions to run those tasks in Azure.
When I use the Flow, it works, but when I shared it with a user, the Flow fails and the error message states that that user's account doesn't have permission to perform those actions, which makes sense and what's why we want to use a Service Account.
What's going on? Why is the flow using the connection's specified account when I use it but when a user uses it, it tries to use their account?
When you trigger a flow using a Manual trigger, for example from a button in a Power App, then the flow runs in the context of the user pressing the button and not the original maker. To get it to run using the security of the flow maker you must use an automated trigger, like when an item is created or modified.
But that makes no sense. I understand the flow running in the context of the user, but if I specified a Connection's account for that particular action, it shouldn't be related to the user's context, it should be independant.
Sorry, but if you are running with a manual trigger that is how it works. The account you specified for the connect account only applies to you for almost all the connectors. Which specific connector are you referring to.
Keep up to date with current events and community announcements in the Power Automate community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!