Skip to content

Commit 9aeaa19

Browse files
committed
edits
1 parent 76859cb commit 9aeaa19

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/container-apps/authentication-entra.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Enable Authentication and Authorization in Azure Container Apps with Microsoft Entra ID
2+
title: Enable Authentication and Authorization in Container Apps with Microsoft Entra ID
33
description: Learn how to use the built-in Microsoft Entra authentication provider in Azure Container Apps.
44
services: container-apps
55
author: craigshoemaker
@@ -88,7 +88,7 @@ To register the app, perform the following steps:
8888

8989
The **Application ID URI** uniquely identifies your application when it's used as a resource. It allows requested tokens to grant access. The value is also used as a prefix for scopes you create.
9090

91-
For a single-tenant app, you can use the default value, which is in the form `api://<APPLICATION_CLIENT_ID>`. You can also specify a more readable URI, like `https://contoso.com/api`, based on one of the verified domains for your tenant. For a multitenant app, you must provide a custom URI. To learn more about accepted formats for app ID URIs, see the [app registrations best practices reference](../active-directory/develop/security-best-practices-for-app-registration.md#application-id-uri).
91+
For a single-tenant app, you can use the default value, which is in the form `api://<APPLICATION_CLIENT_ID>`. You can also specify a more readable URI, like `https://contoso.com/api`, based on one of the verified domains for your tenant. For a multitenant app, you must provide a custom URI. To learn more about accepted formats for app ID URIs, see [Security best practices for application properties in Microsoft Entra ID](../active-directory/develop/security-best-practices-for-app-registration.md#application-id-uri).
9292

9393
The value is automatically saved.
9494

@@ -122,7 +122,7 @@ To register the app, perform the following steps:
122122
|**Issuer URL**| Use `<AUTHENTICATION-ENDPOINT>/<TENANT-ID>/v2.0`. Replace *\<AUTHENTICATION-ENDPOINT>* with the [authentication endpoint for your cloud environment](../active-directory/develop/authentication-national-cloud.md#azure-ad-authentication-endpoints) (for example, "https://login.microsoftonline.com" for global Azure). Replace *\<TENANT-ID>* with the **Directory (tenant) ID** in which the app registration was created. This value is used to redirect users to the correct Microsoft Entra tenant, and to download the metadata to determine the appropriate token signing keys and token issuer claim value, for example. For applications that use Azure Active Directory v1, omit `/v2.0` in the URL.|
123123
|**Allowed token audiences**| The configured **Application (client) ID** is *always* implicitly considered to be an allowed audience. If this value refers to a cloud or server app and you want to accept authentication tokens from a client container app (the authentication token can be retrieved in the `X-MS-TOKEN-AAD-ID-TOKEN` header), add the **Application (client) ID** of the client app here. |
124124

125-
The client secret is stored as [secrets](manage-secrets.md) in your container app.
125+
The client secret is stored as a [secret](manage-secrets.md) in your container app.
126126

127127
1. If this is the first identity provider configured for the application, you see a **Container Apps authentication settings** section. Otherwise, you move on to the next step.
128128

0 commit comments

Comments
 (0)