You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-guestos-retirement-policy.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,11 +17,11 @@ The information on this page relates to the Azure Guest operating system ([Guest
17
17
18
18
Microsoft has a published [support policy for the Guest OS](https://support.microsoft.com/gp/azure-cloud-lifecycle-faq). This page describes how the policy is implemented.
19
19
20
-
The policy is
20
+
The policy is:
21
21
22
-
1. Microsoft supports **at least the latest two families of the Guest OS**. When a family is retired, customers have 12 months from the official retirement date to update to a newer supported Guest OS family.
23
-
2. Microsoft supports **at least the latest two versions of the supported Guest OS families**.
24
-
3. Microsoft supports **at least the latest two versions of the Azure SDK**. When a version of the SDK is retired, customers have 12 months from the official retirement date to update to a newer version.
22
+
* Microsoft supports **at least the latest two families of the Guest OS**. When a family is retired, customers have 12 months from the official retirement date to update to a newer supported Guest OS family.
23
+
* Microsoft supports **at least the latest two versions of the supported Guest OS families**.
24
+
* Microsoft supports **at least the latest two versions of the Azure SDK**. When a version of the SDK is retired, customers have 12 months from the official retirement date to update to a newer version.
25
25
26
26
At times, more than two families or releases may be supported. Official Guest OS support information appears on the [Azure Guest OS Releases and SDK Compatibility Matrix](cloud-services-guestos-update-matrix.md).
27
27
@@ -33,9 +33,9 @@ Once the retirement is announced, customers have a 12 month "transition" period
33
33
34
34
A gradual retirement process begins six (6) months into the transition period. During this time:
35
35
36
-
1. Microsoft notifies customers of the retirement.
37
-
2. The newer version of the Azure SDK doesn't support the retired Guest OS family.
38
-
3. New deployments and redeployments of Cloud Services are prohibited on the retired family
36
+
* Microsoft notifies customers of the retirement.
37
+
* The newer version of the Azure SDK doesn't support the retired Guest OS family.
38
+
* New deployments and redeployments of Cloud Services are prohibited on the retired family
39
39
40
40
Microsoft continues to introduce new Guest OS version incorporating the latest MSRC updates until the last day of the transition period, known as the "expiration date." On the expiration date, cloud services still running are unsupported under the Azure Service Level Agreement (SLA). Microsoft has the discretion to force upgrade, delete or stop those services after that date.
41
41
@@ -61,9 +61,9 @@ These periods may be made longer at Microsoft's discretion to ease customer tran
61
61
62
62
We recommend that you use latest Guest OS family for designing your Cloud Services.
63
63
64
-
1. Start planning your migration to a newer family early.
65
-
2. Set up temporary test deployments to test your Cloud Service running on the new family.
66
-
3. Set your Guest OS version to **Automatic** (osVersion=* in the [.cscfg](cloud-services-model-and-package.md#cscfg) file) so the migration to new Guest OS versions occurs automatically.
64
+
* Start planning your migration to a newer family early.
65
+
* Set up temporary test deployments to test your Cloud Service running on the new family.
66
+
* Set your Guest OS version to **Automatic** (osVersion=* in the [.cscfg](cloud-services-model-and-package.md#cscfg) file) so the migration to new Guest OS versions occurs automatically.
67
67
68
68
**What if my web application requires deeper integration with the OS?**
0 commit comments