Hi, anyone seeing Office 365 app problems today? Error “Something Went Wrong [1001]” signing in to Microsoft 365 Desktop Applications. We are getting this on multiple customer environments after Office 365 autoupdate to 16.0.17328.20588 . Environments are Windows 2019 RDS servers, CVAD 2203 LTSR CU3, Office 365 SAEC with shared computer activation. At this moment we are no longer autoupdating Office 365. Initial tests with version 16.0.17328.20550 don’t show this error but it needs to be confirmed by customers.

We saw some of this too. Did you figure it out?

No, not a solution yet. Customers confirm that the workaround prevents the error.

What's the workaround?

Yep, downgrade to that version did it.

Looks like we still see this issue with users on 16.0.17328.20550

Hmm @Ryan Gallier, I hope I don’t see this issue tomorrow morning when the users are on 16.0.17328.20550 again.

Upgrade the VDA to 2402 (with or without CU1) and the message should clear up, but there may be some authentication issues, but eventually should be able to get logged in. I think that clearing the "\appdata\local\packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy" path helps with the authentication issues I was seeing.

No troubles today on version 16.0.17328.20550 . I’ll look into your possible solution @Dennis Parker

Im seeing this at one customer. AVD, Win 11 Multi-Session, O365 16.0.17830.20210. FSLogix Profile Containers

Error is not reported since about 2 weeks. I guess Microsoft changed something in the backend.

We get this now instead 😂

I've seen that one too, but it usually clears up after a logout/login, but it is still annoying and I'm frustrated not knowing what to do to prevent issues for the users consistently still.

So, we found that if you have RoamIdentity=1 in your FSLogix config, this can cause the 1001 error