Create SQL MI with jumpbox inside new virtual network
This template allows you to create a Azure SQL Database Managed Instances inside a new virtual network with Virtual Machine that comes with the latest version of SQL Server Management Studio (SSMS) preinstalled.
Tags: Azure, SqlDb, Managed Instance, SSMS, Microsoft.Network/networkSecurityGroups, Microsoft.Network/routeTables, Microsoft.Network/virtualNetworks, Microsoft.Sql/managedInstances, SystemAssigned, Microsoft.Compute/virtualMachines, extensions, CustomScriptExtension, Microsoft.Network/networkInterfaces, Microsoft.Network/publicIpAddresses
Solution overview and deployed resources
This deployment will create an Azure Virtual Network with two subnets ManagedInstance and Management. Managed Instance will be deployed in ManagedInstance subnet. Virtual machine with the latest version of SQL Server Management Studio (SSMS) will be deployed in Management subnet.
You can click the "Deploy to Azure" button at the beginning of this document or follow the instructions for command line deployment using the scripts in the root of this repo, and populate following parameters:
- Name of the Managed Instance that will be create including Managed Instance admin name and password
- Name of the Azure Virtual Network that will be created and configured, including the address range that will be associated to this VNet. Default address range is 10.0.0.0/16 but you could change it to fit your needs.
- Name of the subnet where Managed Instance will be created. The name will be ManagedInstance, if you don't want to change it. Default address range is 10.0.0.0/24 but you could change it to fit your needs.
- Name of the subnet where VM with SSMS will be created. The name will be Management, if you don't want to change it. Default address range is 10.0.1.0/24 but you could change it to fit your needs.
- Sku name that combines service tear and hardware generation, number of virtual cores and storage size in GB. The table below shows supported combinations.
- License type that could be BasePrice if you are eligible for Azure Hybrid Use Benefit for SQL Server or LicenseIncluded otherwise
|Tier||General Purpose||Busines Critical|
|Hardware||Gen 5||Gen 5|
|Min storage size||32||32|
|Max storage size||8192||1024 GB for 8, 16 vCores
2048 GB for 24 vCores
4096 GB for 32, 40, 64, 80 vCores
Deployment of first instance in the subnet might take up to six hours, while subsequent deployments take up to 1.5 hours. This is because a virtual cluster that hosts the instances needs time to deploy or resize the virtual cluster. For more details visit Overview of Azure SQL Managed Instance management operations
Each virtual cluster is associated with a subnet and deployed together with first instance creation. In the same way, a virtual cluster is automatically removed together with last instance deletion leaving the subnet empty and ready for removal.