Issue with Power BI Button Not Triggering Power Automate Flow for One User

[PA_DA]

Hey,
I’m having an issue with Power BI and the integration of Power Automate.

The button fails to trigger, showing an error message that says "not successful." However, the button works perfectly fine for other users, and the flow performs as expected.

The affected user has the same permissions as the others—both for the flow and the SharePoint site. (They also all have the same license.)

I’ve already tried resetting all permissions and even removed and recreated the button, but unfortunately, that didn’t solve the issue.

Additionally, in Power Automate, there is no indication that the flow was triggered at all.

Do you have any ideas what might be causing this?

[PA_DA · Accepted solution]

I found the problem !

Thanks for your suggestions and advice!

The problem was that SharePoint sharing did not work for overlapping tenants.
Since Power BI's Automate button checks the entire retrieval process to see if all connections can be established, if not, this leads to the so-called error.

The second problem was the license. MS has apparently changed it so that if a Premium connector is used, the user must also have a Premium single license, otherwise the flows will not work.

So Thank you for your respons!! 

[v-agajavelly]

Hi @PA_DA ,

Appreciate you trying all that out and sharing the update. The fact that even a super simple flow gives the same error makes me think this isn’t about the flow setup itself but something tied to the user’s account/environment.

A couple of extra checks that might be worth trying before digging into group policies:

• Make sure the flow and the Power BI report are both in the same environment. If the button is calling a flow in a different environment, it can silently fail.

• Try running the button from a different browser or an InPrivate/Incognito window, just to rule out any cached token/auth issue.

• If your tenant has DLP (Data Loss Prevention) rules set up, it’s worth checking if this user is falling into a stricter policy group that blocks the trigger/SharePoint connector.

If those don’t point to anything, then yes, I’d also suspect something on the Power Platform Admin side. Sometimes it ends up being a conditional access/DLP policy difference that only hits certain user.

Regards,
Akhil.

[v-agajavelly]

Hi @PA_DA ,

Hey, just checking in to see if you had a chance to go through those points we discussed especially re-authenticating the flow’s connections and checking for any user-specific references. Sometimes those little tweaks are all it takes, but if it’s still acting stubborn, we can look at duplicating the flow and updating the button link as a backup plan. Let me know how it went on your side.

Regards,
Akhil.

[PA_DA]

Hey @v-agajavelly, 

I went through the points and built a small second flow with only the permission to create a folder in SharePoint.

The same error occurred with the flow.

Unfortunately, the re-authentication did not work.

The connection to SharePoint is not made via the user themselves but via a general user.

I adjusted this and gave the user direct permission, but unfortunately this did not work either.

My next step is to check the group policies to see if that is the reason or if a permission is missing in the Power Admin Center.

Or do you have any other ideas?

Thnak you! 

[v-agajavelly]

Hi @PA_DA ,

Thanks for testing that and sharing the update. Since the user is able to run a brand new flow without any issues (even without being a co-owner), but still gets the error on the original one despite having co-owner rights, it really sounds like something specific inside that original flow is causing trouble not just permissions.

A couple of things worth double-checking.

• Any connections used in the flow (like SharePoint, Outlook, etc.): Even if the user is a co-owner, some flows are tied to the original creator’s credentials. It might help to open the flow, check the “connections” section, and have the user re-auth or switch to their own where needed.
• Any steps that reference the user’s email or profile: Sometimes flows use dynamic content like User().Email, and it can behave differently depending on who triggers it especially if there's a lookup or condition depending on that value.
• Flow parameters: If the button in Power BI passes parameters, check if those are being received correctly by the flow. One small mismatch can cause it to silently fail.

If none of that helps one workaround that’s worked for me in the past, duplicate the flow (export and re-import), then update the button to call the new one. I’ve seen cases where something gets “stuck” in the connection between Power BI and the original flow for just one user, and starting fresh fixed it. Let us know if anything changes happy to dig further if you’re still stuck.

Regards,
Akhil.

[PA_DA]

Hey, thanks for the response.
I’ve now created a new flow, which the user was able to run without any issues (not as a co-owner).
However, in the flow where the issue occurs, the user has co-owner rights but still receives the error message.

[SamWiseOwl]

Can the user trigger the flow in Power Automate directly? Try changing the trigger action.

Can the user run any flows from Power BI? Create one that does nothing and see if that triggers.

If you add them as a co-owner to the flow does it run then?

Can they trigger the flow from the PBIX files directly?