You’re offline. This is a read only version of the page.
Hello Power Automate Community,
I'm encountering an issue with a flow that's triggered by a Power Apps, where any OneDrive for Business action fails when triggered by users other than myself. I'm reaching out for insights or possible solutions from the community.
Issue Description
The flow works flawlessly when I, the creator, trigger it from Power Apps. However, when other users initiate the flow, actions such as "Get file metadata" and other OneDrive for Business actions result in "Forbidden" or "Access denied" errors. This suggests a permissions' problem, but it's unexpected because the actions are set to use a specific connection that should not be affected by the user triggering the flow.
For example, here is the same action for 2 runs :
The action when another user triggers the flow from Power Apps
When the flow is trigger by me using Power Apps (with the same parameters) :
Troubleshooting Done:
Questions:
Your assistance or suggestions would be immensely helpful. I'm happy to provide further details if needed.
Thank you for your time and help!
Best regards,
Nicolas
Giving the users permission to the OneDrive folder and contents should also work. But the Solution is the better choice since that becomes important if you want to move the app and flow to a different environment also.
Thank you so much for the quick response, I didn't know about this security logics!
So either all users using the Power Apps should have permission for those OneDrive folders/files, or the Power App and Power Automate need to be put in a Solution and use the "Run Only User" settings to run with the maker's connection.
I will try to use a solution immediately!
Thank you again!
1. When you trigger a flow from Power Apps it runs in the security context of the person who triggered it. So no in that case it won't run with the connection credentials.
2. That is the default setting. If you build the flow and the app in a solution there is a setting on the flow called Run Only User which will let you change the connection to run with the maker's connection, not the security of the person triggering the flow.
3. See #2. This is the way it operates by default. Using the steps in #2 you can change it.
#1
WarrenBelz
146,745
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,091
Most Valuable Professional
Share
Report
All responses (
Answers (