Dataflows Gen2 cannot access Lakehouse Files — missing OneLake internal provider

Hello pbiadminjenhill, 

What you’re seeing is expected behavior based on the current design of Dataflows Gen2 in Microsoft Fabric.

Dataflows Gen2 connects to a Lakehouse through the SQL analytics endpoint, which exposes Delta tables only. It does not surface the Lakehouse Files folder structure. As a result:

• The Lakehouse connector shows tables, not /Files/...

• File paths are treated as external sources and may prompt for a gateway

• Combining Parquet files directly from Lakehouse Files isn’t supported

• Incremental refresh applies to table sources, not raw file paths

This is a product capability boundary, not a tenant, region, trial, or GoDaddy limitation.

If you need to transform Parquet files stored in Files, first materialize them as Delta tables (via Notebook or Pipeline). Once the data exists as a Lakehouse table, Dataflows Gen2 can access it and support transformations and incremental refresh.