Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into su

Author: gitName

.openpublishing.redirection.json

@@ -1,5 +1,25 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/cdn/cdn-advanced-http-reports.md",
+      "redirect_url": "/previous-versions/azure/cdn/cdn-advanced-http-reports",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cdn/cdn-preload-endpoint.md",
+      "redirect_url": "/previous-versions/azure/cdn/cdn-preload-endpoint",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cdn/cdn-real-time-stats.md",
+      "redirect_url": "/previous-versions/azure/cdn/cdn-real-time-stats",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cdn/cdn-token-auth.md",
+      "redirect_url": "/previous-versions/azure/cdn/cdn-token-auth",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cdn/edgio-retirement-faq.md",
       "redirect_url": "/previous-versions/azure/cdn/edgio-retirement-faq",
@@ -6471,27 +6491,27 @@
     },
     {
       "source_path": "articles/cloud-services/cloud-services-guestos-family-2-3-4-retirement.md",
-      "redirect_url": "/previous-versions/azure/cloud-services/cloud-services-guestos-family-2-3-4-retirement",
+      "redirect_url": "/azure/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement",
       "redirect_document_id": false
     },
     {
       "source_path": "articles/cloud-services/cloud-services-guestos-family1-retirement.md",
-      "redirect_url": "/previous-versions/azure/cloud-services/cloud-services-guestos-family1-retirement",
+      "redirect_url": "/azure/cloud-services-extended-support/cloud-services-guestos-family-1-retirement",
       "redirect_document_id": false
     },
     {
       "source_path": "articles/cloud-services/cloud-services-guestos-msrc-releases.md",
-      "redirect_url": "/previous-versions/azure/cloud-services/cloud-services-guestos-msrc-releases",
+      "redirect_url": "/azure/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases",
       "redirect_document_id": false
     },
     {
       "source_path": "articles/cloud-services/cloud-services-guestos-retirement-policy.md",
-      "redirect_url": "/previous-versions/azure/cloud-services/cloud-services-guestos-retirement-policy",
+      "redirect_url": "/azure/cloud-services-extended-support/cloud-services-guestos-retirement-policy",
       "redirect_document_id": false
     },
     {
       "source_path": "articles/cloud-services/cloud-services-guestos-update-matrix.md",
-      "redirect_url": "/previous-versions/azure/cloud-services/cloud-services-guestos-update-matrix",
+      "redirect_url": "/azure/cloud-services-extended-support/cloud-services-guestos-update-matrix",
       "redirect_document_id": false
     },
     {
@@ -6740,7 +6760,7 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/work-with-styx-objects-and-indicators.md",
+      "source_path": "articles/sentinel/work-with-styx-objects-and-indicators.md",
       "redirect_url": "/azure/sentinel/work-with-styx-objects-indicators",
       "redirect_document_id": false
     },
@@ -6753,6 +6773,36 @@
       "source_path": "articles/defender-for-iot/organizations/extra-deploy-enterprise-iot.md",
       "redirect_url": "/azure/defender-for-iot/organizations/eiot-defender-for-endpoint",
            "redirect_document_id": false
-    }
+    },
+    {
+      "source_path": "articles/sentinel/work-with-styx-objects-indicators.md",
+      "redirect_url": "/azure/sentinel/work-with-stix-objects-indicators",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-functions/migration.md",
+      "redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-functions/migration/lambda-functions-migration-assess.md",
+      "redirect_url": "/azure/azure-functions/migration/assess-lambda-workloads",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-functions/migration/lambda-functions-migration-discover.md",
+      "redirect_url": "/azure/azure-functions/migration/discover-lambda-workloads",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-functions/migration/lambda-functions-migration-migrate.md",
+      "redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-functions/migration/lambda-functions-migration-overview.md",
+      "redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
+      "redirect_document_id": false
+    },
   ]
 }

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

@@ -196,7 +196,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 233 |	Ghana|	10	| 30 |
 | 234 | Nigeria | 20 | 100 |
 | 236 |	Central African Republic  |	10	| 30 |
-| 238 | Cape Verde | 10 | 30 |
+| 238 | Cabo Verde | 10 | 30 |
 | 249 |  Sudan | 10  |  30  |
 | 251 |	Ethiopia  |	10	| 30 |
 | 252 |  Somalia   | 10  |  30  |  

articles/active-directory-b2c/tutorial-create-user-flows.md

@@ -58,7 +58,7 @@ The sign-up and sign-in user flow handles both experiences with a single configu
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
 1. In the Azure portal, search for and select **Azure AD B2C**.
-1. Under **Policies**, select **User flows**, and then select **New user flow**.
+1. <a name="new_user_flow"></a>Under **Policies**, select **User flows**, and then select **New user flow**.
 
     ![Screenshot of the User flows page from the Azure portal with New user flow button highlighted.](./media/tutorial-create-user-flows/sign-up-sign-in-user-flow.png)
 

articles/api-center/enable-api-center-portal-vs-code-extension.md

@@ -46,7 +46,6 @@ Enterprise developers must sign in with a Microsoft account to see the API Cente
 
 [!INCLUDE [api-center-portal-user-sign-in](includes/api-center-portal-user-sign-in.md)]
 
-### For API center administrators
 ## Steps for enterprise developers to access the API Center portal 
 
 Developers can follow these steps to connect and sign in to view an API Center portal using the Visual Studio Code extension. Settings to connect to the API center need to be provided by the API center administrator.

articles/api-center/enable-managed-api-analysis-linting.md

@@ -3,7 +3,7 @@ title: Managed API linting and analysis - Azure API Center
 description: Automatic linting of API definitions in your API center helps you analyze compliance of APIs with the organization's API style guide.
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 12/03/2024
+ms.date: 03/31/2025
 ms.author: danlep
 author: dlepow
 ms.custom: 
@@ -18,17 +18,15 @@ With API analysis:
 
 * Azure API Center automatically analyzes your API definitions whenever you add or update an API definition. API definitions are linted by default with a [spectral:oas ruleset](https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules) (API style guide).  
 * API analysis reports are generated in the Azure portal, showing how your API definitions conform to the style guide.
-* You can use the Azure API Center extension for Visual Studio Code to customize and test your own API style guide locally and then deploy it to your API center. 
-
+* Use analysis profiles to specify the ruleset and filter conditions for the APIs that are analyzed. Customize a profile's ruleset using the Azure API Center extension for Visual Studio Code. 
 
 > [!IMPORTANT]
 > If you prefer, you can enable [self-managed](enable-api-analysis-linting.md) linting and analysis using a custom Azure function, overriding the built-in capabilities. **Disable any function used for self-managed linting before using managed API analysis.**
 
 ## Limitations
 
 * Currently, only OpenAPI and AsyncAPI specification documents in JSON or YAML format are analyzed.
-* Currently, you configure a single ruleset, and it's applied to all OpenAPI definitions in your API center.
-* There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) for the maximum number of API definitions analyzed. Analysis can take a few minutes to up to 24 hours to complete.
+* There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) for the number of analysis profiles and the maximum number of API definitions analyzed. Analysis can take a few minutes to up to 24 hours to complete.
 
 ## Prerequisites
 
@@ -57,27 +55,50 @@ To view an analysis summary in your API center:
     > [!TIP]
     > You can also view the API analysis report by selecting **Analysis** from the API definition's menu bar.
 
-## Customize ruleset
+## Manage analysis profiles
+
+Azure API Center uses *analysis profiles* for linting and analyzing APIs. An analysis profile specifies a ruleset and optionally filter conditions for APIs that are analyzed. The default analysis profile applies the `spectral:oas` ruleset to all OpenAPI and AsyncAPI definitions. 
+
+You can customize the ruleset and define filter conditions in the default profile, or you can create a new profile. For example, you might want to use one profile for APIs that are in development and a different one for APIs that are in production.
+
+> [!NOTE]
+> In the Standard plan of API Center, you can create up to 3 analysis profiles. Only a single profile is supported in the Free plan.
+
+To create an analysis profile:
+
+1. In the Azure portal, navigate to your API center.
+1. In the left-hand menu, under **Governance**, select **API Analysis** > **Manage analysis profiles** > **+ Create analysis profile**.
+1. In the **Create new analysis profile** pane, enter a **Name** and **Description** for the profile.
+1. In **Ruleset**, the analyzer type (linting engine) for the ruleset appears. Currently only Spectral is supported.
+1. Under **Define filter conditions**, add one or more filter conditions for API definitions that the profile is applied to.
+1. Select **Create**.
+
+
+:::image type="content" source="media/enable-managed-api-analysis-linting/create-analysis-profile.png" alt-text="Screenshot of creating an analysis profile in the portal.":::
+
+The profile is created and a ruleset scaffold is created. To view the current ruleset, select the profile, and in the context (...) menu, select **View the ruleset**.
+
+Continue to the following sections to customize the ruleset. 
 
-You can use the Azure API Center extension for Visual Studio Code to customize the default ruleset for your API center or replace it as your organization's API style guide. For example, you can [extend the ruleset](https://docs.stoplight.io/docs/spectral/83527ef2dd8c0-extending-rulesets) or add [custom functions](https://docs.stoplight.io/docs/spectral/a781e290eb9f9-custom-functions).
+### Customize the profile's ruleset
 
-To customize or replace the ruleset:
+Use the Visual Studio Code extension for Azure API Center to customize a profile's ruleset. After customizing the ruleset and testing it locally, you can deploy it back to your API center.
 
 1. In Visual Studio Code, select the Azure API Center icon from the Activity Bar.
-1. Open the `.api-center-rules` folder at the root of your working folder.
-1. In the folder for your API center resource, open the `ruleset.yml` file.
+1. In the API Center pane, expand the API center resource you are working with, and expand **Profiles**.
+1. Expand the profile you want to modify, and select `ruleset.yaml`.
 1. Modify or replace the content as needed. 
-1. Save your changes to `ruleset.yml`.
+1. Save your changes to `ruleset.yaml`.
 
 ### Test ruleset locally
 
 Before deploying the custom ruleset to your API center, validate it locally. The Azure API Center extension for Visual Studio Code provides integrated support for API specification linting with Spectral.
 
 1. In Visual Studio Code, use the **Ctrl+Shift+P** keyboard shortcut to open the Command Palette. 
 1. Type **Azure API Center: Set active API Style Guide** and hit **Enter**.
-1. Choose **Select Local File** and specify the `ruleset.yml` file that you customized. Hit **Enter**. 
+1. Choose **Select Local File** and specify the `ruleset.yaml` file that you customized. Hit **Enter**. 
 
-    This step makes the custom ruleset the active API style guide for linting.
+    This step makes the custom ruleset the active API style guide for local linting.
 
 Now, when you open an OpenAPI-based API definition file, a local linting operation is automatically triggered in Visual Studio Code. Results are displayed inline in the editor and in the **Problems** window (**View > Problems** or **Ctrl+Shift+M**).
 
@@ -94,9 +115,10 @@ To deploy the custom ruleset to your API center:
 
 1. In Visual Studio Code, select the Azure API Center icon from the Activity Bar.
 1. In the API Center pane, expand the API center resource in which you customized the ruleset.
-1. Right-click **Rules** and select **Deploy Rules to API Center**.
+1. Expand **Profiles**.
+1. Right-click the profile in which you customized the ruleset, and select **Deploy Rules to API Center**.
 
-A message notifies you after the rules are successfully deployed to your API center. The linting engine uses the updated ruleset to analyze API definitions.
+A message notifies you after the rules are successfully deployed to your API center. The linting engine uses the updated ruleset to analyze API definitions in the profile.
 
 To see the results of linting with the updated ruleset, view the API analysis reports in the portal. 
 

articles/api-center/frequently-asked-questions.yml

@@ -59,5 +59,6 @@ additionalContent: |
     ## Related content
 
     * [Azure API Center overview](overview.md)
-    * [Build APIs | Microsoft Developer](https://developer.microsoft.com/build-apis
+    * [Build APIs | Microsoft Developer](https://developer.microsoft.com/build-apis)
+    * [API Center flash workshop](https://azure-samples.github.io/API-Center-Workshop/)
 

articles/api-center/includes/api-center-portal-app-registration.md

@@ -11,8 +11,6 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-## Create Microsoft Entra app registration
-
 First configure an app registration in your Microsoft Entra ID tenant. The app registration enables the API Center portal to access data from your API center on behalf of a signed-in user.
 
 1. In the [Azure portal](https://portal.azure.com), navigate to **Microsoft Entra ID** > **App registrations**.
@@ -24,5 +22,13 @@ First configure an app registration in your Microsoft Entra ID tenant. The app r
     1. In **Redirect URI**, select **Single-page application (SPA)** and set the URI. 
         Enter the URI of your API Center portal deployment, in the following form: `https://<service-name>.portal.<location>.azure-api-center.ms`. Replace `<service name>` and `<location>` with the name of your API center and the location where it's deployed, Example: `https://myapicenter.portal.eastus.azure-api-center.ms`.
     1. Select **Register**.
-    1. On the **Manage** > **Authentication** page, Select **Add a platform** and select **Mobile and desktop applications**. 
-    1. Configure the following three custom redirect URIs: `https://vscode.dev/redirect`, `http://localhost`, and `ms-appx-web://Microsoft.AAD.BrokerPlugin/<application-client-id>`. Replace `<application-client-id>` with the application (client) ID of this app. You can find this value on the **Overview** page. 
+
+When enabling the API Center portal in the Visual Studio Code extension for API Center, also configure the following redirect URIs. 
+
+1. On the **Manage** > **Authentication** page, Select **Add a platform** and select **Mobile and desktop applications**. 
+1. Configure the following three custom redirect URIs:<br/>
+    `https://vscode.dev/redirect`<br/>
+    `http://localhost`<br/>
+    `ms-appx-web://Microsoft.AAD.BrokerPlugin/<application-client-id>`<br/>
+    
+    Replace `<application-client-id>` with the application (client) ID of this app. You can find this value on the **Overview** page. 

articles/api-center/includes/api-center-portal-user-sign-in.md

@@ -11,9 +11,7 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-## Enable sign-in to portal by Microsoft Entra users and groups 
-
-Users must sign in to see the APIs in your API center. To enable sign-in, assign the **Azure API Center Data Reader** role to users or groups in your organization, scoped to your API center.
+To enable sign-in, assign the **Azure API Center Data Reader** role to users or groups in your organization, scoped to your API center.
 
 > [!IMPORTANT]
 > By default, you and other administrators of the API center don't have access to APIs in the API Center portal. Be sure to assign the **Azure API Center Data Reader** role to yourself and other administrators.  

articles/api-center/includes/api-center-service-limits.md

@@ -23,6 +23,7 @@ ms.custom: Include file
 | Maximum number of child properties in custom metadata property of type "object" | 10 |10 | 
 | Maximum requests per minute (data plane) | 3,000 | 6,000  |
 | Maximum number of API definitions [analyzed](../enable-managed-api-analysis-linting.md) | 10 | 2,000<sup>4</sup>  |
+| Maximum number of analysis profiles | 1 | 3 |
 | Maximum number of linked API sources<sup>5</sup> | 1  |  3 |
 | Maximum number of APIs synchronized from a linked API source | 200 | 2,000<sup>4</sup>  |