I'm resposting from this thread to hopefully create more attention for this problem:
Me and other admins (from reposted thread) have specific users who experience M365 authentication problems after upgrading to the latest FSLogix version(s) that offers support for New Teams.
The error occurs in the Azure Virtual Desktop environment, when a user tries to open a Microsoft application (Outlook, OneDrive etc.).
Not all users have the problem that they need to reauthenticate, or can't authenticate at all, with the 48v35 error. The users who do however, repeatedly get the same error after a few days or a week.
We tried multiple things, like removing the Microsoft.AADBrokerPlugin directory or creating a completely new FSLogix profile, but the problem stays for these users.
In my case I am using the FSLogix setting RoamIdentity=1.
Is there any news from FSLogix on this issue? Or does anyone have workarounds to share?
I would like to update more customer environments to use the New Teams, but with these issues I would rather wait.
13 Comments
Hey I also wonder if this happens if you spin up a new AVD host? That is something I'll be trying next, especially since you mentioned it's an issue even after re-creating the user's FSLogix profile. Curious to know if you made any headway on this issue?
Same issue for us. We're Hybrid AD environment. We however do not use: RoamIdentity=1.
I created a post on Reddit detailing our issue. Logging off and back into AVD is the band aid fix.
Win11 23H2 & Sign-in Office Apps (OneDrive, Teams, Outlook) : r/AzureVirtualDesktopI was attacking another error message with logging into Microsoft 365. I did the following and now I do not receive any of the error messages.
M365 HTTP 404 login.microsoftonline.com error - Microsoft Community
Same problem here, AVD FSLogix environment too. Continuing to troubleshoot - will feed back if I find anything. Irritating issue.
Hello,
We have the same problem. We are using Horizon 2406 with FSLogix in Instant Clone but with persistent machines. We try to migrate our users on the new Teams but after a few days of use, the users have this error “48v35”. Restarting Windows solves the problem.By any chance does your environment have more than 1 VM. I ask because I usually see this behavior whenever users have been logged in to a host, and they don't close their sessions appropriately (i.e. the session is just disconnected or the host is turned off and then when they log in to another host then they get that error).
Except restarting the machine or forcing log off/log on doesn't actually fix it in the long term. It will come back for people in that VM eventually.
Restarting fixed for me too, thanks
I am seeing the same thing. If you delete their office tokens and move them to a new host the problem goes away and then they can log on to any other host without issues and least for a few days then the process starts all over again. But it does not affect everyone, just random user and not always the same one. It is bananas :banana:
