Forum Discussion
Autopatch - Microsoft 365 Apps Update Rings
Thanks for taking a look at my question. My goal here is specifically to understand the behaviour of the UpdateDeferredVersions value in an Autopatch scenario, particularly how the FileTime is determined and what triggers its update.
I’m not trying to achieve a separate outcome beyond that clarification; I’m looking to better understand the underlying mechanism so I can interpret and manage update behavior more accurately in our environment.
I do have a working theory, which I’m planning to validate during the next Patch Tuesday cycle. Once I’ve confirmed whether it’s correct or not, I’ll share my findings here as well.
If you have any insight into how that timestamp is calculated or updated, I’d really appreciate it.
Thanks again.
Ok, from my perspective i think the UpdateDeferredVersions is handeld as a timestamp that Microsoft's CDN stamps on a build when it becomes available for your specific ring, not a record of anything you did in Intune. When you tweak deferral or deadline settings in Autopatch, that stamp doesn't change, because the build itself didn't change on Microsoft's end.
The deferral days you configure in Autopatch simply tell the C2R client: "wait this many days after that CDN stamp before actually applying the update." So if the stamp says a build arrived 1 day ago but your deferral is set to 2 days, the client will sit and wait. The moment you backdate that timestamp to be older than your deferral window, which is exactly what your 4-day test did, the client sees the waiting period as already elapsed and proceeds with the update.
If you were able to find mismatches, just raise a ticket with Microsoft and maybe they'll have more insights.
Good luck!