Dynamic resolution of the target machines for an update deployment. After the update deployment is created, any new machines added to Update Management that meet the search criteria will be automatically picked up without requiring the user to modify the update deployment itself.

As an example, the following group target for the update deployment will select all onboarded VMs in the selected resource groups that have the tag PatchWindow=SundayNight. This deployment can be set to run weekly. When additional onboarded VMs are tagged with PatchWindow=SundayNight, they will automatically be picked up and updated in the next deployment run.

Update inclusion

You can now specify inclusion lists for updates. When you use inclusion lists, you can whitelist updates so you can control exactly what updates are applied during a deployment run. This can be useful if you want to ensure that only patches you have approved are rolled out to your service.

Products

Related feedback

Update deployments needs to be dynamic. As of now if we target a group of 5 servers the deployment is static and will always target only these 5 servers, even if the group changes and have 100 servers in it. The update deployment should be able to evaluate the group membership at each runtime.

In our environment all large amount of vm's is not started all the time. But need to be up to date. I could create runbooks to start the vm just before the scheduled update and deallocate at the end. But controlling this from the schedule itself could be helpfull.