Skip to content

Commit ad19b91

Browse files
authored
Update validate-azure-ad-token-policy.md
1 parent 807f895 commit ad19b91

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/api-management/validate-azure-ad-token-policy.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,10 +66,6 @@ The `validate-azure-ad-token` policy enforces the existence and validity of a JS
6666
| failed-validation-error-message | Error message to return in the HTTP response body if the JWT doesn't pass validation. This message must have any special characters properly escaped. Policy expressions are allowed. | No | Default error message depends on validation issue, for example "JWT not present." |
6767
| output-token-variable-name | String. Name of context variable that will receive token value as an object of type [`Jwt`](api-management-policy-expressions.md) upon successful token validation. Policy expressions aren't allowed. | No | N/A |
6868

69-
70-
71-
72-
7369
## Elements
7470

7571
| Element | Description | Required |
@@ -96,6 +92,7 @@ The `validate-azure-ad-token` policy enforces the existence and validity of a JS
9692
### Usage notes
9793

9894
* You can use access restriction policies in different scopes for different purposes. For example, you can secure the whole API with Azure AD authentication by applying the `validate-azure-ad-token` policy on the API level, or you can apply it on the API operation level and use `claims` for more granular control.
95+
* When using a custom header (`header-name`), the header value cannot be prefixed with `Bearer ` and should be removed.
9996

10097
## Examples
10198

0 commit comments

Comments
 (0)