Event details
MicrosoftHi jeddy_ ,
That's a good suggestion. Internally, we are exploring how to improve the feature update experience in a number of ways, including providing some form of automated approvals, possibly similar to how drivers does it, but better tuned to feature updates and some of the other important aspects unique to managing feature updates. So stay tuned!
-David
FWIW, that feature already exists in Update Rings. The whole point of Feature Update Policies is to have the level of control that require manual intervention that jeddy_ mentions.
If you want to automatically roll out the latest FU then don't use FUP, just specify a delay in your update rings and all devices will automatically receive the latest FU.
So jeddy_, what functionality are you looking for that Update Rings does not provide?
Appreciate the info there as I do have Update rings set up also, and that makes sense how they work for "Latest" Feature Updates where no Feature Update Policy applies. This would really be to target specific groups and leverage some of the other potential/future items mentioned on the AMA like potential "Latest Feature Update minus 1", or to enforce expanded Rollout options that Feature Update Policies offer such as "specific date" and "gradually" that could apply to a rolling calendar date vs. a fixed point in time (i.e. have a policy to always deploy the previous H2 update every year starting January 15th and running until January 30th).
So let's take your hypothetical: "always deploy the previous H2 update every year starting January 15th and running until January 30th" I realize that might not be your actual plan but the numbers don't really matter.
In 2027 you want to start a FU rollout on a Friday and then in 2028 start on Saturday?
If so, that's cool, not kink shaming anyone here, but I seriously doubt that's a widespread desire. That's definitely a bit more control over Update Rings but I suspect not enough control for most orgs.
At a bare minimum, we'd need something like "Second Tuesday of Jan with a 2 day offset" ... basically we need ConfigMgr ADRs. All to avoid having to go in a couple of times a year and review and update our policies.
