With the Intune update at Week of November 26, 2018 there is a new way to create a Delivery optimization (DO) in Intune. Before that update is was only possible to create DO settings in Windows Update for Business policy (WUfB). Now we can create it as a standard Intune Windows 10 profile so that we can leverage on DO for other things then Windows Update like the Intune Win32 app content.
In this blog post I will explain how to migrate from WUfB to the new Intune Windows 10 profile type Delivery Optimization.
First we need to migrate from Windows 10 update Ring settings
So find all you WUfB rings and look if it has DO configured like this one:
The DO mode need to be changed to Not Configured
If you are creating a WUfB policy is it not a error that you cannot set the DO settings, but by design – you need to use the new Windows 10 profile type “Delivery optimization”
Create the new Delivery optimization profile
- Enter a Name : Windows 10 – Delivery optimization
- Select Configure
- Choose you “Delivery optimization download mode” in my case “HTTP blended with peering behind same NAT”
Delivery optimization download mode is:
- HTTP only, no peering
- HTTP blended with peering behind same NAT
- HTTP blended with peering across private group
- HTTP blended with internet peering
- Simple download mode with no peering
- Bypass mode
Before you begin, go to Software updates – Windows 10 Update Rings and migrate your existing Delivery optimization download mode setting.
Then you just need to assign the DO profile to a user or device group.
Read more:
Delivery Optimization for Windows 10 updates
Cloud First 
Thanks for the update. What’s the benefit from using this method from the old way?
Ps, it looks like there is a typo ‘but be design’
Hello Per, thanks for the update.
we have another scenario that we need to update about 3,000 windows 10 tablets to Windows 10 1803 os version, those devices come with different old windows 10 versions.
my question is what is the best scenario to update those tablets.
I assume that it is Windows 10 1709 – if you are using WUfB you need to be in a hurry do to you can only postpone a feature update for 365 days. So if you have managed to block Windows update for so long there is a risk that they will be upgraded to 1809. If that is the case a MDT/SCCM task sequence or manual reinstall of the devices is the only option