Azure Policy capability that checks or enforces settings at the OS level on Azure VMs and Arc-enabled machines; it replaces Automation State Configuration and the DSC extension.
Also called guest configuration, Azure Automanage Machine Configuration, Guest configuration.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Machine Configuration in context, with comparison tables and the common traps.
Terms in this definition
- Azure Policy
Azure service that audits and enforces how resources are configured, for example their location, SKU or tags, using definitions and assignments. It neither deploys resources nor controls access.
- Capability
Something that a person, organisation or system is able to do.
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- State
A parameter in OAuth that carries custom data through the authorisation flow and back, as with the "Support state parameter" option in APIM.
- Desired State Configuration VM extension
An extension for Azure virtual machines that pushes PowerShell DSC configurations to them. It is due to be retired on 31 March 2028, with Azure Machine Configuration as its successor.
Related terms
- Apply and Monitor
An assignment mode in Azure Machine Configuration that applies settings a single time and afterwards just reports drift. Audit only reports, while Apply and Autocorrect fixes drift too.
- Guest Configuration Resource Contributor
Assigning Azure Machine Configuration policies, which manage settings inside machines, requires the permissions in this built-in role.
- Machine configuration enforcement modes
Azure Machine Configuration offers three ways to assign: Audit only, which just reports; ApplyAndMonitor, applying settings once then flagging drift; and ApplyAndAutoCorrect, fixing drift when it is next evaluated.
- Pull server
The source a DSC node fetches configurations from when its LCM is set to pull. Azure Automation State Configuration provides one that also reports compliance; that service retires on 30 September 2027, to be replaced by Azure Machine Configuration.