Forum Discussion
Outlook login issues with WVD - FSLogix
DAsnow this scenario isn't ringing a bell in terms of a common scenario, probably best to contact support on this.
So it seems to have nothing to do with the windows update.
I fixed my issue by rolling back FSLogix to 2210 to 2201. There is a known issue for those devices that can't be Azure AD joined or Hybrid joined. So if you are using AADDS then don't update past version 2201 of FSLogix.
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications
The problem is wider then that. My machines ARE Hybrid joined. Even if they're Hybrid joined, you will be prompted every single logon for O365 credentials for SECONDARY (mail) O365 accounts. Granted, that's not a very common use-case but still.
My fix doesn't work for 2210 either. It looks like you can redirect those folders out of FSLogix as much as you want to, FSLogix will still "ignore" them. Obviously they changed something in the behaviour there. Still awaiting MS response on the open Case.
- Did you look at this link? It's actually documented right in their known issues. It doesn't matter how many times you try to work around it 2210 forces this behavior. The only solution I have found is to downgrade back to FSLogix 2201 until Microsoft creates a path forward. Stay on 2201 do not upgrade to 2210.
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications- I have. Still in talks with MS regarding a fix or at the very least a switch to control the behaviour in 2210+.
From 2210+ those 3 folder locations "no longer roam" with FSLogix. The manner in how they do that is unknown to me at the moment. You can still redirect those folders to the local disk and they actually get populated. But it looks like 2210 just ignores them altogether.
My way (only works 2201 and before) is better for persistent VM's: Just use the Microsoft Azure AD broker plugin and dump that info local to the host. Their way requires the user to login everytime on every O365 app. Unworkable in my opinion. But my way only works with persistent hosts so both have their flaws I guess. Will keep the post live with updates from the case. It's being escalated...again.- Supper frustrating. Almost like firing your whole UAT team was a bad idea for Microsoft 🤔🤔.
My last response from Microsoft on my ticket says they will have a hotfix for this but I'm not holding my breath.
Does the change of basic authentication to modern authentication anything to do with it? Microsoft is forcing modern authentication for tenants now.
Ofcourse. With Basic Auth you don't/didn't have any of these issues. It's the way Modern Auth works (token based with Device ID) that's breaking things.
Modern Auth is a good thing, it just creates issues for AVD/VDI that haven't been properly vetted out yet.
