Dataflow Gen2 Issue

Hi all

Sorry for the late reply. Here is the update of this issue. 

Symptom

• Refresh of a Dataflow Gen 2 with output destination failing via gateway. Gateway refreshes in Dataflows Gen2 writes directly to destination from the Gateway (LakeHouse, DataLake, etc.).
• ​Dataflows through a Gateway may fail to reach DataLake, LakeHouse, or other destination if the gateway is not configured to allow connections directly to that destination.

Solutions and Workarounds

There is not going to be a fix for this, this is by design, please refer to below details to overcome the situation:

• The gateway must be configured to be able to pass through the firewall or proxy to reach destination data source. If the user is using a proxy server, this may require enable-listing URLs to appropriate destinations. i.e. (*-datawarehouse.pbidedicated.windows.net) for LakeHouse, (*.dfs.core.windows.net) for DataLake, etc.
• Users using LakeHouse destinations must be running at least the May 2023 release of the gateway (the connector is not available in gateways prior to this release).
• Public doc updates for this are now live - https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-proxy#configure-gateway-for-output-destinations .

Best Regards,
Community Support Team _ Jing
If this post helps, please Accept it as Solution to help other members find it.