Forum Discussion

Scheneyder's avatar
Scheneyder
Helper I
5 months ago
Solved

Blank Page - Embedded Report

I'm trying to embed a report in a SaaS platform, the report is conected to a semantic model and the model is build with Direct Query mode, however when I open the page I can only see a Blank Page wit...
  • v-echaithra's avatar
    5 months ago

    Hi Scheneyder ,

    Thank you for the additional details.

    In an App-Owns-Data scenario where the end users do not have Microsoft Entra ID (Azure AD) accounts, Power BI is unable to propagate a real user identity to Databricks. This is a current platform limitation.
    Reference: Security in Power BI embedded analytics - Power BI | Microsoft Learn.

    The document clearly states that when you supply an identity with an embed token, the RLS permissions of that identity will be applied to the data.

    This means The identity passed in the embed token is evaluated by Power BI (semantic model) not automatically delegated to the underlying database. So in App-Owns-Data, RLS enforcement happens inside Power BI unless you explicitly configure token based SSO.


    Features such as SSO, EffectiveIdentity with an identity blob, and OBO flow require an authenticated Entra ID user context.

    In this model:

    The embedded application queries Power BI using a service principal. Since the end user is not an Entra ID identity, Power BI has no user identity to forward to the DirectQuery source. As a result, Databricks RLS that depends on functions such as current_user() or email-based identity cannot resolve the user context and returns an empty result set. Power BI receives no rows and renders a blank report page without an error.

    Recommended Approach for This Scenario

    For embedded solutions without Entra ID users, we recommend enforcing security within the Power BI semantic model instead of relying on source-side RLS.

    Hope this helps,
    Thank you.