What is Delivery Optimization?

Applies to

  • Windows 10
  • Windows 11

Looking for Group Policy objects? See Delivery Optimization reference or the master spreadsheet available at the Download Center.

Windows updates, upgrades, and applications can contain packages with large files. Downloading and distributing updates can consume quite a bit of network resources on the devices receiving them. You can use Delivery Optimization to reduce bandwidth consumption by sharing the work of downloading these packages among multiple devices in your deployment. Delivery Optimization is a cloud-managed solution that allows clients to download those packages from alternate sources (such as other peers on the network) in addition to the traditional Internet-based servers. You can use Delivery Optimization with Windows Update, Windows Server Update Services (WSUS), Windows Update for Business, or Microsoft Endpoint Manager (when installation of Express Updates is enabled).

Access to the Delivery Optimization cloud services and the Internet, are both requirements for using the peer-to-peer functionality of Delivery Optimization.

For information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see Set up Delivery Optimization. For a comprehensive list of all Delivery Optimization settings, see Delivery Optimization reference.

Note

WSUS can also use BranchCache for content sharing and caching. If Delivery Optimization is enabled on devices that use BranchCache, Delivery Optimization will be used instead.

Requirements

The following table lists the minimum Windows 10 version that supports Delivery Optimization:

Device type Minimum Windows version
Computers running Windows 10 Windows 10 1511
Computers running Server Core installations of Windows Server Windows Server 2019
Windows IoT devices Windows 10 1803

Types of download content supported by Delivery Optimization

Windows Client

Windows Client Minimum Windows version HTTP Downloader Peer to Peer Microsoft Connected Cache (MCC)
Windows Update (feature updates quality updates, language packs, drivers) Windows 10 1511, Windows 11 ✔️ ✔️ ✔️
Windows 10 Store files Windows 10 1511, Windows 11 ✔️ ✔️ ✔️
Windows 10 Store for Business files Windows 10 1511, Windows 11 ✔️ ✔️ ✔️
Windows Defender definition updates Windows 10 1511, Windows 11 ✔️ ✔️ ✔️
Intune Win32 apps Windows 10 1709, Windows 11 ✔️ ✔️ ✔️
Microsoft 365 Apps and updates Windows 10 1709, Windows 11 ✔️ ✔️ ✔️
Edge Browser Updates Windows 10 1809, Windows 11 ✔️ ✔️ ✔️
Configuration Manager Express updates Windows 10 1709 + Configuration Manager version 1711, Windows 11 ✔️ ✔️ ✔️
Dynamic updates Windows 10 1903, Windows 11 ✔️ ✔️ ✔️
MDM Agent Windows 11 ✔️ ✔️ ✔️
Xbox Game Pass (PC) Windows 10 1809, Windows 11 ✔️ ✔️
Windows Package Manager Windows 10 1809, Windows 11 ✔️
MSIX Windows 10 2004, Windows 11 ✔️

Windows Server

Windows Server Minimum Windows version HTTP Downloader Peer to Peer Microsoft Connected Cache (MCC)
Windows Update Windows Server 2019 (1809) ✔️ ✔️ ✔️
Edge Browser Updates Windows Server 2019 (1809) ✔️ ✔️ ✔️

Linux (Public Preview)

Linux (Public Preview) Linux versions HTTP Downloader Peer to Peer Microsoft Connected Cache (MCC)
Device Update for IoT Hub Ubuntu 18.04, 20.04 / Debian 9, 10 ✔️ ✔️

Note

Starting with Configuration Manager version 1910, you can use Delivery Optimization for the distribution of all Windows update content for clients running Windows 10 version 1709 or newer, not just express installation files. For more, see Delivery Optimization starting in version 1910.

In Windows client Enterprise, Professional, and Education editions, Delivery Optimization is enabled by default for peer-to-peer sharing on the local network (NAT). Specifically, all of the devices must be behind the same NAT (which includes either Ethernet or WiFi), but you can configure it differently in Group Policy and mobile device management (MDM) solutions such as Microsoft Intune. For more information on Download mode options.

How Microsoft uses Delivery Optimization

At Microsoft, to help ensure that ongoing deployments weren't affecting our network and taking away bandwidth for other services, Microsoft IT used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Based on recommendations from the Delivery Optimization team, we used the "group" configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. More than 76 percent of content came from peer devices versus the Internet.

For more information, check out the Adopting Windows as a Service at Microsoft technical case study.

Using a proxy with Delivery Optimization

If a proxy is being used in your environment, see Using a proxy with Delivery Optimization to understand the proxy settings needed to properly using Delivery Optimization.

Delivery Optimization client-service communication explained

To gain a deeper understanding of the Delivery Optimization client-service communication workflow, see Delivery Optimization client-service communication explained

Set up Delivery Optimization for Windows

Learn more about the Delivery Optimization settings to ensure proper set up in your environment.

Delivery Optimization reference

For a complete list of Delivery Optimization settings, see Delivery Optimization reference.

New in Windows 10, version 20H2 and Windows 11

See What's new in Delivery Optimization