You’re offline. This is a read only version of the page.
Announcements
70
I have a flow that is failing in a weird way, here is the setup.
We have numerous Microsoft Groups setup and an Power App for onboarding employees. Based on user's role, they get automagically add to their groups using an App button and an instant flow. All of these groups have a service account with owner access. That service account is connected to all of the potential 'Add member to group' actions throughout the flow.
When I use the app, the flow works great most of the time. But then I have a colleague when he uses the app, the flow fails every time. Except for the first 'Add member to group' action of the flow, that works:
After that first action, there's a bunch of logic to check a users role to add to their appropriate groups. That appears to work as intended for the expression and the action it attempts to run next, but because the dependent actions fail, the flow gives up and stops attempting to do anything else:
After the condition is met it hits the actual snag and says "Forbidden":
Looking at the fail logs the action fails due to "Insufficient privileges to complete the operation."
Looking at the specific action itself I can see in the body:
At the bottom of the output, it states status code 403 and just beneath that I can see the service account listed for the connection. Its weird that if I run the flow from Power Apps, it works. If my colleague runs it, fail. I gave the colleague owner permissions on the flow, no change. I checked the flow from his logged in account, it looks identical to mine.
I'm a bit stumped. Anyone run into something like this and other suggestions on where to look next?
Share
Report
All responses (
Answers (
