Private Endpoint not resolved using Private Link - VNet Data Gateway

Anonymous

Not applicable

2 years ago

Clients can connect to a private endpoint from the same virtual network, from a peer-to-peer interconnected virtual network in the same region, or through a cross-region virtual network. In addition, clients can connect locally using ExpressRoute, private peering, or VPN tunnels. The following simplified diagram shows common use cases.

First, please refer to the official documentation below to ensure that the Virtual Network Data Gateway is created and used correctly. Also, make sure that your Azure VNet region is in a supported region.
Create virtual network (VNet) data gateways | Microsoft Learn
Use virtual network data gateway and data sources in Power BI | Microsoft Learn

The detailed steps for creating a dedicated endpoint in Azure SQL are as follows:

In the Azure portal, browse to an Azure SQL Server (not an individual SQL Database)
Under the Security section, select Networking sub-section
Click the Private Access tab
Click + Private Endpoint to create a new private endpoint
On the Basics tab, enter the following information:
- Select a Resource Group or create a new one
- Provide a name E.G. dhsqlprivateendpoint
- Select the appropriate region E.G. UK South
On the Resource tab, ensure the following property is set:
- Target Sub-Resource: sqlServer
On the Virtual Network tab, enter the following information:
- Virtual Network: Select the VNet created in the first step
- Subnet: The default subnet should be automatically selected
On the DNS tab, ensure the following property is set:
- Integrate With Private DNS Zone: Yes
Click Review & Create