Forum Discussion
Outlook login issues with WVD - FSLogix
- Nov 22, 2019
DAsnow this scenario isn't ringing a bell in terms of a common scenario, probably best to contact support on this.
Looking at this thread more closely there could be several issues, we'll have to focus on one for now.
The issue that @FinTechSean is describing is very likely related due to the "registered" vs. "Hybrid Azure AD" status. I think Deanbostedor is spot on.
If I look at our internal selfhost all VMs are in a "Hybrid Azure AD" state and SSO is working in Windows 10 Enterprise multi-session (including Outlook). I can ask our Azure AD team what could result in the "registered" state. That will have to be corrected followed by a FSLogix profile reset.
that must be my problem as well.
- PieterWiglevenApr 02, 2020Former Employee
There are two ways of preventing this:
- For AD joined VMs, follow this guidance on how to prevent the VMs from being registered
- Configure hybrid Azure Active Directory join for managed domains <- preferred
Registering is supposed to be done against another tenant (e.g. user has AADJ device from CompanyA and is registering to the tenant of CompanyB). Registering to the same tenant as the device is AD joined to will cause issues, most likely the ones described in this thread.
VMs can get to this state when a user selects the "use this account everywhere" prompt from an Office app, this can be done by standard (non-admin) users. I'm exploring options to see what we can do to prevent this from happening on Win10 Enterprise multi-session.