update migration guidance

Author: dlepow

articles/api-management/compute-infrastructure.md

@@ -1,10 +1,10 @@
 ---
 title: Azure API Management compute platform
-description: Learn about the compute platform used to host your API Management service instance
+description: Learn about the compute platform used to host your API Management service instance. Instances in the dedicated service tiers of API Management are hosted on the stv1 or stv2 compute platform.
 author: dlepow
 ms.service: api-management
 ms.topic: conceptual
-ms.date: 03/09/2023
+ms.date: 04/17/2023
 ms.author: danlep
 ms.custom: 
 ---
@@ -22,11 +22,11 @@ The following table summarizes the compute platforms currently used for instance
 
 | Version | Description | Architecture | Tiers |
 | -------| ----------| ----------- | ---- |
-| `stv2`, `stv2.1` | Single-tenant v2 | Azure-allocated VM infrastructure that supports availability zones, private endpoints<br/><br/>`stv2.1` provides upgraded VM infrastructure with greater unit performance<br/><br/>See [What are the benefits of the `stv2` platform?](#what-are-the-benefits-of-the-stv2-platform) | Developer, Basic, Standard, Premium<sup>1</sup> |
+| `stv2` | Single-tenant v2 | Azure-allocated compute infrastructure that supports added resiliency and security features. See [What are the benefits of the `stv2` platform?](#what-are-the-benefits-of-the-stv2-platform) in this article. | Developer, Basic, Standard, Premium<sup>1</sup> |
 | `stv1` |  Single-tenant v1 | Azure-allocated compute infrastructure |  Developer, Basic, Standard, Premium | 
 | `mtv1` | Multi-tenant v1 |  Shared infrastructure that supports native autoscaling and scaling down to zero in times of no traffic |  Consumption |
 
-<sup>1</sup> Newly created instances in these tiers and some existing instances in Developer and Premium tiers configured with virtual networks or availability zones. Hosting on higher performance `stv2.1` platform is provided subject to regional availability and capacity.  
+<sup>1</sup> Newly created instances in these tiers and some existing instances in Developer and Premium tiers configured with virtual networks or availability zones.
 
 > [!NOTE]
 > Currently, the `stv2` platform isn't available in the US Government cloud or in the following Azure regions: China East, China East 2, China North, China North 2.
@@ -39,8 +39,8 @@ You can find the platform version of your instance using the portal, the API Man
 
 To find the platform version in the portal:
 
-1. Go to your API Management instance.
-1. On the **Overview** page, the **Platform Version** is displayed.
+1. Sign in to the [portal](https://portal.azure.com) and go to your API Management instance.
+1. On the **Overview** page, under **Essentials**, the **Platform Version** is displayed.
 
     :::image type="content" source="media/compute-infrastructure/platformversion-property.png" alt-text="Screenshot of the API Management platform version in the portal.":::
 
@@ -52,29 +52,15 @@ The `stv2` platform infrastructure supports several resiliency and security feat
 * [Private endpoints](private-endpoint.md)
 * [Protection with Azure DDoS](protect-with-ddos-protection.md)
 
-### Additional benefits of `stv2.1` platform 
-Starting in March 2023, API Management is introducing the `stv2.1` platform with the capabilities of the `stv2` platform along with upgraded CPU and memory resources. 
-
-This compute upgrade in `stv2.1` provides several benefits to API Management customers:
-
-* Increased performance per API Management scale unit, at no additional cost
-* Increased unit capacity, as measured by the capacity metric
-* Reduced times to provision and scale out instances
-
-The `stv2.1` infrastructure is being introduced over time to Azure regions and is provided to customers based on available capacity. Instances that are updated will show a `platformVersion` value of `stv2.1`.    
 
 ## How do I migrate to the `stv2` platform? 
 
 > [!IMPORTANT]
 > Support for API Management instances hosted on the `stv1` platform will be [retired by 31 August 2024](breaking-changes/stv1-platform-retirement-august-2024.md). To ensure proper operation of your API Management instance, you should migrate any instance hosted on the `stv1` platform to `stv2` before that date.
 
-Migration steps depend on features enabled in your API Management instance. For details, see the [migration guidance](migrate-stv1-to-stv2.md):
-
-* **Non-VNet-injected API Management instance** - Use the [Migrate to stv2](/rest/api/apimanagement/current-preview/api-management-service/migratetostv2) REST API
-
-* **VNet-injected API Management instance** - Update the VNet connection, or enable zone redundancy
+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).
 
 ## Next steps
 
-* Learn more about using a [virtual network](virtual-network-concepts.md) with API Management.
-* Learn more about enabling [availability zones](../reliability/migrate-api-mgt.md).
+* [Migrate an API Management instance to the stv2 platform](migrate-stv1-to-stv2.md).
+* Learn more about [upcoming breaking changes](breaking-changes/overview.md) in API Management.

articles/api-management/migrate-stv1-to-stv2.md

@@ -5,7 +5,7 @@ description: Follow the steps in this article to migrate your Azure API Manageme
 author: dlepow
 ms.service: api-management
 ms.topic: how-to
-ms.date: 03/09/2023
+ms.date: 04/17/2023
 ms.author: danlep
 
 ---
@@ -14,14 +14,15 @@ ms.author: danlep
 
 You can migrate an API Management instance hosted on the `stv1` compute platform to the `stv2` platform. This article provides migration steps for two scenarios, depending on whether or not your API Management instance is currently deployed (injected) in an [external](api-management-using-with-vnet.md) or [internal](api-management-using-with-internal-vnet.md) VNet.
 
-* **Non-VNet-injected API Management instance** - Use the [Migrate to stv2](/rest/api/apimanagement/current-preview/api-management-service/migratetostv2) REST API
+* **Non-VNet-injected API Management instance** - Use the [Migrate to stv2](/rest/api/apimanagement/current-ga/api-management-service/migratetostv2) REST API
 
-* **VNet-injected API Management instance** - Update the VNet connection, or enable zone redundancy
+* **VNet-injected API Management instance** - Manually update the VNet configuration settings
 
 For more information about the `stv1` and `stv2` platforms and the benefits of using the `stv2` platform, see [Compute platform for API Management](compute-infrastructure.md).
 
 > [!IMPORTANT]
-> * Migration is a long-running operation and could take several minutes to complete. Your instance will experience downtime during the migration.
+> * Migration is a long-running operation. Your instance will experience downtime during the last 10-15 minutes of migration. Plan your migration accordingly.
+> * The VIP address(es) of your API Management will change.
 > * Migration to `stv2` is not reversible.
 
 > [!IMPORTANT]
@@ -61,20 +62,22 @@ RG_NAME={name of your resource group}
 APIM_RESOURCE_ID=$(az apim show --name $APIM_NAME --resource-group $RG_NAME --query id --output tsv)
 
 # Call REST API to migrate to stv2
-az rest --method post --uri "$APIM_RESOURCE_ID/migrateToStv2?api-version=2022-04-01-preview"
+az rest --method post --uri "$APIM_RESOURCE_ID/migrateToStv2?api-version=2022-08-01"
 ```
 
 ## Scenario 2: Migrate a network-injected API Management instance
 
-Trigger migration of a network-injected API Management instance to the `stv2` platform by updating the existing network configuration (see the following section), or enable [zone redundancy](../reliability/migrate-api-mgt.md).
+Trigger migration of a network-injected API Management instance to the `stv2` platform by updating the existing network configuration (see the following section). You can also cause migrate to the `stv2` platform by enabling [zone redundancy](../reliability/migrate-api-mgt.md).
 
 ### Update VNet configuration
 
+Update the configuration of the VNet in each location (region) where the API Management instance is deployed.
+
 #### Prerequisites
 
-* A new or existing virtual network and subnet in the same region and subscription as your API Management instance. The subnet must be different from the one currently used for the instance hosted on the `stv1` platform, and a network security group must be attached.
+* A new subnet in the current virtual network. (Alternatively, set up a subnet in a different virtual network in the same region and subscription as your API Management instance). A network security group must be attached to the subnet.
 
-* A new or existing Standard SKU [public IPv4 address](../virtual-network/ip-services/public-ip-addresses.md#sku) resource in the same region and subscription as your API Management instance.
+* A Standard SKU [public IPv4 address](../virtual-network/ip-services/public-ip-addresses.md#sku) resource in the same region and subscription as your API Management instance.
 
 For details, see [Prerequisites for network connections](api-management-using-with-vnet.md#prerequisites).
 
@@ -91,15 +94,11 @@ To update the existing external or internal VNet configuration:
 
 The virtual network configuration is updated, and the instance is migrated to the `stv2` platform.
 
-> [!NOTE]
-> * Updating the VNet configuration takes from 15 to 45 minutes to complete.
-> * The VIP address(es) of your API Management instance will change.
-
-
 ## Verify migration
 
 To verify that the migration was successful, check the [platform version](compute-infrastructure.md#how-do-i-know-which-platform-hosts-my-api-management-instance) of your API Management instance. After successful migration, the value is `stv2`.
 
 ## Next steps
 
-* Learn about [stv1 platform retirement](breaking-changes/stv1-platform-retirement-august-2024.md).
+* Learn about [stv1 platform retirement](breaking-changes/stv1-platform-retirement-august-2024.md).
+* For instances deployed in a VNet, see the [Virtual network configuration reference](virtual-network-reference.md).