SQL VM content fixes

Author: MashaMSFT

articles/virtual-machines/windows/sql/media/virtual-machines-windows-portal-sql-availability-group-dr/add-cluster-ip-address.png

@@ -92,26 +92,33 @@ To create a replica in a remote data center, do the following steps:
 
 1. [Add the new SQL Server to the Windows Server Failover Cluster](virtual-machines-windows-portal-sql-availability-group-tutorial.md#addNode).
 
-1. Create an IP address resource on the cluster.
+1. Add an IP address resource to the cluster. 
+   You can create the IP address resource in Failover Cluster Manager. Select the name of the cluster, then right-click the cluster name under **Cluster Core Resources** and select **Properties**: 
 
-   You can create the IP address resource in Failover Cluster Manager. Right-click the availability group role, click **Add Resource**, **More Resources**, and click **IP Address**.
+   ![Cluster properties](./media/virtual-machines-windows-portal-sql-availability-group-dr/cluster-name-properties.png)
 
-   ![Create IP Address](./media/virtual-machines-windows-portal-sql-availability-group-dr/20-add-ip-resource.png)
+   On the **Properties** dialog box, select **Add** under **IP Address**, and then add the IP address of the cluster name from the remote network region. 
 
-   Configure this IP address as follows:
+   ![Add cluster IP](./media/virtual-machines-windows-portal-sql-availability-group-dr/add-cluster-ip-address.png)
 
-   - Use the network from the remote data center.
-   - Assign the IP address from the new Azure load balancer. 
 
-1. On the new SQL Server in SQL Server Configuration Manager, [enable Always On Availability Groups](https://msdn.microsoft.com/library/ff878259.aspx).
+1. Add the IP address as a dependency for the core cluster name. 
+   Right-click the **IP Address**  and select **Properties**. 
 
-1. [Open firewall ports on the new SQL Server](virtual-machines-windows-portal-sql-availability-group-prereq.md#endpoint-firewall).
+   ![IP Address properties](./media/virtual-machines-windows-portal-sql-availability-group-dr/cluster-ip-properties.png)
 
-   The port numbers you need to open depend on your environment. Open ports for the mirroring endpoint and Azure load balancer health probe.
+   On the **Dependencies** tab, create an OR dependency for both IP addresses: 
 
-1. [Add a replica to the availability group on the new SQL Server](https://msdn.microsoft.com/library/hh213239.aspx).
+1. Add an IP address resource to the availability group role in the cluster. 
 
-   For a replica in a remote Azure region, set it for asynchronous replication with manual failover.  
+   Right-click the availability group role in Failover Cluster Manager, select **Add Resource**, **More Resources**, and select **IP Address**.
+
+   ![Create IP Address](./media/virtual-machines-windows-portal-sql-availability-group-dr/20-add-ip-resource.png)
+
+   Configure this IP address as follows:
+
+   - Use the network from the remote data center.
+   - Assign the IP address from the new Azure load balancer. 
 
 1. Add the IP address resource as a dependency for the listener client access point (network name) cluster.
 
@@ -137,6 +144,17 @@ Run the PowerShell script with the cluster network name, IP address, and probe p
    Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ILBIP";"ProbePort"=$ProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
    ```
 
+1. On the new SQL Server in SQL Server Configuration Manager, [enable Always On Availability Groups](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server).
+
+1. [Open firewall ports on the new SQL Server](virtual-machines-windows-portal-sql-availability-group-prereq.md#endpoint-firewall).
+
+   The port numbers you need to open depend on your environment. Open ports for the mirroring endpoint and Azure load balancer health probe.
+
+
+1. [Add a replica to the availability group on the new SQL Server](/sql/database-engine/availability-groups/windows/use-the-add-replica-to-availability-group-wizard-sql-server-management-studio).
+
+   For a replica in a remote Azure region, set it for asynchronous replication with manual failover.  
+
 ## Set connection for multiple subnets
 
 The replica in the remote data center is part of the availability group but it is in a different subnet. If this replica becomes the primary replica, application connection time-outs may occur. This behavior is the same as an on-premises availability group in a multi-subnet deployment. To allow connections from client applications, either update the client connection or configure name resolution caching on the cluster network name resource.

articles/virtual-machines/windows/sql/media/virtual-machines-windows-portal-sql-availability-group-dr/cluster-ip-properties.png

@@ -79,6 +79,7 @@ Before you complete the steps in this article, you should already have:
    - An IP address for each FCI.
 - DNS configured on the Azure network, pointing to the domain controllers.
 - A [premium file share](../../../storage/files/storage-how-to-create-premium-fileshare.md) based on the storage quota of your database for your data files.
+- If you're on Windows Server 2012 R2 and older, you will need another file share to use as the file share witness, since cloud witnesses are supported for Windows 2016 and newer. It does not need to be premium. 
 
 With these prerequisites in place, you can start building your failover cluster. The first step is to create the virtual machines.
 
@@ -175,7 +176,8 @@ After you create and configure the virtual machines, you can configure the premi
 1. Repeat these steps on each SQL Server VM that will participate in the cluster.
 
   > [!IMPORTANT]
-  > Consider using a separate file share for backup files to save the IOPS and space capacity of this share for Data and Log files. You can use either a premium or standard file share for backup files.
+  > - Consider using a separate file share for backup files to save the IOPS and space capacity of this share for Data and Log files. You can use either a premium or standard file share for backup files.
+  > - If you're on Windows 2012 R2 and older, follow these same steps to mount your file share that you are going to use as the file share witness. 
 
 ## Step 3: Configure the failover cluster with the file share
 
@@ -184,7 +186,7 @@ The next step is to configure the failover cluster. In this step, you'll complet
 1. Add the Windows Server Failover Clustering feature.
 1. Validate the cluster.
 1. Create the failover cluster.
-1. Create the cloud witness.
+1. Create the cloud witness (for Windows Server 2016 and newer) or the file share witness (for Windows Server 2012 R2 and older).
 
 
 ### Add Windows Server Failover Clustering
@@ -258,17 +260,21 @@ New-Cluster -Name <FailoverCluster-Name> -Node ("<node1>","<node2>") –StaticAd
 ```
 
 
-### Create a cloud witness
+### Create a cloud witness (Win 2016 +)
 
-Cloud Witness is a new type of cluster quorum witness that's stored in an Azure storage blob. This removes the need for a separate VM that hosts a witness share.
+If you're on Windows Server 2016 and greater, you'll need to create a Cloud Witness. Cloud Witness is a new type of cluster quorum witness that's stored in an Azure storage blob. This removes the need for a separate VM that hosts a witness share, or using a separate file share.
 
 1. [Create a cloud witness for the failover cluster](https://technet.microsoft.com/windows-server-docs/failover-clustering/deploy-cloud-witness).
 
 1. Create a blob container.
 
 1. Save the access keys and the container URL.
 
-1. Configure the failover cluster quorum witness. See [Configure the quorum witness in the user interface](https://technet.microsoft.com/windows-server-docs/failover-clustering/deploy-cloud-witness#to-configure-cloud-witness-as-a-quorum-witness).
+### Configure quorum 
+
+For Windows Server 2016 and greater, configure the cluster to use the cloud witness you just created. Follow all of the steps [Configure the quorum witness in the user interface](https://technet.microsoft.com/windows-server-docs/failover-clustering/deploy-cloud-witness#to-configure-cloud-witness-as-a-quorum-witness).
+
+For Windows Server 2012 R2 and older, follow the same steps in [Configure the quorum witness in the user interface](https://technet.microsoft.com/windows-server-docs/failover-clustering/deploy-cloud-witness#to-configure-cloud-witness-as-a-quorum-witness) but on the **Select Quorum Witness** page, select the **Configure a file share witness** option, and then specify the file share you mounted previously for witness purposes. 
 
 
 ## Step 4: Test cluster failover