Forum Discussion
Copy Data with VNET gateway error
Hi TK12345 ,
Before continuing the investigation, we need to clarify a couple of things.
Are you using Azure SQL Database / Azure SQL Managed Instance in the cloud, or is it a SQL Server on a VM or on-premises environment? Depending on this, the diagnosis changes:
- If it is on-premises, first verify that the gateway is active and working correctly, as a gateway with issues can allow preview to work but fail when running the full pipeline execution.
- If it is Azure cloud, although using the VNET is valid and adds an extra security layer, try creating the same Copy Data activity using a direct connection without the VNET. If the pipeline works correctly with that direct connection, the problem is confirmed to be in the gateway and not in the source or destination.
In any case, verify that the connection is correctly configured and in active status from the Connections section in Fabric before running the pipeline again.
This is the quickest way to identify where the error is really coming from.
Hope this helps.
If my comments helped solve your question, it would be great if you could like the two comments and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.
Thanks a lot, I really appreciate it.
- TK123453 months agoResolver II
Hi there,
It is a SQL Server in a private network, reachable througout my VNET.
LIMIT 1 / TOP 1 still gives me directly the preview but the copy activity still stays in transfer state for a few minutes before giving the same error message.- v-aatheeque3 months agoCommunity Support
Hi TK12345
Thanks for the update and for validating all the suggested troubleshooting steps.
Since the source preview is working successfully, even minimal queries such as TOP 1 are returning data correctly, but the Copy Activity consistently fails during the transfer/write phase to the Lakehouse, this behavior appears to be related to the VNET gateway network path, OneLake/Azure Storage connectivity, or a backend Fabric service issue rather than the SQL source itself.
As the issue persists even after recreating the pipeline, connection and Lakehouse, the next recommended step would be to raise a Microsoft Fabric Support and Status | Microsoft Fabric for deeper backend investigation.