Unable to Configure Run-Only User Power Automate Flow

(0) Share

Report

Posted on by US-09030836-0

Hi Team,

I have a requirement to export all the Power BI content into an excel file (i.e., All the visuals in all the tabs of the report to one single excel file)

I have added a Power Automate button in Power BI report and created the flow to export data from Power BI (using Run a Query against a dataset) to Excel and the Excel will be stored into One drive for Business. My flow works very well with my credentials.

But the requirement is When I share the report to users and when the user clicks on the button, Power Automate should consider the User credentials and run all the actions with that specific user credentials.

I tried to add users to Run-Only Users but couldn't able to configure the connections with those Users.

How to achieve this?

FYI - Our Power BI Report is a Direct Query mode connected to Databricks and Security is implemented at Data bricks layer. Power BI doesn't have RLS.

Thanks,

Udaya Sindhu

Categories:

Building flows

Using flows

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Sam_Fawzi 917 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Udaya @US-09030836-0,

In general, Power Automate can run an instant flow in the invoking user’s context only when all connectors involved support “Provided by run‑only user” and each user can create their own connection.

However, there is an important limitation when the trigger is a Power BI button. While you can share the flow as run‑only, the Power BI connector (Run a query against a dataset) does not support true per‑user impersonation for execution, especially with DirectQuery datasets. In practice, the query and export still run using the dataset’s configured identity rather than the clicking user’s identity.

This means that even if Excel/OneDrive actions are configured as run‑only user connections, the Power BI step itself will not execute under the viewer’s Databricks security context.

Because your security is enforced in Databricks (not Power BI RLS), the export cannot reliably reflect each user’s permissions when triggered from a Power BI button.

Was this reply helpful? Yes No
lbendlin 8,716 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

You need to add USERPRINCIPALNAME() (or equivalent) as a payload to your Power Automate button and then use that as a filter in your "query against a dataset"

Was this reply helpful? Yes No