format links

Author: cherylmc

articles/virtual-wan/point-to-site-entra-gateway.md

@@ -1,5 +1,5 @@
 ---
-title: 'Configure P2S User VPN for Microsoft Entra ID authentication: Microsoft-registered client'
+title: Configure P2S User VPN for Microsoft Entra ID authentication - Microsoft-registered client
 titleSuffix: Azure Virtual WAN
 description: Learn how to configure Virtual WAN P2S User VPN server settings for Microsoft Entra ID authentication using Microsoft-registered Azure VPN Client.
 services: virtual-wan
@@ -73,7 +73,7 @@ A User VPN configuration defines the parameters for connecting remote clients. I
     :::image type="content" source="./media/virtual-wan-point-to-site-azure-ad/values.png" alt-text="Screenshot of the Microsoft Entra ID page." lightbox="./media/virtual-wan-point-to-site-azure-ad/values.png"::: Configure the following values:
 
    * **Azure Active Directory** - Select **Yes**.
-   * **Audience** - Enter the corresponding value for the Microsoft-registered Azure VPN Client App ID, Azure Public: `c632b3df-fb67-4d84-bdcf-b95ad541b5c8`. [Custom audience](../vpn-gateway/point-to-site-entra-register-custom-app.md) is also supported for this field.
+   * **Audience** - Enter the corresponding value for the Microsoft-registered Azure VPN Client App ID, Azure Public: `c632b3df-fb67-4d84-bdcf-b95ad541b5c8`. [Custom audience](point-to-site-entra-register-custom-app.md) is also supported for this field.
    * **Issuer** - Enter `https://sts.windows.net/<your Directory ID>/`.
    * **AAD Tenant** - Enter the TenantID for the Microsoft Entra tenant. Make sure there isn't an `/` at the end of the Microsoft Entra tenant URL.
 

articles/vpn-gateway/point-to-site-about.md

@@ -1,5 +1,5 @@
 ---
-title: 'About Azure Point-to-Site VPN connections'
+title: About Azure Point-to-Site VPN connections
 titleSuffix: Azure VPN Gateway
 description: Learn about Point-to-Site VPN.
 author: cherylmc
@@ -43,7 +43,7 @@ When you configure your P2S gateway for certificate authentication, you upload t
 
 To authenticate, each client that connects must have an installed client certificate that's generated from the trusted root certificate. This is in addition to VPN client software. The validation of the client certificate is performed by the VPN gateway and happens during establishment of the P2S VPN connection.
 
-#### <a name='certificate-workflow'></a>Certificate authentication workflow
+#### <a name="certificate-workflow"></a>Certificate authentication workflow
 
 At a high level, you need to perform the following steps to configure Certificate authentication:
 
@@ -53,13 +53,13 @@ At a high level, you need to perform the following steps to configure Certificat
 1. Configure the VPN client on the client computer using the settings found in the VPN profile configuration package.
 1. Connect.
 
-### <a name='entra-id'></a>Microsoft Entra ID authentication
+### <a name="entra-id"></a>Microsoft Entra ID authentication
 
 You can configure your P2S gateway to allow VPN users to authenticate using Microsoft Entra ID credentials. With Microsoft Entra ID authentication, you can use Microsoft Entra Conditional Access and multifactor authentication (MFA) features for VPN. Microsoft Entra ID authentication is supported only for the OpenVPN protocol. To authenticate and connect, clients must use the Azure VPN Client.
 
 [!INCLUDE [entra app id descriptions](../../includes/vpn-gateway-entra-app-id-descriptions.md)]
 
-#### <a name='entra-workflow'></a>Microsoft Entra ID authentication workflow
+#### <a name="entra-workflow"></a>Microsoft Entra ID authentication workflow
 
 At a high level, you need to perform the following steps to configure Microsoft Entra ID authentication:
 
@@ -69,7 +69,7 @@ At a high level, you need to perform the following steps to configure Microsoft
 1. Download, install, and configure the Azure VPN Client on the client computer.
 1. Connect.
 
-### <a name='active-directory'></a>RADIUS - Active Directory (AD) Domain Server authentication
+### <a name="active-directory"></a>RADIUS - Active Directory (AD) Domain Server authentication
 
 AD Domain authentication allows users to connect to Azure using their organization domain credentials. It requires a RADIUS server that integrates with the AD server. Organizations can also use their existing RADIUS deployment.
 

articles/vpn-gateway/point-to-site-entra-vpn-client-linux.md

@@ -1,5 +1,5 @@
 ---
-title: 'Configure Azure VPN Client - Microsoft Entra ID authentication - Linux'
+title: Configure Azure VPN Client - Microsoft Entra ID authentication - Linux
 description: Learn how to configure the Linux Azure VPN Client for Microsoft Entra ID authentication for gateways configured to use the Microsoft-registered Azure VPN Client App ID.
 titleSuffix: Azure VPN Gateway
 author: cherylmc

includes/vpn-gateway-entra-app-id-descriptions.md

@@ -1,7 +1,7 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 08/06/2024
+ms.date: 01/16/2025
 ms.service: azure-vpn-gateway
 ms.custom: linux-related-content
 ms.topic: include
@@ -14,17 +14,17 @@ When possible, we recommend that you configure new P2S gateways using the Micros
 
 If you have an existing P2S gateway that you want to update to use a new Audience value, see [Change Audience for a P2S VPN gateway](../articles/vpn-gateway/point-to-site-entra-gateway-update.md). If you want to create or modify a custom Audience value, see [Create a custom audience app ID for P2S VPN](../articles/vpn-gateway/point-to-site-entra-register-custom-app.md). If you want to configure or restrict access to P2S based on users and groups, see [Scenario: Configure P2S VPN access based on users and groups](../articles/vpn-gateway/point-to-site-entra-users-access.md).
 
-**Considerations and limitations**
+**Considerations**
 
 * A P2S VPN gateway can only support one Audience value. It can't support multiple Audience values simultaneously.
 
 * At this time, the newer Microsoft-registered App ID doesn't support as many Audience values as the older, manually registered app. If you need an Audience value for anything other than Azure Public or Custom, use the older manually registered method and values.
 
-* The Azure VPN Client for Linux isn't backward compatible with P2S gateways configured to use the older Audience values that align with the manually registered app. The Azure VPN Client for Linux does support Custom Audience values.
+* The Azure VPN Client for Linux isn't backward compatible with P2S gateways configured to use the older Audience values that align with the manually registered app. However, the Azure VPN Client for Linux does support Custom Audience values.
 
 * [!INCLUDE [Supported versions](vpn-gateway-azure-vpn-client-linux-supported-releases.md)]
 
-* The Azure VPN Client for macOS and Windows is backward compatible with P2S gateways configured to use the older Audience values that align with the manually registered app. You can also use Custom Audience values with these clients.
+* The Azure VPN Clients for macOS and Windows are backward compatible with P2S gateways configured to use the older Audience values that align with the manually registered app. These clients also support Custom Audience values.
 
 **Azure VPN Client Audience values**