Forum Discussion
Azure ARM template vs Desired state configuration
I'm studying for az104, I need some clarity on this; So if we can already Make deployments streamlined and consistent using arm templates (or bicep files); what would be the purpose of using Azure automation state configuration/PowerShell desired state configuration?
Is it specifically for servers?
is it to automate configuration post deployment of a VM?
If we used a custom image with the desired configuration already in place, would we still need to use PowerShell DSC?
1 Reply
- It's not really one-or-the-other type of deal, even though it might seem like that on the surface. In short the main difference comes from resource provisioning versus desired state management. While you could use a custom image to set things up, there's a chance that later down the road you'll experience some configuration drift for a multitude of reasons, and this is where the dynamic nature of AASC and DSC would come in play.
For more info you can refer to https://learn.microsoft.com/en-us/azure/automation/automation-dsc-overview
