Skip to content

Commit 78d9d6e

Browse files
TaojunshenTaojunshen
authored
Merge pull request #288350 from MicrosoftDocs/main
10/14/2024 AM Publish
2 parents ff4bb14 + e27fa5d commit 78d9d6e

File tree

172 files changed

+1591
-1010
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

172 files changed

+1591
-1010
lines changed

‎articles/active-directory-b2c/secure-rest-api.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 01/11/2024
9+
ms.date: 10/14/2024
1010
ms.author: kengaderdus
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type
@@ -276,7 +276,10 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
276276

277277
### Acquiring an access token
278278

279-
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](../active-directory/develop/v2-oauth-ropc.md), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
279+
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](/entra/identity-platform/v2-oauth-ropc), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
280+
281+
> [!WARNING]
282+
> Microsoft recommends you do *not* use the ROPC flow. This flow requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows aren't viable.
280283
281284
<a name='acquiring-an-azure-ad-access-token-'></a>
282285

@@ -577,12 +580,12 @@ The following XML snippet is an example of a RESTful technical profile configure
577580
```
578581
::: zone-end
579582

580-
## Next steps
583+
## Related content
581584

582585
::: zone pivot="b2c-user-flow"
583586
- Get started with our [samples](api-connector-samples.md#api-connector-rest-api-samples).
584587
::: zone-end
585588

586589
::: zone pivot="b2c-custom-policy"
587590
- Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
588-
::: zone-end
591+
::: zone-end

‎articles/api-management/validate-jwt-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ The `validate-jwt` policy enforces existence and validity of a supported JSON we
8585
| Element | Description | Required |
8686
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
8787
| openid-config |Add one or more of these elements to specify a compliant OpenID configuration endpoint URL from which signing keys and issuer can be obtained.<br/><br/>Configuration including the JSON Web Key Set (JWKS) is pulled from the endpoint every 1 hour and cached. If the token being validated references a validation key (using `kid` claim) that is missing in cached configuration, or if retrieval fails, API Management pulls from the endpoint at most once per 5 min. These intervals are subject to change without notice. <br/><br/>The response should be according to specs as defined at URL: `https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata`. <br/><br/>For Microsoft Entra ID use the OpenID Connect [metadata endpoint](../active-directory/develop/v2-protocols-oidc.md#find-your-apps-openid-configuration-document-uri) configured in your app registration such as:<br/>- v2 `https://login.microsoftonline.com/{tenant-name}/v2.0/.well-known/openid-configuration`<br/>- v2 Multi-Tenant ` https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration`<br/>- v1 `https://login.microsoftonline.com/{tenant-name}/.well-known/openid-configuration` <br/>- Customer tenant (preview) `https://{tenant-name}.ciamlogin.com/{tenant-id}/v2.0/.well-known/openid-configuration` <br/><br/> Substituting your directory tenant name or ID, for example `contoso.onmicrosoft.com`, for `{tenant-name}`. | No |
88-
| issuer-signing-keys | A list of Base64-encoded security keys, in [`key`](#key-attributes) subelements, used to validate signed tokens. If multiple security keys are present, then each key is tried until either all are exhausted (in which case validation fails) or one succeeds (useful for token rollover). <br/><br/>Optionally specify a key by using the `id` attribute to match a `kid` claim. To validate a token signed with an asymmetric key, optionally specify the public key using a `certificate-id` attribute with value set to the identifier of a certificate uploaded to API Management, or the RSA modulus `n` and exponent `e` pair of the signing key in Base64url-encoded format. | No |
88+
| issuer-signing-keys | A list of Base64-encoded security keys, in [`key`](#key-attributes) subelements, used to validate signed tokens. If multiple security keys are present, then each key is tried until either all are exhausted (in which case validation fails) or one succeeds (useful for token rollover). <br/><br/>Optionally, specify a key by using the `id` attribute to match the token's `kid` claim. To validate a token signed with an asymmetric key, optionally specify the public key using a `certificate-id` attribute with value set to the identifier of a certificate uploaded to API Management, or the RSA modulus `n` and exponent `e` pair of the signing key in Base64url-encoded format. | No |
8989
| decryption-keys | A list of Base64-encoded keys, in [`key`](#key-attributes) subelements, used to decrypt the tokens. If multiple security keys are present, then each key is tried until either all keys are exhausted (in which case validation fails) or a key succeeds.<br/><br/> To decrypt a token encrypted with an asymmetric key, optionally specify the public key using a `certificate-id` attribute with value set to the identifier of a certificate uploaded to API Management. | No |
9090
| audiences | A list of acceptable audience claims, in `audience` subelements, that can be present on the token. If multiple audience values are present, then each value is tried until either all are exhausted (in which case validation fails) or until one succeeds. At least one audience must be specified. | No |
9191
| issuers | A list of acceptable principals, in `issuer` subelements, that issued the token. If multiple issuer values are present, then each value is tried until either all are exhausted (in which case validation fails) or until one succeeds. | No |
@@ -94,7 +94,7 @@ The `validate-jwt` policy enforces existence and validity of a supported JSON we
9494
### key attributes
9595
| Attribute | Description | Required | Default |
9696
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
97-
| id | (Issuer signing key only) String. Identifier used to match `kid` claim presented in JWT. | No | N/A |
97+
| id | (Issuer signing key only) String. Identifier used to match `kid` claim presented in JWT. If no keys match the claim, API Management will attempt each specified key. [Learn more about the `kid` claim in the RFC](https://www.rfc-editor.org/rfc/rfc7515#section-4.1.4). | No | N/A |
9898
| certificate-id | Identifier of a certificate entity [uploaded](/rest/api/apimanagement/apimanagementrest/azure-api-management-rest-api-certificate-entity#Add) to API Management, used to specify the public key to verify a token signed with an asymmetric key. | No | N/A |
9999
| n | (Issuer signing key only) Modulus of the public key used to verify the issuer of a token signed with an asymmetric key. Must be specified with the value of the exponent `e`. Policy expressions aren't allowed. | No | N/A|
100100
| e | (Issuer signing key only) Exponent of the public key used to verify the issuer of a token signed with an asymmetric key. Must be specified with the value of the modulus `n`. Policy expressions aren't allowed. | No | N/A|

‎articles/azure-maps/routing-coverage.md

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -399,11 +399,11 @@ The Azure Maps Routing service (preview) contains different levels of geographic
399399
| Bulgaria | Good | ✓ | ✓ | ✓ |
400400
| Burkina Faso | Fair | | ✓ | |
401401
| Burundi | Good | | ✓ | |
402+
| Cabo Verde | Good | | ✓ | |
402403
| Cambodia | Good | | ✓ | |
403404
| Cameroon | Fair | | ✓ | |
404405
| Canada | Good | ✓ | ✓ | ✓ |
405-
| Cape Verde | Good | | ✓ | |
406-
| Caribbean Netherlands | | | ✓ | |
406+
| Cape Verde | | | ✓ | |
407407
| Cayman Islands | Good | | ✓ | |
408408
| Central African Republic | Major Roads Only | | ✓ | |
409409
| Chad | Major Roads Only | | ✓ | |
@@ -547,12 +547,12 @@ The Azure Maps Routing service (preview) contains different levels of geographic
547547
| Russia | Good | ✓ | ✓ | ✓ |
548548
| Rwanda | Good | | ✓ | |
549549
| Saba | Good | | | |
550-
| Saint Barthélemy | Good | | | |
550+
| Saint Barthélemy | Good | | ✓ | |
551551
| Saint Kitts & Nevis | Good | | | |
552-
| Saint Lucia | Good | | | |
553-
| Saint Martin | Good | | | |
554-
| Saint Pierre & Miquelon | Good | | | |
555-
| Saint Vincent & the Grenadines | Good | | | |
552+
| Saint Lucia | Good | | ✓ | |
553+
| Saint Martin | Good | | ✓ | |
554+
| Saint Pierre & Miquelon | Good | | ✓ | |
555+
| Saint Vincent & the Grenadines | Good | | ✓ | |
556556
| Samoa | Major Roads Only | | ✓ | |
557557
| San Marino | Good | ✓ | ✓ | ✓ |
558558
| São Tomé & Príncipe | Major Roads Only | | ✓ | |
@@ -573,13 +573,7 @@ The Azure Maps Routing service (preview) contains different levels of geographic
573573
| South Sudan | Major Roads Only | | ✓ | |
574574
| Spain | Good | ✓ | ✓ | ✓ |
575575
| Sri Lanka | Major Roads Only | | ✓ | |
576-
| St. Barthélemy | | | ✓ | |
577576
| St Helena, Ascension, Tristan da Cunha | Major Roads Only | | ✓ | |
578-
| St. Kitts & Nevis | | | ✓ | |
579-
| St. Lucia | | | ✓ | |
580-
| St. Martin | | | ✓ | |
581-
| St. Pierre & Miquelon | | | ✓ | |
582-
| St. Vincent & Grenadines | | | ✓ | |
583577
| Sudan | Major Roads Only | | ✓ | |
584578
| Suriname | Good | | ✓ | |
585579
| Svalbard | Good | | | |
@@ -596,7 +590,7 @@ The Azure Maps Routing service (preview) contains different levels of geographic
596590
| Tonga | Major Roads Only | | ✓ | |
597591
| Trinidad & Tobago | Good | | ✓ | |
598592
| Tunisia | Good | | ✓ | |
599-
| Turkey | Good | ✓ | ✓ | ✓ |
593+
| Türkiye | Good | ✓ | ✓ | ✓ |
600594
| Turkmenistan | Major Roads Only | | ✓ | |
601595
| Turks & Caicos Islands | Good | | ✓ | |
602596
| Tuvalu | Major Roads Only | | ✓ | |

‎articles/azure-resource-manager/bicep/diagnostics/bcp007.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,36 @@
11
---
22
title: BCP007
3-
description: Error - This declaration type isn't recognized. Specify a metadata, parameter, variable, resource, or output declaration.
3+
description: This declaration type isn't recognized. Specify a metadata, parameter, variable, resource, or output declaration.
44
ms.topic: reference
55
ms.custom: devx-track-bicep
66
ms.date: 08/23/2024
77
---
88

9-
# Bicep error code - BCP007
9+
# Bicep diagnostic code - BCP007
1010

11-
This error occurs when the declaration type isn't recognized. For a list of declaration types, see [Understand the structure and syntax of Bicep files](../file.md).
11+
This diagnostic occurs when the declaration type isn't recognized. For a list of declaration types, see [Understand the structure and syntax of Bicep files](../file.md).
1212

13-
## Error description
13+
## Description
1414

15-
`This declaration type isn't recognized. Specify a metadata, parameter, variable, resource, or output declaration.`
15+
This declaration type isn't recognized. Specify a metadata, parameter, variable, resource, or output declaration.
16+
17+
## Level
18+
19+
Error
1620

1721
## Solution
1822

1923
Use the correct declaration type. For more information, see [Bicep file](../file.md).
2024

2125
## Examples
2226

23-
The following example raises the error because `parameter` isn't a correct declaration type:
27+
The following example raises the diagnostic because `parameter` isn't a correct declaration type:
2428

2529
```bicep
2630
parameter name string
2731
```
2832

29-
You can fix the error by using the correct declaration type, `param`.
33+
You can fix the diagnostic by using the correct declaration type, `param`.
3034

3135
```bicep
3236
param name string
@@ -36,4 +40,4 @@ For more information, see [Parameters](../parameters.md).
3640

3741
## Next steps
3842

39-
For more information about Bicep error and warning codes, see [Bicep core diagnostics](../bicep-core-diagnostics.md).
43+
For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

0 commit comments

Comments
 (0)