![]() Having now implemented MFA for a subset of users, I'm also finding Outlook's handling of the new password very patchy several users have needed their loal Windows accounts deleted and recreated to get past the "Loading. I assume it's something to do with the underlying code structure in the Outlook client because Teams (for example) works in the traditional MFA way sign in and await security code / SMS. Surely it negates the whole concept of M/2FA? ![]() This is a minor inconvenience (but also a potential security concern) for me but a complete headache forĪ normal user. I hope I'm missing something, but as far as I can see, I need to store a password should I ever need to reinstall Outlook or log in on another device. I'm looking to roll out MFA to my users but I can't get over the hurdle of the Outlook desktop app password am I the only person who thinks it's stupid at best and outright dangerous at worst?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |