edits

Author: dlepow

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

@@ -43,8 +43,6 @@ API Management platform migration from `stv1` to `stv2` involves updating the un
 
 [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
-[!INCLUDE [api-management-migration-precreated-ip](../../includes/api-management-migration-precreated-ip.md)]
-
 ## Migrate the instance to stv2 platform
 
 ### Public IP address options 

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

@@ -105,8 +105,6 @@ When migrating a VNet-injected instance and keeping the same subnet configuratio
 |Internal     |    Preserve VIP     |  Downtime for approximately 20 minutes during migration while the existing IP address is assigned to the new `stv2` deployment.       | No retention |
 |Internal     |  New VIP       |   No downtime | Retained by default for 4 hours to allow you to update network dependencies   |
 
-[!INCLUDE [api-management-migration-no-preserve-ip](../../includes/api-management-migration-no-preserve-ip.md)]
-
 ### Migration script
 
 [!INCLUDE [api-management-migration-no-preserve-ip](../../includes/api-management-migration-no-preserve-ip.md)]

includes/api-management-migration-no-preserve-ip.md

@@ -7,4 +7,4 @@ ms.author: danlep
 ---
 
 > [!IMPORTANT]
-> As of August 2024, the option to migrate and preserve the VIP address is temporarily available for VNet-injected instances. All migrations during this time to the `stv2` platform must use a new VIP address.
+> As of August 2024, the option to migrate and preserve the VIP address is temporarily available for VNet-injected instances. All migrations to the `stv2` platform during this time must use a new VIP address.