
Configure Always On availability groups in Azure VM (GUI).

This article requires that your availability groups are already configured. If you prefer, you can manually configure an availability group. This template automatically creates an internal load balancer for you. You can use the Microsoft template to automatically create the availability group in Resource Manager. Both SQL Server virtual machines must belong to the same availability set. To complete this task, you need to have a SQL Server Always On availability group deployed in Azure VMs that are running with Resource Manager. If an availability group spans multiple regions, each region needs a load balancer. The load balancer stores the IP address for the availability group listener. An availability group requires a load balancer when the SQL Server instances are on Azure Virtual Machines. This article explains how to create a load balancer for a SQL Server Always On availability group in Azure Virtual Machines within a single subnet that are running with Azure Resource Manager.

If you've already created your availability group in a single subnet, you can migrate it to a multi-subnet environment. Simplify your deployment and eliminate the need for an Azure Load Balancer or distributed network name (DNN) for your Always On availability group by creating your SQL Server virtual machines (VMs) in multiple subnets within the same Azure virtual network. There are many methods to deploy an availability group.
