Dataflow Gen2 cannot see Lakehouse in same workspace — EntityNotFound (Lakehouse034) error

Hi Powerbidevelop7 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

Hi Powerbidevelop7,

Hope you're doing well!

--> SITUATION :

- The error "Lakehouse034 / EntityNotFound" combined with a 404 on the West Europe redirect URL while your workspace is tagged as Germany region is the smoking gun. This is a cross-region metadata routing issue, not a permissions or provisioning problem. Here's the chain of events:

1. Your new tenant was provisioned with its home region set to Germany (probably "German West Central").

2. Your Dataflow Gen2 backend is still routing API calls through the West Europe WABI endpoint ("wabi-west-europe-e-primary-redirect").

3. The Lakehouse metadata lives in Germany, West Europe can't find it --> EntityNotFound.

So, this is a known pain point with new tenants on F-SKUs where the capacity region and the tenant's default Power BI region don't align immediately.

--> SOLUTION :

1. Verify your tenant's actual home region : Go to Admin Portail --> About MS Fabric and check "Data storage region". Then check your F2 capacity region. They need to match or at least be in the same geographic boundary.

2. Reassign your workspace capacity : Even if it looks assigned, try this --> Remove the workspace from F2 capacity --> Wait 2 or 3 minutes --> Reassign it to F2. Why ? This forces a metadata reregistration and often fixes the routing mismatch on new tenants.

3. Check the Dataflow Gen2 staging Lakehouse : Dataflow Gen2 uses an auto-created staging Lakehouse internally. On new tenants, this sometimes gets provisioned in the wrong region or fails silently. So, Go to your workspace settings --> Dataflow Gen2 settings --> verify a staging Lakehouse exists. If it's missing or showing an error, delete it and let Fabric recreate it.

4. Force reevaluation via Support ticket : Since this is a new tenant +F2+Germany region combo, there's a real chance the WABI routing table hasn't been updated for your tenant ID on the backend. This is not someting you can fix yourself. File a Fabric support ticket with:

--> Your tenant ID

--> Workspace ID (e7190939-ebd2-4290-bab6-351cc330059a)

--> The exact error + request ID (97a65eef-a89e-44a5-bd1c-450cf6fd8711)

--> Mention specifically: "West Europe WABI endpoint returning 404 for a Germany-region tenant"

That Request ID is gold, because support can trace the exact failed call.

--> Why it works in your older tenant ? 

Your older tenant was provisioned before the Germany region was added as a distinct boundary. Its routing was established against West Europe and everything is consistent. Your new tenant got Germany routing for storage but the Dataflow Gen2 service registration didn't fully follow, and a timing/provisioning race condition that happens specifically with new tenants on new regional capacity.

--> Quick workaround while you wait :

Since Notebooks work fine against the Lakehouse, you can use a Fabric Notebook as a bridge:

• Load/transform your data in the Notebook
• Write to the Lakehouse via spark.write
• Trigger the Notebook from a Data Pipeline on a schedule

Not elegant, but it unblocks you immediately while Microsoft sorts out the backend routing.

Finally, Your instinct about provisioning was right 😉 it's just more specifically a regional routing registration issue on a new tenant, not a generic "not provisioned yet." The support ticket with that Request ID should get it resolved within 1 or 3 business days normally. Hope this helps. Feel free to ask me questions if needed, and don’t forget to Accept as Solution if this guidance worked for you. That's motivate me to keep helping.

Best regards,

Oussama (Data Consultant & Fabric's Expert)

Hi,

This is a classic region mismatch issue, and the clue is right inside your error message.

Look at the URL in the error: it points to wabi-west-europe, which is the West Europe region. But at the bottom of the error, the region is listed as germany.

What is happening is that Dataflow Gen2 runs on the Power Query Online backend, which is hosted in your primary Power BI tenant home region (West Europe). When it tries to read or write to your Lakehouse, it calls the metadata API in West Europe. Because your F2 capacity is provisioned in Germany, the West Europe endpoint cannot find the Lakehouse entity, resulting in the 404 EntityNotFound error.

Here is how you can resolve this:

Point 1: Enable Cross-Region Data Movement In the Fabric Admin Portal, under Tenant Settings, search for the setting named Allow cross-region data movement. Ensure this is enabled for the users or the entire tenant. If this is disabled, the Power Query backend in West Europe is blocked from communicating with the Lakehouse storage in Germany.

Point 2: Match Regions (Best Practice) If this is a new tenant, check where your F2 capacity is provisioned. If the capacity is in Germany, but your Power BI home region is in West Europe, you will face latency and connectivity challenges. The easiest fix is to delete and recreate your F2 capacity in the West Europe region so it matches your tenant home region. Once both are in the same region, Dataflow Gen2 will resolve the Lakehouse instantly without needing cross-region routing.

Point 3: Wait for DNS Propagation Since this is a brand new tenant, backend route syncs between Microsoft regional data hubs can sometimes take up to 24 hours to fully propagate. If you just created the capacity, it might start working on its own after the global route tables update, but aligning the regions is still the recommended path.

Hope this helps! Let me know if aligning the regions fixes the error.

Thanks!
Datta Sable

Hi Powerbidevelop7 ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the suggestions  provided by the community members for the issue worked. Please feel free to contact us if you have any further questions.

Thanks and regards