Power Platform Community Forum Thread Details

Hi everyone, I’m using a Power Apps canvas app embedded in a Power BI report (Power Apps visual). The app connects to a Fabric SQL Database and executes stored procedures for filtering and CRUD operations.

My security setup:

Users are in an Entra ID security group
The Power App is shared with that group
The same group is added to a SQL role with read/write/delete/execute permissions

My problem: when users open the report for the first time, they see a popup asking them to “Allow” access to the stored procedures. After clicking Allow, everything works — but after a few days, they are prompted again. This repeats periodically even though permissions haven’t changed. Additionally, the embedded Power App fills the entire report page. Sometimes the consent popup renders outside the visible area, so users can’t see or click it, making the app appear broken. My workaround was creating a second “zoomed out” report just to allow consent, which isn’t ideal.

Now I have a few questions:

Why does Power Apps repeatedly require users to re-authorize access if database permissions are already granted?
Is this per-user consent mandatory and expected behavior?
Is there a recommended way to handle authorization UX for embedded Power Apps to avoid hidden popups?

Any best practices or architecture guidance would be appreciated.

Categories:

Building Power Apps

Hi @KG-10021631-0,

Apart form UX, did you explicitly set stroed proced permission? Meaning, the SQL role has EXECUTE permission on the stored procedures, not just table read/write. This is something like:

GRANT EXECUTE ON SCHEMA::dbo TO [YourEntraGroupRole];

Or grant execute on specific procedures.

If that is there and you still see the recurring “Allow access” prompt - probably it’s about how Power Apps connections are cached and consented when used inside the Power BI visual. Apparently, by default, each user has to consent to the connector, and that consent token can expire or be refreshed periodically. That’s why it works after “Allow,” but then reappears after a few days.

Here are two important areas - you can take care:

1. Azure AD authenticaiton for SQL: Configure the SQL connection in Power Apps to use Azure AD Integrated authentication, so the app runs under each user’s Entra identity and tenant‑level consent eliminates repeated access prompts.

2. Service Account Connection: Use a single shared service account SQL connection for the Power App so all users run under that identity and avoid repeated consent prompts, though this sacrifices per‑user granularity since everyone shares the same SQL role.

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!