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 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.