Merge pull request #289704 from dlepow/premreg

[APIM][release-preview-apim-premv2] Regions, limited preview

Author: prmerger-automator[bot]

articles/api-management/api-management-region-availability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 10/01/2024
+ms.date: 11/20/2024
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -28,27 +28,27 @@ Information in the following table is updated regularly. Capacity availability i
 | Australia Central | ✅ | ✅ | | |
 | Australia East | ✅ | ✅ | ✅ | ✅ |
 | Australia Southeast | ✅ | ✅ | | |
-| Brazil South | ✅ | ✅ | ✅ |  |
+| Brazil South | ✅ | ✅ | |  |
 | Central India  | ✅ | ✅ | |  |
 | Central US  | |  | ✅ |  |
-| East Asia | ✅ | ✅ | ✅ | ✅ |
+| East Asia | ✅ | ✅ | | ✅ |
 | East US  | ✅ | ✅ |  |  |
 | East US 2 | ✅ | ✅ |  | ✅ |
-| France Central  | ✅ | ✅ | ✅ | ✅ |
+| France Central  | ✅ | ✅ | | ✅ |
 | Germany West Central  | ✅ | ✅ | ✅ | ✅ |
-| Japan East | ✅ | ✅ | ✅ | ✅ |
+| Japan East | ✅ | ✅ | | ✅ |
 | Korea Central | ✅ | ✅ | ✅ | | 
 | North Central US | ✅ | ✅ |  | ✅ |
 | North Europe | ✅ | ✅ |  | ✅ |
 | Norway East | ✅ | ✅ | ✅ | |
-| South Africa North | ✅ | ✅ | ✅ |  |
+| South Africa North | ✅ | ✅ | |  |
 | South Central US | ✅ | ✅ |  |  |
 | South India | ✅ | ✅ |  |  |
-| Southeast Asia | ✅ | ✅ | ✅ | ✅ |
+| Southeast Asia | ✅ | ✅ | | ✅ |
 | Switzerland North | ✅ |✅ |  | |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
-| West Europe  | ✅ | ✅ | ✅ |  |
+| West Europe  | ✅ | ✅ | |  |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 

articles/api-management/inject-vnet-v2.md

@@ -32,19 +32,20 @@ If you want to enable *public* inbound access to an API Management instance in t
 > [!IMPORTANT]
 > * Virtual network injection described in this article is available only for API Management instances in the Premium v2 tier (preview). For networking options in the different tiers, see [Use a virtual network with Azure API Management](virtual-network-concepts.md).
 > * Currently, you can inject a Premium v2 instance into a virtual network only when the instance is **created**. You can't inject an existing Premium v2 instance into a virtual network. However, you can update the subnet settings for injection after the instance is created.
+> * Currently, you can't switch between virtual network injection and virtual network integration for a Premium v2 instance.
 
 ## Prerequisites
 
 - An Azure API Management instance in the [Premium v2](v2-service-tiers-overview.md) pricing tier.
-- A virtual network with a subnet where your client apps and your API Management backend APIs are hosted. See the following sections for requirements and recommendations for the virtual network and subnet.
+- A virtual network where your client apps and your API Management backend APIs are hosted. See the following sections for requirements and recommendations for the virtual network and subnet used for the API Management instance.
 
 ### Network location
 
 * The virtual network must be in the same region and Azure subscription as the API Management instance.
 
 ### Subnet requirements
 
-* The subnet can't be shared with another Azure resource.
+* The subnet for the API Management instance can't be shared with another Azure resource.
 
 ### Subnet size 
 
@@ -89,7 +90,7 @@ When you [create](get-started-create-service-instance.md) a Premium v2 instance
 
 ## DNS settings for integration with private IP address
 
-When a Premium v2 API Management instance is injected in a virtual network, you have to manage your own DNS to enable inbound access to your API Management endpoints. 
+When a Premium v2 API Management instance is injected in a virtual network, you have to manage your own DNS to enable inbound access to API Management. 
 
 We recommend:
 

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

@@ -12,9 +12,9 @@ ms.date: 10/16/2024
 
 [!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 so that your instance can make outbound requests to API backends that are isolated in the 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 hosted in a delegated subnet of 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. In this configuration, the API Management instance can reach both public and network-isolated backend services.
+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."  :::
 
@@ -23,6 +23,8 @@ If you want to inject a Premium v2 API Management instance into a virtual networ
 > [!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).
 > * You can enable virtual network integration when you create an API Management instance in the Standard v2 or Premium v2 tier, or after the instance is created.
+> * Currently, you can't switch between virtual network injection and virtual network integration for a Premium v2 instance.
+
 
 
 ## Prerequisites

articles/api-management/v2-service-tiers-overview.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 10/22/2024
+ms.date: 11/20/2024
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -25,13 +25,16 @@ The following v2 tiers are generally available:
 
 The following v2 tier is in preview:
 
-* **Premium v2** (preview) - Premium v2 offers enterprise features including full virtual network isolation and scaling for high volume workloads.
+* **Premium v2** - Premium v2 offers enterprise features including full virtual network isolation and scaling for high volume workloads.
+
+    > [!NOTE]
+    > The Premium v2 tier is currently in limited preview. To sign up, fill [this form](https://aka.ms/premiumv2).
 
 ## Key capabilities
 
 * **Faster deployment, configuration, and scaling** - Deploy a production-ready API Management instance in minutes. Quickly apply configurations such as certificate and hostname updates. Scale a Basic v2 or Standard v2 instance quickly to up to 10 units to meet the needs of your API management workloads. Scale a Premium v2 instance to up to 30 units.
 
-* **Simplified networking** - The Standard v2 and Premium v2 tiers provide [networking options](#networking-options) to isolate inbound and outbound traffic to API Management.
+* **Simplified networking** - The Standard v2 and Premium v2 tiers provide [networking options](#networking-options) to isolate API Management's inbound and outbound traffic.
 
 * **More options for production workloads** - The v2 tiers are all supported with an SLA. Upgrade from Basic v2 to Standard v2 to Premium v2 to add more production options.
 
@@ -48,7 +51,7 @@ The latest capabilities of the v2 tiers are supported in API Management API vers
 
 * **Standard v2** and **Premium v2** support **virtual network integration** to allow your API Management instance to reach API backends that are isolated in a single connected virtual network. The API Management gateway, management plane, and developer portal remain publicly accessible from the internet. The virtual network must be in the same region as the API Management instance. [Learn more](integrate-vnet-outbound.md).
 
-* **Premium v2** supports simplified **virtual network injection** for complete isolation of inbound and outbound traffic without imposing dependencies on the customer's virtual network. [Learn more](inject-vnet-v2.md).
+* **Premium v2** also supports simplified **virtual network injection** for complete isolation of inbound and outbound traffic without needing to open traffic to API Management's internal dependencies. [Learn more](inject-vnet-v2.md).
 
 ### Supported regions