4.2.1. Update Rings, Feature Updates, and Quality Updates
💡 First Principle: Every Windows update raises two separate questions: when may this device install and restart, and which update should it get? Update rings answer the first, on the device. Feature, quality and driver update policies answer the second, in the cloud. Most wrong answers on the exam use a tool built for one question to answer the other.
How the pieces fit. Intune stores only the policy assignments. It sends the content policies to Windows Autopatch, which decides which updates are approved, and devices download approved content directly from Windows Update.
Update rings control client behavior: deferrals, deadlines, restarts, active hours and notifications. They need only Intune Plan 1 — no Autopatch entitlement — and Microsoft Entra registered devices are limited to rings and other Windows Update client policies. Create them at Devices > By platform > Windows > Manage updates > Windows updates > Update rings tab > Create profile, and assign to device groups so no user sign-in is needed. The ranges are classic exam material:
| Ring setting | Range | Note |
|---|---|---|
| Quality update deferral period | 0–30 days | Delays when monthly updates are offered |
| Feature update deferral period | 0–365 days | Counts from Microsoft's release of the update |
| Feature update uninstall period | 2–60 days | After it expires, rollback files are removed |
| Deadline for feature updates | 2–30 days | Requires Use deadline settings = Allow |
| Deadline for quality updates | 2–30 days | Counts from when the device's scan first discovered the update |
| Grace period | 0–7 days | Extra time before a forced restart |
| Pause (feature or quality, separately) | Up to 35 days | Expires automatically; Extend resets to 35 |
Work through two examples. If the feature update uninstall period is 20 days, a device that installed the update 25 days ago can no longer roll back, because the rollback files were removed on day 20. If a ring defers quality updates 7 days with a 3-day quality deadline, a security update released on day 0 is offered on day 7 and must be installed by about day 10.
Ring actions follow the same logic. Pause stops feature or quality updates for up to 35 days; Uninstall rolls back the latest update immediately and pauses that update type; Delete stops enforcement but leaves the device's current settings in place. For devices Windows Autopatch manages, Microsoft says not to assign your own custom rings, because the service maintains its own.
Feature update policies lock devices to a specific Windows release, or target an upgrade to one, and stop devices moving beyond it. Restart behavior still comes from the ring. When you use both, set the ring's feature update deferral to 0 and don't pause feature updates in the ring. Feature update policies don't apply during Autopilot's out-of-box experience; they take effect at the first Windows Update scan after provisioning.
Quality update policies are optional — rings alone deliver monthly updates — but you need one for cloud-based approval, hotpatch control or policy-based reporting. For each update type (monthly security, monthly non-security preview, out-of-band security and out-of-band non-security) you choose automatic or manual approval. Monthly security defaults to automatic and the rest to manual, and the approval method can't be edited later. Automatic approval uses Make updates available after (0–30 days). The key interaction: the quality update policy's deferral overrides the ring's deferral, while the ring's deadline and grace period still apply. In the earlier example, adding a quality update policy with a 2-day deferral would make the update available on day 2, with the 3-day deadline landing around day 5. Quality update policies also cover supported .NET Framework updates.
Expedite installs one specific security update as soon as possible, bypassing deferrals without changing your monthly policies, with a forced restart after 0, 1 or 2 days if needed. Driver update policies approve drivers and firmware automatically or manually; switching modes loses existing approvals.
Licensing and device requirements. Feature, quality and driver update policies are all orchestrated by Windows Autopatch. They require a Windows license that includes the Windows Autopatch entitlement (for example Microsoft 365 Business Premium, Windows Enterprise E3 or E5 including through Microsoft 365 F3, E3 or E5, or Education A3 or A5), Pro, Enterprise or Education editions (not LTSC), devices that are Entra joined or hybrid joined, diagnostic data at Required and the Microsoft Account Sign-In Assistant service running.
⚠️ Exam Trap: A long feature update deferral looks like it holds devices on their current Windows version, but update ring deferrals only delay when an update is offered — they can't pin a version. Locking devices to a release, or targeting an upgrade to a specific one, is the job of a feature update policy, which requires a Windows license with the Autopatch entitlement and doesn't support Entra registered devices.
Reflection Question: A company's ring defers quality updates by 7 days with a 3-day deadline. It adds a quality update policy with automatic approval and Make updates available after set to 1 day. When do devices get next month's security update, and which settings decide the deadline?