Deploy Windows Feature Updates Using Intune

In this post, we will be looking into the Feature Update policies in Microsoft Intune and how they can be used to deploy an Upgrade to Windows 11 on managed devices.

Introduction

Using Intune to deploy feature updates to your managed devices can take out some of the complexities of managing a task that can otherwise prove time-consuming, as it allows you to target specific groups of users or devices to perform the upgrade on so that it can be done in manageable stages.

On top of this, you can also use these policies to upgrade any viable devices that are currently running Windows 10 to Windows 11 with little to no effort. And with the end of support for Windows 10 approaching in 2025, it is important to start taking steps towards getting all viable devices onto Windows 11.

Requirements

Before you can start pushing out feature updates with Intune some requirements need to be met, this includes some device and licensing requirements that will change depending on the settings that you plan to configure. So make sure to check these carefully before proceeding to the next steps.

First, is the licensing requirements, this will vary depending on the settings that you are planning to implement, but essentially if you are just looking to use basic settings in the policy there is no license requirement. This includes:

  • Selecting any feature update
  • Setting the update required 
  • Making the updates available as soon as possible or scheduling a date (basically any timeframe setting excluding gradual deployment)

All other options that are available in these policies will then require your organisation to have at least one license that includes the ‘Windows Update for Business Deployment Service’ feature, this feature can be found in a variety of license options such as the following:

  • Microsoft 365 F3, E3, & above
  • Microsoft 365 A3 & above
  • Microsoft 365 Business Premium
  • Windows 10/11 Enterprise E3 & E5 (Standalone)
  • Windows 10/11 Education A3 & A5 (Standalone)

When creating your policy you will also notice that there is a warning when you select any version of Windows 11 to deploy. This is simply a warning to inform you that the device you are deploying this update to needs to have a valid Windows license.

Then there are several requirements on the devices that you are planning on pushing these updates to that you need to ensure you are implementing. 

The first of which is that the device you are applying this update to needs to be running a version of Windows that is still currently supported By Microsoft. This is an important step to consider as it means you cannot use these policies to bring outdated devices up to the latest versions. Currently, you will need to get your devices to a minimum of Windows 10 22H2 to utilise these policies.

Next the devices that you are planning on deploying these updates to need to allow the Microsoft Account Sign-In Assistant service or wlidsvc to run, if this is disabled the update will not be able to run on the device. If this is something that you have issues with you can utilise a remediation script to check the service on the targeted devices and change the startup type if it is set to “disabled”. To learn more about how to use remediation scripts in Intune check out my guide below:

Traverse Cloud – Using PowerShell Scripts in Intune

The final requirement is not actually needed to push out updates to devices, however is strongly recommended as without it, if you select a version of Windows that is not the latest, there is a chance the device in question will update beyond the selected version.

To avoid this you will need to enable Telemetry data on the targeted devices to be required or higher. This can be done with a device restriction policy, under ‘Reporting and Telemetry’ set the ‘Share Usage Data’ to Required

Getting Started

Once you have ensured the requirements have been met you can start the process of creating your Feature Update Policy in Intune.

To get started with this go to the Intune Admin Center and select Devices > Windows 10 and later updates (under Manage Updates) > Feature updates:

Then press the “Create Profile” option at the top of the page to start making a new policy. You will be taken straight into the deployment settings once on the ‘Create feature update deployment’ page, here the first section is to add a name and description for the policy.

As always you should ensure to give your policy a descriptive name and description so that others who look back on your policy can easily determine what it was being used for.

Creating Your Policy

Now that you have given your new policy a descriptive name it is time to move on to the settings that are available in the policy itself, the first of which is to select which feature update you want to deploy with the new policy. 

From here you can select any of the currently supported versions of Windows from Windows 10 22H2 to Windows 11 23H2. If you select to deploy a Windows 11 policy to a Windows 10 device it will perform the upgrade to Windows 11, making this a very efficient way of deploying the latest OS version.

After you have selected the feature update that you want to deploy you can then select the type of deployment. Your options are between making the update Required or Optional for the selected users.

Required updates will be installed on the targeted devices automatically when they check in, once done the device will show that it requires a reboot to complete the upgrade. Optional updates will make it so that the user can choose when to install the update, this will show as an optional update on the Windows Update page in settings.

There is also a check box in this section that determines the upgrade availability if the target device is currently Windows 10 and the target version is Windows 11 but the device does not meet the requirements for Windows 11. 

Checking this box will ensure that these Windows 10 devices will upgrade to the latest available feature update for Windows 10 instead of upgrading to Windows 11. Exact Windows 11 requirements can be found in the link below:

https://learn.microsoft.com/en-us/windows/whats-new/windows-11-requirements

Next is the Rollout options for your policy, the first of which is to make the update available immediately. This option will do exactly as it says and make it so that the update is applied as soon as the device checks in.

The second option that is available is to make an update available on a specific date. This option will allow you to set the date that the update is deployed to your targeted devices, allowing you to configure updates that will take place in the future and giving you time to inform the end users before the deployment.

When you select this option another section will be displayed below the Rollout options, here you can specify the date you would like the update to deploy. Using this option will still honour the Required or Optional selection you made in the availability section.

The final option is to make the selected update available to targeted devices gradually. This option will break down the group that you assign this policy to and deploy the update to subsets of the original group over a specified timeframe.

Selecting this option will reveal another section below the Rollout options allowing you to enter several new options:

  •  First Group Availability
    This section will allow you to specify the date on which the first subset of the targeted devices will receive the upgrade. This can be set to a minimum of 2 days from the current date.

  • Final group availability
    This section is the date in which the final subset (or all remaining devices) will receive the specified update

  • Days Between Groups
    This allows you to determine how many days the subsets updates will be spaced out by.

The ‘Days between groups’ selection will determine how many devices are in each subset as they will be split into even groups. 

For the above example, the availability period is 10 days, and the days between update groups is set to 2 days. This means that there will be a total of 5 groups to deploy the update to. If the total of targeted devices is 20, this means each group will contain 4 devices. If the total number of devices is 50, they will be separated into groups of 10.

This option is particularly useful if you expect to have to remediate issues for your end users following the updates, as it will give you time to work on any issues raised for one group before another is updated, instead of all users being updated and raising issues at once.

Once you have got the settings that meet your needs in place select the ‘Next’ button on the bottom of the page to move on. Next, you will be able to configure the assignments for your policy, similar to other policies and apps, here you can select the groups to target with your new policy.

One thing to consider at this stage however is that you cannot select ‘All Devices’ or ‘All Users’ with the policy (you can however create a dynamic group and target that instead). You also cannot use device filters to narrow down the targeted devices further and instead have to rely on the excluded groups section to narrow down if needed.

Finally, once you have selected your target groups you can move on to the final page which is the Review and Create page. From here you can check over all of the settings that you have configured in the previous steps. If everything appears to be correct select the ‘Create’ button at the bottom of the page to save and create your policy.

If your policy is configured to make the update available immediately then the devices will start to update when they next check into Intune to receive the new policy.

What Comes Next

Once you have created your policy you will be returned to the Feature Updates page where you started and your new policy will be listed (you may have to refresh the page for this to show). 

This will also show you what Feature Update each policy targets, whether or not the policy has been assigned, if the update version is still supported, and finally when the support for the targeted version ends. Allowing you to determine if a policy is still viable or if is not redundant at a glance.

After your new feature update policies have been applied you will be able to check in on the results from this policy by going to Reports > Device Management > Windows Updates and then running the Windows Feature Update Summary.

From here you will be able to see each of the policies that you have created along with a general overview of how many devices this has either successfully applied on or failed on.

You can also get a more detailed report on the Windows Update Feature update policies as well as the status of your managed devices from the Windows updates > Reports section. For more information on how to utilise follow the link below to find our guide on Windows update Reports:

Traverse Cloud – Get Windows Update Reports with Microsoft Intune

Considerations

There are a few considerations that you should make before looking into using Feature Update policies in Intune. The first consideration to make before implementing a new feature update policy is the target versions’ compatibility with your managed devices.

You will likely have already considered this however, you need to ensure that updating to a later version of Windows is not going to have drastic effects on your end users’ ability to perform day-to-day work. 

For the average device a step up in version will have little to no effect, however devices that are running more specialist software, there may be an issue caused in a later version of Windows that needs to be addressed before deployment.

That being the case you should always test new versions on a smaller selection of devices (preferably with a similar setup to that of the intended targets) so that you can ensure no major issues occur following the update. This can easily be accomplished with a Feature Update policy simply by targeting a test group and monitoring those devices from there.

The same consideration needs to be taken when using these policies to Upgrade to Windows 11 from Windows 10, except there is an additional check to perform which is your managed devices; compatibility for Windows 11. You will need to ensure that any device you target meets the requirements for Windows 11, if they do not the updates will fail (or it will install the latest Windows 10 Feature Update depending on the settings you apply).

This is something that can be checked from Intune by going to Reports > Endpoint Analytics > Work From Anywhere, then selecting the ‘Windows’ bar. Doing so will open a section on the right of the page, from here you will be able to see an overall view of how many devices in your organisation meet the requirements for Windows 11

From this section, you can select the text that reports the % of devices that meet the requirements to be taken to the full Windows Update report. This report can be used to determine why devices are failing Windows 11 requirement checks, allowing you to determine if these devices can be adjusted in preparation of if they need replacing.

If you are using Update Rings in Intune to keep your devices up to date then you will also need to check these policies for Feature Update Deferral settings. It is strongly recommended that this be set to 0 to avoid any unexpected delays in the update deployment

The final consideration to make is related to the behaviour of a device after receiving a feature update from Intune. When a managed device receives an update using a Feature update policy from Intune it is enrolled into the Windows Update for Business deployment service, which is used to manage updates for your devices.

This is a normal behaviour however, after the update has been applied the device will remain enrolled to this service, as a result, once the target feature update has been deployed to a managed device, no further feature updates can be applied to the device in question if it is not applied via a Feature Update Policy.

Which means if you use other services that deploy feature updates the WUfB Service will prevent this from taking place. To work around this you will either have to deploy all future updates from Intune or unenroll the devices from Intune which in turn removes the devices from the service.

It is also possible to remove the device from the Windows Update for Business Service using Microsoft Graph and PowerShell. The following command can be used to remove a device from the service, this is for one individual device using its ID in MSGraph, to remove multiple devices you will have to adjust the command to loop through a list of Device IDs

This does require you to have ‘WindowsUpdates.ReadWrite.All’ permissions and you will need to collect the device’s ID before running:

Summary

Applying feature updates to managed devices is often viewed as a tedious and time-consuming task as there is an element of testing or trial and error that needs to be done before you can proceed with deploying to a broader scope.

However, using feature updates policies in Intune can help streamline the process of deploying these updates by allowing you to easily target groups of devices and adjust the deployment methods and timescale to best suit your organisation or end users without having to implement a 3rd party tool, making management that much simpler.

On top of this, you can also use this feature to upgrade compatible Windows 10 devices to Windows 11 with ease, which with the end of support for Windows 10 looming in 2025, is something that all IT departments should be considering and planning for devices still running Windows 10.

Author: Curtis Cannon

My name is Curtis, I am a service engineer for an MSP. My focus is on specialising on Azure/Entra ID and other related cloud technologies found in the Microsoft 365 Suite. This content has been written from my own knowledge on the subject in question, and any opinions given throughout the post are mine and do not represent the opinion of others.

Related Posts