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