When I look at tenants in June 2025, I keep running into the same Windows 11 migration blockers. There are a handful of ancient laptops, a few critical apps that "might break", some remote endpoints with vague specs, and nobody is quite sure whether they'll be ready by October 14th. Windows 10 support ends in four months, so organizations need real visibility now, less for the mass deployment and more for clearing whatever is left. In many projects I find that Intune's reporting has made it much easier to see exactly what is holding things up. Endpoint analytics and the newer update readiness tools are where that visibility comes from.

The Work from anywhere report shows which devices can run Windows 11

If you haven't opened it in a while, the Endpoint analytics "Work from anywhere" report (Intune admin center → Reports → Endpoint analytics → Work from anywhere → Windows) is still the fastest way to see which devices are Windows 11 capable. It also tells you which ones aren't, usually because of a missing TPM, Secure Boot or an unsupported CPU. In practice it helps you find aging hardware and gaps in your inventory quickly, including remote endpoints that rarely check in. Teams are regularly surprised by how many machines fall short, and the number is almost always higher than they expected. I use it mainly for hardware refresh planning. Microsoft's official overview is here.

Pro tip: Export the Work from anywhere report once a month and go through it with your procurement team. That way old devices don't get forgotten until it's too late.

Compatibility reports reveal the real blockers behind feature updates

Once hardware is sorted, software compatibility comes next. Intune's Windows update readiness and compatibility reports live under Intune admin center → Reports → Windows updates (they require Windows diagnostic data to be enabled in Tenant administration → Connectors and tokens → Windows data). They show which devices can actually receive a feature update, which are blocked and, most importantly, why. This is where the hidden problems surface, such as legacy antivirus, outdated drivers, line-of-business software that refuses to run or forgotten tools nobody can assess. Each risk comes with detailed information, and in environments with custom software I consider this indispensable. Microsoft's guide to these reports is here.

The feature update readiness dashboard (also under Windows updates) lets you track rollout status for your target version, for example 24H2, and keeps your migration roadmap current. Put that next to the compatibility warnings and you can see where you can move quickly and where you need to dig deeper.

# PowerShell: Find devices below your Windows 11 target version and their compliance state
# Where: PowerShell 7 with Intune PowerShell SDK; requires Intune Administrator or Global Reader
Get-IntuneManagedDevice | Where-Object { $_.OperatingSystem -eq "Windows" -and $_.OSVersion -lt "10.0.26100" } | Select-Object DeviceName, OSVersion, ComplianceState

Feature update policies steer devices towards Windows 11 24H2

What I've seen work well is a rollout in waves with Intune feature update policies that target "Windows 11 24H2" (see docs). You keep full control over timing and version consistency, and because everyone stays current there are fewer surprises. Now that 24H2 is broadly available, it is the obvious migration target for the rest of 2025. You can move compatible hardware over now and set the problem devices aside for separate handling. I cover the practical side of rolling out with Intune and Autopatch in Windows 11 24H2: Controlled rollout with Intune and Autopatch.

These policies also give you change tracking and reporting, which makes management updates and compliance documentation much easier. By this stage the technical blockers matter less than showing progress in a transparent, auditable way.

Ineligible devices end up replaced, on ESU or in Windows 365

Not every device will make it to Windows 11. Some hardware can't be upgraded, some budgets won't cover replacements, and some legacy applications force you to hold out for a while. For those cases there are three main options:

  • Replace devices (best long-term, but highest cost)
  • Windows 10 ESU (extended security updates, expensive and a last resort)
  • Move workloads to Windows 365 Cloud PCs (a good fit for remote or temporary needs)

Whichever route you take, start planning and documenting it now and keep the number of devices that need a temporary exception as low as possible. If you haven't done so yet, compare where you are today with the one-year-left milestone. There isn't much time left.

My final push rests on reporting and staged deployment in Intune

In my own projects, the Windows 11 migration has turned into a routine of systematic reporting, troubleshooting and targeted deployment through Intune. Monthly Endpoint analytics exports, detailed compatibility risk reports and staged feature update policies do most of the work. One point I always make is not to focus only on the technical rollout. Keep procurement, security and the business units informed so everyone knows what still needs fixing and what is already done.

This diagram shows how the process fits together:

flowchart TD
    Devices["Windows 10 devices"] --> HWCheck["Intune Work from anywhere report"]
    HWCheck --> HWReady["Hardware ready?"]
    HWReady -- "Yes" --> UpdateCheck["Windows update readiness report"]
    HWReady -- "No" --> Exception["Replace/ESU/Windows 365"]
    UpdateCheck --> Compatible["Compatible?"]
    Compatible -- "Yes" --> Policy["Feature update policy 24H2"]
    Compatible -- "No" --> Analyze["Analyze issues"]
    Analyze --> Fix["Remediate issues"]
    Fix --> UpdateCheck
    Policy --> Migration["Windows 11 migration"]

Figure: End-to-end migration workflow using Intune reports and policies

I wouldn't wait until autumn. Summer is the time to finish the Windows 11 migration, with Intune as the place where you see the status and act on it. For a refresher on what's at stake or how to prepare for 24H2, read my post on one year to go and the detailed 24H2 rollout guide.