Quickstart: Configure a point-to-site connection to Azure SQL Managed Instance from on-premises

Applies to: Azure SQL Managed Instance

This quickstart teaches you how to connect to Azure SQL Managed Instance by using SQL Server Management Studio (SSMS) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see About Point-to-Site VPN.

Prerequisites

This quickstart:

• Uses the resources created in Create a managed instance as its starting point.
• Requires PowerShell 5.1 and Azure PowerShell 1.4.0 or later on your on-premises client computer. If necessary, see the instructions to install the Azure PowerShell module.
• Requires the newest version of SQL Server Management Studio on your on-premises client computer.

Attach a VPN gateway to a virtual network

1. Open PowerShell on your on-premises client computer.

2. Copy the following PowerShell script to attach a VPN gateway to the SQL Managed Instance virtual network that you created in the Create a managed instance quickstart. This script uses the Azure PowerShell Az Module and does the following for either Windows or Linux-based hosts:

   • Creates and installs certificates on a client machine

   • Calculates the future VPN gateway subnet IP range

   • Creates the gateway subnet

   • Deploys the Azure Resource Manager template that attaches the VPN gateway to the VPN subnet

     $scriptUrlBase = 'https://raw.githubusercontent.com/Microsoft/sql-server-samples/master/samples/manage/azure-sql-db-managed-instance/attach-vpn-gateway'
     
     $parameters = @{
       subscriptionId = '<subscriptionId>'
       resourceGroupName = '<resourceGroupName>'
       virtualNetworkName = '<virtualNetworkName>'
       certificateNamePrefix  = '<certificateNamePrefix>'
       }
     
     Invoke-Command -ScriptBlock ([Scriptblock]::Create((iwr ($scriptUrlBase+'/attachVPNGateway.ps1?t='+ [DateTime]::Now.Ticks)).Content)) -ArgumentList $parameters, $scriptUrlBase
     

3. Paste the script in your PowerShell window and provide the required parameters. The values for <subscriptionId>, <resourceGroup>, and <virtualNetworkName> should match the ones that you used for the Create a managed instance quickstart. The value for <certificateNamePrefix> can be a string of your choice.

   Note

   If you get an error about parsing the Internet Explorer engine, either launch Internet Explorer to complete the initial set up or upgrade to a newer version of PowerShell.

4. Execute the PowerShell script.

Important

Do not continue until the PowerShell script completes.

Create a VPN connection

1. Sign in to the Azure portal.

2. Open the resource group where you created the virtual network gateway, and then open the virtual network gateway resource.

3. Select Point-to-site configuration and then select Download VPN client.

   

4. On your on-premises client computer, extract the files from the zip file and then open the folder with the extracted files.

5. Open the WindowsAmd64 folder and open the VpnClientSetupAmd64.exe file.

6. If you receive a Windows protected your PC message, select More info and then select Run anyway.

   

7. In the User Account Control dialog box, select Yes to continue.

8. In the dialog box referencing your virtual network, select Yes to install the VPN client for your virtual network.

Connect to the VPN connection

1. Go to VPN in Network & Internet on your on-premises client computer and select your SQL managed instance virtual network to establish a connection to this VNet. In the following image, the VNet is named MyNewVNet:

   

2. Select Connect.

3. In the dialog box, select Connect.

   

4. When you're prompted that Connection Manager needs elevated privileges to update your route table, choose Continue.

5. Select Yes in the User Account Control dialog box to continue.

   You've established a VPN connection to your SQL managed instance VNet.

   

Connect with SSMS

1. On the on-premises client computer, open SQL Server Management Studio (SSMS).

2. In the Connect to Server dialog box, enter the fully qualified host name for your SQL managed instance in the Server name box.

3. Select SQL Server Authentication, provide your username and password, and then select Connect.

   

After you connect, you can view your system and user databases in the Databases node. You can also view various objects in the Security, Server Objects, Replication, Management, SQL Server Agent, and XEvent Profiler nodes.

Connection could not be established

If your connection works initially but after some time, you see the error The connection could not be established when you try to connect to the VPN, follow these steps:

1. Open your Windows VPN Settings.
2. Remove the VPN connection.
3. Repeat the steps in Create a VPN connection to download the VPN client and install it again.
4. Connect to the VPN.

Next steps

• For a quickstart showing how to connect from an Azure virtual machine, see Configure a point-to-site connection.
• For an overview of the connection options for applications, see Connect your applications to SQL Managed Instance.
• To restore an existing SQL Server database from on-premises to a managed instance, you can use Azure Database Migration Service for migration or the T-SQL RESTORE command to restore from a database backup file.