Merge pull request #250524 from MicrosoftDocs/release-preview-apim-skuv2

[READY TO MERGE] [APIM] Release preview apim skuv2 -> main

Author: v-alje

articles/api-management/TOC.yml

@@ -7,6 +7,8 @@
         href: api-management-key-concepts.md
       - name: API Management features availability
         href: api-management-features.md
+      - name: v2 service tiers
+        href: v2-service-tiers-overview.md
       - name: Service limits
         href: ../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json#api-management-limits
 - name: Quickstarts
@@ -163,17 +165,19 @@
               displayName: soft delete
               href: soft-delete.md
             - name: Migrate to stv2 platform
-              href: migrate-stv1-to-stv2.md
+              href: migrate-stv1-to-stv2.md 
             - name: Configure networking
               items:
-                - name: Connect to a virtual network
+                - name: Deploy to a VNet - external
                   href: api-management-using-with-vnet.md
-                - name: Connect to an internal virtual network
+                - name: Deploy to a VNet - internal
                   href: api-management-using-with-internal-vnet.md
-                - name: Integrate Application Gateway in an internal virtual network
+                - name: Integrate Application Gateway in an internal VNet
                   href: api-management-howto-integrate-internal-vnet-appgateway.md
                 - name: Connect privately using private endpoint
                   href: private-endpoint.md
+                - name: Integrate with VNet for outbound requests
+                  href: integrate-vnet-outbound.md
                 - name: Retrieve IP addresses
                   href: api-management-howto-ip-addresses.md
                 - name: Defend against DDoS attacks
@@ -251,7 +255,7 @@
                   href: import-api-from-odata.md
                 - name: Import SAP OData metadata
                   href: sap-api.md
-                - name: Configure API for SSE
+                - name: Configure API for SSE 
                   href: how-to-server-sent-events.md
                 - name: API import restrictions
                   href: api-management-api-import-restrictions.md

articles/api-management/api-management-features.md

@@ -17,7 +17,9 @@ Each API Management [pricing tier](https://aka.ms/apimpricing) offers a distinct
 
 > [!IMPORTANT]
 > * The Developer tier is for non-production use cases and evaluations. It doesn't offer SLA.
-> * The Consumption tier isn't available in the US Government cloud or the Microsoft Azure operated by 21Vianet cloud. 
+> * The Consumption tier isn't available in the US Government cloud or the Microsoft Azure operated by 21Vianet cloud.  
+> * API Management **v2 tiers** are now in preview, with updated feature availability. [Learn more](v2-service-tiers-overview.md).
+
 
 | Feature                                                                                      | Consumption | Developer | Basic | Standard | Premium |
 | -------------------------------------------------------------------------------------------- | ----------- | --------- | ----- | -------- | ------- |

articles/api-management/api-management-gateways-overview.md

@@ -21,6 +21,8 @@ Related information:
 
 * For more information about the API Management service tiers and features, see [Feature-based comparison of the Azure API Management tiers](api-management-features.md).
 
+[!INCLUDE [api-management-v2-tier-preview](../../includes/api-management-v2-tier-preview.md)]
+
 ## Role of the gateway
 
 The API Management *gateway* (also called *data plane* or *runtime*) is the service component that's responsible for proxying API requests, applying policies, and collecting telemetry. 

articles/api-management/api-management-howto-cache.md

@@ -37,6 +37,9 @@ What you'll learn:
 
 > [!NOTE]
 > Internal cache is not available in the **Consumption** tier of Azure API Management. You can [use an external Azure Cache for Redis](api-management-howto-cache-external.md) instead.
+> 
+> For feature availability in the v2 tiers (preview), see the [v2 tiers overview](v2-service-tiers-overview.md).
+
 
 ## Prerequisites
 

articles/api-management/api-management-howto-developer-portal-customize.md

@@ -1,12 +1,12 @@
 ---
 title: Tutorial - Access and customize the developer portal - Azure API Management | Microsoft Docs
-description: Follow this to tutorial to learn how to customize the API Management developer portal, an automatically generated, fully customizable website with the documentation of your APIs. 
+description: In this tutorial, customize the API Management developer portal, an automatically generated, fully customizable website with the documentation of your APIs. 
 services: api-management
 author: dlepow
 
 ms.service: api-management
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 09/06/2023
 ms.author: danlep
 ms.custom: engagement-fy23
 ---
@@ -40,8 +40,12 @@ You can find more details on the developer portal in the [Azure API Management d
 Follow the steps below to access the managed version of the portal.
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-1. Select the **Developer portal** button in the top navigation bar. A new browser tab with an administrative version of the portal will open.
-
+1. If you created your instance in a v2 service tier that supports the developer portal, first enable the developer portal. 
+    1. In the left menu, under **Developer portal**, select **Portal settings**. 
+    1. In the **Portal settings** window, select **Enabled**. Select **Save**. 
+    
+    It might take a few minutes to enable the developer portal.
+1. In the left menu, under **Developer portal**, select **Portal overview**. Then select the **Developer portal** button in the top navigation bar. A new browser tab with an administrative version of the portal will open.
 
 ## Developer portal architectural concepts
 

articles/api-management/api-management-howto-manage-protocols-ciphers.md

@@ -22,6 +22,7 @@ By default, API Management enables TLS 1.2 for client and backend connectivity a
 
 :::image type="content" source="media/api-management-howto-manage-protocols-ciphers/api-management-protocols-ciphers.png" alt-text="Screenshot of managing protocols and ciphers in the Azure portal.":::
 
+[!INCLUDE [api-management-v2-tier-preview](../../includes/api-management-v2-tier-preview.md)]
 
 > [!NOTE]
 > * If you're using the self-hosted gateway, see [self-hosted gateway security](self-hosted-gateway-overview.md#security) to manage TLS protocols and cipher suites.

articles/api-management/api-management-using-with-internal-vnet.md

@@ -1,6 +1,6 @@
 ---
-title: Connect to an internal virtual network using Azure API Management
-description: Learn how to set up and configure Azure API Management in a virtual network using internal mode
+title: Deploy Azure API Management instance to internal VNet
+description: Learn how to deploy (inject) your Azure API instance to a virtual network in internal mode and access API backends through it.
 author: dlepow
 
 ms.service: api-management
@@ -9,8 +9,9 @@ ms.date: 01/03/2022
 ms.author: danlep
 ---
 
-# Connect to a virtual network in internal mode using Azure API Management 
-With Azure virtual networks (VNets), Azure API Management can manage internet-inaccessible APIs using several VPN technologies to make the connection. For VNet connectivity options, requirements, and considerations, see [Using a virtual network with Azure API Management](virtual-network-concepts.md).
+# Deploy your Azure API Management instance to a virtual network - internal mode
+
+Azure API Management can be deployed (injected) inside an Azure virtual network (VNet) to access backend services within the network. For VNet connectivity options, requirements, and considerations, see [Using a virtual network with Azure API Management](virtual-network-concepts.md).
 
 This article explains how to set up VNet connectivity for your API Management instance in the *internal* mode. In this mode, you can only access the following API Management endpoints within a VNet whose access you control.
 * The API gateway
@@ -30,7 +31,7 @@ Use API Management in internal mode to:
 
 :::image type="content" source="media/api-management-using-with-internal-vnet/api-management-vnet-internal.png" alt-text="Connect to internal VNet":::
 
-For configurations specific to the *external* mode, where the API Management endpoints are accessible from the public internet, and backend services are located in the network, see [Connect to a virtual network using Azure API Management](api-management-using-with-vnet.md). 
+For configurations specific to the *external* mode, where the API Management endpoints are accessible from the public internet, and backend services are located in the network, see [Deploy your Azure API Management instance to a virtual network - external mode](api-management-using-with-vnet.md). 
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 

articles/api-management/api-management-using-with-vnet.md

@@ -1,6 +1,6 @@
 ---
-title: Connect to a virtual network using Azure API Management
-description: Learn how to set up a connection to a virtual network in Azure API Management and access API backends through it.
+title: Deploy Azure API Management instance to external VNet
+description: Learn how to deploy (inject) your Azure API instance to a virtual network in external mode and access API backends through it.
 services: api-management
 author: dlepow
 
@@ -9,15 +9,15 @@ ms.topic: how-to
 ms.date: 01/03/2022
 ms.author: danlep
 ---
-# Connect to a virtual network using Azure API Management
+# Deploy your Azure API Management instance to a virtual network - external mode
 
-Azure API Management can be deployed inside an Azure virtual network (VNet) to access backend services within the network. For VNet connectivity options, requirements, and considerations, see [Using a virtual network with Azure API Management](virtual-network-concepts.md).
+Azure API Management can be deployed (injected) inside an Azure virtual network (VNet) to access backend services within the network. For VNet connectivity options, requirements, and considerations, see [Using a virtual network with Azure API Management](virtual-network-concepts.md).
 
 This article explains how to set up VNet connectivity for your API Management instance in the *external* mode, where the developer portal, API gateway, and other API Management endpoints are accessible from the public internet, and backend services are located in the network. 
 
 :::image type="content" source="media/api-management-using-with-vnet/api-management-vnet-external.png" alt-text="Connect to external VNet":::
 
-For configurations specific to the *internal* mode, where the endpoints are accessible only within the VNet, see [Connect to an internal virtual network using Azure API Management](./api-management-using-with-internal-vnet.md). 
+For configurations specific to the *internal* mode, where the endpoints are accessible only within the VNet, see [Deploy your Azure API Management instance to a virtual network - internal mode](./api-management-using-with-internal-vnet.md). 
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 

articles/api-management/compute-infrastructure.md

@@ -4,7 +4,7 @@ description: Learn about the compute platform used to host your API Management s
 author: dlepow
 ms.service: api-management
 ms.topic: conceptual
-ms.date: 04/17/2023
+ms.date: 09/18/2023
 ms.author: danlep
 ms.custom:
 ---
@@ -19,7 +19,7 @@ Most new instances created in service tiers other than the Consumption tier are
 
 ## What are the compute platforms for API Management?
 
-The following table summarizes the compute platforms currently used for instances in the different API Management service tiers. 
+The following table summarizes the compute platforms currently used in the **Consumption**, **Developer**, **Basic**, **Standard**, and **Premium** tiers of API Management.  
 
 | Version | Description | Architecture | Tiers |
 | -------| ----------| ----------- | ---- |
@@ -64,6 +64,12 @@ The `stv2` platform infrastructure supports several resiliency and security feat
 
 Migration steps depend on features enabled in your API Management instance. If the instance isn't injected in a VNet, you can use a migration API. For instances that are VNet-injected, follow manual steps. For details, see the [migration guide](migrate-stv1-to-stv2.md).
 
+## What about the v2 pricing tiers?
+
+The v2 pricing tiers are a new set of tiers for API Management currently in preview. Hosted on a new, highly scalable and available Azure infrastructure that's different from the `stv1` and `stv2` compute platforms, the v2 tiers aren't affected by the retirement of the `stv1` platform.
+
+The v2 tiers are designed to make API Management accessible to a broader set of customers and offer flexible options for a wider variety of scenarios. For more information, see [v2 tiers overview](v2-service-tiers-overview.md).
+
 ## Next steps
 
 * [Migrate an API Management instance to the stv2 platform](migrate-stv1-to-stv2.md).

articles/api-management/integrate-vnet-outbound.md

@@ -0,0 +1,63 @@
+---
+title: Connect API Management instance to a private network | Microsoft Docs
+description: Learn how to integrate an Azure API Management instance in the Standard v2 tier with a virtual network to access backend APIs hosted within the network.
+author: dlepow
+ms.author: danlep
+ms.service: api-management
+ms.topic: how-to 
+ms.date: 09/20/2023
+---
+
+# Integrate an Azure API Management instance with a private VNet for outbound connections (preview)
+
+This article guides you through the process of configuring *VNet integration* for your Azure API Management instance so that your API Management instance can make outbound requests to API backends that are isolated in the network.
+
+When an API Management instance is integrated with a virtual network for outbound requests, the API Management itself is not deployed in a VNet; the gateway and other endpoints remain publicly accessible. In this configuration, the API Management instance can reach both public and network-isolated backend services.
+
+:::image type="content" source="./media/integrate-vnet-outbound/vnet-integration.svg" alt-text="Diagram of integrating API Management instance with a delegated subnet."  :::
+
+[!INCLUDE [api-management-availability-standard-v2](../../includes/api-management-availability-standard-v2.md)] 
+
+## Prerequisites
+
+- An Azure API Management instance in the [Standard v2](v2-service-tiers-overview.md) pricing tier
+- A virtual network with a subnet where your API Management backend APIs are hosted
+    - The network must be deployed in the same region as your API Management instance
+- (Optional) For testing, a sample backend API hosted within a different subnet in the virtual network. For example, see [Tutorial: Establish Azure Functions private site access](../azure-functions/functions-create-private-site-access.md).
+
+## Delegate the subnet
+
+The subnet used for integration must be delegated to the **Microsoft.Web/serverFarms** service. In the subnet settings, in **Delegate subnet to a service**, select **Microsoft.Web/serverFarms**.
+
+:::image type="content" source="media/integrate-vnet-outbound/delegate-subnet.png" alt-text="Screenshot of delegating the subnet to a service in the portal.":::
+
+For details, see [Add or remove a subnet delegation](../virtual-network/manage-subnet-delegation.md).
+
+## Enable VNet integration
+
+This section will guide you through the process of enabling VNet integration for your Azure 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 **VNET integration**.
+
+    :::image type="content" source="media/integrate-vnet-outbound/integrate-vnet.png" lightbox="media/integrate-vnet-outbound/integrate-vnet.png" alt-text="Screenshot of VNet 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 VNet 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 VNet settings in the portal.":::
+
+## (Optional) Test VNet integration
+
+If you have an API hosted in the virtual network, you can import it to your Management instance and test the VNet integration. For basic steps, see [Import and publish an API](import-and-publish.md).
+
+
+## Related content
+
+* [Use a virtual network with Azure API Management](virtual-network-concepts.md)
+
+
+