Unable to select Lakehouse as output destination in Gen2 Dataflow

[mh20221111]

Hi ,

I'm experiencing an issue when trying to configure a Gen2 Dataflow in Power BI Service to output data to a Lakehouse. When I attempt to select Lakehouse as the destination, I receive the following error:

Exception occurred: The specified data source type is not supported. Data source type: Lakehouse. (Session ID: a509ed9f-d906-411a-ba97-eb23b582cf61, Region: asia)

What’s puzzling is that I have another Gen2 Dataflow in the same workspace that successfully outputs data to the same Lakehouse without any problems. This suggests that the Lakehouse itself is accessible and functioning correctly.

Additionally, in the "Advanced settings" section, I see the option "Navigate using full hierarchy", but changing this setting doesn’t seem to affect the behavior — the error persists regardless of the selection.

Has anyone encountered this issue before? Could this be related to workspace configuration, regional limitations, or a bug in the service?

Any help or suggestions would be greatly appreciated.

Thanks in advance!

[ANVS]

Hi @mh20221111 

This issue must be resolved after refreshing, but if it doesnt resolve even after recreating the Data Flow Gen2 or after refreshing, raise a fabric Support ticket!

If you find my answer Helpful, feel free to give some kudos.
And also mark it as accepted solution!

[mh20221111]

Hi @AntoineW  @tayloramy ,

Thank you! I’ll contact Microsoft Support about this issue. I appreciate your help.

[tayloramy]

I agree with @AntoineW, if recreating the dataflow does not resolve the problem submit a ticket. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[AntoineW]

Hi @mh20221111,

It's seems like a bug, if the non-working dataflow was cloned or created before the workspace had full Fabric capabilities enabled, it might still be tied to an older internal connector catalog.
Recreating it from scratch usually fixes it.

Sometimes you have to refresh the whole page on the dataflow gen2 and the lakehouse to sync metadata.

Thanks for sharing this problem, and it's not working properly, raise a Fabric Support ticket ! 

Antoine

[mh20221111]

Hi @AntoineW ,
I looked into the issue further and found that the dataflow which works correctly is connected to a cloud-based database. The one that fails to allow Lakehouse as an output is connected to an on-premises database via gateway. This difference might be the reason why Lakehouse isn't available as a destination in Gen2 Dataflow.

※I'm also currently in contact with Microsoft Support regarding this issue.

Miho