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

Author: v-thepet

.openpublishing.redirection.json

@@ -6740,7 +6740,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
     },

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/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>  |
 

articles/api-center/media/enable-api-analysis-linting/api-analysis-summary.png

@@ -5,20 +5,20 @@ author: dlepow
 ms.author: danlep
 ms.service: azure-api-management
 ms.topic: how-to 
-ms.date: 03/20/2025
+ms.date: 04/03/2025
 ---
 
 # Integrate an Azure API Management instance with a private virtual network for outbound connections 
 
 [!INCLUDE [api-management-availability-standardv2-premiumv2](../../includes/api-management-availability-standardv2-premiumv2.md)] 
 
-This article guides you through the process of configuring *virtual network integration* for your Standard v2 or Premium v2 (preview) Azure API Management instance. With virtual network integration, your instance can make outbound requests to APIs hosted in a delegated subnet of a single connected virtual network.
+This article guides you through the process of configuring *virtual network integration* for your Standard v2 or Premium v2 (preview) Azure API Management instance. With virtual network integration, your instance can make outbound requests to APIs that are isolated in a single connected virtual network.
 
 When an API Management instance is integrated with a virtual network for outbound requests, the gateway and developer portal endpoints remain publicly accessible. The API Management instance can reach both public and network-isolated backend services.
 
 :::image type="content" source="./media/integrate-vnet-outbound/vnet-integration.png" alt-text="Diagram of integrating API Management instance with a virtual network for outbound traffic."  :::
 
-If you want to inject a Premium v2 API Management instance into a virtual network to isolate both inbound and outbound traffic, see [Inject a Premium v2 instance into a virtual network](inject-vnet-v2.md).
+If you want to inject a Premium v2 (preview) API Management instance into a virtual network to isolate both inbound and outbound traffic, see [Inject a Premium v2 instance into a virtual network](inject-vnet-v2.md).
 
 > [!IMPORTANT]
 > * Outbound virtual network integration described in this article is available only for API Management instances in the Standard v2 and Premium v2 tiers. For networking options in the different tiers, see [Use a virtual network with Azure API Management](virtual-network-concepts.md).
@@ -48,7 +48,7 @@ If you want to inject a Premium v2 API Management instance into a virtual networ
 
 ### Network security group
 
-A network security group must be associated with the subnet. No specific rules are required. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
+A network security group must be associated with the subnet. Configure any network security group rules that you need for the gateway to access your API backends. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
 
 ### Subnet delegation
 
@@ -76,21 +76,14 @@ You must have at least the following role-based access control permissions on th
 
 ## Configure virtual network integration
 
-This section guides you through the process of configure external virtual network integration for an existing Azure API Management instance.
+This section guides you through the process to configure external virtual network integration for an existing Azure API Management instance. You can also configure virtual network integration when you create a new API Management instance.
 
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-1. In the left menu, under **Deployment + Infrastructure**, select **Network**.
-1. On the **Outbound traffic** card, select **virtual network integration**.
-
-    :::image type="content" source="media/integrate-vnet-outbound/integrate-vnet.png" lightbox="media/integrate-vnet-outbound/integrate-vnet.png" alt-text="Screenshot of virtual network integration in the portal.":::
-
-1. In the **Virtual network** blade, enable the **Virtual network** checkbox.
-1. Select the location of your API Management instance.
-1. In **Virtual network**, select the virtual network and the delegated subnet that you want to integrate. 
-1. Select **Apply**, and then select **Save**. The virtual network is integrated.
-
-    :::image type="content" source="media/integrate-vnet-outbound/vnet-settings.png" lightbox="media/integrate-vnet-outbound/vnet-settings.png" alt-text="Screenshot of virtual network settings in the portal.":::
+1. In the left menu, under **Deployment + Infrastructure**, select **Network** > **Edit**.
+1. On the **Network configuration** page, under **Outbound features**, select **Enable** virtual network integration.
+1. Select the virtual network and the delegated subnet that you want to integrate. 
+1. Select **Save**. The virtual network is integrated.
 
 ## (Optional) Test virtual network integration