Merge pull request #108321 from cherylmc/p2svwan1

PRMerger18 · web-flow · commit 12bf1c79e453 · 2020-03-19T09:48:39.000-07:00
change gateway wording
diff --git a/articles/virtual-wan/openvpn-azure-ad-tenant-multi-app.md b/articles/virtual-wan/openvpn-azure-ad-tenant-multi-app.md
@@ -6,18 +6,18 @@ author: anzaman
 
 ms.service: virtual-wan
 ms.topic: conceptual
-ms.date: 02/19/2020
+ms.date: 03/19/2020
 ms.author: alzam
 
 ---
 # Create an Azure Active Directory tenant for P2S OpenVPN protocol connections
 
-When connecting to your VNet, you can use certificate-based authentication or RADIUS authentication. However, when you use the Open VPN protocol, you can also use Azure Active Directory authentication. If you want different set of users to be able to connect to different VPN gateways, you can register multiple apps in AD and link them to different VPN gateways.
+When connecting to your VNet, you can use certificate-based authentication or RADIUS authentication. However, when you use the Open VPN protocol, you can also use Azure Active Directory authentication. If you want different set of users to be able to connect to different gateways, you can register multiple apps in AD and link them to different gateways.
 
 This article helps you set up an Azure AD tenant for P2S OpenVPN authentication, and create and register multiple apps in Azure AD to allow different access for different users and groups.
 
 > [!NOTE]
-> Azure AD authentication is supported only for OpenVPN® protocol connections.
+> Azure AD authentication is supported only for OpenVPN&reg; protocol connections.
 >
 
 [!INCLUDE [create](../../includes/openvpn-azure-ad-tenant-multi-app.md)]
@@ -41,7 +41,7 @@ A P2S configuration defines the parameters for connecting remote clients.
    ```
 
    > [!NOTE]
-   > Do not use the Azure VPN client's application ID in the commands above: It will grant all users access to the VPN gateway. Use the ID of the application(s) you registered.
+   > Do not use the Azure VPN client's application ID in the commands above: It will grant all users access to the gateway. Use the ID of the application(s) you registered.
 
 ## <a name="hub"></a>7. Edit hub assignment
 
@@ -77,7 +77,7 @@ Use the VPN profile to configure your clients.
 
 5. Extract the downloaded zip file.
 
-6. Browse to the unzipped “AzureVPN” folder.
+6. Browse to the unzipped "AzureVPN" folder.
 
 7. Make a note of the location of the "azurevpnconfig.xml" file. The azurevpnconfig.xml contains the setting for the VPN connection and can be imported directly into the Azure VPN Client application. You can also distribute this file to all the users that need to connect via e-mail or other means. The user will need valid Azure AD credentials to connect successfully.
 
@@ -86,7 +86,7 @@ Use the VPN profile to configure your clients.
 To connect, you need to download the Azure VPN Client and import the VPN client profile that was downloaded in the previous steps on every computer that wants to connect to the VNet.
 
 > [!NOTE]
-> Azure AD authentication is supported only for OpenVPN® protocol connections.
+> Azure AD authentication is supported only for OpenVPN&reg; protocol connections.
 >
 
 #### To download the Azure VPN client
@@ -147,16 +147,10 @@ Use this [link](https://go.microsoft.com/fwlink/?linkid=2117554) to download the
 
 1. Navigate to the virtual WAN.
 
-2. On the Overview page, each point on the map represents a hub. Hover over any point to view the hub health summary.
+2. On the Overview page, each point on the map represents a hub.
 
 3. In the Hubs and connections section, you can view hub status, site, region, VPN connection status, and bytes in and out.
 
-## <a name="viewhealth"></a>11. View your resource health
-
-1. Navigate to your WAN.
-
-2. On your WAN page, in the **SUPPORT + Troubleshooting** section, click **Health** and view your resource.
-
 ## <a name="cleanup"></a>Clean up resources
 
 When you no longer need these resources, you can use [Remove-AzureRmResourceGroup](/powershell/module/azurerm.resources/remove-azurermresourcegroup) to remove the resource group and all of the resources it contains. Replace "myResourceGroup" with the name of your resource group and run the following PowerShell command:
diff --git a/articles/virtual-wan/virtual-wan-point-to-site-azure-ad.md b/articles/virtual-wan/virtual-wan-point-to-site-azure-ad.md
@@ -27,7 +27,6 @@ In this article, you learn how to:
 > * Connect a VNet to a hub
 > * Download and apply the VPN client configuration
 > * View your virtual WAN
-> * View resource health
 
 ![Virtual WAN diagram](./media/virtual-wan-about/virtualwanp2s.png)
 
@@ -182,14 +181,9 @@ Use this [link](https://www.microsoft.com/p/azure-vpn-client-preview/9np355qt2sq
 ## <a name="viewwan"></a>View your virtual WAN
 
 1. Navigate to the virtual WAN.
-2. On the Overview page, each point on the map represents a hub. Hover over any point to view the hub health summary.
+2. On the Overview page, each point on the map represents a hub.
 3. In the Hubs and connections section, you can view hub status, site, region, VPN connection status, and bytes in and out.
 
-## <a name="viewhealth"></a>View your resource health
-
-1. Navigate to your WAN.
-2. On your WAN page, in the **SUPPORT + Troubleshooting** section, click **Health** and view your resource.
-
 
 ## <a name="cleanup"></a>Clean up resources
 
diff --git a/articles/virtual-wan/virtual-wan-point-to-site-portal.md b/articles/virtual-wan/virtual-wan-point-to-site-portal.md
@@ -25,7 +25,6 @@ In this tutorial, you learn how to:
 > * Connect a VNet to a hub
 > * Download and apply the VPN client configuration
 > * View your virtual WAN
-> * View resource health
 
 ![Virtual WAN diagram](./media/virtual-wan-about/virtualwanp2s.png)
 
@@ -145,14 +144,9 @@ Use the downloaded profile to configure the remote access clients. The procedure
 ## <a name="viewwan"></a>View your virtual WAN
 
 1. Navigate to the virtual WAN.
-2. On the Overview page, each point on the map represents a hub. Hover over any point to view the hub health summary.
+2. On the Overview page, each point on the map represents a hub.
 3. In the Hubs and connections section, you can view hub status, site, region, VPN connection status, and bytes in and out.
 
-## <a name="viewhealth"></a>View your resource health
-
-1. Navigate to your WAN.
-2. On your WAN page, in the **SUPPORT + Troubleshooting** section, click **Health** and view your resource.
-
 
 ## <a name="cleanup"></a>Clean up resources
 
diff --git a/articles/virtual-wan/vpn-over-expressroute.md b/articles/virtual-wan/vpn-over-expressroute.md
@@ -6,7 +6,7 @@ author: cherylmc
 
 ms.service: virtual-wan
 ms.topic: article
-ms.date: 02/18/2020
+ms.date: 03/19/2020
 ms.author: cherylmc
 
 ---
@@ -218,14 +218,9 @@ If you need instructions to configure your device, you can use the instructions
 ## <a name="viewwan"></a>5. View your virtual WAN
 
 1. Go to the virtual WAN.
-1. On the **Overview** page, each point on the map represents a hub. Hover over any point to view the hub's health summary.
+1. On the **Overview** page, each point on the map represents a hub.
 1. In the **Hubs and connections** section, you can view hub, site, region, and VPN connection status. You can also view bytes in and out.
 
-## <a name="viewhealth"></a>6. View your resource health
-
-1. Go to your WAN.
-1. In the **SUPPORT + Troubleshooting** section, select **Health** and view your resource.
-
 ## <a name="connectmon"></a>7. Monitor a connection
 
 Create a connection to monitor communication between an Azure virtual machine (VM) and a remote site. For information about how to set up a connection monitor, see [Monitor network communication](~/articles/network-watcher/connection-monitor.md). The source field is the VM IP in Azure, and the destination IP is the site IP.
diff --git a/includes/vpn-gateway-vwan-always-on-intro.md b/includes/vpn-gateway-vwan-always-on-intro.md
@@ -14,7 +14,7 @@
 
 A new feature of the Windows 10 VPN client, Always On, is the ability to maintain a VPN connection. With Always On, the active VPN profile can connect automatically and remain connected based on triggers, such as user sign-in, network state change, or device screen active.
 
-You can use Azure virtual network gateways with Windows 10 Always On to establish persistent user tunnels and device tunnels to Azure. This article helps you configure an Always On VPN user tunnel.
+You can use gateways with Windows 10 Always On to establish persistent user tunnels and device tunnels to Azure. This article helps you configure an Always On VPN user tunnel.
 
 Always On VPN connections include either of two types of tunnels:
 
