Merge pull request #281757 from cherylmc/vpntoc

VPNGW - titles

Author: Jill Grant

articles/vpn-gateway/TOC.yml

@@ -27,6 +27,8 @@
     href: vpn-gateway-vpn-faq.md
   - name: About VPN Gateway design
     href: design.md
+  - name: Design highly available gateway connections
+    href: vpn-gateway-highlyavailable.md
   - name: About VPN Gateway settings
     href: vpn-gateway-about-vpn-gateway-settings.md
   - name: About gateway SKUs
@@ -39,8 +41,6 @@
     href: vpn-gateway-about-compliance-crypto.md
   - name: About BGP and VPN Gateway
     href: vpn-gateway-bgp-overview.md
-  - name: About highly available connections
-    href: vpn-gateway-highlyavailable.md
   - name: About point-to-site VPN
     href: point-to-site-about.md
   - name: About point-to-site VPN routing
@@ -203,7 +203,7 @@
           href: point-to-site-entra-vpn-client-mac.md
       - name: Generate VPN client profile configuration files
         href: about-vpn-profile-download.md
-      - name: Change Audience values - gateway and clients
+      - name: Migrate manually registered client to Microsoft-registered client
         href: point-to-site-entra-gateway-update.md
     - name: RADIUS authentication
       items:

articles/vpn-gateway/point-to-site-entra-gateway-update.md

@@ -1,25 +1,25 @@
 ---
-title: 'Update Audience for P2S VPN gateway connections - Microsoft Entra ID authentication'
+title: 'Migrate manually registered Azure VPN client to Microsoft-registered for P2S Microsoft Entra ID authentication'
 titleSuffix: Azure VPN Gateway
 description: Learn how to update Audience values for P2S VPN gateway connections that use Microsoft Entra ID authentication.
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: how-to
-ms.date: 06/18/2024
+ms.date: 07/24/2024
 ms.author: cherylmc
 
 # Customer intent: As an VPN Gateway administrator, I want to update point-to-site Audience values for Microsoft Entra ID authentication.
 ---
 
-# Change Audience value for P2S VPN gateway and VPN clients
+# Migrate a manually registered Azure VPN Client to the Microsoft-registered client
 
-This article helps you change (update) the Audience value for point-to-site (P2S) VPN Gateway connections that use Microsoft Entra ID authentication. When you update an Audience value, you must make the change on both the P2S VPN gateway, and on any previously configured VPN clients. For more information about Audience values, see [About point-to-site VPN - Microsoft Entra ID authentication](point-to-site-about.md#entra-id).
+This article helps you migrate from a manually registered Azure VPN Client to the Microsoft-registered Azure VPN Client for point-to-site (P2S) Microsoft Entra ID authentication. The Microsoft-registered Azure VPN client uses a different Audience value. When you update an Audience value, you must make the change on both the P2S VPN gateway, and on any previously configured VPN clients.
 
-The following table shows the available supported Audience values. P2S VPN gateways also support custom Audience.
+For more information about Audience values, see [About point-to-site VPN - Microsoft Entra ID authentication](point-to-site-about.md#entra-id). The examples in this article use the new Audience value for Azure Public.
 
-[!INCLUDE [Audience values](../../includes/vpn-gateway-entra-audience-values.md)]
+The following table shows the available supported Audience values.
 
-In most cases, you'll be changing an older *Azure Public* audience value to the new Azure Public audience value to take advantage of the Microsoft-registered Azure VPN Client new features and supported operating systems. The examples in this article show the new Audience value for Azure Public. However, the process is the same if you want to change to a different supported Audience value, such as a custom value.
+[!INCLUDE [Audience values](../../includes/vpn-gateway-entra-audience-values.md)]
 
 ## Workflow
 
@@ -38,7 +38,7 @@ When you update audience values on an existing gateway, you incur fewer than 5 m
 
    :::image type="content" source="./media/update-entra-audience/audience.png" alt-text="Screenshot showing settings for Tunnel type, Authentication type, and Microsoft Entra settings." lightbox="././media/update-entra-audience/audience.png":::
 
-1. Change the **Audience** value. For this example, we changed the Audience value to the Azure Public value for the Microsoft-registered Azure VPN Client; **c632b3df-fb67-4d84-bdcf-b95ad541b5c8**. You can also use a different Audience value, such as a custom value, for this setting.
+1. Change the **Audience** value. For this example, we changed the Audience value to the Azure Public value for the Microsoft-registered Azure VPN Client; **c632b3df-fb67-4d84-bdcf-b95ad541b5c8**.
 1. Leave the other settings the same, unless you have changed tenants and need to change the tenant IDs. If you update the Issuer field, take care to include the trailing slash at the end. For more information about each of the fields, see [Microsoft Entra ID](point-to-site-entra-gateway.md#configure-vpn) values.
 1. Once you finish configuring settings, click **Save** at the top of the page.
 1. The new settings save to the P2S gateway and the gateway updates. This takes about 5 minutes to complete.
@@ -51,9 +51,11 @@ However, when you update only the Audience or tenant values, you have a couple o
 
 * If the Azure VPN Client is already configured to connect to this P2S gateway, you can [manually update](#manual) the VPN client.
 
-* If you've updated multiple values on the P2S gateway, or you want easily update the VPN clients by importing the new values, you can generate and download a new P2S VPN client profile configuration package and import it to each client.
+* If you've updated multiple values on the P2S gateway, or you want easily update the VPN clients by importing the new values, you can generate and download a new P2S VPN [client profile configuration package](#generate) and import it to each client.
+
+### <a name="manual"></a>Update an Azure VPN Client
 
-### <a name="manual"></a>Manually update an Azure VPN Client
+These steps help you update the Azure VPN Client manually, without using the profile configuration package.
 
 1. Launch the Azure VPN Client app.
 1. Select the VPN connection profile that you want to update.
@@ -62,7 +64,7 @@ However, when you update only the Audience or tenant values, you have a couple o
 1. If you also updated the Tenant ID values, change them on the client. These values must match the P2S gateway values.
 1. Click **Save** to save the settings.
 
-### <a name="generate"></a>Generate a profile configuration package
+### <a name="generate"></a>Update using a profile configuration package
 
 If you want to use the VPN client profile configuration files to configure your Azure VPN Client, you can generate a profile configuration package that contains the new P2S gateway settings.
 

articles/vpn-gateway/vpn-gateway-highlyavailable.md

@@ -1,17 +1,17 @@
 ---
-title: 'About Highly Available gateway configurations'
+title: 'Design highly available gateway connectivity'
 titleSuffix: Azure VPN Gateway
-description: Learn about highly available configuration options using Azure VPN Gateways.
+description: Learn about highly available configuration options for VPN Gateway.
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: article
-ms.date: 07/11/2024
+ms.date: 07/24/2024
 ms.author: cherylmc
 
 ---
-# Highly Available cross-premises and VNet-to-VNet connectivity
+# Design highly available gateway connectivity for cross-premises and VNet-to-VNet connections
 
-This article provides an overview of Highly Available configuration options for your cross-premises and VNet-to-VNet connectivity using Azure VPN gateways.
+This article helps you understand how to design highly available gateway connectivity for cross-premises and VNet-to-VNet connections.
 
 ## <a name = "activestandby"></a>About VPN gateway redundancy
 
@@ -31,7 +31,7 @@ To provide better availability for your cross premises connections, there are a
 
 You can use multiple VPN devices from your on-premises network to connect to your Azure VPN gateway, as shown in the following diagram:
 
-:::image type="content" source="./media/vpn-gateway-highlyavailable/multiple-onprem-vpns.png" alt-text="Diagram shows multiple on-premises sites with private I P subnets and on-premises V P N connected to an active Azure V P N gateway to connect to subnets hosted in Azure, with a standby gateway available.":::
+:::image type="content" source="./media/vpn-gateway-highlyavailable/multiple-onprem-vpns.png" alt-text="Diagram shows multiple on-premises sites with private IP subnets and on-premises VPN connected to an active Azure VPN gateway to connect to subnets hosted in Azure, with a standby gateway available.":::
 
 This configuration provides multiple active tunnels from the same Azure VPN gateway to your on-premises devices in the same location. There are some requirements and constraints: