| title | description | services | ms.service | ms.subservice | ms.topic | ms.date |
|---|---|---|---|---|---|---|
Remediate noncompliant Azure Automation State Configuration servers |
This article tells how to reapply configurations on demand to servers where configuration state has drifted. |
automation |
automation |
dsc |
conceptual |
07/17/2019 |
When servers are registered with Azure Automation State Configuration,
the configuration mode is set to ApplyOnly, ApplyAndMonitor, or ApplyAndAutoCorrect. If the mode isn't set to ApplyAndAutoCorrect,
servers that drift from a compliant state for any reason
remain noncompliant until they're manually corrected.
Azure compute offers a feature named Run Command that allows customers to run scripts inside virtual machines. This document provides example scripts for this feature when manually correcting configuration drift.
You can correct drift of Windows virtual machines using the Run command feature. See Run PowerShell scripts in your Windows VM with Run command.
To force an Azure Automation State Configuration node to download the latest configuration and apply it, use the Update-DscConfiguration cmdlet.
Update-DscConfiguration -Wait -VerboseFor Linux virtual machines, you don't have the option of using the Run command. You can only correct drift for these machines by repeating the registration process.
For Azure nodes, you can correct drift from the Azure portal or using Az module cmdlets. Details about this process are documented in Enable a VM using Azure portal.
For hybrid nodes, you can correct drift using the Python scripts. See Performing DSC operations from the Linux computer.
- For a PowerShell cmdlet reference, see Az.Automation.
- To see an example of using Azure Automation State Configuration in a continuous deployment pipeline, see Set up continuous deployment with Chocolatey.