Underlying ErrorOnPremiseServiceException

[Rohan-Kumar]

When a report uses a semantic model that inherits data from another semantic model, some data is not visible in the embedded report when using a service principal for authentication.

error message:
Error fetching data for this visualCouldn't retrieve the data for this visual. Please try again later.
Please check the technical details for more information. If you contact support, please provide these details.

[v-pnaroju-msft]

Hi Rohan-Kumar,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @alish_b and @Zanqueta for your responses.

Hi Rohan-Kumar,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @alish_b and @Zanquetato resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[Zanqueta]

Hi @Rohan-Kumar 

This error typically occurs in scenarios where semantic models inherit data from other semantic models (sometimes called composite models or DirectQuery over Power BI datasets), and the authentication method is a service principal. The underlying cause is usually related to security context propagation and permissions.

---

Why This Happens

• When using a service principal, the embedded report runs under that identity.
• If the semantic model references another dataset (via DirectQuery or composite model), the service principal must also have access to the source dataset.
• If permissions are missing or the service principal is not enabled for dataset-to-dataset chaining, visuals fail with:

  Error fetching data for this visual
  Underlying ErrorOnPremiseServiceException

  This often appears when the second dataset is in a different workspace or uses RLS.

---

Best Practice Fix

1. Grant Access to the Service Principal
   • Ensure the service principal has Build permission on:
     • The primary semantic model.
     • The referenced semantic model(s).
   • If the models are in different workspaces, grant access in each workspace.
2. Enable Service Principal for Dataset Chaining
   • In the Power BI Admin Portal:
     • Go to Tenant Settings → Allow service principals to use Power BI APIs.
     • Enable Allow service principals to use datasets across workspaces.
3. Check RLS and Security Filters
   • If Row-Level Security is applied on the source dataset, confirm that the service principal is assigned to a role or bypass RLS for that identity.
4. Validate Authentication Flow
   • Embedded scenarios require the service principal to authenticate via Azure AD and have the correct permissions in Power BI Service.
   • If using On-Premises Gateway, ensure the service principal is configured for the gateway connection.

---

Reference Documentation

Use composite models in Power BI Desktop - Power BI | Microsoft Learn

Embed Power BI content in an embedded analytics application with service principal and an applicatio...

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

[alish_b · Accepted solution]

Hey @Rohan-Kumar ,

It could be because the service principal only has permissions in one semantic model and not the other. Please make sure that the service principal has build permissions to all the semantic models that are in the chain and access to the workspace holding these semantic models.

Hope it helps!