Configuration Manager technical preview version 2401

Bala_Delli  There's no reboot required but it's being interpreted as such because there are i presume locked files needing updates presumably because it's setting that reg key you mentioned and there's no distinguishing between "close the app" and "reboot the system". Once the user closes and reopens office the updates take effect but if a reboot has been prompted for already, the user may go and do it anyway.

I suspect this is more of an office thing than an SCCM thing but since you have the O365 update integration and ADRs it would be nice to have some facility to suppress it somehow. For example if we could see the update in software centre, but have it show a status of reboot required but not actually pop up a notification saying that, that would be a good compromise. I.e. if user goes looking into software centre and nosing around they would see a spurious "please reboot" but it wouldn't actually prompt for one interactively through the normal software centre toast / popup notifications.

Co-management requires Azure Hybrid registration right? Which happens at system / machine level. So when we use proxies, which we do, this goes looking for a system level proxy. Which is fine and all, except setting a system level proxy then went and broke WiFi captive portals etc. because they went trying to find our proxy before they'd actually connected to our DirectAccess.  So we abandoned any plan to softly move into a hybrid joined world I'm afraid.

On another semi-related topic in the sense that it's SCCM related but probably not SCCM's fault.....have just discovered we can't offline service Windows 11 images anymore using SCCM, because of the switch to UUPs? I've seen elsewhere that the recommendation is to just download updated ISOs every month but for orgs like ours where we still customise the image to do things like zap store apps and add language packs and so on, this isn't a runner. Any plan for this much needed automation facility to return?