Power BI embed error

[jgarden6]

I've publish my bi desktop data to the bi service.  all the visuals display corectly on the service.  after i try to embed the report, some of the visuals wont display but some of them do.  the ones that do not, i get the following message.

Error fetching data for this visual

Couldn'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.Hide details

• Underlying ErrorPowerBIAnonymousArbitraryDaxExpressionException
• Http Status Code403
• Correlation ID8933ba65-243b-50b9-2ef1-4f70e803eaef
• Activity ID490656cc-d7b4-4284-8791-702fb92f2919
• Request IDd22412e9-b4fb-702b-0958-e1478404d829
• TimeThu Jan 01 2026 18:18:44 GMT-0700 (Mountain Standard Time)
• Service version13.0.27321.33
• Client version2512.3.27315-train
• Cluster URI https://wabi-us-north-central-c-primary-api.analysis.windows.net/
• Activity ID490656cc-d7b4-4284-8791-702fb92f2919
• Request IDd22412e9-b4fb-702b-0958-e1478404d829
• TimeThu Jan 01 2026 18:18:44 GMT-0700 (Mountain Standard Time)
• Service version13.0.27321.33
• Client version2512.3.27315-train
• Cluster URIhttps://wabi-us-north-central-c-primary-api.analysis.windows.net/Copy

  Contact support

  I really would appreciate some help.

[cengizhanarslan]

A 403 in an embedded report almost always means the identity used for embedding (user/service principal) is allowed to open the report, but is not authorized to run one of the DAX queries that specific visuals generate. That’s why it can look “random”: some visuals only need basic dataset read, while others trigger queries that require additional permissions, hit a different dataset, or are blocked by RLS/SSO rules. 

What to check first: (1) confirm you’re not using “Publish to web” / anonymous embed for content that needs security (RLS, private data, etc.)—use a proper embedded flow (“user owns data” or “app owns data”). Make sure the embed token includes every dataset the report uses (composite models / multiple datasets are a common reason only some visuals fail). Ensure the embedded identity has the right permissions on the dataset(s): at minimum Read, and in many cases Build (or the right workspace role) depending on how those visuals query the model.

If you’re using RLS, verify the embed is passing the correct effective identity (username/roles) when generating the token—otherwise some queries can be rejected even though the report loads. If after verifying the above it still happens, capture the failing request in browser dev tools/Fiddler and compare which dataset/query endpoint that failing visual is calling (Microsoft explicitly recommends a trace for 403 investigations).

[jgarden6]

I think I narrowed the problem down to the new visual measures.  If I create the same measure in DAX everything works correctly.  However, if I create a visual measure and use it in my visuals then I get the error message.  Is this a bug or do I need to change a setting somewhere?

[Murtaza_Ghafoor]

Hi,

It looks persmissions matter when embedding the Power BI report, let's try these simple steps one by one i hope you will be fine to dig out this

 1-The issue is security & identity, not visuals or data
 2-Some visuals need user identity → they fail in embedded mode

 3-Correct RLS or identity passing fixes the problem

[v-sgandrathi]

Hi @jgarden6,

This issue often happens because the permissions and authentication context for embedding differ from those in Power BI Service, even if the report works fine there. The 403 (Forbidden) error means the embedded identity (user or service principal) lacks access to some data or DAX expressions in the visuals. Make sure the embedded user or service principal has Build permission on the dataset and is a Member or Admin of the workspace. If Row-Level Security (RLS) is enabled, confirm the identity is assigned to the correct RLS role, as visuals may fail if RLS is not set up properly in embedded mode. Also, check data source authentication, especially for DirectQuery or Live connections, since some authentication types may not work when embedded. Review any visuals that fail, those using user-based or complex DAX expressions or custom visuals might act differently in embedded scenarios. To troubleshoot, try embedding a simple visual from the same dataset, check permissions and RLS, and review the DAX logic.

Thank you.

[jgarden6]

I think I narrowed the problem down to the new visual measures.  If I create the same measure in DAX everything works correctly.  However, if I create a visual measure and use it in my visuals then I get the error message.  Is this a bug or do I need to change a setting somewhere?

[v-sgandrathi · Accepted solution]

Hi @jgarden6,

Thank you for confirming. Since the issue is happening specifically with visual measures in embedded reports, it appears to be a product limitation or bug rather than a configuration problem on your end. Visual measures behave differently in Power BI Embedded compared to the Power BI Service, which can lead to 403 errors even if permissions and RLS are set up correctly.

At this point, it’s best to raise a Microsoft support ticket. This will help the Power BI team determine if this is a known issue for your cluster or version and provide guidance on any fixes or timelines.

To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Thank you.