Skip to content

Commit 6b3c9b2

Browse files
committed
review
1 parent 65b35f4 commit 6b3c9b2

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,8 @@ If you have existing instances hosted on the `stv1` platform, follow our **[migr
4646

4747
## What happens after 31 August 2024?
4848

49+
**Your `stv1` instance will not be shut down, deactivated, or deleted.** However, the SLA commitment for the instance ends, and any `stv1` instance after the retirement date will be scheduled for automatic migration to the `stv2` platform.
50+
4951
### End of SLA commitment for `stv1` instances
5052

5153
As of 1 September 2024, API Management will no longer provide any service level guarantees, and by extension service credits, for performance or availability issues related to the Developer, Basic, Standard, and Premium service instances running on the `stv1` compute platform. Also, no new security and compliance investments will be made in the API Management `stv1` platform.

includes/api-management-migration-support.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,3 +19,6 @@ If you have questions, get fast answers from community experts in [Microsoft Q&A
1919
1. For **Problem type**, select **Administration and Management**.
2020
1. For **Problem subtype**, select **Upgrade, Scale or SKU Changes**.
2121

22+
> [!NOTE]
23+
> Azure support can't extend the timeline for automatic migration or for SLA support of `stv1` instances after the retirement date.
24+

0 commit comments

Comments
 (0)