Skip to content

Commit 76ded43

Browse files
authored
Merge pull request #271645 from cherylmc/fix-ad
screenshot
2 parents d2bd565 + 5adbb38 commit 76ded43

File tree

2 files changed

+13
-12
lines changed

2 files changed

+13
-12
lines changed
-4.29 KB
Loading

articles/vpn-gateway/openvpn-azure-ad-tenant.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,18 @@
11
---
2-
title: 'Configure a P2S VPN gateway and Microsoft Entra tenant: Microsoft Entra authentication: OpenVPN'
2+
title: 'Configure P2S VPN gateway for Microsoft Entra ID authentication'
33
titleSuffix: Azure VPN Gateway
44
description: Learn how to set up a Microsoft Entra tenant and P2S gateway for P2S Microsoft Entra authentication - OpenVPN protocol.
55
author: cherylmc
66
ms.service: vpn-gateway
77
ms.topic: how-to
8-
ms.date: 03/22/2024
8+
ms.date: 04/09/2024
99
ms.author: cherylmc
1010

1111
---
12-
# Configure a P2S VPN gateway and Microsoft Entra tenant for Microsoft Entra authentication
1312

14-
This article helps you configure your AD tenant and P2S (point-to-site) VPN Gateway settings for Microsoft Entra authentication. For more information about point-to-site protocols and authentication, see [About VPN Gateway point-to-site VPN](point-to-site-about.md). To authenticate using the Microsoft Entra authentication type, you must include the OpenVPN tunnel type in your point-to-site configuration.
13+
# Configure a P2S VPN gateway for Microsoft Entra ID authentication
14+
15+
This article helps you configure your Microsoft Entra tenant and point-to-site (P2S) VPN Gateway settings for Microsoft Entra ID authentication. For more information about point-to-site protocols and authentication, see [About VPN Gateway point-to-site VPN](point-to-site-about.md). To authenticate using Microsoft Entra ID authentication, you must include the OpenVPN tunnel type in your point-to-site configuration.
1516

1617
[!INCLUDE [OpenVPN note](../../includes/vpn-gateway-openvpn-auth-include.md)]
1718

@@ -22,7 +23,7 @@ The steps in this article require a Microsoft Entra tenant. If you don't have a
2223
* Organizational name
2324
* Initial domain name
2425

25-
If you already have an existing P2S gateway, the steps in this article help you configure the gateway for Microsoft Entra authentication. You can also create a new VPN gateway that specifies Microsoft Entra authentication. The link to create a new gateway is included in this article.
26+
If you already have an existing P2S gateway, the steps in this article help you configure the gateway for Microsoft Entra ID authentication. You can also create a new VPN gateway. The link to create a new gateway is included in this article.
2627

2728
<a name='create-azure-ad-tenant-users'></a>
2829

@@ -40,7 +41,7 @@ If you already have an existing P2S gateway, the steps in this article help you
4041

4142
[!INCLUDE [Steps to authorize the Azure VPN app](../../includes/vpn-gateway-vwan-azure-ad-tenant.md)]
4243

43-
## <a name="enable-authentication"></a>Configure the VPN gateway - Entra authentication
44+
## <a name="enable-authentication"></a>Configure the VPN gateway
4445

4546
> [!IMPORTANT]
4647
> [!INCLUDE [Entra ID note for portal pages](../../includes/vpn-gateway-entra-portal-note.md)]
@@ -59,14 +60,14 @@ If you already have an existing P2S gateway, the steps in this article help you
5960
* **Tunnel type:** OpenVPN (SSL)
6061
* **Authentication type**: Microsoft Entra ID
6162

62-
For **Microsoft Entra ID** values, use the following guidelines for **Tenant**, **Audience**, and **Issuer** values. Replace {AzureAD TenantID} with your tenant ID, taking care to remove **{}** from the examples when you replace this value.
63+
For **Microsoft Entra ID** values, use the following guidelines for **Tenant**, **Audience**, and **Issuer** values. Replace {TenantID} with your tenant ID, taking care to remove **{}** from the examples when you replace this value.
6364

6465
* **Tenant:** TenantID for the Microsoft Entra tenant. Enter the tenant ID that corresponds to your configuration. Make sure the Tenant URL doesn't have a `\` (backslash) at the end. Forward slash is permissible.
6566

66-
* Azure Public AD: `https://login.microsoftonline.com/{AzureAD TenantID}`
67-
* Azure Government AD: `https://login.microsoftonline.us/{AzureAD TenantID}`
68-
* Azure Germany AD: `https://login-us.microsoftonline.de/{AzureAD TenantID}`
69-
* China 21Vianet AD: `https://login.chinacloudapi.cn/{AzureAD TenantID}`
67+
* Azure Public AD: `https://login.microsoftonline.com/{TenantID}`
68+
* Azure Government AD: `https://login.microsoftonline.us/{TenantID}`
69+
* Azure Germany AD: `https://login-us.microsoftonline.de/{TenantID}`
70+
* China 21Vianet AD: `https://login.chinacloudapi.cn/{TenantID}`
7071

7172
* **Audience**: The Application ID of the "Azure VPN" Microsoft Entra Enterprise App.
7273

@@ -77,7 +78,7 @@ If you already have an existing P2S gateway, the steps in this article help you
7778

7879
* **Issuer**: URL of the Secure Token Service. Include a trailing slash at the end of the **Issuer** value. Otherwise, the connection might fail. Example:
7980

80-
* `https://sts.windows.net/{AzureAD TenantID}/`
81+
* `https://sts.windows.net/{TenantID}/`
8182

8283
1. Once you finish configuring settings, click **Save** at the top of the page.
8384

0 commit comments

Comments
 (0)