Power Apps flow error: shared_powerbi_1 connection reference not allowed for run-only users

(1) Share

Report

Posted on by FR-27081326-0

Hi all!

An user receives this error NotAllowedConnectionReference Connection reference 'shared_powerbi_1' can not be given by invoker. when trying to run a flow from Power Apps that triggers a Power BI dataset refresh. I have already tried opening the flow and saving it again.

This flow uses Run-only users permissions for the group that includes the user, and it uses the configured Power BI connection to perform the dataset refresh.

The last time I resolved the issue by opening the app, removing the flow, and adding it back. However, this time the app is in a production environment and is a managed solution, so I cannot modify or open it. How can I resolve this issue?

Thanks

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

BCBuizer 22,833 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @FR-27081326-0,

The way I would go about to fix this is to check the run-only user connections of the flow in the unmanaged solution, probably in a developer environment. Once confirmed correct, edit the app, refresh the flow and publish the app. Then push the solution to the production environment.

If this is for not an option for you because of any reason, there is a way to edit apps in a managed solution: In the production environment, open the Default solution. In there, locate the app, refresh the flow and publish. However, this will create an unmanaged layer on the app which will need to be removed before the next time the solution is imported to the prod environment. Also, the same change needs to be applied in the unamanged version of the solution in order for the issue to not return upon the next solution import.

If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @FR-27081326-0,

The error means the Power BI connection in the flow is set to "Provided by run-only user" but Power BI connectors don't support that mode when triggered from Power Apps. The connection must be embedded (static) in the flow itself.

Fix without touching the managed app:

1. Open the flow directly in Power Automate (not through the app)

2. Go to the flow's detail page > Run only users > Edit

3. For the Power BI connection (shared_powerbi_1), change it from "Provided by run-only user" to "Use this connection" and select the actual Power BI connection

4. Save

This change is on the flow itself, not the managed app, so it doesn't create an unmanaged layer on the solution components. The flow can be edited independently even in a managed environment as long as the flow definition change goes through your normal pipeline afterward.

If the flow is also locked as part of the managed solution and you can't edit it at all, the cleanest fix without breaking ALM is to create an unmanaged layer on the flow specifically (add it to a new unmanaged solution in PROD, make the connection change there), then merge that back into your managed solution via DEV on the next deploy.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @FR-27081326-0,

Let's follow these steps

Have the solution owner or admin update the connection reference in the managed solution to include the user or a service principal with delegated permissions.

Use a service principal or dedicated service account connection for Power BI refreshes, and assign run-only permissions accordingly.

If you have access to the environment admin, ask them to reconfigure or re-share the connection reference.

Final thought, re-import or update the Solution
If the connection reference is broken or locked, the solution may need to be updated or re-imported with correct connection references and permissions.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
Given that:

The flow runs from Power Apps.

The Power BI connection is shared.

Re-adding the flow previously fixed it.

The app is now managed.

The most likely issue is a stale connection reference binding between the Power App and the flow, not a Power BI permissions problem.

First verify that the Power BI action is configured to use a fixed connection in Run-only users, then check the shared_powerbi_1 connection

reference health.

If those look correct, you'll likely need to refresh the app-to-flow binding through a new solution deployment from your development

environment.

Was this reply helpful? Yes No