# Cloud Patch Management: AWS and Azure VMs

Canonical: https://patchmanagementpolicy.com/patching/cloud-virtual-machines/
Last reviewed: 19 Nov 2026

## Cloud patch management

Cloud virtual machines are patched by the customer unless a managed service does it. AWS Patch Manager runs by patch policy, maintenance window or on-demand Patch now, and Azure Update Manager uses maintenance configurations, up to 250 schedules per subscription per region. Read 19 Nov 2026.

### Who patches what

NIST lists “the party who administrates the asset (for example IT department, third party, end user, vendor/manufacturer, shared responsibility model)” among the fields to inventory, and names moving to SaaS, where the provider patches, as a way to transfer risk ([NIST SP 800-40 Rev. 4](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)). For virtual machines the guest operating system is the customer's. The cloud provider's host maintenance is a separate matter and outside this page.

Guest operating system windows come from the [Windows](https://patchmanagementpolicy.com/patching/windows-endpoints/) and [Linux](https://patchmanagementpolicy.com/patching/linux-servers/) pages, and the process steps are in the [overview](https://patchmanagementpolicy.com/process/).

### Two orchestration models compared

| Feature | AWS Systems Manager Patch Manager | Azure Update Manager |
|---|---|---|
| How patching is scheduled | Patch policy in Quick Setup (single policy across accounts and Regions with AWS Organizations), maintenance window, or on-demand Patch now | Maintenance configurations: recurring schedules, daily, weekly or hourly |
| What decides the patches | Patch baselines, predefined or custom; default Windows Server and many Linux baselines wait 7 days | Update classifications chosen in the schedule |
| Status vocabulary | INSTALLED, INSTALLED_PENDING_REBOOT, MISSING, FAILED and others | Per-machine results in the service |
| Documented limit worth planning around | Windows Server default baselines include a 7-day auto-approval delay; a custom baseline is needed to install sooner | 250 schedules per subscription per region; 3,000 resource associations per schedule |
| Hooks | Maintenance window tasks | Pre-events and post-events; a failed pre-event must be cancelled by you or the run proceeds |

Sources: AWS Systems Manager User Guide and Microsoft Learn, read 19 Nov 2026. Vendor descriptions of their own services.

Azure also states that VMs created from a supported Windows Server image have Automatic VM Guest Patching enabled by default, which means a policy must say whether that behavior is acceptable or turned off in favor of a customer-managed schedule. Machines in the same Azure availability set that patch in overlapping schedules may be skipped or fail if the window overruns; split them or lengthen the window.

### Testing, rollback and evidence

Use tags or groups to run a canary group first, and take a snapshot or image before the install. The sources read here document the baselines and schedules, not rollback; the [deploy step](https://patchmanagementpolicy.com/process/deploy/) covers what to record. Evidence for an auditor: the baseline or configuration identifier and its date, the compliance report showing installed and missing patches, and the list of nodes with patches installed but not restarted (AWS counts that as compliant, so report it separately; see [verify](https://patchmanagementpolicy.com/process/verify/)).

### Questions

**automated patch management aws**

In AWS, automated patching is done by Systems Manager Patch Manager. A patch baseline decides which patches are approved, and a patch policy in Quick Setup, a maintenance window or a Patch now operation applies them. Default Windows Server baselines wait 7 days after release before approving.

**aws patch management policy**

An AWS patch management policy can be written as a Patch Manager patch policy: one Quick Setup configuration that defines schedules and baselines for an AWS Organizations scope. The written policy should also state which baseline is used and who owns exceptions.

### Sources

- [AWS Systems Manager Patch Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager.html), read 19 Nov 2026
- [AWS Systems Manager, predefined and custom patch baselines](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-predefined-and-custom-patch-baselines.html), read 19 Nov 2026
- [AWS Systems Manager, patch compliance states](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-compliance-states.html), read 19 Nov 2026
- [Microsoft Learn, Azure Update Manager scheduled patching](https://learn.microsoft.com/en-us/azure/update-manager/scheduled-patching), read 19 Nov 2026
- [Microsoft Learn, Hotpatch for Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/hotpatch), read 19 Nov 2026
- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Step 6: Patch Deployment Process and Rollback](https://patchmanagementpolicy.com/process/deploy/)
- [Step 7: How to Verify Patches Are Installed](https://patchmanagementpolicy.com/process/verify/)
- [Windows Patch Management Policy: Windows Rhythm](https://patchmanagementpolicy.com/patching/windows-endpoints/)
- [Linux Patch Management Policy by Distribution](https://patchmanagementpolicy.com/patching/linux-servers/)
