How to Deploy Windows 11 Feature Updates via SCCM

Feature updates (the annual Windows 11 version upgrades, like moving from 23H2 to 24H2) are functionally an in-place upgrade rather than a small patch, and SCCM handles them through servicing plans specifically designed for this. Treating them like a regular software update will work technically but loses the staged rollout control that makes feature updates manageable at scale.

Step 1: Confirm your Windows servicing products are synced

In the Software Update Point component properties, ensure “Windows 11” is selected under Products in the classification/product sync settings. Feature updates won’t appear in SCCM at all until this is enabled and a sync has completed.

Step 2: Create a servicing plan targeting a pilot collection

Under Software Library > Windows 10/11 Servicing > Servicing Plans, create a new plan targeting a small pilot collection first, filtering to the specific target version (e.g. 24H2). Set a deadline that gives adequate time for the upgrade to download and stage before it forces installation.

Step 3: Monitor the pilot before expanding

Feature update failures often relate to insufficient free disk space (the upgrade process needs significant temporary space), incompatible drivers, or third-party security software interfering with the upgrade process. Use the built-in Feature Update compliance reports to check pilot success rates before expanding the servicing plan’s target collection to the wider fleet. Don’t assume a pilot with high failure rates will magically succeed at scale.

Step 4: Expand gradually with rings, not all at once

Once the pilot succeeds, expand to a broader “ring 2” collection, then finally the full fleet, rather than jumping straight from pilot to everyone. This staged approach means a problem specific to a hardware model or software combination surfaces at a manageable scale rather than across your entire organisation simultaneously.

For official guidance, see Microsoft’s Configuration Manager documentation.