Forum Discussion
Virtual Network Gateways not publishing data into Lakehouse
Hi LouisSh ,
We checked trace with the ReqeustId you provided and noticed that your gateway cannot resolve api.powerbi.com. It seems that there is an incorrect DNS record in the private DNS zone probably becauase you had a PowerBI privatelink setup that hasn't being cleaned up correctly.
In the future, you can get more insight of the failure by checking the diagnostic logs (Download logs on the VNet data gateway | Microsoft Learn), and use the network troubleshooting tool for networking problems (Troubleshoot a virtual network (VNet) network | Microsoft Learn).
Thanks.
Hi LouisSh
I have tried to repro the same scenario but didn't find any difficulty in publishing the data into a destination which is a Lakehouse using Dataflow Gen2. Please find the screenshots for reference.
You can also try connecting to the Azure SQL database uisng onprem-gateway.
For more details please refer to the below mentioned links:
Install an on-premises data gateway.
How to access on-premises data sources in Data Factory for Microsoft Fabric.
On-premises data gateway considerations for data destinations in Dataflow Gen2.
I also tried connecting using on-prem gateway:
Please try connecting as stated above and let us know if you have any further issues.
This might seems to be an intermittent issue. Can you please try again after a day and let me know if you are still facing this issue?
Hope this helps.
Thanks.
Hi v-cboorla-msft
As I understand from your first set of screenshots to recreate the issue, you have not used a virtual-network gateway as the data-gateway = none, so won't be able to recreate the issue I am seeing. As for it being a intermittent issue, we have been trying overcome this for 3-4 weeks now. We would prefer to continue to use the virtual gateway rather than an on premise gateway. The virtual gateway works fine connecting to the Azure SQL, but fails pushing it into the Lakehouse inside Fabric, this is where the problem lies.
Is there anything additional I can provide to help understand the issue?
Hi LouisSh ,
We checked trace with the ReqeustId you provided and noticed that your gateway cannot resolve api.powerbi.com. It seems that there is an incorrect DNS record in the private DNS zone probably becauase you had a PowerBI privatelink setup that hasn't being cleaned up correctly.
In the future, you can get more insight of the failure by checking the diagnostic logs (Download logs on the VNet data gateway | Microsoft Learn), and use the network troubleshooting tool for networking problems (Troubleshoot a virtual network (VNet) network | Microsoft Learn).
Thanks.