Azure Patch Management applies patches & causes the vm to be manually restarted. Any suggestions?

Hi Lynne Becker,

You can use Azure Update Management to assess available updates, schedule installations, and verify deployment results, allowing you to test patches before applying them to your VMs.

You can configure instance reboots using Azure Update Management, which allows you to assess available updates, schedule installations, and review deployment results. By specifying reboot options in the update deployment, you can manage how instances are rebooted after updates are applied.

If needed, you can configure updates to install but delay reboots until a more convenient time. Additionally, the Azure Activity Log and Log Analytics can provide more details on what triggered the reboot.

You can enroll all VMs across resource groups at once using Azure Update Management, allowing you to assess updates, schedule installations, and verify deployment results. If you’re using Azure Update Manager, ensure the maintenance window is set to a time that works best for your workload.

You can utilize Azure Update Management to test patches before applying them to your VMs. This solution enables you to assess available updates, schedule necessary installations, and review deployment results to ensure updates are successfully applied to managed VMs.

If you’re running Windows Server VMs and qualify for hot patching, you can apply security updates without requiring a reboot.

For production workloads, consider using Availability Sets or Scale Sets to help ensure uptime during maintenance.

The Update Management Center (preview) provides a centralized way to manage updates and maintenance for Azure VMs and will remain available until its general release.

If the answer was helpful, please don't forget to "Accept Answer" and to click "Upvote".

If you have any further queries, please let us know we are glad to help you.

Thank You.