Azure Update Manager series — Deploy Maintenance Configuration through Bicep
Have you shifted your Azure Virtual Machines or Azure Arc Managed Machines to Azure Update Manager to get those Windows Updates?
Since the General Availability of Azure Update Manager, many folks are moving their workloads to be managed from a more “global” solution, instead of the old Update Management in an Azure Automation Account.
The reason is pretty obvious. If you haven’t caught on yet, the Log Analytics Agent, which keeps track of your Windows Updates progress, will be phased out in August.
While Azure Update Manager itself is a global solution across Azure, the magic settings occur at the Subscription and Resource Group level.
In this first part of this series on Azure Update Manager, we’ll be exploring how you can create Maintenance Configurations and dynamic assignments using Bicep. We’ll be using Azure Verified Modules (AVM) to accelerate our development of Bicep code.
Lastly, we’ll also have a look at how you can make direct assignments using Azure PowerShell.
