This message was deleted.

I have customers using it with success and no complaints - I've seen strange references to fslogix redirections exclusions as well as custom scripts registering the appX packages to mitigate the issue - but I'm not sure on the full use case for those @Kasper Johansen seems to have a good handle on it

Tested further by ensuring a hybrid join exists but i'm still seeing Wamdefaultset=no when running dsregcmd /status as a published app. Tried the powershell in this to register the AAD package but still no luck. https://discussions.citrix.com/topic/403721-office-365-pro-plus-shared-activation-password-screen-not-able-to-select/page/9/

I resolved it by setting the keys as described here (even though they're not recommended by Microsoft) https://support.citrix.com/article/CTX267071 Be aware that in my scenario, i had to set the registry keys on fresh profiles. Modifying/adding these registry keys on already existing profiles didn't help, so i ended up resetting profiles before rolling out these keys. I had to do it this way because i couldn't get the powershell method to work either

As a follow up, we ended up getting success with the registry keys like the article suggests - fingers crossed no long term issues persist.

If you want to modify existing profiles you need to delete the HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity, we did this when adding those keys from the CTX article and it worked. This is anecdotal and I've not been able to confirm for sure, but we found it seemed to affect users with MFA enabled and not those without MFA.