Merge pull request #293680 from cherylmc/P2S-vpn

Update VPN Client instructions

Author: JamesJBarnett

articles/virtual-wan/media/vpn-client-certificate-windows/configure-certificate.png

@@ -5,7 +5,7 @@ description: Learn how to configure VPN clients on Windows computers for User VP
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: how-to
-ms.date: 08/24/2023
+ms.date: 01/28/2025
 ms.author: cherylmc
 ---
 
@@ -74,29 +74,11 @@ For more information about User VPN client profile files, see [Working with User
 
 ### Download the Azure VPN Client
 
-[!INCLUDE [Download the Azure VPN Client](../../includes/vpn-gateway-download-vpn-client.md)]
+[!INCLUDE [Download the Azure VPN client](../../includes/vpn-gateway-download-vpn-client.md)]
 
 ### Configure the Azure VPN Client
 
-1. Open the Azure VPN Client.
-
-1. Click **+** on the bottom left of the page, then select **Import**.
-
-1. In the window, navigate to the **azurevpnconfig.xml** file, select it, then click **Open**.
-
-1. From the **Certificate Information** dropdown, select the name of the child certificate (the client certificate). For example, **P2SChildCert**.
-
-   :::image type="content" source="./media/vpn-client-certificate-windows/configure-certificate.png" alt-text="Screenshot showing Azure VPN Client profile configuration page." lightbox="./media/vpn-client-certificate-windows/configure-certificate.png":::
-
-   If you don't see a client certificate in the **Certificate Information** dropdown, you'll need to cancel the profile configuration import and fix the issue before proceeding. It's possible that one of the following things is true:
-
-   * The client certificate isn't installed locally on the client computer.
-   * There are multiple certificates with exactly the same name installed on your local computer (common in test environments).
-   * The child certificate is corrupt.
-
-1. After the import validates (imports with no errors), click **Save**.
-
-1. In the left pane, locate the **VPN connection**, then click **Connect**.
+[!INCLUDE [Configure the Azure VPN client](../../includes/vpn-gateway-vwan-configure-azure-vpn-client-certificate.md)]
 
 ## Next steps
 

articles/virtual-wan/vpn-client-certificate-windows.md

@@ -5,7 +5,7 @@ description: Learn how to configure VPN clients for P2S configurations that use
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 05/20/2024
+ms.date: 01/28/2025
 ms.author: cherylmc
 ---
 
@@ -63,27 +63,7 @@ If you don't see either file, or you don't have an **AzureVPN** folder, verify t
 
 ## Configure the Azure VPN Client profile
 
-1. Open the Azure VPN Client.
-
-1. Select **+** on the bottom left of the page, then select **Import**.
-
-1. In the window, navigate to the **azurevpnconfig.xml** or **azurevpnconfig_cert.xml** file. Select the file, then select **Open**.
-
-1. On the client profile page, notice that many of the settings are already specified. The preconfigured settings are contained in the VPN client profile package that you imported. Even though most of the settings are already specified, you need to configure settings specific to the client computer.
-
-   From the **Certificate Information** dropdown, select the name of the child certificate (the client certificate). For example, **P2SChildCert**. You can also (optionally) select a [Secondary Profile](#secondary-profile). For this exercise, select **None**.
-
-   :::image type="content" source="./media/point-to-site-vpn-client-cert-windows/configure-certificate.png" alt-text="Screenshot showing Azure VPN client profile configuration page." lightbox="./media/point-to-site-vpn-client-cert-windows/configure-certificate.png":::
-
-   If you don't see a client certificate in the **Certificate Information** dropdown, you'll need to cancel and fix the issue before proceeding. It's possible that one of the following things is causing the problem:
-
-   * The client certificate isn't installed locally on the client computer.
-   * There are multiple certificates with exactly the same name installed on your local computer (common in test environments).
-   * The child certificate is corrupt.
-
-1. After the import validates (imports with no errors), select **Save**.
-
-1. In the left pane, locate the **VPN connection**, then select **Connect**.
+[!INCLUDE [Configure the Azure VPN client](../../includes/vpn-gateway-vwan-configure-azure-vpn-client-certificate.md)]
 
 ### Optional settings for the Azure VPN Client
 

articles/vpn-gateway/point-to-site-vpn-client-certificate-windows-azure-vpn-client.md

@@ -0,0 +1,33 @@
+---
+ ms.topic: include
+ author: cherylmc
+ ms.service: azure-vpn-gateway
+ ms.date: 01/28/2025
+ ms.author: cherylmc
+
+
+ # this file is used for both virtual wan and vpn gateway. When modifying, make sure that your changes work for both environments.
+---
+
+
+1. Open the Azure VPN Client.
+
+1. Select **+** on the bottom left of the page, then select **Import**.
+
+1. In the window, navigate to the **azurevpnconfig.xml** or **azurevpnconfig_cert.xml** file, depending on your configuration. Select the file, then select **Open**.
+
+1. On the client profile page, notice that many of the settings are already specified. The preconfigured settings are contained in the VPN client profile package that you imported. Even though most of the settings are already specified, you need to configure settings specific to the client computer.
+
+   From the **Certificate Information** dropdown, select the name of the child certificate (the client certificate). For example, **P2SChildCert**. For this exercise, for secondary profile, select **None**.
+
+   :::image type="content" source="./media/vpn-gateway-vwan-configure-azure-vpn-client-certificate/configure-certificate.png" alt-text="Screenshot showing Azure VPN client profile configuration page." lightbox="./media/vpn-gateway-vwan-configure-azure-vpn-client-certificate/configure-certificate.png":::
+
+   If you don't see a client certificate in the **Certificate Information** dropdown, you'll need to cancel the profile configuration import and fix the issue before proceeding. It's possible that one of the following things is true:
+
+   * The client certificate isn't installed locally on the client computer.
+   * There are multiple certificates with exactly the same name installed on your local computer (common in test environments).
+   * The child certificate is corrupt.
+
+1. After the import validates (imports with no errors), select **Save**.
+
+1. In the left pane, locate the **VPN connection**, then select **Connect**.