Microsoft
MicrosoftHey Marc,
Let me help clarify a bit.
When you check the “Feature updates” box during Autopatch group creation, it automatically creates a single feature update policy assigned to all deployment rings in that group. While this works, it limits flexibility and control—especially if you want to use multi-phase rollout strategies or manage Windows 10 to Windows 11 upgrades separately.
The checkbox exists to support simpler scenarios where a single policy is sufficient if you want devices in that group to be on that minimum version. But for phased rollouts and ring-specific targeting it’s better to manage feature updates separately.
It is recommended using separate Autopatch Group since devices staying on Windows 10 (e.g., ESU-enrolled) and those upgrading to Windows 11 have different servicing needs. Keeping them in the same Autopatch group risks conflicting policies or accidental upgrades.
Thanks Akash for the explanation. So for us where we want to move everyone to Windows 11 but do it in a phased roll-out, we should use two separate groups until the rollout is complete then just use one group for continued maintenance (if I am understanding it correctly).
