Skip to content

Commit 1ca12e2

Browse files
committed
Update TOC.yml
1 parent 132b37e commit 1ca12e2

File tree

4 files changed

+15
-7
lines changed

4 files changed

+15
-7
lines changed

articles/virtual-wan/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -212,6 +212,8 @@
212212
href: point-to-site-entra-gateway.md
213213
- name: Configure P2S - manually registered VPN client
214214
href: virtual-wan-point-to-site-azure-ad.md
215+
- name: Create or modify custom audience app ID
216+
href: point-to-site-entra-register-custom-app.md
215217
- name: Configure a tenant
216218
href: openvpn-azure-ad-tenant.md
217219
- name: Configure multifactor authentication (MFA)

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.author: cherylmc
1717
This article helps you configure point-to-site User VPN connection to Virtual WAN that uses Microsoft Entra ID authentication and the new Microsoft-registered Azure VPN Client App ID.
1818

1919
> [!NOTE]
20-
> The steps in this article apply to Microsoft Entra ID authentication using the new Microsoft-registered Azure VPN Client App ID and associated Audience values. This article doesn't apply to the older, manually registered Azure VPN Client app for your tenant. For the manually registered Azure VPN Client steps, see [Configure P2S using manually registered VPN client](virtual-wan-point-to-site-azure-ad.md).
20+
> The steps in this article apply to Microsoft Entra ID authentication using the new Microsoft-registered Azure VPN Client App ID and associated Audience values. This article doesn't apply to the older, manually registered Azure VPN Client app for your tenant. For the manually registered Azure VPN Client steps, see [Configure P2S User VPN using manually registered VPN client](virtual-wan-point-to-site-azure-ad.md).
2121
2222
[!INCLUDE [About Microsoft-registered app](../../includes/virtual-wan-entra-app-id-descriptions.md)]
2323

@@ -48,6 +48,8 @@ Verify that you've met the following criteria before beginning your configuratio
4848

4949
* You need a Microsoft Entra ID tenant for this configuration. If you don't have one, you can create one by following the instructions in [Create a new tenant](/entra/fundamentals/create-new-tenant).
5050

51+
* If you want to use a custom audience value, see [Create or modify custom audience app ID](point-to-site-entra-register-custom-app.md).
52+
5153
## <a name="wan"></a>Create a virtual WAN
5254

5355
From a browser, navigate to the [Azure portal](https://portal.azure.com) and sign in with your Azure account.

articles/virtual-wan/point-to-site-entra-register-custom-app.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.author: cherylmc
1111

1212
# Create or modify a custom audience app ID for User VPN Microsoft Entra ID authentication
1313

14-
The steps in this article help you create a Microsoft Entra ID custom App ID (custom audience) for the new Microsoft-registered Azure VPN Client for point-to-site (P2S) connections. You can also update your existing tenant to [change the new Microsoft-registered Azure VPN Client app](#change) from the previous Azure VPN Client app.
14+
The steps in this article help you create a Microsoft Entra ID custom App ID (custom audience) for the new Microsoft-registered Azure VPN Client for User VPN point-to-site (P2S) connections. You can also update your existing tenant to [change the new Microsoft-registered Azure VPN Client app](#change) from the previous Azure VPN Client app.
1515

16-
When you configure a custom audience app ID, you can use any of the supported values associated with the Azure VPN Client app. We recommend that you associate the Microsoft-registered App ID Azure Public audience value `c632b3df-fb67-4d84-bdcf-b95ad541b5c8` to your custom app when possible. For the full list of supported values, see [P2S VPN - Microsoft Entra ID](point-to-site-about.md#entra-id).
16+
When you configure a custom audience app ID, you can use any of the supported values associated with the Azure VPN Client app. We recommend that you associate the Microsoft-registered App ID Azure Public audience value `c632b3df-fb67-4d84-bdcf-b95ad541b5c8` to your custom app when possible. For the full list of supported values, see the [Azure VPN Client Audience values table](point-to-site-entra-gateway.md).
1717

1818
This article provides high-level steps. The screenshots to register an application might be slightly different, depending on the way you access the user interface, but the settings are the same. For more information, see [Quickstart: Register an application](/entra/identity-platform/quickstart-register-app).
1919

@@ -39,7 +39,7 @@ This article provides high-level steps. The screenshots to register an applicati
3939

4040
[!INCLUDE [Configure custom audience](../../includes/vpn-gateway-custom-audience.md)]
4141

42-
## Configure the VPN gateway
42+
## Configure the gateway
4343

4444
After you've completed the steps in the previous sections, continue to [Configure Virtual WAN User VPN for Microsoft Entra ID authentication - Microsoft-registered app](point-to-site-entra-gateway.md).
4545

@@ -52,5 +52,4 @@ After you've completed the steps in the previous sections, continue to [Configur
5252

5353
## Next steps
5454

55-
[Configure Virtual WAN P2S User VPN for Microsoft Entra ID authentication - Microsoft-registered app](point-to-site-entra-gateway.md).
56-
55+
[Configure Virtual WAN P2S User VPN for Microsoft Entra ID authentication - Microsoft-registered app](point-to-site-entra-gateway.md).

articles/virtual-wan/virtual-wan-point-to-site-azure-ad.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: cherylmc
77

88
ms.service: azure-virtual-wan
99
ms.topic: how-to
10-
ms.date: 09/24/2024
10+
ms.date: 01/15/2025
1111
ms.author: cherylmc
1212

1313
#Audience ID values are not sensitive data.
@@ -17,6 +17,11 @@ ms.author: cherylmc
1717

1818
This article shows you how to use Virtual WAN to connect to your resources in Azure. In this article, you create a point-to-site User VPN connection to Virtual WAN that uses Microsoft Entra authentication. Microsoft Entra authentication is only available for gateways that use the OpenVPN protocol.
1919

20+
> [!NOTE]
21+
> Instead of using the steps in this article, we recommend that you use the new [Microsoft-registered Azure VPN Client App ID](point-to-site-entra-gateway.md) article for your User VPN configuration when possible.
22+
23+
[!INCLUDE [About Microsoft-registered app](../../includes/virtual-wan-entra-app-id-descriptions.md)]
24+
2025
[!INCLUDE [OpenVPN note](../../includes/vpn-gateway-openvpn-auth-include.md)]
2126

2227
In this article, you learn how to:

0 commit comments

Comments
 (0)