Power BI Desktop - Dataflow - The name 'Lakehouse.Contents' does not exist in the current context.

[_David_]

Hi everyone,

I'm encountering the following error when trying to connect to a Dataflow using the Dataflow connector in Power BI:

The name 'Lakehouse.Contents' does not exist in the current context.

This happens when attempting to access a Dataflow that is stored in a Microsoft Fabric environment, specifically within a Fabric workspace.

Context:

• I'm using the Dataflow connector in Power BI Desktop.
• The Dataflow is created and stored in a Fabric workspace (not a legacy workspace or classic Power BI workspace).
• The error appears immediately after selecting the Dataflow and trying to load or transform the data.

Troubleshooting so far:

• Verified permissions to the workspace and the Dataflow.
• Confirmed that the Dataflow is published and accessible via the Fabric UI.
• Tried using both organizational and personal accounts for authentication.

Question:

Has anyone else experienced this issue when working with Dataflows in Fabric environments? Is there a known workaround or update needed to support this connector in Fabric?

Any insights or suggestions would be greatly appreciated!

Thanks in advance,
David

[_David_]

Facing the same issue with the July Version - Re: Power BI Desktop - Dataflow - The name 'Lakeho... - Microsoft Fabric Community

[Jeroen_Geenen]

I have exactly the same problem. Accessing the lakehouse tables using Lakehouse.Contents() has been working fine for months. No changes made and today all queries on the lakehouse tables fail. Only in Power BI desktop, that is. On the service they work fine. Also, the lakehouse itself is working fine. Even made some changes to it this very morning. Also, only the 'dataflow 2' connector visible in Power BI desktop. 

I also have the July version of Power BI desktop. Strong suspicion something went horribly wrong with this version.

[andrew_tran]

I am also facing the same issue. Microsoft, please fix!

[JochemvdStoel]

We have the same issue. Microsoft, please fix!

[_manu_]

Hello,

(Sorry for my broken English...)
I have the same problem: the Lakehouse.Contents([]) connector no longer seems to be recognized!

Power BI Desktop Version :
Version: 2.145.1105.0 64-bit (July 2025)

Everything was still working yesterday morning (July 15) at 9:00 AM (French time).

Here is the list of Microsoft Fabric connectors currently available in Power Query: many are missing!

Thanks in advance,

Manuel

[rohit1991]

Hi @vikramkumawat ,

This error means the Lakehouse.Contents connector is either missing or not recognized in your current Power BI or Fabric environment. This often happens due to either recent service changes or outages in Microsoft Fabric or Updates or breaking changes to the connector or permissions or Attempting to use a Fabric-only function in classic Power BI Desktop or unsupported environments.

To fix the issue you can start by Checking the Fabric Service Health by going to the Power BI/Fabric Support page to see if there are any ongoing incidents affecting Lakehouse or Dataflows. Then update Power BI Desktop as connector support is updated frequently. Validate Permissions: Double-check that your user account still has access to the Lakehouse and Dataflows in Fabric. Restart and Reconnect: Close and reopen Power BI/Desktop, and try reconnecting to the Dataflows. Microsoft Community & Docs: Fabric documentation on Lakehouse connector

[vikramkumawat]

Hi @rohit1991 ,

Thank You so much for your response, Yes I tried the refresh in a different system with PBI Desktop June 2025 version in that it refreshed without any error. but in my system it is July version. I am not sure if it can be possible that it is happing due to the update or anything else is happning, because to refresh I used same creds and same network, just the difference was PBI Desktop version. 
If the issue is with version only then is it possible to install older versions of PBI Desktop ?

Thanks.

[rohit1991]

Hi @vikramkumawat ,

It definitely sounds like this issue is related to the July 2025 Power BI Desktop update, especially since the same dataflow refresh works perfectly on the June version with identical credentials and environment.

Yes, you can install an older version of Power BI Desktop:

1. Uninstall your current version first.

2. Download and install the June 2025 (or any previous) version from the official Power BI Desktop archive.

[HarishKM]

@vikramkumawat Hey,
I will troubleshoot this in below steps

s1- Go to the data lake or Power BI environment and confirm the lake house content (tables, files, or datasets) exists and is accessible.

s2- I will verify that the names, paths, or dataset IDs used in the dataflow or connector are accurate and up to date.

s3- I will also make sure my user account has proper permissions to access the data lakehouse content.

Thanks

Harish M

Please accepts this as a solution if it is solve your problem and give kudos as well

[vikramkumawat]

Hi @HarishKM ,

Thank You for your response. Actually I am using this report from past few months and nothing is changed, in data source and access permissions. also in febric it is working fine like scheduled refresh working properly with same creds and same data sources. but when i download that and try to refresh this in local with same creds its giving the error.

[bhofbauer]

Same issue. Do we have an update from MS on if they are aware of the problem and working toward a fix?

[andrew_tran]

This issue seems to be related to Expression.Error: Lakehouse.Contents doesn't exits... - Microsoft Fabric Community, I think we can combine with that thread

[dataflip]

Yes, you’re right this issue seems to be related to Expression.Error: Lakehouse.Contents doesn't exist, as mentioned in the Microsoft Fabric Community thread. I agree that it makes sense to combine this with that discussion to avoid duplication and track any official resolutions or updates in one place.

[Anthony_G1]

I'm experiencing this same issue this morning - is there an outage of some kind currently?