Recommended Setup for SQL Server on Azure VM

[CoulterJames2]

I am working with a customer on a new Fabric setup. They have an F2 capacity and need to ingest data from a SQL Server database hosted on an Azure VM (not an Azure SQL Database). The connection from Fabric to the SQL Server database must ensure that data stays on the MS backbone and there is no risk of data going via the public internet. I have limited access to the customer's Azure tenant but I understand that the VM is within its own Virtual Network. I am not a networking expert, but I expected that because the SQL Server was on a VM, a gateway of some kind was needed, but having read some information on Microsft Learn, I am not so sure that this is the case. Can this be achieved using Managed Private Endpoint/Private Links and if so, can you point me in the direction of some easy to follow setup instructions? The connection will be used in CopyData tasks within Data Factory pipelines. We are not using Dataflows Gen2 or Notebooks for data ingestion. I believe that a Cloud connection can be setup to the SQL Server from the 'Manage Connections and Gateways' page in Fabric, but does this ensure the connection is a) secure and b) avoids public internet?

[v-pgoloju]

Hi @CoulterJames2,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @deborshi_nag  for prompt and helpful responses.

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[CoulterJames2]

By 'Fabric Data Gateway' do you mean a VNet Data Gateway?

[deborshi_nag]

The On-premises data gateway @CoulterJames2, not the VNet data gateway - the latter is targeted for Azure PaaS services.  

What is an on-premises data gateway? | Microsoft Learn

[CoulterJames2]

Is there no option to avoid having an On Premises Data Gateway? That will require another VM to be spun up.

[deborshi_nag]

VNet Data Gateway requires F8 and above. 

What is a virtual network (VNet) data gateway | Microsoft Learn

A decicated VM for the gateway is the preferred architecture according to Microsoft best practices, however you can look at exiting VMs within your network, preferably one that is consuming low resources, if you don't intend spinning up a new VM.

[deborshi_nag · Accepted solution]

Hello @CoulterJames2 

Since your customer's SQL Server is on a VM in it's own VNet, there is no private endpoint-native access, and Fabric capacity is <64 - you should use a Fabric Data Gateway. 

Fabric On-Premises Data Gateway runs inside customer's VNet, and data flows through Microsoft backbone network - Data Factory Copy tasks should be able to reach it.