t
image.png
j
Do you have all the GPOs in place to disable the micro-updates? Same with all the scheduled tasks that MS likes to use? Could be that there is a zero day found with the version you have running and MS is attempting to force an update to address it. I would recommend spinning up that office layer, getting it patched to the latest, and get it deployed ASAP.
t
I did some more testing and the registry looks a lot different in the app layer vs the final image. The app layer has more details and includes the correct version info. see below - first picture, broken o365 in image, second picture is working registry in app layer
So I created a net new O365 layer and it seems to have resolved the issue. Perhaps the change via XML from Current to Semiannual wasn't completely cleaning it up.
b
MSFT turned this on at the tenant level for everyone in August. We had to have our tenant admin turn it off.