Skip to content

Commit 2355d8a

Browse files
normestanormesta
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into cost-scenario-prototype
2 parents 5cb8d9d + e839be5 commit 2355d8a

File tree

2,797 files changed

+31450
-16374
lines changed

Some content is hidden

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

2,797 files changed

+31450
-16374
lines changed

‎.openpublishing.redirection.json

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,75 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/cdn/cdn-traffic-manager.md",
5+
"redirect_url": "/previous-versions/azure/cdn/cdn-traffic-manager",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/frontdoor/quickstart-create-front-door.md",
10+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/frontdoor/quickstart-create-front-door-terraform.md",
15+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door-terraform",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/frontdoor/quickstart-create-front-door-template.md",
20+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door-template",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/frontdoor/quickstart-create-front-door-powershell.md",
25+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door-powershell",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/frontdoor/quickstart-create-front-door-cli.md",
30+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door-cli",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/frontdoor/quickstart-create-front-door-bicep.md",
35+
"redirect_url": "/previous-versions/azure/frontdoor/quickstart-create-front-door-bicep",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/cloud-services/cloud-services-application-and-service-availability-faq.yml",
40+
"redirect_url": "/previous-versions/azure/cloud-services/cloud-services-application-and-service-availability-faq",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/cloud-services/cloud-services-configuration-and-management-faq.yml",
45+
"redirect_url": "/previous-versions/azure/cloud-services/cloud-services-configuration-and-management-faq",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/cloud-services/cloud-services-connectivity-and-networking-faq.yml",
50+
"redirect_url": "/previous-versions/azure/cloud-services/cloud-services-connectivity-and-networking-faq",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/cloud-services/cloud-services-deployment-faq.yml",
55+
"redirect_url": "/previous-versions/azure/cloud-services/cloud-services-deployment-faq",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/cloud-services/index.yml",
60+
"redirect_url": "/previous-versions/azure/cloud-services/index",
61+
"redirect_document_id": false
62+
},
363
{
464
"source_path": "articles/private-multi-access-edge-compute-mec/index.yml",
565
"redirect_url": "/previous-versions/azure/private-multi-access-edge-compute-mec/index",
666
"redirect_document_id": false
767
},
68+
{
69+
"source_path": "articles/site-recovery/shared-disks-common-questions.md",
70+
"redirect_url": "/azure/site-recovery/azure-to-azure-common-questions",
71+
"redirect_document_id": false
72+
},
873
{
974
"source_path": "articles/network-watcher/traffic-analytics-schema-update.md",
1075
"redirect_url": "/previous-versions/azure/network-watcher/traffic-analytics-schema-update",
@@ -499,6 +564,11 @@
499564
"redirect_url": "/azure/security/fundamentals/azure-CA-details",
500565
"redirect_document_id": false
501566
},
567+
{
568+
"source_path": "articles/security/fundamentals/recover-from-identity-compromise.md",
569+
"redirect_url": "/azure/security/fundamentals/ransomware-detect-respond#road-to-recovery",
570+
"redirect_document_id": false
571+
},
502572
{
503573
"source_path": "articles/event-grid/event-schema-storage-actions.md",
504574
"redirect_url": "/azure/storage-actions/overview",
@@ -6968,6 +7038,26 @@
69687038
"source_path": "articles/defender-for-iot/organizations/eiot-sensor.md",
69697039
"redirect_url": "/azure/defender-for-iot/organizations/concept-enterprise",
69707040
"redirect_document_id": false
7041+
},
7042+
{
7043+
"source_path": "articles/cyclecloud/release-notes/ccws/2024.09.18.md",
7044+
"redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-09-18",
7045+
"redirect_document_id": false
7046+
},
7047+
{
7048+
"source_path": "articles/cyclecloud/release-notes/ccws/2024.11.08.md",
7049+
"redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-11-08",
7050+
"redirect_document_id": false
7051+
},
7052+
{
7053+
"source_path": "articles/cyclecloud/release-notes/ccws/2024.12.18.md",
7054+
"redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-12-18",
7055+
"redirect_document_id": false
7056+
},
7057+
{
7058+
"source_path": "articles/cyclecloud/release-notes/ccws/2025.02.06.md",
7059+
"redirect_url": "/azure/cyclecloud/release-notes/ccws/2025-02-06",
7060+
"redirect_document_id": false
69717061
}
69727062
]
69737063
}

‎articles/active-directory-b2c/identity-provider-adfs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ zone_pivot_groups: b2c-policy-type
3131

3232
To enable sign-in for users with an AD FS account in Azure Active Directory B2C (Azure AD B2C), create an Application Group in your AD FS. For more information, see [Build a web application using OpenID Connect with AD FS 2016 and later](../active-directory/develop/msal-migration.md)
3333

34-
To create an Application Group, follow theses steps:
34+
To create an Application Group, follow these steps:
3535

3636
1. In **Server Manager**, select **Tools**, and then select **AD FS Management**.
3737
1. In AD FS Management, right-click on **Application Groups** and select **Add Application Group**.

‎articles/active-directory-b2c/password-complexity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Allows you to control the different character types used in the password.
8383

8484
- **2 of 4: Lowercase character, Uppercase character, Number (0-9), Symbol** ensures the password contains at least two character types. For example, a number and a lowercase character.
8585
- **3 of 4: Lowercase character, Uppercase character, Number (0-9), Symbol** ensures the password contains at least three character types. For example, a number, a lowercase character and an uppercase character.
86-
- **4 of 4: Lowercase character, Uppercase character, Number (0-9), Symbol** ensures the password contains all for character types.
86+
- **4 of 4: Lowercase character, Uppercase character, Number (0-9), Symbol** ensures the password contains all four character types.
8787

8888
> [!NOTE]
8989
> Requiring **4 of 4** can result in end-user frustration. Some studies have shown that this requirement doesn't improve password entropy. See [NIST Password Guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html#appA)

‎articles/active-directory-b2c/policy-keys-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ If an Azure AD B2C keyset has multiple keys, only one of the keys is active at a
7575
- When the current date and time is greater than a key's activation date, Azure AD B2C activates the key and stop using the prior active key.
7676
- When the current key's expiration time has elapsed and the key container contains a new key with valid *nbf (not before)* and *exp (expiration)* times, the new key becomes active automatically. New tokens are signed with the newly active key. It's possible to keep an expired key published for token validation until disabled by an admin, but this must be requested by [filing a support request](/azure/active-directory-b2c/find-help-open-support-ticket).
7777

78-
- When the current key's expiration time has elapsed and the key container *doesn't* contain a new key with valid *not before* and *expiration* times, Azure AD B2C won't be able to use the expired key. Azure AD B2C raises an error message within a dependant component of your custom policy. To avoid this issue, you can create a default key without activation and expiration dates as a safety net.
78+
- When the current key's expiration time has elapsed and the key container *doesn't* contain a new key with valid *not before* and *expiration* times, Azure AD B2C won't be able to use the expired key. Azure AD B2C raises an error message within a dependent component of your custom policy. To avoid this issue, you can create a default key without activation and expiration dates as a safety net.
7979
- The key's endpoint (JWKS URI) of the OpenId Connect well-known configuration endpoint reflects the keys configured in the Key Container, when the Key is referenced in the [JwtIssuer Technical Profile](./jwt-issuer-technical-profile.md). An application using an OIDC library will automatically fetch this metadata to ensure it uses the correct keys to validate tokens. For more information, learn how to use [Microsoft Authentication Library](../active-directory/develop/msal-b2c-overview.md), which always fetches the latest token signing keys automatically.
8080

8181
:::image type="content" source="media/policy-keys-overview/key-rollover.png" alt-text="A diagram describing the process for key rollover in Azure AD B2C." lightbox="media/policy-keys-overview/key-rollover.png":::

‎articles/active-directory-b2c/service-limits.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,8 @@ zone_pivot_groups: b2c-policy-type
1414

1515

1616
#Customer intent: As an Azure AD B2C user, I want to understand the service limits and restrictions, so that I can ensure that my application stays within the allowed usage constraints and request limits.
17-
17+
ms.custom:
18+
- build-2025
1819
---
1920

2021
# Azure Active Directory B2C service limits and restrictions

‎articles/api-center/authorize-api-access.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to configure access to APIs in the Azure API Center inven
44
author: dlepow
55
ms.service: azure-api-center
66
ms.topic: how-to
7-
ms.date: 04/30/2025
7+
ms.date: 06/02/2025
88
ms.author: danlep
99
ms.custom:
1010
# Customer intent: As an API program manager, I want to store API authorization information in my API center and enable authorized users to test APIs in the API Center portal.
@@ -57,12 +57,12 @@ To manage the API key securely, store it in Azure Key Vault, and access the key
5757

5858
| **Setting** | **Description** |
5959
|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
60-
| **Title** | A name for the authorization. |
61-
| **Description** | Optional description for the authorization. |
60+
| **Title** | Enter a name for the authorization. |
61+
| **Description** | Optionally, enter a description for the authorization. |
6262
| **Security scheme** | Select **API Key**. |
63-
|**API key location** | How the key is presented in API requests. Available values are **Header** (request header) and **Query** (query parameter). |
64-
| **API key parameter name** | Name of the HTTP header or query parameter that contains the API key. Example: `x-api-key` |
65-
| **API key Key Vault secret reference** | Secret identifier of the API key in Azure Key Vault. Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>/<version>` |
63+
|**API key location** | Select how the key is presented in API requests. Available values are **Header** (request header) and **Query** (query parameter). |
64+
| **API key parameter name** | Enter the name of the HTTP header or query parameter that contains the API key. Example: `x-api-key` |
65+
| **API key Key Vault secret reference** | Click **Select** and select the subscription, key vault, and secret that you stored. Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>` |
6666

6767
1. Select **Create**.
6868

@@ -114,24 +114,24 @@ To manage the secret securely, store it in Azure Key Vault, and access the key v
114114
1. In the left menu, under **Governance**, select **Authorization (preview)** > **+ Add configuration**.
115115
1. In the **Add configuration** page, set the values as follows:
116116

117-
:::image type="content" source="media/authorize-api-access/configure-oauth.png" alt-text="Screenshot of configuring OAuth 2.0 in the portal.":::
117+
:::image type="content" source="media/authorize-api-access/configure-oauth.png" lightbox="media/authorize-api-access/configure-oauth.png" alt-text="Screenshot of configuring OAuth 2.0 in the portal.":::
118118

119119

120120
> [!NOTE]
121121
> Configure settings based on the app registration you created previously in your identity provider. If you're using Microsoft Entra ID, find the **Client ID** on the **Overview** page of the app registration, and find the URL endpoints on the **Overview** > **Endpoints** page.
122122
123123
| **Setting** | **Description** |
124124
|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
125-
| **Title** | A name for the authorization. |
126-
| **Description** | Optional description for the authorization. |
125+
| **Title** | Enter a name for the authorization. |
126+
| **Description** | Optionally, enter a description for the authorization. |
127127
| **Security scheme** | Select **OAuth2**. |
128-
| **Client ID** | Client ID (GUID) of the app that you created in your identity provider. |
129-
| **Client secret** | Secret identifier of the client secret in Azure Key Vault.<br/><br/>Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>/<version>` |
130-
| **Authorization URL** | OAuth 2.0 authorization endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/authorize` |
131-
| **Token URL** | OAuth 2.0 token endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token` |
132-
| **Refresh URL** | OAuth 2.0 token refresh endpoint for the identity provider. For most providers, same as the **Token URL**<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token` |
133-
| **OAuth2 flow** | One or both of the OAuth 2.0 flows that you want to use. Available values are **Authorization code (PKCE)** and **Client credentials**. |
134-
| **Scopes** | One or more API scopes configured for your API, separated by spaces. If no scopes are configured, enter `.default`. |
128+
| **Client ID** | Enter the client ID (GUID) of the app that you created in your identity provider. |
129+
| **Client secret** | Click **Select** and select the subscription, key vault, and client secret that you stored.<br/><br/>Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>` |
130+
| **Authorization URL** | Enter the OAuth 2.0 authorization endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/authorize` |
131+
| **Token URL** | Enter the OAuth 2.0 token endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token` |
132+
| **Refresh URL** | Enter the OAuth 2.0 token refresh endpoint for the identity provider. For most providers, same as the **Token URL**<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token` |
133+
| **OAuth2 flow** | Select one or both of the OAuth 2.0 flows that you want to use. Available values are **Authorization code (PKCE)** and **Client credentials**. |
134+
| **Scopes** | Enter one or more API scopes configured for your API, separated by spaces. If no scopes are configured, enter `.default`. |
135135

136136
1. Select **Create** to save the configuration.
137137

‎articles/api-center/build-register-apis-vscode-extension.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: API developers can use the Azure API Center extension for Visual St
44
author: dlepow
55
ms.service: azure-api-center
66
ms.topic: how-to
7-
ms.date: 11/08/2024
7+
ms.date: 05/28/2025
88
ms.author: danlep
99
ms.collection: ce-skilling-ai-copilot
1010
ms.custom:
@@ -60,6 +60,8 @@ Use the power of [GitHub Copilot](https://marketplace.visualstudio.com/items?ite
6060
6161
:::image type="content" source="media/build-register-apis-vscode-extension/generate-api-documentation.gif" alt-text="Animation showing how to use GitHub Copilot to generate an OpenAPI spec from code." lightbox="media/build-register-apis-vscode-extension/generate-api-documentation.gif":::
6262

63+
You can also generate an OpenAPI specification from all of the files in your current project. Use the **Azure API Center: Generate OpenAPI Spec from Entire Project** command from the Command Palette.
64+
6365
After generating the OpenAPI specification file and checking for accuracy, you can register the API with your API center using the **Azure API Center: Register API** command.
6466

6567
> [!TIP]
@@ -70,6 +72,6 @@ After generating the OpenAPI specification file and checking for accuracy, you c
7072
* [Azure API Center - key concepts](key-concepts.md)
7173
* [Discover and consume APIs with the Azure API Center extension for Visual Studio Code](discover-apis-vscode-extension.md)
7274
* [Govern APIs with the Azure API Center extension for Visual Studio Code](govern-apis-vscode-extension.md)
73-
* [Enable and view API Center portal in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
75+
* [Enable API Center portal view in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
7476
* [Overview of GitHub Copilot for Azure](/azure/developer/github-copilot-azure/introduction)
7577

0 commit comments

Comments
 (0)