I've started implementing Passkey for some clients, and it's been going smoothly so far. We've been able to use Windows Hello for Business, hardware FIDO2 keys, and Microsoft Authenticator without any issues. However, I've hit a snag with one customer who doesn't have Windows Hello for Business and is relying solely on Microsoft Authenticator. When they try to log into Outlook Classic, they only see a login prompt for hardware tokens, which is frustrating because there's no option to switch to using QR codes or Bluetooth like you can with all the other Microsoft apps and browsers. Why is Outlook Classic different? I haven't found an alternative solution that works besides Windows Hello for Business for this client because of the legacy plugins required in Outlook. Also, some users are still on Windows 10 with extended support, which seems to be part of the problem. Any insights on this?
1 Answer
I ran into the same issue with Outlook Classic, but I managed to log in just fine using my authenticator app’s passkey with QR code and Bluetooth. What version of Outlook Classic are you using? It could be a version conflict. I have colleagues who are using M365 Business Premium with Outlook 365, and it works well for them. Let me know, and we can troubleshoot this together!
Thanks for your reply! I'm looking into the version difference. I believe the users affected are still on Windows 10 with Extended Support. I’ll try it again on Windows 11 to see if it makes a difference. Appreciate your input!