Skip to content

Commit 9ea224d

Browse files
committed
wording
1 parent 3a1861e commit 9ea224d

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

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

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

4747
## What happens after 31 August 2024?
4848

49+
<<<<<<< HEAD
4950
### End of SLA support for `stv1` instances
5051

5152
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.
53+
=======
54+
### End of SLA coverage for `stv1` instances
55+
56+
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
57+
API Management `stv1` platform.
58+
>>>>>>> 8ca110326c91 ([APIM] SLA post stv1 retirement)
5259
5360
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.
5461

5562
### Automatic migration
5663

64+
<<<<<<< HEAD
5765
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. Alternatively, migrate your own instances before automatic migration takes place.
66+
=======
67+
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.
68+
>>>>>>> 8ca110326c91 ([APIM] SLA post stv1 retirement)
5869
5970
[!INCLUDE [api-management-migration-support](../../../includes/api-management-migration-support.md)]
6071

0 commit comments

Comments
 (0)