4.2. Manage Device Updates
💡 First Principle: Patching is a race: Microsoft publishes a fix, attackers study it, and every device that hasn't installed it is exposed. Update management balances speed against breakage by sending updates to a small group first and widening once it's safe. Intune splits the job in two: rules on the device decide when it installs and restarts, and approvals in the cloud decide which update it gets.
Why care? An unpatched device is the cheapest breach an attacker can find, and the update policy types look alike, so the exam tests picking the right one.
Think of one controller per platform, plus one transport:
| Platform | Timing and enforcement | Content approval | Configured in |
|---|---|---|---|
| Windows | Update rings (Windows Update client policies) | Feature, quality and driver update policies, orchestrated by Windows Autopatch | Devices > Manage updates > Windows updates |
| iOS/iPadOS, macOS | Declarative Device Management (DDM) software update settings | Apple publishes; you target or enforce a version | Settings Catalog |
| Android Enterprise | System update setting and freeze periods | Google and the OEM publish; FOTA can target firmware | Device restrictions; FOTA connectors |
| Transport (Windows) | Delivery Optimization | — | Settings Catalog |
⚠️ Common Misconception: Because hotpatch launched as an opt-in setting in quality update policies, many people believe it's off by default and must be enabled device by device. In 2026 Microsoft inverted that: Windows Autopatch enables hotpatch security updates by default for all eligible Intune devices — Windows 11 24H2 or later, with virtualization-based security (VBS) running and an eligible license. Administrators now opt out, for the whole tenant or for groups through a quality update policy.