Skip to content

Commit 002b295

Browse files
author
gitName
committed
alternative policy
1 parent d786090 commit 002b295

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/api-management-howto-oauth2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -290,7 +290,7 @@ After saving the OAuth 2.0 server configuration, configure an API or APIs to use
290290

291291
In the configuration so far, API Management doesn't validate the access token. It only passes the token in the authorization header to the backend API.
292292

293-
To pre-authorize requests, configure a [validate-jwt](validate-jwt-policy.md) policy to validate the access token of each incoming request. If a request doesn't have a valid token, API Management blocks it. In the case of the Microsoft Entra ID provider, you can also use the `validate-azure-ad-token` policy.
293+
To pre-authorize requests, configure a [validate-jwt](validate-jwt-policy.md) policy to validate the access token of each incoming request. If a request doesn't have a valid token, API Management blocks it. When you use the Microsoft Entra ID provider, you can also use the [validate-azure-ad-token](validate-azure-ad-token-policy.md) policy.
294294

295295
[!INCLUDE [api-management-configure-validate-jwt](../../includes/api-management-configure-validate-jwt.md)]
296296

0 commit comments

Comments
 (0)