Frequently asked questions for SQL Server running on Windows virtual machines in Azure

This article provides answers to some of the most common questions about running SQL Server on Windows Virtual Machines in Azure.


This article focuses on issues specific to SQL Server on Windows VMs. If you are running SQL Server on Linux VMs, see the Linux FAQ.

If your Azure issue is not addressed in this article, visit the Azure forums on MSDN and Stack Overflow. You can post your issue in these forums, or post to @AzureSupport on Twitter. You also can submit an Azure support request. To submit a support request, on the Azure support page, select Get support.


  1. What SQL Server virtual machine gallery images are available?

    Azure maintains virtual machine images for all supported major releases of SQL Server on all editions for both Windows and Linux. For more information, see the complete list of Windows VM images and Linux VM images.

  2. Are existing SQL Server virtual machine gallery images updated?

    Every two months, SQL Server images in the virtual machine gallery are updated with the latest Windows and Linux updates. For Windows images, this includes any updates that are marked important in Windows Update, including important SQL Server security updates and service packs. For Linux images, this includes the latest system updates. SQL Server cumulative updates are handled differently for Linux and Windows. For Linux, SQL Server cumulative updates are also included in the refresh. But at this time, Windows VMs are not updated with SQL Server or Windows Server cumulative updates.

  3. Can SQL Server virtual machine images get removed from the gallery?

    Yes. Azure only maintains one image per major version and edition. For example, when a new SQL Server service pack is released, Azure adds a new image to the gallery for that service pack. The SQL Server image for the previous service pack is immediately removed from the Azure portal. However, it is still available for provisioning from PowerShell for the next three months. After three months, the previous service pack image is no longer available. This removal policy would also apply if a SQL Server version becomes unsupported when it reaches the end of its lifecycle.

  4. Is it possible to deploy an older image of SQL Server that is not visible in the Azure portal?

    Yes, by using PowerShell. For more information about deploying SQL Server VMs using PowerShell, see How to provision SQL Server virtual machines with Azure PowerShell.

  5. Can I create a VHD image from a SQL Server VM?

    Yes, but there are a few considerations. If you deploy this VHD to a new VM in Azure, you do not get the SQL Server Configuration section in the portal. You must then manage the SQL Server configuration options through PowerShell. Also, you will be charged for at the rate of the SQL VM your image was originally based on. This is true even if you remove SQL Server from the VHD before deploying.

  6. Is it possible to set up configurations not shown in the virtual machine gallery (For example Windows 2008 R2 + SQL Server 2012)?

    No. For virtual machine gallery images that include SQL Server, you must select one of the provided images either through the Azure portal or via PowerShell.


  1. How do I create an Azure virtual machine with SQL Server?

    The easiest solution is to create a Virtual Machine that includes SQL Server. For a tutorial on signing up for Azure and creating a SQL VM from the portal, see Provision a SQL Server virtual machine in the Azure portal. You can select a virtual machine image that uses pay-per-second SQL Server licensing, or you can use an image that allows you to bring your own SQL Server license. You also have the option of manually installing SQL Server on a VM with either a freely licensed edition (Developer or Express) or by reusing an on-premises license. If you bring your own license, you must have License Mobility through Software Assurance on Azure. For more information, see Pricing guidance for SQL Server Azure VMs.

  2. How can I migrate my on-premises SQL Server database to the Cloud?

    First create an Azure virtual machine with a SQL Server instance. Then migrate your on-premises databases to that instance. For data migration strategies, see Migrate a SQL Server database to SQL Server in an Azure VM.


  1. How can I install my licensed copy of SQL Server on an Azure VM?

    There are two ways to do this. You can provision one of the virtual machine images that supports licenses, which is also known as bring-your-own-license (BYOL). Another option is to copy the SQL Server installation media to a Windows Server VM, and then install SQL Server on the VM. However, if you install SQL Server manually, there is no portal integration and the SQL Server IaaS Agent Extension is not supported, so features such as Automated Backup and Automated Patching will not work in this scenario. For this reason, we recommend using one of the BYOL gallery images. To use BYOL or your own SQL Server media on an Azure VM, you must have License Mobility through Software Assurance on Azure. For more information, see Pricing guidance for SQL Server Azure VMs.

  2. Do I have to pay to license SQL Server on an Azure VM if it is only being used for standby/failover?

    If you have Software Assurance and use License Mobility as described in Virtual Machine Licensing FAQ, then you do not have to pay to license one SQL Server participating as a passive secondary replica in an HA deployment. Otherwise, you need to pay to license it.

  3. Can I change a VM to use my own SQL Server license if it was created from one of the pay-as-you-go gallery images?

    Yes. You can move easily move between the two licensing models, if you originally started with a pay-as-you-go gallery image. However, you will not be able to switch your license to PAYG if you initially started with a BYOL image. For more information, see How to change the licensing model for a SQL Server VM.


    Currently, this facility is available only for Public Cloud customers.

  4. Should I use BYOL images or SQL VM RP to create new SQL VM?

    Bring-your-own-license (BYOL) images are only available for EA customers. Other customers who have Software Assurance should use the SQL VM resource provider to create a SQL VM with Azure Hybrid Benefit (AHB).

  5. Will switching licensing models require any downtime for SQL Server?

    No. Changing the licensing model does not require any downtime for SQL Server as the change is effective immediately and does not require a restart of the VM. However, to register your SQL Server VM with the SQL VM resource provider, the SQL IaaS extension is a prerequisite and installing the SQL IaaS extension restarts the SQL Server service. As such, if the SQL IaaS extension needs to be installed, then it should be done during a maintenance window.

  6. Can CSP subscriptions activate the Azure Hybrid Benefit?

    Yes, the Azure Hybrid Benefit is available for CSP subscriptions. CSP customers should first deploy a pay-as-you-go image, and then change the licensing model to bring-your-own-license.

  7. Will registering my VM with the new SQL VM resource provider bring additional costs?

    No. The SQL VM resource provider just enables additional manageability for SQL Server on Azure VM with no additional charges.

  8. Is the SQL VM resource provider available for all customers?

    Yes. All customers are able to register with the new SQL VM resource provider. However, only customers with Software Assurance Benefit can activate the Azure Hybrid Benefit (AHB) (or BYOL) on a SQL Server VM.

  9. What happens to the Microsoft.SqlVirtualMachine resource if the VM resource is moved or dropped?

    When the Microsoft.Compute/VirtualMachine resource is dropped or moved, then the associated Microsoft.SqlVirtualMachine resource is notified to asynchronously replicate the operation.

  10. What happens to the VM if the Microsoft.SqlVirtualMachine resource is dropped?

    The Microsoft.Compute/VirtualMachine resource is not impacted when the Microsoft.SqlVirtualMachine resource is dropped. However, the licensing changes will default back to the original image source.

  11. Is it possible to register self-deployed SQL Server VMs with the SQL VM resource provider?

    Yes. If you deployed SQL Server from your own media, and installed the SQL IaaS extension you can register your SQL Server VM with the resource provider to get the manageability benefits provided by the SQL IaaS extension. However, you are unable to convert a self-deployed SQL VM to pay-as-you-go.


  1. Can I install a second instance of SQL Server on the same VM? Can I change installed features of the default instance?

    Yes. The SQL Server installation media is located in a folder on the C drive. Run Setup.exe from that location to add new SQL Server instances or to change other installed features of SQL Server on the machine. Note that some features, such as Automated Backup, Automated Patching, and Azure Key Vault Integration, only operate against the default instance, or a named instance that was configured properly (See Question 3).

  2. Can I uninstall the default instance of SQL Server?

    Yes, but there are some considerations. As stated in the previous answer, there are features that rely on the SQL Server IaaS Agent Extension. If you uninstall the default instance without removing the IaaS extension also, the extension continues to look for it and may generate event log errors. These errors are from the following two sources: Microsoft SQL Server Credential Management and Microsoft SQL Server IaaS Agent. One of the errors might be similar to the following:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.

    If you do decide to uninstall the default instance, also uninstall the SQL Server IaaS Agent Extension as well.

  3. Can I use a named instance of SQL Server with the IaaS extension?

    Yes, if the named instance is the only instance on the SQL Server, and if the original default instance was uninstalled properly. If there is no default instance and there are multiple named instances on a single SQL Server VM, the IaaS extension will fail to install.

  4. Can I remove SQL Server completely from a SQL VM?

    Yes, but you will continue to be charged for your SQL VM as described in Pricing guidance for SQL Server Azure VMs. If you no longer need SQL Server, you can deploy a new virtual machine and migrate the data and applications to the new virtual machine. Then you can remove the SQL Server virtual machine.

Updating and Patching

  1. How do I change to a different version/edition of the SQL Server in an Azure VM?

    Customers can change their version/edition of SQL Server by using setup media that contains their desired version or edition of SQL Server. Once the edition has been changed, use the Azure portal to modify the edition property of the VM to accurately reflect billing for the VM. For more information, see change edition of a SQL Server VM.

  2. How are updates and service packs applied on a SQL Server VM?

    Virtual machines give you control over the host machine, including when and how you apply updates. For the operating system, you can manually apply windows updates, or you can enable a scheduling service called Automated Patching. Automated Patching installs any updates that are marked important, including SQL Server updates in that category. Other optional updates to SQL Server must be installed manually.


  1. Are SQL Server Failover Cluster Instances (FCI) supported on Azure VMs?

    Yes. You can create a Windows Failover Cluster on Windows Server 2016 and use Storage Spaces Direct (S2D) for the cluster storage. Alternatively, you can use third-party clustering or storage solutions as described in High availability and disaster recovery for SQL Server in Azure Virtual Machines.


    At this time, the SQL Server IaaS Agent Extension is not supported for SQL Server FCI on Azure. We recommend that you uninstall the extension from VMs that participate in the FCI. This extension supports features, such as Automated Backup and Patching and some portal features for SQL. These features will not work for SQL VMs after the agent is uninstalled.

  2. What is the difference between SQL VMs and the SQL Database service?

    Conceptually, running SQL Server on an Azure virtual machine is not that different from running SQL Server in a remote datacenter. In contrast, SQL Database offers database-as-a-service. With SQL Database, you do not have access to the machines that host your databases. For a full comparison, see Choose a cloud SQL Server option: Azure SQL (PaaS) Database or SQL Server on Azure VMs (IaaS).

  3. How do I install SQL Data tools on my Azure VM?

    Download and install the SQL Data tools from Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013.

  4. Are distributed transactions with MSDTC supported on SQL Server VMs?

    Yes. Local DTC is supported for SQL Server 2016 SP2 and greater. However, applications must be tested when utilizing Always On availability groups, as transactions in-flight during a failover will fail and must be retried. Clustered DTC is available starting with Windows Server 2019.


Windows VMs:

Linux VMs: