Skip to content

Commit 1a62354

Browse files
Merge pull request #284252 from cherylmc/entra-add
add older values
2 parents 3fe51f2 + 428382e commit 1a62354

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

articles/vpn-gateway/point-to-site-entra-register-custom-app.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to create or modify a custom audience App ID or upgrade a
55
author: cherylmc
66
ms.service: azure-vpn-gateway
77
ms.topic: concept-article
8-
ms.date: 08/05/2024
8+
ms.date: 08/09/2024
99
ms.author: cherylmc
1010
---
1111

@@ -19,7 +19,23 @@ This article provides high-level steps. The screenshots to register an applicati
1919

2020
## Prerequisites
2121

22-
This article assumes that you already have a Microsoft Entra tenant and the permissions to create an Enterprise Application, typically the Cloud Application administrator role or higher. For more information, see [Create a new tenant in Microsoft Entra ID](/entra/fundamentals/create-new-tenant) and [Assign user roles with Microsoft Entra ID](/entra/fundamentals/users-assign-role-azure-portal).
22+
* This article assumes that you already have a Microsoft Entra tenant and the permissions to create an Enterprise Application, typically the Cloud Application administrator role or higher. For more information, see [Create a new tenant in Microsoft Entra ID](/entra/fundamentals/create-new-tenant) and [Assign user roles with Microsoft Entra ID](/entra/fundamentals/users-assign-role-azure-portal).
23+
24+
* This article assumes that you're using the **Microsoft-registered App ID Azure Public** audience value `c632b3df-fb67-4d84-bdcf-b95ad541b5c8` to configure your custom app. This value has global consent, which means you don't need to manually register it to provide consent for your organization. We recommend that you use this value.
25+
26+
* At this time, there's only one supported audience value for the Microsoft-registered app. See the [supported audience value table](point-to-site-about.md#entra-id) for additional supported values.
27+
28+
* If the Microsoft-registered audience value isn't compatible with your configuration, you can still use the older manually registered ID values.
29+
30+
* If you need to use a manually registered app ID value instead, you must give consent to allow the app to sign in and read user profiles before proceeding with this configuration.
31+
32+
1. To grant admin consent for your organization, modify the following command to contain the desired `client_id` value. In the example, the client_id value is for Azure Public. See the [table](point-to-site-about.md#entra-id) for additional supported values.
33+
34+
```https://login.microsoftonline.com/common/oauth2/authorize?client_id=41b23e61-6c1e-4545-b367-cd054e0ed4b4&response_type=code&redirect_uri=https://portal.azure.com&nonce=1234&prompt=admin_consent```
35+
36+
1. Copy and paste the URL that pertains to your deployment location in the address bar of your browser.
37+
1. Select the account that has the **Global administrator** role if prompted.
38+
1. On the **Permissions** requested page, select **Accept**.
2339

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

0 commit comments

Comments
 (0)