In previous posts we have seen how to create a vanilla image build. It’s recommended to keep your image as vanilla as possible. That means there are no unneeded applications installed in the image. The goal of this is, that when updates or patches for Microsoft Windows are needed, you rebuild the image to deploy it to Test/Acceptance and Production in a continuous delivery method.
Rebuilding the image can be done in multiple ways. If you have for example a install script for your applications, you can use the sourcetrigger in Azure. If you would like to be more in control, you can use DevOps with Bicep or Terraform.
Source Trigger
Within Azure Virtual Desktop you will be able to create a Custom Image Template. This is a ImageBuilder process with Built-in Scripts provided by Microsoft. Once created as described in a previous post Azure Image Builder you will be able to add an Automatic Image Build trigger.

This trigger can be added and can only be based on the source image. This means, when the source image (for example the Marketplace image) will be updated, then the image builder will be triggered to recreate the golden image and distribute to a newer version. The marketplace image will be updated every Patch Tuesday.
Azure DevOps
If you want to use DevOps with your ARM template or Azure Bicep, you need to setup the ConJob schedule. This can be generated with for example, Cron job every month (crontab.guru). This is a static time recurring every time you have set. The benefit is that you are more in control, the downside is that you will not have the latest updates IF you are not configuring it correctly.
IT Professional on a journey to discover the cloud platforms and become certified and an expert.
A Blog that follows the journey to get to the Cloud.
Azure Local | Azure Bicep | Azure Virtual Desktop | Powershell | Azure Certified | MCSA | Microsoft 365

