Has anyone seen/dealt with this in the wild: https://www.reddit.com/r/VMwareHorizon/comments/1avofn9/authentication_issues_with_latest_version_of_365/?rdt=57828 I have one customer experiencing it, but none others across 40+ different deployments. Essentially after recent Windows Updates, VDI VMs are getting an HTTP 404 when trying to authentication Azure AD accounts on Office logons.

Have had someone in the wild ask questions about this because it is periodically happen to them on their non-persistent desktops in Horizon. They can seem to get around a couple of cheesy ways they can launch wireshark and it seems to fix the issue or they can run a netsh command to start a capture and it fixes it as well

This is one of those times that I wish I had access to deploy a new base image, rip apart Azure AD, and fully review their Azure SSO situation... lol

Hm, this happened to me this week. Rebuilt my Office container which resolved it. Another user reported and recovered quickly...

@Coleman Kelly, container? What platform, and did the re-install on the "container" resolve? In the case I'm referring to, it's office baked in to a golden image.

FSLogix ODFC container, just deleted the current one and rebuilt it on next logon. VMware Horizon, and Office installed on the golden image.

Ohhhh, so no office re-install was required?

Has only happened twice so haven't gotten to that step yet

Thanks. This is happening in the environment I'm working with, even with new profiles and profiles reset.

There are new posts in Reddit where a Windows Update preview for one of the KBs fixes it. Having people that asked me about it testing to confirm

@Johnny Ma thank you! Any chance you can provide a link to the Reddit thread?

@Stephen Daniel Wagner it was the one you posted above, here is a link to the Preview Windows Update that they said fixes it: https://support.microsoft.com/en-us/topic/february-29-2024-kb5034843-os-build-19045-4123-preview-c576e1b5-9b0d-4411-9be8-57328f41954d

Oh, awesome, thanks! I didn't see that!

@Stephen Daniel Wagner did that patch fix the issue for you?

Unfortunately I can't test it with the customer. I'm in more of an advisory role with this specific customer, so all I can do is provide information. Applying preview patches aren't an option.

understood, thanks!

I'm going to keep on this though, and I'll post any updates I come across. I just wish it was happening in an environment that I was authorized to actively troubleshoot. From the behavior, I'm almost suspecting it's a result of modification of the base image, in addition to something wrong with Seamless SSO, Azure AD, UPN configuration, and the disablement or modification of some of the Azure authentication functions.

anybody had a chance to apply March patches and see if the issue is resolved?

That is proving to be hit or miss so far, at least in our environment.