Work with Azure Desired State Configuration extension version history

Note

Before you enable Automation State Configuration, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Policy named guest configuration. The guest configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Guest configuration also includes hybrid machine support through Arc-enabled servers.

The Azure Desired State Configuration (DSC) VM extension is updated as-needed to support enhancements and new capabilities delivered by Azure, Windows Server, and the Windows Management Framework (WMF) that includes Windows PowerShell.

This article provides information about each version of the Azure DSC VM extension, what environments it supports, and comments and remarks on new features or changes.

Latest version

Version 2.83

• Release date:
  • February 2021
• OS support:
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2 SP1
  • Windows Client 7/8.1/10
  • Nano Server
• WMF support:
  • WMF 5.1
  • WMF 5.0 RTM
  • WMF 4.0 Update
  • WMF 4.0
• Environment:
  • Azure
  • Microsoft Azure operated by 21Vianet
  • Azure Government
• Remarks: This release includes a fix for unsigned binaries with the Windows VM extension.

Version 2.80

• Release date:
  • September 26, Sep-2019 (Azure) | July 6, 2020 (Microsoft Azure operated by 21Vianet) | July 20, 2020 (Azure Government)
• OS support:
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2 SP1
  • Windows Client 7/8.1/10
  • Nano Server
• WMF support:
  • WMF 5.1
  • WMF 5.0 RTM
  • WMF 4.0 Update
  • WMF 4.0
• Environment:
  • Azure
  • Microsoft Azure operated by 21Vianet
  • Azure Government
• Remarks: No new features are included in this release.

Version 2.76

• Release date:
  • May 9, 2018 (Azure) | June 21, 2018 (Microsoft Azure operated by 21Vianet, Azure Government)
• OS support:
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2 SP1
  • Windows Client 7/8.1/10
  • Nano Server
• WMF support:
  • WMF 5.1
  • WMF 5.0 RTM
  • WMF 4.0 Update
  • WMF 4.0
• Environment:
  • Azure
  • Microsoft Azure operated by 21Vianet
  • Azure Government
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Improvement in extension metadata for substatus and other minor bug fixes.

Supported versions

Warning

Versions 2.4 through 2.13 use WMF 5.0 Public Preview, whose signing certificates expired in August 2016. For more information about this issue, see the following blog article.

Version 2.75

• Release date: March 5, 2018
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Client 7/8.1/10, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:

  • After GitHub's enforcement of TLS 1.2, you can't onboard a VM to Azure Automation State Configuration using DIY Resource Manager templates available on Azure Marketplace, or use DSC extension to retrieve any configurations hosted on GitHub. An error similar to the following while deploying the extension is returned:

    {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
        "details": [{
            "code": "Conflict",
            "message": "{
                \"status\": \"Failed\",
                \"error\": {
                    \"code\": \"ResourceDeploymentFailure\",
                    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",
                    \"details\": [ {
                        \"code\": \"VMExtensionProvisioningError\",
                        \"message\": \"VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'.
                        Error message: \\\"The DSC Extension failed to execute: Error downloading
                        https://github.com/Azure/azure-quickstart-templates/raw/master/dsc-extension-azure-automation-pullserver/UpdateLCMforAAPull.zip
                        after 29 attempts: The request was aborted: Could not create SSL/TLS secure channel..\\nMore information about the failure can
                        be found in the logs located under 'C:\\\\WindowsAzure\\\\Logs\\\\Plugins\\\\Microsoft.Powershell.DSC\\\\2.74.0.0' on the VM.\\\".\"
                    } ]
                }
            }"
        }]
    }
    

  • In the new extension version, TLS 1.2 is now enforced. While deploying the extension, if you already specified AutoUpgradeMinorVersion = true in the Resource Manager template, the extension is autoupgraded to 2.75. For manual updates, specify TypeHandlerVersion = 2.75 in your Resource Manager template.

Version 2.70 - 2.72

• Release date: November 13, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Client 7/8.1/10, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Bug fixes & improvements that simplify using Azure Automation State Configuration in the portal and with a Resource Manager template. For more information, see Default Configuration Script in the DSC extension documentation.

Version 2.26

• Release date: June 9, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Client 7/8.1/10, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Telemetry improvements.

Version 2.25

• Release date: June 2, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Client 7/8.1/10, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Several bug fixes and other minor improvements were added.

Version 2.24

• Release date: April 13, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Exposes VM UUID & DSC Agent ID as extension metadata. Other minor improvements were added.

Version 2.23

• Release date: March 15, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • Bug fixes and other improvements were added.

Version 2.22

• Release date: February 8, 2017
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Nano Server
• WMF support: WMF 5.1, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.1 (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • The DSC extension now supports WMF 5.1.
  • Minor other improvements were added.

Version 2.21

• Release date: December 2, 2016
• OS support: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Nano Server
• WMF support: WMF 5.1 Preview, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot). For Nano Server, DSC role is installed on the VM.
• New features:
  • The DSC extension is now available on Nano Server. This version primarily contains code changes for running the extension on Nano Server.
  • Minor other improvements were added.

Version 2.20

• Release date: August 2, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.1 Preview, WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • Support for WMF 5.1 Preview. When first published, this version was an optional upgrade and you had to specify Wmfversion = '5.1PP' in Resource Manager templates to install WMF 5.1 preview. Wmfversion = 'latest' still installs the WMF 5.0 RTM. For more information on WMF 5.1 preview, see this blog.
  • Minor other fixes and improvements were added.

Version 2.19

• Release date: June 3, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure, Microsoft Azure operated by 21Vianet, Azure Government
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • The DSC extension is now available in Microsoft Azure operated by 21Vianet. This version contains fixes for running the extension on Microsoft Azure operated by 21Vianet.

Version 2.18

• Release date: June 3, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • Make telemetry non-blocking when an error occurs during telemetry hotfix download (known Azure DNS issue) or during install.
  • Fix for the intermittent issue where extension stops processing configuration after a reboot. This was causing the DSC extension to remain in 'transitioning' state.
  • Minor other fixes and improvements were added.

Version 2.17

• Release date: April 26, 2016

• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1

• WMF support: WMF 5.0 RTM, WMF 4.0 Update, WMF 4.0

• Environment: Azure

• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).

• New features:

  • Support for WMF 4.0 Update. For more information on WMF 4.0 Update, see this blog.
  • Retry logic on errors that occur during the DSC extension install or while applying a DSC configuration post extension install. As a part of this change, the extension will retry the installation if a previous install failed or re-enact a DSC configuration that had previously failed, for a maximum three times until it reaches the completion state (Success/Error) or if a new request comes. If the extension fails due to invalid user settings/user input, it does not retry. In this case, the extension needs to be invoked again with a new request and correct user settings.

  Note

  The DSC extension is dependent on the Azure VM agent for the retries. Azure VM agent invokes the extension with the last failed request until it reaches a success or error state.

Version 2.16

• Release date: April 21, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.0 RTM, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • Improvement in error handling and other minor bug fixes.
  • New property in DSC extension settings. ForcePullAndApply in AdvancedOptions is added to enable the DSC extension enact DSC configurations when the refresh mode is Pull (as opposed to the default Push mode). For more information about the DSC extension settings, refer to this blog.

Version 2.15

• Release date: March 14, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.0 RTM, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • In extension version 2.14, changes to install WMF RTM were included. While upgrading from extension version 2.13.2.0 to 2.14.0.0, you may notice that some DSC cmdlets fail or your configuration fails with an error - 'No Instance found with given property values'. For more information, see the DSC release notes. The workarounds for these issues have been added in 2.15 version.
  • If you already installed version 2.14 and are running into one of the above two issues, you need to perform these steps manually. In an elevated PowerShell session run the following commands:
    • Remove-Item -Path $env:SystemRoot\system32\Configuration\DSCEngineCache.mof
    • mofcomp $env:windir\system32\wbem\DscCoreConfProv.mof

Version 2.14

• Release date: February 25, 2016
• OS support: Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1
• WMF support: WMF 5.0 RTM, WMF 4.0
• Environment: Azure
• Remarks: This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSs, it installs the Windows Management Framework 5.0 RTM (installing WMF requires a reboot).
• New features:
  • Uses WMF RTM.
  • Enables data collection in order to improve the quality of the DSC extension. For more information, see this blog article.
  • Provides an updated settings format for the extension in a Resource Manager template. For more information, see this blog article.
  • Bug fixes and other enhancements.

Next steps

• For more information about PowerShell DSC, see PowerShell documentation center.
• Examine the Resource Manager template for the DSC extension.
• For other functionality and resources that you can manage with PowerShell DSC, browse the PowerShell gallery.
• For details about passing sensitive parameters into configurations, see Manage credentials securely with the DSC extension handler.