Azure Guest OS releases and SDK compatibility matrix

Provides you with up-to-date information about the latest Azure Guest OS releases for Cloud Services. This information helps you plan your upgrade path before a Guest OS is disabled. If you configure your roles to use automatic Guest OS updates as described in Azure Guest OS Update Settings, it is not vital that you read this page.

Important

This page applies to Cloud Services web and worker roles, which run on top of a Guest OS. It does not apply to IaaS Virtual Machines.

Note

The RSS Feed was recently deprecated. Watch for updates on a new feed coming soon!

Unsure about what the Guest OS is or how the Guest OS releases work? Read this section.

News updates

August 3, 2017

July Guest OS has released.

July 19, 2017

July Guest OS rollout is starting July 19 and has a projected release of August 8.

July 7, 2017

June Guest OS has released.

June 16, 2017

June Guest OS rollout is starting June 16 and has a projected release of July 11.

June 5, 2017

May Guest OS has released.

May 17, 2017

Due to a security bug, we are disabling the following December 2016 and January 2017 OS Releases that do not have the fix from the portal: WA-GUEST-OS-5.4_201612-01, WA-GUEST-OS-4.39_201612-01, WA-GUEST-OS-3.46_201612-01, WA-GUEST-OS-2.59_201701-01

May 12, 2017

May Guest OS rollout is starting May 12 and has a projected release of June 13.

April 18, 2017

April Guest OS rollout is starting April 18 and has a projected release of May 9.

April 10, 2017

March Guest OS rollout started March 14, 2017, and released on April 10, 2017.

January 10, 2017

The January Guest OS contains patches that only impact OS family 2 (Windows 2008 Server R2). We have therefore released only the OS Family 2 image (WA-GUEST-OS-2.59_201701-01) for this month. For all other OS families, the December OS (201612-01) remains the latest.

Releases

Family 5 releases

Windows Server, 2016

.NET Framework Installed: 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2

Note

Dates with a * are subject to change.

The RDP Password for OS Family 5 must be a minimum of 10 characters.

Configuration String Release date Disable date Expired date
WA-GUEST-OS-5.9_201707-01 August 3, 2017 Post 5.11 TBD
WA-GUEST-OS-5.8_201706-01 July 7, 2017 Post 5.10 TBD
WA-GUEST-OS-5.7_201705-01 June 5, 2017 Post 5.9 TBD
WA-GUEST-OS-5.6_201704-01 May 9, 2017 August 3, 2017 TBD
WA-GUEST-OS-5.5_201703-01 April 10, 2017 July 7, 2017 TBD
WA-GUEST-OS-5.4_201612-01 January 10, 2017 June 5, 2017 TBD
WA-GUEST-OS-5.3_201611-01 December 14, 2016 May 9, 2017 TBD
WA-GUEST-OS-5.2_201610-02 November 1, 2016 April 10, 2017 TBD

Family 4 releases

Windows Server 2012 R2

Supports .NET 4.0, 4.5, 4.5.1, 4.5.2

Note

Dates with a * are subject to change

Configuration String Release date Disable date Expired date
WA-GUEST-OS-4.44_201707-01 August 3, 2017 Post 4.46 TBD
WA-GUEST-OS-4.43_201706-01 July 7, 2017 Post 4.45 TBD
WA-GUEST-OS-4.42_201705-01 June 5, 2017 Post 4.44 TBD
WA-GUEST-OS-4.41_201704-01 May 9, 2017 August 3, 2017 TBD
WA-GUEST-OS-4.40_201703-01 April 10, 2017 July 7, 2017 TBD
WA-GUEST-OS-4.39_201612-01 January 10, 2017 June 5, 2017 TBD
WA-GUEST-OS-4.38_201611-01 December 14, 2016 May 9, 2017 TBD
WA-GUEST-OS-4.37_201610-02 November 16, 2016 April 10, 2017 TBD
WA-GUEST-OS-4.36_201609-01 October 13, 2016 January 14, 2017 TBD
WA-GUEST-OS-4.35_201608-01 September 13, 2016 December 16, 2016 TBD
WA-GUEST-OS-4.34_201607-01 August 8, 2016 November 13, 2016 TBD

Family 3 releases

Windows Server 2012

Supports .NET 4.0, 4.5, 4.5.1, 4.5.2

Note

Dates with a * are subject to change

Configuration String Release date Disable date Expired date
WA-GUEST-OS-3.51_201707-01 August 3, 2017 Post 3.53 TBD
WA-GUEST-OS-3.50_201706-01 July 7, 2017 Post 3.52 TBD
WA-GUEST-OS-3.49_201705-01 June 5, 2017 Post 3.51 TBD
WA-GUEST-OS-3.48_201704-01 May 9, 2017 August 3, 2017 TBD
WA-GUEST-OS-3.47_201703-01 April 10, 2017 July 7, 2017 TBD
WA-GUEST-OS-3.46_201612-01 January 10, 2017 June 5, 2017 TBD
WA-GUEST-OS-3.45_201611-01 December 14, 2016 May 9, 2017 TBD
WA-GUEST-OS-3.44_201610-02 November 16, 2016 May 1, 2017 TBD
WA-GUEST-OS-3.43_201609-01 October 13, 2016 January 14, 2017 TBD
WA-GUEST-OS-3.42_201608-01 September 13, 2016 December 16, 2016 TBD
WA-GUEST-OS-3.41_201607-01 August 8, 2016 November 13, 2016 TBD

Family 2 releases

Windows Server 2008 R2 SP1

Supports .NET 3.5, 4.0, 4.5, 4.5.1, 4.5.2

Note

Dates with a * are subject to change

Configuration String Release date Disable date Expired date
WA-GUEST-OS-2.64_201707-01 August 3, 2017 Post 2.66 TBD
WA-GUEST-OS-2.63_201706-01 July 7, 2017 Post 2.65 TBD
WA-GUEST-OS-2.62_201705-01 June 5, 2017 Post 2.64 TBD
WA-GUEST-OS-2.61_201704-01 May 9, 2017 August 3, 2017 TBD
WA-GUEST-OS-2.60_201703-01 April 10, 2017 July 7, 2017 TBD
WA-GUEST-OS-2.59_201701-01 January 10, 2017 June 5, 2017 TBD
WA-GUEST-OS-2.58_201612-01 January 10, 2017 May 9, 2017 TBD
WA-GUEST-OS-2.57_201611-01 December 14, 2016 April 10, 2017 TBD
WA-GUEST-OS-2.56_201610-02 November 16, 2016 February 10, 2017 TBD
WA-GUEST-OS-2.55_201609-01 October 13, 2016 January 14, 2017 TBD
WA-GUEST-OS-2.54_201608-01 September 13, 2016 December 16, 2016 TBD
WA-GUEST-OS-2.53_201607-01 August 8, 2016 November 13, 2016 TBD

MSRC patch updates

The list of patches that are included with each monthly Guest OS release is available here.

SDK support

Even though the retirement policy for the Azure SDK indicates that only versions above 2.2 are supported, specific Guest OS families allow you to use earlier versions. You should always use the latest supported SDK.

Guest OS Family Compatible SDK Versions
5 Version 2.9.5.1+
4 Version 2.1+
3 Version 1.8+
2 Version 1.3+
1 Version 1.0+

Guest OS Release Information

There are three dates that are important to Guest OS releases: release date, disabled date, and expiration date. A Guest OS is considered available when it is in the Portal and can be selected as the target Guest OS. When a Guest OS reaches the disabled date, it is removed from Azure. However, any Cloud Service targeting that Guest OS will still operate as normal.

The window between the disabled date and the expiration date provides you with a buffer to easily transition from one Guest OS to one newer. If you're using automatic as your Guest OS, you'll always be on the latest version and you don't have to worry about it expiring.

When the expiration date passes, any Cloud Service still using that Guest OS will be stopped, deleted, or forced to upgrade. You can read more about the retirement policy here.

Guest OS Family-Version Explanation

The Guest OS families are based on released versions of Microsoft Windows Server. The Guest OS is the underlying operating system that Azure Cloud Services runs on. Each Guest OS has a family, version, and release number.

  • Guest OS family
    A Windows Server operating system release that a Guest OS is based on. For example, family 3 is based on Windows Server 2012.
  • Guest OS version
    Specific to a Guest OS family image plus relevant Microsoft Security Response Center (MSRC) patches that are available at the date the new Guest OS version is produced. Not all patches may be included.

    Numbers start at 0 and increment by 1 each time a new set of updates is added. Trailing zeros are only shown if important. That is, version 2.10 is a different, much later version than version 2.1.

  • Guest OS release
    A rerelease of a Guest OS version. A rerelease occurs if Microsoft finds issues during testing; requiring changes. The latest release always supersedes any previous releases, public or not. The Azure portal will only allow users to pick the latest release for a given version. Deployments running on a previous release are usually not force upgraded depending on the severity of the bug.

In the example below, 2 is the family, 12 is the version and "rel2" is the release.

Guest OS release - 2.12 rel2

Configuration string for this release - WA-GUEST-OS-2.12_201208-02

The configuration string for a Guest OS has this same information embedded in it, along with a date showing which MSRC patches were considered for that release. In this example, MSRC patches produced for Windows Server 2008 R2 up to and including August 2012 were considered for inclusion. Only patches specifically applying to that version of Windows Server are included. For example, if an MSRC patch applies to Microsoft Office, it will not be included because that product is not part of the Windows Server base image.

Guest OS System Update Process

This page includes information on upcoming Guest OS Releases. Customers have indicated that they want to know when a release occurs because their cloud service roles will reboot if they are set to "Automatic" update. Guest OS releases typically occur at least five (5) days after the MSRC update release that occurs on the second Tuesday of every month. New releases include all the relevant MSRC patches for each Guest OS family.

Microsoft Azure is constantly releasing updates. The Guest OS is only one such update in the pipeline. A release can be affected by many factors too numerous to list here. In addition, Azure runs on literally hundreds of thousands of machines. This means that it's impossible to give an exact date and time when your role(s) will reboot. We are working on a plan to limit or time reboots.

When a new release of the Guest OS is published, it can take time to fully propagate across Azure. As services are updated to the new Guest OS, they are rebooted honoring update domains. Services set to use "Automatic" updates will get a release first. After the update, you’ll see the new Guest OS version listed for your service in the Azure portal. Rereleases may occur during this period. Some versions may be deployed over longer periods of time and automatic upgrade reboots may not occur for many weeks after the official release date. Once a Guest OS is available, you can then explicitly choose that version from the portal or in your configuration file.

For a great deal of valuable information on restarts and pointers to more information technical details of Guest and Host OS updates, see the MSDN blog post titled Role Instance Restarts Due to OS Upgrades.

If you manually update your Guest OS, see the Guest OS retirement policy for additional information.

Guest OS Supportability and Retirement Policy

The Guest OS supportability and retirement policy is explained here.