Merge pull request MicrosoftDocs#11882 from MikeRayMSFT/20170502_freshness

updating for freshness review.

Author: v-thepet

articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-alwayson-int-listener.md

@@ -17,10 +17,10 @@ ms.date: 05/01/2017
 ms.author: mikeray 
 
 ---
-# Configure an internal load balancer for an Always On availability group in Azure
-This topic explains how to create an internal load balancer for a SQL Server Always On availability group in Azure virtual machines running with Azure Resource Manager. An availability group requires a load balancer when the SQL Server instances are on Azure virtual machines. The load balancer stores the IP address for the availability group listener. If an availability group spans multiple regions, each region needs a load balancer.
+# Configure a load balancer for an Always On availability group in Azure
+This topic explains how to create a load balancer for a SQL Server Always On availability group in Azure virtual machines running with Azure Resource Manager. An availability group requires a load balancer when the SQL Server instances are on Azure virtual machines. The load balancer stores the IP address for the availability group listener. If an availability group spans multiple regions, each region needs a load balancer.
 
-To complete this task, you need to have a SQL Server availability group deployed on Azure virtual machines Resource Manager. Both SQL Server virtual machines must belong to the same availability set. You can use the [Microsoft template](virtual-machines-windows-portal-sql-alwayson-availability-groups.md) to automatically create the availability group in Azure Resource Manager. This template automatically creates the internal load balancer for you. 
+To complete this task, you need to have a SQL Server availability group deployed on Azure virtual machines Resource Manager. Both SQL Server virtual machines must belong to the same availability set. You can use the [Microsoft template](virtual-machines-windows-portal-sql-alwayson-availability-groups.md) to automatically create the availability group in Azure Resource Manager. This template automatically creates an internal load balancer for you. 
 
 If you prefer, you can [manually configure an availability group](virtual-machines-windows-portal-sql-alwayson-availability-groups-manual.md).
 
@@ -56,7 +56,7 @@ The first step is to create the load balancer. In the Azure portal, open the res
    | Setting | Value |
    | --- | --- |
    | **Name** |A text name representing the load balancer. For example, **sqlLB**. |
-   | **Type** |**Internal** |
+   | **Type** |**Internal** - Most implementations use an internal load balancer. This allows applications within the same virtual network to connect to the availability group.  </br> **External** - Allows applications to connect to the availability group through a public internet connection. |
    | **Virtual network** |Choose the virtual network that the SQL Servers are in. |
    | **Subnet** |Choose the subnet that the SQL Servers are in. |
    | **IP address assignment** |**Static** |

articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-dr.md

@@ -15,14 +15,14 @@ ms.custom: na
 ms.topic: article
 ms.tgt_pltfrm: vm-windows-sql-server
 ms.workload: iaas-sql-server
-ms.date: "01/09/2017"
+ms.date: "05/02/2017"
 ms.author: mikeray
 
 ---
 
-# Configure a SQL Server Always On Availability Group on Azure Virtual Machines in Different Regions
+# Configure an Always On availability group on Azure virtual machines in different regions
 
-This article explains how to configure a SQL Server Always On Availability Group replica on Azure Virtual Machines in a remote Azure location. Use this configuration to support disaster recovery.
+This article explains how to configure a SQL Server Always On availability group replica on Azure virtual machines in a remote Azure location. Use this configuration to support disaster recovery.
 
 This article applies to Azure Virtual Machines in Resource Manager mode.
 
@@ -77,7 +77,7 @@ To create a replica in a remote data center, do the following steps:
    This load balancer must:
 
    - Be in the same network and subnet as the new virtual machine.
-   - Have a static IP address for the Availability Group listener.
+   - Have a static IP address for the availability group listener.
    - Include a backend pool consisting of only the virtual machines in the same region as the load balancer.
    - Use a TCP port probe specific to the IP address.
    - Have a load balancing rule specific to the SQL Server in the same region.  

articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-ps-alwayson-int-listener.md

@@ -13,19 +13,19 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: vm-windows-sql-server
 ms.workload: iaas-sql-server
-ms.date: 12/28/2016
+ms.date: 05/02/2017
 ms.author: mikeray
 
 ---
-# Configure one or more Always On Availability Group Listeners - Resource Manager
+# Configure one or more Always On availability group listeners - Resource Manager
 This topic shows how to:
 
 * Create an internal load balancer for SQL Server availability groups using PowerShell cmdlets.
 * Add additional IP addresses to a load balancer for more than one availability group. 
 
 An availability group listener is a virtual network name that clients connect to for database access. On Azure virtual machines, a load balancer holds the IP address for the listener. The load balancer routes traffic to the instance of SQL Server that is listening on the probe port. Usually, an availability group uses an internal load balancer. An Azure internal load balancer can host one or many IP addresses. Each IP address uses a specific probe port. This document shows how to use PowerShell to create a load balancer, or add IP addresses to an existing load balancer for SQL Server availability groups. 
 
-The ability to assign multiple IP addresses to an internal load balancer is new to Azure and is only available in Resource Manager model. To complete this task, you need to have a SQL Server availability group deployed on Azure virtual machines in Resource Manager model. Both SQL Server virtual machines must belong to the same availability set. You can use the [Microsoft template](virtual-machines-windows-portal-sql-alwayson-availability-groups.md) to automatically create the availability group in Azure Resource Manager. This template automatically creates the availability group, including the internal load balancer for you. If you prefer, you can [manually configure an AlwaysOn availability group](virtual-machines-windows-portal-sql-alwayson-availability-groups-manual.md).
+The ability to assign multiple IP addresses to an internal load balancer is new to Azure and is only available in Resource Manager model. To complete this task, you need to have a SQL Server availability group deployed on Azure virtual machines in Resource Manager model. Both SQL Server virtual machines must belong to the same availability set. You can use the [Microsoft template](virtual-machines-windows-portal-sql-alwayson-availability-groups.md) to automatically create the availability group in Azure Resource Manager. This template automatically creates the availability group, including the internal load balancer for you. If you prefer, you can [manually configure an Always On availability group](virtual-machines-windows-portal-sql-alwayson-availability-groups-manual.md).
 
 This topic requires that your availability groups are already configured.  
 
@@ -151,99 +151,6 @@ $ILB | Add-AzureRmLoadBalancerRuleConfig -Name $LBConfigRuleName -FrontendIpConf
 
 [!INCLUDE [ag-listener-configure](../../../../includes/virtual-machines-ag-listener-configure.md)]
 
-
-<!------------------------------- The content below is duplicated. Pointing to the link. Thinking about an include. 
-
-## Configure the cluster to use the load balancer IP address
-The next step is to configure the listener on the cluster, and bring the listener online. To accomplish this, do the following: 
-
-1. Create the availability group listener on the failover cluster  
-2. Bring the listener online
-
-## Create the availability group listener on the failover cluster
-
-The availability group listener is an IP address and network name that the SQL Server availability group listens on. To create the availability group listener, do the following steps:
-
-1. [Get the name of the cluster network resource](#getnet).
-
-1. [Add the client access point](#addcap).
-
-1. [Configure the IP resource for the availability group](#congroup).
-
-1. [Make the availability group resource dependent on the listener resource name](#listname).
-
-1. [Set the cluster parameters in PowerShell](#setparam).
-
-The following sections provide detailed instructions for each of these steps. 
-
-### <a name="getnet">Get the name of the cluster network resource</a> 
-
-1. Use RDP to connect to the Azure virtual machine that hosts the primary replica. 
-
-1. Open Failover Cluster Manager.
-
-1. Select the **Networks** node, and note the cluster network name. Use this name in the `$ClusterNetworkName` variable in the PowerShell script.
-
-### <a name="addcap">Add the client access point</a>
-
-1. Expand the cluster name, and then click **Roles**.
-
-1. In the **Roles** pane, right-click the availability group name and then select **Add Resource** > **Client Access Point**.
-
-1. In the **Name** box, create a name for this new listener. 
-
-   The name for the new listener is the network name that applications will use to connect to databases in the SQL Server availability group.
-   
-   To finish creating the listener, click **Next** twice, and then click **Finish**. Do not bring the listener or resource online at this point.
-   
-### <a name="congroup">Configure the IP resource for the availability group</a>
-
-1. Click the **Resources** tab, then expand the Client Access Point you just created. Right-click the IP resource and click properties. Note the name of the IP address. You will use this name in the `$IPResourceName` variable in the PowerShell script.
-
-1. Under **IP Address** click **Static IP Address** and set the static IP address to the same address that you used when you set the load balancer IP address on the Azure portal. 
-
-1. Disable NetBIOS for this address and click **OK**. Repeat this step for each IP resource if your solution spans multiple Azure VNets. 
-
-### <a name="listname">Make the availability group resource dependent on the listener resource</a>
-
-1. In Failover Cluster Manager click **Roles** and click your Availability Group. 
-
-1. On the **Resources** tab, right-click the availability resource group and click **Properties**. 
-
-1. Click the **Dependencies** tab. Set a dependency on the listener resource name. If there are multiple resources listed, verify that the IP addresses have OR, not AND, dependencies. Click **OK**. 
-
-1. Right-click the listener name and click **Bring Online**. 
-
-### <a name="setparam">Set the cluster parameters in PowerShell</a>
-
-Set the cluster parameters. To do this, update the following PowerShell script. Set the variables with the values for your environment. Run the PowerShell script on one of the cluster nodes.  
-    
-   ```PowerShell
-   $ClusterNetworkName = "<MyClusterNetworkName>" # the cluster network name (Use Get-ClusterNetwork on Windows Server 2012 of higher to find the name)
-   $IPResourceName = "<IPResourceName>" # the IP Address resource name
-   $ILBIP = “<n.n.n.n>” # the IP Address of the Internal Load Balancer (ILB). This is the static IP address for the load balancer you configured in the Azure portal.
-   [int]$ProbePort = <nnnnn>
-
-   Import-Module FailoverClusters
-
-   Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ILBIP";"ProbePort"=$ProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
-   ```
-> [!NOTE]
-> If your SQL Servers are in separate regions, you need to run the PowerShell script twice. The first time use the `$ILBIP` and `$ProbePort` from the first region. The second time, use the `$ILBIP` and `$ProbePort` from the second region. The cluster network name, and the cluster IP resource name are the same. 
-
-## Set the listener port in SQL Server Management Studio
-
-1. Launch SQL Server Management Studio and connect to the primary replica.
-
-1. Navigate to **AlwaysOn High Availability** | **Availability Groups** | **Availability Group Listeners**. 
-
-1. You should now see the listener name that you created in Failover Cluster Manager. Right-click the listener name and click **Properties**.
-
-1. In the **Port** box, specify the port number for the availability group listener by using the $EndpointPort you used earlier (1433 was the default), then click **OK**.
-
-You now have a SQL Server availability group in Azure virtual machines running in Resource Manager mode. 
--------------------------------->
-
 ## Set the listener port in SQL Server Management Studio
 
 1. Launch SQL Server Management Studio and connect to the primary replica.

articles/virtual-machines/windows/sqlclassic/virtual-machines-windows-classic-ps-sql-int-listener.md

@@ -14,7 +14,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: vm-windows-sql-server
 ms.workload: iaas-sql-server
-ms.date: 03/01/2017
+ms.date: 05/02/2017
 ms.author: mikeray
 
 ---
@@ -26,14 +26,13 @@ ms.author: mikeray
 > 
 
 ## Overview
-This topic shows you how to configure a listener for an Always On Availability Group by using an **Internal Load Balancer (ILB)**.
 
 > [!IMPORTANT] 
 > Azure has two different deployment models for creating and working with resources: [Resource Manager and Classic](../../../azure-resource-manager/resource-manager-deployment-model.md). This article covers using the Classic deployment model. Microsoft recommends that most new deployments use the Resource Manager model.
 
-To configure an ILB listener for an Always On availability group in Resource Manager model, see [Configure an internal load balancer for an Always On availability group in Azure](../sql/virtual-machines-windows-portal-sql-alwayson-int-listener.md).
+To configure a listener for an Always On availability group in Resource Manager model, see [Configure a load balancer for an Always On availability group in Azure](../sql/virtual-machines-windows-portal-sql-alwayson-int-listener.md).
 
-Your Availability Group can contain replicas that are on-premises only, Azure only, or span both on-premises and Azure for hybrid configurations. Azure replicas can reside within the same region or across multiple regions using multiple virtual networks (VNets). The steps below assume you have already [configured an availability group](../classic/portal-sql-alwayson-availability-groups.md) but have not configured a listener.
+Your availability group can contain replicas that are on-premises only, Azure only, or span both on-premises and Azure for hybrid configurations. Azure replicas can reside within the same region or across multiple regions using multiple virtual networks (VNets). The steps below assume you have already [configured an availability group](../classic/portal-sql-alwayson-availability-groups.md) but have not configured a listener.
 
 ## Guidelines and limitations for internal listeners
 Note the following guidelines on the availability group listener in Azure using ILB: