# Step 5: Patch Approval Process and Scheduling

Canonical: https://patchmanagementpolicy.com/process/approve-and-schedule/
Last reviewed: 19 Nov 2026

## Patch approval process

A patch approval process turns a tested patch into an approved change with a window. NIST SP 800-40 Rev. 4 says routine patches need not install at once but must be forced after a grace period, directly or by blocking network access for unpatched assets. Read 19 Nov 2026.

### What approval decides

Approval fixes three things: which maintenance group gets the patch, when the window opens and closes, and the date after which installation is forced. NIST notes that many organizations schedule deployments “as part of their enterprise change management activities,” and that a routine patch “does not necessitate immediate installation, but at some point, patches must be installed.” Forcing can be direct (trigger the install) or indirect, such as preventing network access for unpatched assets ([NIST SP 800-40 Rev. 4, sections 2.3.1 and 3.5.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)). The approver should see the [test evidence](https://patchmanagementpolicy.com/process/acquire-and-test/) and the asset's outage limits from the [inventory](https://patchmanagementpolicy.com/process/inventory/).

### Scheduling controls and what each one actually enforces

| Platform | Control | Detail to write into the procedure |
|---|---|---|
| Intune, iOS/iPadOS and macOS | Declarative software update policy: “Enforce Latest” | A delay in days before the deadline, counted from Apple's release or from when the policy is set, plus an install time on a 24-hour clock; the delay sets the enforcement date, not when the update is offered |
| Intune, Windows | Update rings | Deferral, restart and deadline settings per ring; pause up to 35 days |
| Azure Update Manager | Maintenance configurations | Recurring schedules at daily, weekly or hourly cadence; machines in one availability set patched in overlapping schedules may fail or be skipped, so split them across schedules or lengthen the window |
| Azure Update Manager | Pre-events and post-events | A pre-event can turn machines on before patching; cancelling a run after a failed pre-event must be started by you, or the run goes ahead in the window |
| AWS Systems Manager | Maintenance window running a Scan or Install task, or a patch policy | The patch baseline decides what is approved; the window decides when |

Sources: Microsoft Learn and AWS documentation, read 19 Nov 2026.

The Azure point about reboots matters for the window length: the registry keys that manage restart “can cause your machines to reboot” even if the schedule says Never Reboot.

### Windows where only the asset's own constraints apply

Some assets cannot take a general window. NIST's inventory examples include an asset that can be rebooted only during a monthly maintenance outage, and for operational technology SP 800-82 Rev. 3 says patching “should be deployed during planned OT outages.” Write those windows into the maintenance group, not into the exception list. The wording of a window clause is on [maintenance windows](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/).

### The record to keep

- The change record: patch identifiers, groups, window, approver, rollback plan.
- The forced-install date and the mechanism chosen for it.
- Any approval refused or deferred, with the reason and the new date.

### Sources

- [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
- [Microsoft Learn, Intune Apple software update policies](https://learn.microsoft.com/en-us/mem/intune/protect/software-updates-ios), 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, Azure Update Manager pre and post events](https://learn.microsoft.com/en-us/azure/update-manager/pre-post-scripts-overview), read 19 Nov 2026
- [Microsoft Learn, Intune Windows update rings](https://learn.microsoft.com/en-us/mem/intune/protect/windows-10-update-rings), read 19 Nov 2026
- [AWS Systems Manager Patch Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager.html), read 19 Nov 2026
- [NIST SP 800-82 Rev. 3](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-82r3.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Management Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/)
- [Step 6: Patch Deployment Process and Rollback](https://patchmanagementpolicy.com/process/deploy/)
- [Patch Maintenance Window Policy Clause](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/)
- [Step 4: Patch Testing Process with Canary Rings](https://patchmanagementpolicy.com/process/acquire-and-test/)
