MicrosoftWe literally just had updates break several users' workflows because they couldn't use Office products and/or they experienced such lag they were unable to work (June 2026 updates). Thankfully, we were able to start uninstalling it across devices (thanks for that feature) but we do have update rings like others have mentioned and some updates are just bad but do not affect everyone until they hit our broad ring or we catch them in the previous ring (not always but at least we have a chance). We also monitor blogs to see if other people have had issues with certain updates.
Until updates can be 100% guaranteed to NOT BE BAD I don't think we would be interested in a <3 day for the amount of devices we have. We couldn't have a bad patch go out and affect 500 machines at once. At least with our rings, we have a chance of mitigating before it hits the entire org.
And let me be clear- it's not that we are uninterested in the faster updates it is that the updates are not close enough to 100% for us to implement. If updates were better, we would be faster.
The reporting looks great but we need really need the ability to adjust to our set policy in days vs the recommended (unusable) timeframes.
MicrosoftThanks for your comment gingerj9077 and for sharing your concerns with us. We've updated our guidance to manage multiple rings within the new recommended quality update deferral, deadline, and grace period values, which can help you make updates faster while still allowing time to validate the patch as it is released. You can read more about what those rings can be within the table on this page Autopatch group policies | Microsoft Learn and see an example of that rollout cadence on this page Configure Windows Update client policies by using CSPs and MDM | Microsoft Learn. Let us know if you have any further questions or concerns.
