Power BI Embedded doesn't load when data source of semantic model is Fabrics Lakehouse

[rakhimov]

Semantic model is in Import Mode and data source is Fabrics Lakehouse. Report which is connected to the Semantic Model loads in Power BI Service, but in Embedded Report doesn't show up properly and gives error saying Contact Admin. SaaS app (that's where we have Power BI Embedded dashboards) is connected to a Fabrics Workspace and it shows up all PBI reports in the workspace. There are 3 reports in the workspace and all 3 are showing up in the report list of SaaS app. Report A is using sql server as data source in import mode and it shows up visuals in SaaS app. Report B is using Fabrics Lakehouse as data source in import mode and when selected from report list of SaaS app, doesn't show anything except error saying Contact Admin. Report C is in direct lake mode and doesn't show anything except error saying Contact Admin when selected from report list. All 3 reports work fine in Power BI Service.

Not sure if it is an issue with datasource and I couldn't find anything in documentation.

Thanks for help!

[v-yajiewan-msft]

Hi @rakhimov ,
For the report b, try to use PowerBI Desktop to import the data from the lakehouse using the SQL endpoint. (Azure SQL Datasource), then publish the Semantic Model to your workspace.

For report c, currently, Power BI Embedded scenarios that rely on embedded entities aren't supported yet for direct lake.

More information for your reference:

Learn about Direct Lake in Power BI and Microsoft Fabric - Microsoft Fabric | Microsoft Learn
Embedding a report with DirectLake dataset. - Microsoft Fabric Community

Best regards,

Joyce

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[rakhimov]

Hi @v-yajiewan-msft, Thank you for your response. As you can see from the screenshot, Report B is already using SQL endpoint (SQL Datasource).

[v-yajiewan-msft]

Hi @rakhimov ,

Thank you for your additonal information.

Are there any other detailed error messages?

In addition, do all reports use the same semantic model?