What should Azure SQL Server endpoint be connected to?

Hello @Steven Karp ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you would like to you would like to connect to your Azure virtual network and related services such as Blob Storage and an Azure SQL using Bastion and want to know what are the best practices to achieve this.

Azure Bastion is a service that lets you connect to a virtual machine using your browser and the Azure portal, or via the native SSH or RDP client already installed on your local computer. Azure Bastion is deployed to a virtual network and supports virtual network peering. Specifically, Azure Bastion manages RDP/SSH connectivity to VMs created in the local or peered virtual networks.

Azure Bastion requires a dedicated subnet "AzureBastionSubnet". You must create this subnet in the same virtual network that you want to deploy Azure Bastion to. The subnet must have the following configuration:

• Subnet name must be "AzureBastionSubnet".
• Subnet size must be /26 or larger (/25, /24 etc.).
• For host scaling, a /26 or larger subnet is recommended. Using a smaller subnet space limits the number of scale units. For more information, see the Host scaling section of this article.
• The subnet must be in the same VNet and resource group as the bastion host.
• The subnet cannot contain additional resources.

Refer: https://video2.skills-academy.com/en-us/azure/bastion/configuration-settings#subnet

Now to connect to your services such as Blob Storage or Azure SQL using Bastion, you can make use of Azure Private Endpoint.

A private endpoint is a network interface that uses a private IP address from your virtual network. This network interface connects you privately and securely to a service that's powered by Azure Private Link.

Refer: https://video2.skills-academy.com/en-us/azure/private-link/private-endpoint-overview

To connect to your Blob Storage or Azure SQL using Bastion, you should follow the below steps:

• Deploy bastion in your Vnet with its own dedicated AzureBastionSubnet. Nothing else can be deployed in this subnet.
• Create a virtual machine in a separate subnet (VM subnet in the same Vnet).
• Create an Azure Storage/Azure SQL server and private endpoint. The private endpoint should be created in your VM subnet.
• Disable public access to Azure Storage/Azure SQL server account and use private access.
• Test connectivity to the storage/SQL server private endpoint by connecting to the VM using Bastion and then accessing SQL server/storage account from this VM by installing Microsoft Azure Storage Explorer or SQL Server Management Studio in the VM.

Below are the docs showing the step-by-step tutorial on how to Connect to an Azure Storage/SQL server account using an Azure Private Endpoint and Azure Bastion:

Azure Storage account: https://video2.skills-academy.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal

Azure SQL server: https://video2.skills-academy.com/en-us/azure/private-link/tutorial-private-endpoint-sql-portal

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Hi,

Azure Bastion is used to connect to a IaaS instance deployed in a VNET. If you have a SQL deployed as VM in the VNET, then you can connect to that VM via Bastion. But if you want to connect to a PaaS resource from the Bastion, it is not possible. You will need to use Bastion to get to one of the VMs and then you can connect storage endpoint from there using service endpoint or Private Endpoint.