Retirement: Support for Desired State Configuration Extension for Azure Virtual Machines to Be Retired on March 31, 2028

Desired State Configuration Extension for Azure Virtual Machines will be retired on March 31, 2028, please transition to Azure Machine Configuration by that date. We encourage you to transition to Azure Machine Configuration prior to the retirement date to experience the new capabilities including: * Configurations are now assigned natively in Azure Resource Manager without the need for an Automation Account * Azure Policy provides at-scale assignment of configurations to machines * When machines drift from the desired state, you control when remediation occurs * Manage multiple configurations for the same machine * Advanced reporting through Azure Resource Graph including resource ID and state * Linux and Windows both consume PowerShell-based DSC resources From now to March 31, 2028 you can continue to use Desired State Configuration Extension for Azure Virtual Machines without disruption. After 31 March 2028 the extension will no longer be supported. Resources to aid in your migration can be found in the following sections. To verify if you’re using the Desired State Configuration Extension on Virtual Machines in the Azure Portal, open “Virtual machines”, select the name of each virtual machine, then “Settings” in the table of contents, and finally “Extensions + Applications”. There you will see a list of extensions assigned. To avoid service disruptions, please follow our instructions to [migrate](https://aka.ms/dscext2gc) to Azure Machine Configuration by March 31, 2028.