4.2.4. Delivery Optimization and Update Monitoring
💡 First Principle: Imagine 500 laptops in one office each downloading the same 4 GB update: the internet link carries 2,000 GB of identical bytes. Delivery Optimization lets devices share pieces of content with nearby peers, or pull from a local cache, so the link carries something closer to one copy. Once updates are flowing, monitoring answers the next question — which devices stalled, and why — and the answer is usually a policy conflict, a safeguard hold or reporting that was never switched on.
Configuring Delivery Optimization. The original Intune Delivery Optimization template was deprecated on April 24, 2025, so new profiles use the Settings Catalog. The most important choice is the download mode:
| Mode | Value | Behavior | When to choose it |
|---|---|---|---|
| HTTP only | 0 | No peer-to-peer; still uses Delivery Optimization cloud services and can use Microsoft Connected Cache | You want to disable peering |
| LAN | 1 | Peers behind the same NAT (public IP); on Windows 11, restricted to the local subnet by default | The Windows default |
| Group | 2 | Peers across internal subnets among devices in the same group (AD site, domain or custom group ID) | Microsoft's recommended option for most organizations |
| Internet | 3 | Also peers with internet devices | Rarely in managed fleets |
| Simple | 99 | No Delivery Optimization cloud services at all | Offline or isolated environments |
| Bypass | 100 | Uses BITS instead | Don't — deprecated starting in Windows 11 and can cause downloads to fail |
Group mode groups peers by a Group ID source: AD site, authenticated domain SID, a DHCP option, DNS suffix or the Microsoft Entra tenant ID. A custom group ID (a GUID) lets you peer across branches on different domains or LANs. Restrict Peer Selection works only in modes 1 and 2. By default, devices don't peer over VPN and don't upload while on battery, and if you don't configure a cache size, Delivery Optimization uses 20% of free disk space.
Bandwidth throttling has moved too: the old maximum download and upload bandwidth settings are deprecated in favor of DO Max Foreground/Background Download Bandwidth in the Settings Catalog, including a "percent with business hours" option. For a local cache, Cache server host names points devices at a Microsoft Connected Cache server; one running on a Configuration Manager distribution point can serve cloud-managed devices. Watch for one cross-domain interaction: a security baseline that configures LocalPolicyMerge can stop devices from retrieving the cache server's DHCP option, especially during Autopilot, and baseline firewall defaults are another reason to validate Delivery Optimization before you assign a baseline.
Turning on update reporting. Many Windows update reports depend on a tenant setting that is off by default: Tenant administration > Connectors and tokens > Windows data > Enable features that require Windows diagnostic data in processor configuration. It powers compatibility reports, expedite reports, and feature, driver and expedited update failure alerts. The same page has a license attestation toggle, required for compatibility reports (and for Remediations, covered in Phase 6).
What to monitor, and where.
- Update rings: per-policy device and user check-in status, assignment status and per-setting status.
- Feature updates: the Windows feature updates organizational report (Reports > Windows Updates) and Feature update failures (Devices > Monitor). Service-side data arrives within an hour; client-side data refreshes about every eight hours.
- Upgrade readiness: the Windows Feature Update Device Readiness and Compatibility Risks reports flag risky apps and drivers, devices that must be replaced and safeguard holds. Their data can be up to about 52 hours old.
- Autopatch: Reports > Windows Autopatch > Windows feature updates summarizes feature update status across Intune devices.
- Expedite and hotpatch: the Windows Expedited Update Report and the Hotpatch quality update report.
Feature update alerts tell you why a device is stuck. DeploymentConflict means the device is in more than one deployment of the same type and only the first applies. PolicyConflictDeferral and PolicyConflictPause mean a client-side deferral or pause is blocking the install — often a ring that wasn't set to 0 deferral beside a feature update policy. SafeguardHold means Microsoft is holding the update for a known compatibility issue, and DeviceRegistrationInvalidGlobalDeviceId points to a disabled Microsoft Account Sign-In Assistant service.
⚠️ Exam Trap: If compatibility reports, expedite reports or update failure alerts are empty while policies are clearly assigned, look first at the tenant's Windows diagnostic data setting. It's off by default, and without it those reports have nothing to show — no change to the update policies will fix that.
Reflection Question: Branch offices with several subnets in the same AD site report heavy WAN traffic during Patch Tuesday, even though Delivery Optimization is left at its Windows default. Which download mode would you choose, and why does the default limit peering on Windows 11?