Intune rollout checklist for Windows 11
Nathan Chadwick · · 8 min read · Updated
Listen
TLDRRead the short version
- Inventory apps that need elevation, and decide whether Windows Update or WSUS is the scan source, before you assign an update ring.
- When a feature update policy targets a device, set the ring's feature update deferral to 0 so the two policies do not fight.
- Ship in rings on device groups: pilot, then early adopters, then broad. Leave safeguard holds in place.
- Target a department with a group. Use a filter for a fact about the device. A one-off exclusion needs an owner and a date.
- Windows 10 is out of support. A device you cannot move needs a written plan, not a silent exception.

The blank checklist is the point#
The expensive way to roll out Windows 11 is to assign a feature update, a new compliance policy, a removal of local admin, and a new VPN in the same week, then call the result "the Windows 11 project". Users will tell you Windows 11 is slow, or broken, or both. They will be describing four changes.
Microsoft's planning guidance is dull on purpose. Inventory, compatibility, a pilot, then broader rings. This is that order, written for an Intune estate, and written for the moment before you flip a policy from report to enforce. The original short version of this post was three sentences. The work was always the sequence.
Before anyone is blocked#
Do these while the user-visible settings are still off. None of them require a reboot of the whole company.
Count the devices that can actually run it. Windows 11 requirements are still a hard floor: a supported CPU, TPM 2.0, Secure Boot, 4 GB of RAM, 64 GB of disk. Endpoint analytics and a readiness report beat a spreadsheet you update by asking people. Firmware is the usual surprise. TPM and Secure Boot are often sitting in the BIOS, switched off, on machines that are otherwise fine.
Write down the apps that still need an administrator. A Windows 11 upgrade does not remove a prompt. If finance has a desktop app that only runs elevated, you will meet it on the first morning in the pilot. Package what you can silently, which is the job in packaging an exe for Intune. For the ones that genuinely need a privileged action, decide whether that action is a managed local admin password via Windows LAPS or a scheduled task, not a user who is a local admin forever. Taking admin rights away is a separate change. Do not hide it inside the upgrade.
Confirm you can recover a disk. Turn on BitLocker, escrow the keys to Entra, and recover one key yourself before you encrypt the rest. An upgrade that goes badly on an encrypted disk is a different conversation if the key is in the portal.
Move the files that matter. Known Folder Move, or whatever you already use, so a profile problem is not a data-loss incident. Shared PCs and labs are a different fleet. They fill with old profiles, and the cleanup for that is the startup script against Win32_UserProfile, not a feature update.
One update authority#
This is the step estates skip, and then the ring reports success while nothing installs.
If a device is configured with a WSUS server and you have not told it otherwise, Windows 10 and Windows 11 both take updates from WSUS. Intune update rings do not override that by being assigned. Microsoft's current model is a scan source policy: for each class of update (feature, quality, drivers, other Microsoft products) you choose WSUS or Windows Update. The old "dual scan" deferral policy is not supported on Windows 11.
So, before the ring:
- Devices in the Intune rings get their feature and quality updates from Windows Update. Say that in the scan source policy.
- Servers or a stubborn site that must stay on WSUS stay out of those rings.
- Do not leave "check online for updates" as the way a user might be offered Windows 11 by accident. An offering policy or a scan source is the deliberate version.
Then split the two Intune controls, because they are not the same knob.
Update rings set deferral, deadlines, restart behaviour, and the user experience. Assign them to device groups. A user group means the ring waits until someone signs in.
Feature update policies pin a device to a Windows version, or move it to one and stop it going further. When a device has both, set Feature update deferral period (days) in the ring to 0. Otherwise the ring's deferral quietly delays the version the feature update policy is trying to offer. Microsoft documents that hand-off in the feature update policy guidance.
Pin a version you have piloted, and check the lifecycle date before you standardise on it. "Latest" is not a plan. A version that is already out of support is the next project, not the target.
Windows 10 is already out of support#
Windows 10 Home and Pro reached end of support on 14 October 2025. This post was first published later that month, when a lot of estates were still "about to" move. If a device is still on it now, the rollout is late.
For a UK certification that matters. Unsupported software in scope is an automatic fail for Cyber Essentials, which I walked through in what it takes to pass in 2026. The options are upgrade, replace, or a properly segregated sub-set with no path that pretends the device is in scope. A silent exclusion in Intune is none of those.
Extended Security Updates are a procurement decision with an end date. They are not a ring.
Rings: pilot, early adopters, broad#
Follow the deployment ring shape. Three is enough.
| Ring | Who | What you are looking for |
|---|---|---|
| Pilot | IT, plus one real user team that will tell you the truth. A mix of models, including a laptop that leaves the building. | Upgrade completes, apps open, VPN and Wi-Fi still work, restart deadlines are tolerable. |
| Early adopters | A willing department, still small enough to visit. | The things the pilot's hardware never had. Specialist apps, docking stations, odd drivers. |
| Broad | Everyone else who passed readiness, in waves you can pause. | Ticket volume. Pause the wave if you cannot explain the tickets. |
Safeguard holds exist so Microsoft can stop an upgrade when a known incompatibility is on the device. Leave them. Overriding a hold to hit a date moves the breakage from Microsoft's list onto your service desk. Fix the driver or the app, then let the device go.
Assign the broad ring with groups and filters, not with a growing list of one device.
- A group is how you target a department or a ring.
- An assignment filter is how you express a fact about the device: ownership, model, operating system, a machine that failed readiness.
- A one-off device exception is allowed when the reason is written down, with an owner and a date. "Finance laptop, app X, review 1 March" is an exception. A device that has sat in an exclude group since the pilot is a second estate.
Quality updates need a deadline inside the window you are prepared to defend. Cyber Essentials now treats critical and high-risk updates older than 14 days as a fail. A 30-day deadline in the ring is a comfortable setting and a certification problem. Set the deadline for the standard you actually have to meet, and expedite the out-of-band patch rather than widening the ring to be kind.
What to enforce, and when#
The order below is the one I want finished before Conditional Access starts requiring a compliant device. That dependency is real: a compliant-device grant pointed at a fleet you have not made compliant is an outage with a policy name.
- Readiness and the app list. No user impact.
- Disk encryption, with one recovery key tested.
- Scan source decided. Update rings for quality updates, on the pilot only.
- Feature update policy to the piloted Windows 11 version, pilot ring.
- Sit with the pilot for a week. Fix apps. Do not start the early ring to escape a problem you have not named.
- Early adopters, then broad, in waves.
- Compliance policy aimed at the settings you have actually deployed. Read the non-compliant list. Then, and only then, let Conditional Access require it for the admin portals and the corporate desktop.
Windows Autopatch is a reasonable way to run rings if you already pay for it. It is not a shortcut around readiness or around the WSUS question. Something still has to decide the scan source.
What still goes wrong#
The pilot is three people on the same dock. You will learn nothing about the other model, the home broadband, or the app that only finance has. Put one awkward device in the pilot on purpose.
The upgrade is also the moment you remove local admin. Users will call the upgrade broken. Split the changes by at least a week, and have the elevation story ready. Standing local admin is the problem LAPS and the PowerShell guardrails exist to shrink. It is still a separate project.
Delivery on a thin site. A feature update is several gigabytes. A small office with no peer caching and a pilot of every machine at 09:00 will decide Windows 11 is the thing that filled the pipe. Stagger the ring.
Readiness ignored. A machine that fails TPM will not become Windows 11 because the ring says so. It will sit, non-compliant, until someone looks. The exclude-with-a-date rule is how that list stays honest.
Configuration profiles from the Windows 10 era applied unchanged. Some will be fine. A few will fight the new UI, the new Start, or a security baseline you also assigned. The pilot is where you find which. Read the profile status. A conflict is not a successful deploy.
A short checklist#
- Readiness report: CPU, TPM 2.0, Secure Boot, RAM, disk. Firmware fixed where that is the only gap.
- Apps that need elevation inventoried. Packages planned. Admin removal not bundled into the same week.
- BitLocker on, one recovery key fetched from Entra.
- Scan source set. Intune-ringed devices use Windows Update for feature and quality updates. WSUS devices are not in those rings.
- Feature update deferral in the ring set to 0 where a feature update policy applies.
- Pilot, early adopters, broad. Device groups. Safeguard holds left alone.
- Department by group, device facts by filter, one-off exceptions with an owner and a date.
- Quality-update deadline inside 14 days if Cyber Essentials is in scope.
- Compliance policy green before Conditional Access requires a compliant device.
Closing#
Windows 11 is an upgrade with a hardware floor and a servicing decision. Intune is how you stage it. The checklist is the part that stops the upgrade becoming every other project you meant to do later.
Pilot a real device. Decide where updates come from. Write down the laptop you are leaving behind, and the date you will look at it again. Then widen the ring.
References#
Sources and further reading for the claims above.
- Microsoft Learn, Plan for Windows 11
- Microsoft Learn, Prepare for Windows 11
- Microsoft Learn, Windows 11 requirements
- Microsoft Learn, Windows 10 end of support
- Microsoft Learn, Windows Update for Business
- Microsoft Learn, Use Windows Update client policies and WSUS together
- Microsoft Learn, Windows update rings in Intune
- Microsoft Learn, Feature update policies in Intune
- Microsoft Learn, Safeguard holds