Skip to content

Commit e9fa1b7

Browse files
authored
Merge pull request #285226 from dlepow/sla
[APIM] SLA post stv1 retirement
2 parents d585ec8 + 569827e commit e9fa1b7

File tree

4 files changed

+35
-11
lines changed

4 files changed

+35
-11
lines changed

articles/api-management/breaking-changes/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The following table lists all the upcoming breaking changes and feature retireme
2626
| [API version retirements][api2023] | June 1, 2024 |
2727
| [Workspaces preview breaking changes][workspaces2024] | June 14, 2024 |
2828
| [stv1 platform retirement - Global Azure][stv12024] | August 31, 2024 |
29-
| [stv1 platform retirement - Azure Government, Azure in China][stv1sov2025] | February 25, 2025 |
29+
| [stv1 platform retirement - Azure Government, Azure in China][stv1sov2025] | February 24, 2025 |
3030
| [Git repository retirement][git2025] | March 15, 2025 |
3131
| [Direct management API retirement][mgmtapi2025] | March 15, 2025 |
3232
| [Workspaces preview breaking changes, part 2][workspaces2025march] | March 31, 2025 |

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

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: reference
8-
ms.date: 08/08/2024
8+
ms.date: 08/28/2024
99
ms.author: danlep
1010
---
1111

@@ -24,11 +24,11 @@ The following table summarizes the compute platforms currently used for instance
2424
| -------| ----------| ----------- | ---- |
2525
| `stv2` | Single-tenant v2 | Azure-allocated compute infrastructure that supports availability zones, private endpoints | Developer, Basic, Standard, Premium |
2626
| `stv1` | Single-tenant v1 | Azure-allocated compute infrastructure | Developer, Basic, Standard, Premium |
27-
| `mtv1` | Multi-tenant v1 | Shared infrastructure that supports native autoscaling and scaling down to zero in times of no traffic | Consumption |
27+
| `mtv1` | Multitenant v1 | Shared infrastructure that supports native autoscaling and scaling down to zero in times of no traffic | Consumption |
2828

2929
**For continued support and to take advantage of upcoming features, customers must [migrate](../migrate-stv1-to-stv2.md) their Azure API Management instances from the `stv1` compute platform to the `stv2` compute platform.** The `stv2` compute platform comes with additional features and improvements such as support for Azure Private Link and other networking features.
3030

31-
New instances created in service tiers other than the Consumption tier are mostly hosted on the `stv2` platform already. Existing instances on the `stv1` compute platform will continue to work normally until the retirement date, but those instances wont receive the latest features available to the `stv2` platform. Support for `stv1` instances will be retired by 31 August 2024.
31+
New instances created in service tiers other than the Consumption tier are mostly hosted on the `stv2` platform already. Existing instances on the `stv1` compute platform will continue to work normally until the retirement date, but those instances won't receive the latest features available to the `stv2` platform. Support for `stv1` instances will be retired by 31 August 2024.
3232

3333
## Is my service affected by this?
3434

@@ -38,17 +38,31 @@ If the value of the `platformVersion` property of your service is `stv1`, it's h
3838

3939
Support for API Management instances hosted on the `stv1` platform will be retired by 31 August 2024.
4040

41-
> [!WARNING]
42-
> If your instance is currently hosted on the `stv1` platform, you must migrate to the `stv2` platform. Failure to migrate by the retirement date might result in loss of the environments running APIs and all configuration data.
43-
4441
## What do I need to do?
4542

46-
**Migrate all your existing instances hosted on the `stv1` compute platform to the `stv2` compute platform by 31 August 2024.**
43+
**Migrate all your existing instances hosted on the `stv1` compute platform to the `stv2` compute platform.**
4744

4845
If you have existing instances hosted on the `stv1` platform, follow our **[migration guide](../migrate-stv1-to-stv2.md)** to ensure a successful migration.
4946

47+
## What happens after 31 August 2024?
48+
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+
51+
### End of SLA commitment for `stv1` instances
52+
53+
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.
54+
55+
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.
56+
57+
### Automatic migration
58+
59+
Starting 1 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.
60+
5061
[!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]
5162

63+
> [!NOTE]
64+
> Azure support can't extend the timeline for automatic migration or for SLA support of `stv1` instances after the retirement date.
65+
5266
## Related content
5367

5468
* [Migrate from stv1 platform to stv2](../migrate-stv1-to-stv2.md)

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

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: reference
8-
ms.date: 08/09/2024
8+
ms.date: 08/28/2024
99
ms.author: danlep
1010
---
1111

@@ -24,7 +24,7 @@ The following table summarizes the compute platforms currently used for instance
2424
| -------| ----------| ----------- | ---- |
2525
| `stv2` | Single-tenant v2 | Azure-allocated compute infrastructure that supports availability zones, private endpoints | Developer, Basic, Standard, Premium |
2626
| `stv1` | Single-tenant v1 | Azure-allocated compute infrastructure | Developer, Basic, Standard, Premium |
27-
| `mtv1` | Multi-tenant v1 | Shared infrastructure that supports native autoscaling and scaling down to zero in times of no traffic | Consumption |
27+
| `mtv1` | Multitenant v1 | Shared infrastructure that supports native autoscaling and scaling down to zero in times of no traffic | Consumption |
2828

2929
**For continued support and to take advantage of upcoming features, customers must [migrate](../migrate-stv1-to-stv2.md) their Azure API Management instances from the `stv1` compute platform to the `stv2` compute platform.** The `stv2` compute platform comes with additional features and improvements such as support for Azure Private Link and other networking features.
3030

@@ -38,14 +38,25 @@ If the value of the `platformVersion` property of your service is `stv1`, it's h
3838

3939
In Azure Government and Azure operated by 21Vianet, support for API Management instances hosted on the `stv1` platform will be retired by 24 February 2025.
4040

41+
Also, as of 1 September 2024, API Management will no longer back API Management instances running on the `stv1` compute platform with an SLA.
42+
4143
## What do I need to do?
4244

4345
**Migrate all your existing instances hosted on the `stv1` compute platform to the `stv2` compute platform by 24 February 2025.**
4446

4547
If you have existing instances hosted on the `stv1` platform, follow our **[migration guide](../migrate-stv1-to-stv2.md)** to ensure a successful migration.
4648

49+
## End of SLA commitment for `stv1` instances - 1 September 2024
50+
51+
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.
52+
53+
Through continued use of an instance hosted on the `stv1` platform beyond 1 September 2024, you acknowledge that Azure does not commit to the SLA of 99.95%.
54+
55+
4756
[!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]
4857

58+
> [!NOTE]
59+
> Azure support can't extend the timeline for SLA support of `stv1` instances.
4960
5061
## Related content
5162

includes/api-management-migration-support.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,3 @@ If you have questions, get fast answers from community experts in [Microsoft Q&A
1818
1. Under **Resource**, select the Azure resource that you’re creating a support request for.
1919
1. For **Problem type**, select **Administration and Management**.
2020
1. For **Problem subtype**, select **Upgrade, Scale or SKU Changes**.
21-

0 commit comments

Comments
 (0)