Quickstart: Create an Azure SQL Database managed instance
This quickstart walks you through how to create an Azure SQL Database managed instance in the Azure portal.
Sign in to the Azure portal
Sign in to the Azure portal.
Create a managed instance
The following steps show you how to create a managed instance.
Select Create a resource in the upper-left corner of the Azure portal.
Locate managed instance, and then select Azure SQL Managed Instance.
Fill out the SQL managed instance form with the requested information by using the information in the following table.
Setting Suggested value Description Subscription Your subscription. A subscription that gives you permission to create new resources. Managed instance name Any valid name. For valid names, see Naming rules and restrictions. Managed instance admin login Any valid username. For valid names, see Naming rules and restrictions. Don't use "serveradmin" because that's a reserved server-level role. Password Any valid password. The password must be at least 16 characters long and meet the defined complexity requirements. Time zone The time zone to be observed by your managed instance. For more information, see Time zones. Collation The collation that you want to use for your managed instance. If you migrate databases from SQL Server, check the source collation by using
SELECT SERVERPROPERTY(N'Collation')and use that value. For information about collations, see Set or change the server collation.
Location The location in which you want to create the managed instance. For information about regions, see Azure regions. Virtual network Select either Create new virtual network or a valid virtual network and subnet. If a network or subnet is unavailable, it must be modified to satisfy the network requirements before you select it as a target for the new managed instance. For information about the requirements for configuring the network environment for a managed instance, see Configure a virtual network for a managed instance. Enable public endpoint Check this option to enable public endpoint For managed instance to be accessible through the public data endpoint, Enable public endpoint needs to be checked. Allow access from Select one of the options:
- Azure services
- No access
Portal experience enables configuring security group with public endpoint.
Based on your scenario, select one of the following options:
- Azure services - recommended when connecting from Power BI or other multi-tenant service.
- Internet - use for test purposes when you want to quickly spin up a managed instance. It’s not recommended for use in production environments.
- No access - this option creates a deny security rule. You’ll need to modify this rule in order to make managed instance accessible through public endpoint.
Connection type Choose between a Proxy and a Redirect connection type. For more information about connection types, see Azure SQL Database connection policy. Resource group A new or existing resource group. For valid resource group names, see Naming rules and restrictions.
To use the managed instance as an instance failover group secondary, select the checkout and specify the DnsAzurePartner managed instance. This feature is in preview and isn't shown in the following screenshot.
Select Pricing tier to size compute and storage resources and to review the pricing tier options. The General Purpose pricing tier with 32 GB of memory and 16 vCores is the default value.
Use the sliders or text boxes to specify the amount of storage and the number of virtual cores.
When you're finished, select Apply to save your selection.
Select Create to deploy the managed instance.
Select the Notifications icon to view the status of the deployment.
Select Deployment in progress to open the managed instance window to further monitor the deployment progress.
For the first instance in a subnet, deployment time is typically much longer than in subsequent instances. Don't cancel the deployment operation because it lasts longer than you expected. Creating the second managed instance in the subnet takes only a couple of minutes.
Review resources and retrieve your fully qualified server name
After the deployment is successful, review the resources that were created and retrieve the fully qualified server name for use in later quickstarts.
Open the resource group for your managed instance. View its resources that were created for you in the create a managed instance quickstart.
Select the route table to review the user-defined route (UDR) table that was created for you.
In the route table, review the entries to route traffic from and within the managed instance virtual network. If you create or configure your route table manually, you must be sure to create these entries in the route table.
Return to the resource group, and select the network security group to review the security rules.
Review the inbound and outbound security rules. If you have configured public endpoints for your managed instance, see the article Configure public endpoint for more information.
Return to the resource group, and select your managed instance.
On the Overview tab, locate the Host property. Copy the fully qualified host address for the managed instance for use in the next quickstart.
The name is similar to your_machine_name.a1b2c3d4e5f6.database.windows.net.
- To learn about how to connect to a managed instance:
- For an overview of the connection options for applications, see Connect your applications to a managed instance.
- For a quickstart that shows how to connect to a managed instance from an Azure virtual machine, see Configure an Azure virtual machine connection.
- For a quickstart that shows how to connect to a managed instance from an on-premises client computer by using a point-to-site connection, see Configure a point-to-site connection.
- To restore an existing SQL Server database from on-premises to a managed instance:
- Use the Azure Database Migration Service (DMS) for migration to restore from a database backup file.
- Use the T-SQL RESTORE command to restore from a database backup file.
- For advanced monitoring of managed instance database performance with built-in troubleshooting intelligence, see Monitor Azure SQL Database by using Azure SQL Analytics.
Send feedback about: