edit

Author: dlepow

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

@@ -60,6 +60,9 @@ Starting 1 September 2024, we'll automatically migrate remaining `stv1` service
 
 [!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]
 
+> [!NOTE]
+> Azure support can't extend the timeline for automatic migration or for SLA support of `stv1` instances after the retirement date.
+
 ## Related content
 
 * [Migrate from stv1 platform to stv2](../migrate-stv1-to-stv2.md)

articles/api-management/breaking-changes/stv1-platform-retirement-sovereign-clouds-february-2025.md

@@ -55,6 +55,8 @@ Through continued use of an instance hosted on the `stv1` platform beyond 1 Sept
 
 [!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]
 
+> [!NOTE]
+> Azure support can't extend the timeline for SLA support of `stv1` instances.
 
 ## Related content
 

includes/api-management-migration-support.md

@@ -18,7 +18,3 @@ If you have questions, get fast answers from community experts in [Microsoft Q&A
 1. Under **Resource**, select the Azure resource that you’re creating a support request for.  
 1. For **Problem type**, select **Administration and Management**. 
 1. For **Problem subtype**, select **Upgrade, Scale or SKU Changes**. 
-
-> [!NOTE]
-> Azure support can't extend the timeline for automatic migration or for SLA support of `stv1` instances after the retirement date.
-