wip

Author: gitName

articles/api-management/breaking-changes/stv1-platform-retirement-august-2024.md

@@ -54,9 +54,7 @@ As of 1 September 2024, API Management will no longer provide any service level
 
 Through continued use of an instance hosted on the `stv1` platform beyond the retirement date, you acknowledge that Azure does not commit to the SLA of 99.95% for the retired instances.
 
-### Automatic migration
-
-[!INCLUDE [api-management-automatic-migration](../../includes/api-management-automatic-migration.md)]
+[!INCLUDE [api-management-automatic-migration](../../../includes/api-management-automatic-migration.md)]
 
 
 [!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]

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

@@ -241,6 +241,9 @@ Under certain conditions, [Option 1: Migrate and keep same subnet](#option-1-mig
 
 * **Azure Key Vault blocked** - If access to Azure Key Vault is currently blocked, you must migrate using Option 2, including setting up NSG rules in the new subnet for access to Azure Key Vault.
 
+[!INCLUDE [api-management-automatic-migration](../../includes/api-management-automatic-migration.md)]
+
+
 [!INCLUDE [api-management-migration-support](../../includes/api-management-migration-support.md)]
 
 ## Frequently asked questions

includes/api-management-automatic-migration.md

@@ -6,6 +6,8 @@ ms.date: 02/19/2025
 ms.author: danlep
 ---
 
+## Automatic migration
+
 Starting September 2024, we'll automatically migrate remaining `stv1` service instances to the `stv2` compute platform. All affected customers will be notified of the upcoming automatic migration a week in advance. Automatic migration might cause downtime for your upstream API consumers. You may still migrate your own instances before automatic migration takes place.
 
 ### Virtual network configuration may be removed during automatic migration