Use the Add Azure Replica Wizard (SQL Server)
Updated: May 17, 2016
Applies To: SQL Server 2016
Use the Add Azure Replica Wizard to help you create a new Windows Azure VM in hybrid IT and configure it as a secondary replica for a new or existing Always On availability group.
Before you begin:
To add a replica, using: Add Azure Replica Wizard (SQL Server Management Studio)
If you have never added any availability replica to an availability group, see the "Server instances" and "Availability groups and replicas" sections in Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server).
You must be connected to the server instance that hosts the current primary replica.
You must have a hybrid-IT environment where your on-premise subnet has a site-to-site VPN with Windows Azure. For more information, see Configure a Site-to-Site VPN in the Management Portal.
Your availability group must contain on-premise availability replicas.
Clients to the availability group listener must have connectivity to the Internet if they want to maintain connectivity with the listener when the availability group is failed over to a Windows Azure replica.
Prerequisites for using full initial data synchronization You will need to specify a network share in order for the wizard to create and access backups. For the primary replica, the account used to start the Database Engine must have read and write file-system permissions on a network share. For secondary replicas, the account must have read permission on the network share.
If you are unable to use the wizard to perform full initial data synchronization, you need to prepare your secondary databases manually. You can do this before or after running the wizard. For more information, see Manually Prepare a Secondary Database for an Availability Group (SQL Server).
The Add Azure Replica Wizard can be launched from the Specify Replicas Page. There are two ways to reach this page:
Once you have launched the Add Azure Replica Wizard, follow the steps below:
First, download a management certificate for your Windows Azure subscription. Click Download to open the sign-in page.
Sign in to Microsoft Azure with your Microsoft account or your organizational account. Your Microsoft or organizational account is in the format of an email address, such as HYPERLINK "mailto:email@example.com" firstname.lastname@example.org. For more information about Azure credentials, see Microsoft Account for Organizations FAQ and Troubleshooting sign-in problems with your organizational account.
Next, connect to your subscription by clicking Connect. Once you are connected, the drop-down lists are populated with your Windows Azure parameters, such as Virtual Network and Virtual Network Subnet.
Specify the settings for the Windows Azure VM that will host the new secondary replica:
The name of the SQL Server image to use for the Windows Azure VM
The size of the Windows Azure VM
The DNS name of the Windows Azure VM
The username of the default administrator for the Windows Azure VM
VM Administrator Password (and Confirm Password)
The password for the default administrator for the Windows Azure VM
The virtual network in which to place the Windows Azure VM
Virtual Network Subnet
The virtual network subnet in which to place the Windows Azure VM
The Active Directory (AD) domain to join the Windows Azure VM
The AD username used to join the Windows Azure VM to the domain
The password used to join the Windows Azure VM to the domain
Click OK to commit your settings and exit the Add Azure Replica Wizard.
Continue with the rest of the configuration steps for Specify Replicas Page as you do for any new replica.
Once you are finished with the Availability Group Wizard or the Add Replica to Availability Group Wizard, the configuration process performs all operations in Windows Azure to create the new VM, join it to the AD domain, add it to the Windows cluster, enable Always On High Availability, and add the new replica to the availability group.
Overview of Always On Availability Groups (SQL Server)
Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server)
Add a Secondary Replica to an Availability Group (SQL Server)