Key Points
- Delivery Optimization uses peer-to-peer and cache-aware updates to cut redundant downloads.
- Intune enables MSPs to enforce consistent DO settings across multiple clients and environments.
- Proper DO configuration lowers bandwidth consumption and speeds up update deployment.
- Standardized Delivery Optimization Intune templates can streamline management across distributed networks.
- You can leverage NinjaOne’s monitoring and reporting capabilities to track caching performance and demonstrate value to clients.
Windows Delivery Optimization enables endpoints to share update content across networks, reducing redundant downloads and saving bandwidth. Although it can be managed locally or via Group Policy, you can configure Windows Delivery Optimization in Intune, which gives you and your MSP team centralized control over caching, bandwidth limits, and update behavior across client environments.
You can use Intune as a central management platform to ensure updates are delivered smoothly, even in bandwidth-limited or multi-site environments. It also simplifies how MSPs manage policies across clients, reduces network strain, avoids patch delays, and keeps SLAs on track.
Ways MSPs can configure delivery optimization in Intune
📌 Prerequisites:
- You need access to the Microsoft Intune admin center with the correct administrative permissions.
- You need Windows 10 or Windows 11 endpoints enrolled and active in Intune.
- You should be familiar with Delivery Optimization concepts such as modes, cache size, and cache age.
- This requires defined patch management SLAs and operational level agreements (OLAs) to track performance and align with Intune patch management workflows.
Step 1: Create a Delivery Optimization profile in Intune
First, create a dedicated Delivery Optimization (DO) profile in Intune. This will ensure consistency across all managed endpoints, allowing you to apply the same settings to multiple tenants.
📌 Use Cases:
- This step lets MSPs standardize Windows update caching policies across distributed client environments.
- This simplifies management by centralizing configuration in Intune, instead of using local or GPO settings.
📌 Prerequisites:
- You need permission to access the Microsoft Intune admin center to make configuration profiles.
- You need to have predefined device groups that are aligned with client or site structures.
Here are the steps for creating a Delivery Optimization profile:
- Navigate to Intune Admin Center > Devices > Configuration Profiles.
- Select Create profile > Platform: Windows 10/11 > Profile type: Templates > Delivery Optimization.
- Name the policy and assign it to the appropriate device groups.
Step 2: Configure Delivery Optimization download mode
The next step is to select the correct download mode. This determines how devices share updates with others in the network. This setting will affect bandwidth efficiency, Windows caching behavior, and how quickly updates spread across environments.
📌 Use Cases:
- This will reduce redundant downloads by enabling peer-to-peer update sharing.
- This step optimizes bandwidth usage for sites with limited WAN capacity or distributed networks.
📌 Prerequisites:
- You will need an existing Delivery Optimization profile created in Intune (see Step 1).
- You should understand how the client’s network is set up, including how devices connect and how much bandwidth is available.
Here’s how to configure the download mode by choosing the appropriate mode:
- Navigate to the Intune Admin Center, then go to Devices > Configuration Profiles.
- Next, select the Delivery Optimization profile you made earlier.
- Under Settings > Download Mode, select one of the following:
- LAN (1): Peers share updates within the same subnet.
- Group (2): Peers share updates within Active Directory or Intune-defined groups.
- Internet (3): Peers share updates across external networks for roaming or remote devices.
- Click Next, review the configuration, then select Save > Assign to deploy the policy.
- Verify that the policy is applied correctly by checking Device Status under the profile details page.
Step 3: Define Windows Update caching policies
Configuring cache policies will ensure that Delivery Optimization uses local storage efficiently without affecting device performance. The proper cache settings will balance speed, disk usage, and update availability across endpoints.
📌 Use Cases:
- This will prevent endpoints from using excessive local disk space for cached updates.
- It improves update reliability by keeping recent update files available for peer sharing.
📌 Prerequisites:
- You need to confirm available disk space and storage configurations on client devices.
- You should define cache retention goals based on patch frequency and update size.
Here’s how to configure caching policies in Intune:
- First, open the Intune Admin Center > Devices > Configuration Profiles.
- Next, select the Delivery Optimization profile you created earlier.
- Under Settings > Cache Server Settings, configure the following options:
- Cache size: Define the maximum cache size. You can configure it in the following options:
- Not configured (Default)
- Absolute – You can specify the absolute maximum cache size (in GB) to configure the amount of drive space a device uses for DO. If you set it to 0, the cache size is unlimited, though DO clears the cache when the device is low on disk space.
- Percentage – Instead of an absolute figure, you can use percentages to configure the maximum amount of drive space a device can use for DO, which constantly assesses the free drive space and clears the cache to keep the max size under the set percentage.
- Cache age: Set how long cached content should be retained before expiration. It is recommended to set the cache value to seven (7) days. In Intune, the number of days you define is converted into the applicable number of seconds. In this case, seven days is 604800 seconds. Cache drive: Specify whether patches should be stored on a secondary drive to preserve system performance.
- Click Next, review your configuration, then select Save > Assign to apply the updated settings.
- Check whether the policy has been successfully deployed by checking the Device Status tab.
Step 4: Set bandwidth and background activity controls
Managing bandwidth limits will ensure that Delivery Optimization won’t overwhelm the network during large patch rollouts. By setting download caps and scheduling delivery windows.
📌 Use Cases:
- This will help prevent network congestion during peak business hours.
- It lets MSPs control when and how updates are downloaded across client sites.
📌 Prerequisites:
- You must know the client’s usual bandwidth usage and maintenance schedule.
- You’ll need approval for any download restrictions that might affect patch timelines.
Here’s how to configure bandwidth and activity controls in Intune:
- Go to the Intune Admin Center, and select Devices > Configuration Profiles.
- Next, select your existing Delivery Optimization profile.
- Under Settings > Bandwidth Settings, configure the following:
- Limit Background Download Bandwidth: Set a maximum percentage, like 20-40%, to avoid WAN saturation.
- Limit Foreground Download Bandwidth: Adjust this to reserve bandwidth for important updates.
- Next, schedule delivery windows under Settings > Delivery Optimization Preferences and configure Active Hours or Maintenance Windows.
- Click Next and select Save > Assign to deploy the changes.
- You can confirm if the bandwidth and activity settings have been applied by checking compliance in your profile’s Device Status view.
Step 5: Assign and monitor the policy
Once your Delivery Optimization settings have been configured, the last step is to assign the policy to the correct device groups and monitor its impact. This will help confirm that Windows update caching, bandwidth limits, and update delivery work as intended across client environments.
📌 Use Cases:
- This ensures consistent patch management performance across all client sites.
- It provides visibility into compliance and bandwidth savings through reporting.
📌 Prerequisites:
- You should have verified device group assignments within Intune.
- You’ll need reporting permissions to access policy and compliance data.
Here’s how to assign and monitor Delivery Optimization in Intune:
- In the Intune Admin Center, navigate to Devices > Configuration Profiles.
- Select your Delivery Optimization policy. Click Assignments.
- Next, pick the appropriate Azure AD groups or device collections based on client or site requirements.
- Deploy the policy and monitor compliance via Reports > Configuration Profiles > Device Status.
- Cross-reference patch success and bandwidth metrics under Reports > Windows Update (for Business) to confirm improved caching and reduced WAN load.
- For deeper visibility, you can try integrating policy outcomes with Intune patch management dashboards that measure update success rates and endpoint efficiency.
⚠️ Things to look out for
| Risks | Potential Consequences | Reversals |
| Incorrect download mode configuration | Devices may bypass peer caching, leading to unnecessary WAN usage | Verify that the selected mode matches the client’s network design and update behavior |
| Cache size set too high or too low | Disk space issues or insufficient cached content for peer sharing | Adjust cache size settings based on average update volume and disk capacity |
| Lack of monitoring after deployment | Missed compliance issues or unoptimized bandwidth usage | Review Intune compliance performance reports regularly to confirm policy effectiveness |
How to verify if Delivery Optimization in Intune is successful
After deploying Delivery Optimization policies, you can perform verification steps to ensure they are reducing bandwidth use and improving update efficiency.
Here’s how to verify Intune Delivery Optimization success:
- To confirm that the Delivery Optimization policy has been applied across target devices, go to Intune Admin Center > Reports > Device Compliance.
- Review Endpoint Analytics or Reports > Windows Update (for Business) to check for decreased WAN usage and faster update downloads.
- Compare patch deployment times and completion rates before and after implementation to validate SLA adherence.
- Investigate devices showing compliance errors for poor caching performance and adjust download mode or cache policies as needed.
Additional considerations for Delivery Optimization in Intune
Some configuration details can help MSPs obtain the most out of Delivery Optimization in Intune. These practices can improve flexibility, ensure compliance, and make scaling easier across client environments.
- Remote users: Enable Internet peer mode for roaming or hybrid workers so devices outside the network can still benefit from peer caching.
- Compliance: Document all Delivery Optimization settings for audit readiness, especially for clients subject to HIPAA, PCI, or DORA regulations.
- Scalability: Use standardized templates to deploy and manage Delivery Optimization configurations across multiple tenants smoothly.
Troubleshooting Delivery Optimization issues for efficient Intune patch management
Delivery Optimization problems can prevent caching and peer sharing from working properly, thus disrupting workflows. These basic troubleshooting steps can help ensure your Intune patch management processes are working properly without unnecessary bandwidth use.
| Issue | Fix |
| Peers not sharing updates | Check the configured download mode and verify that group assignments are correct. |
| High WAN usage persists | Revisit bandwidth throttling and cache retention settings to ensure they align with network capacity. |
| Devices ignoring Intune policies | Ensure devices are properly enrolled in Intune and syncing at the expected frequency. |
NinjaOne integration ideas that can support Intune Delivery Optimization
NinjaOne’s existing Microsoft integrations and patch management tools can complement Delivery Optimization in Intune by improving visibility, reporting, and documentation.
- Patch monitoring: You can use NinjaOne’s patch management features to verify that cached updates have deployed successfully across endpoints.
- Reporting: You can use NinjaOne’s built-in reporting and Intune compliance monitoring to display patch success rates and efficiency gains.
- Documentation: Ninja Docs can store Delivery Optimization configuration and Intune patch management policies in NinjaOne Docs for quick and easy reference.
- Cross-client governance: You can combine Intune and Microsoft 365 integrations to view device health, compliance, and Delivery Optimization results.
Quick-Start Guide
NinjaOne integrates with Microsoft Intune and supports configuring Delivery Optimization for efficient Windows Update caching.
- Delivery Optimization is a peer-to-peer content distribution technology built into Windows 10/11, managed via Intune.
- It reduces bandwidth usage by allowing devices to share updates locally before falling back to the internet.
- NinjaOne’s integration allows MSPs to manage and monitor this process alongside other Intune configurations.
How to Configure:
- Enable Delivery Optimization in Intune:
- Navigate to Device Configuration > Administrative Templates > Windows Components > Delivery Optimization.
- Enable settings like Allow fallback to HTTP, Configure max cache size, and Set cache expiration.
- Use NinjaOne for Monitoring:
- NinjaOne’s dashboard provides insights into patch compliance, update statuses, and device health.
- You can track how many devices are using cached updates versus downloading from the internet.
- Best Practices:
- Deploy a Connected Cache server (optional) for larger environments to further optimize local caching.
- Schedule updates during off-peak hours to minimize impact on bandwidth.
Configure Delivery Optimization in Intune for improved patch efficiency
Configuring Delivery Optimization in Intune gives MSPs an effective way to reduce redundant downloads and speed up patching across endpoints. Standardized caching policies aligned with patch cycles will help deliver faster, more consistent updates while minimizing bandwidth usage via the Intune Delivery Optimization cache feature.
Related topics:
