Lesson247 words

Choosing a configuration management technology

Recommend a configuration management technology

Choose by the capability and lifecycle you need, not by an impermeable resource-versus-guest boundary.

NeedTechnology
Declare Azure resource topologyARM templates, Bicep, or Terraform
Continuously audit or remediate OS/application state across Azure and Arc-enabled machinesAzure Machine Configuration
Run a one-time guest action on an Azure VMDeploy a VM extension with ARM/Bicep and an idempotent script
Externalize runtime application settingsAzure App Configuration
Share pipeline values or secrets across pipelinesAzure Pipelines variable groups

Declarative versus imperative

Microsoft documents Bicep files as idempotent: deploying the same file repeatedly yields the same resource types in the same state. That property does not automatically make an imperative script embedded in a resource declaration idempotent. A Custom Script Extension script must be authored so a retry is safe.

The direction of travel

Azure Automation State Configuration retires 30 September 2027. Migrate to Azure Machine Configuration, which combines features of the DSC Extension and Automation State Configuration and adds hybrid support through Arc-enabled servers.

Azure Automation DSC for Linux has already retired — 30 September 2023.

So when a scenario asks for in-guest configuration across Azure and on-premises machines today, the answer is Machine Configuration with Arc, not Automation State Configuration.

Primary sources

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free