Fix the bugs in the Passwordless Authenticator Experience
There are three major issues with the Passwordless Experience:
Logging in via the web is still sometimes a confusing experience with passwordless enabled.
The "Sign In" page is presented, and the dialog says "We'll send a sign-in request to your phone". But, the sign in request is already sent before the user clicks the button. So, what is happening to our users initially is that they hear/feel the prompt on their phone and go there. It asks for a number. Then they go back to their desktop and have to click the button to "Send notification" even though it's already sent.
2) Our users who tested the passwordless experience get confused, because they visit a website and seamlessly get authenticated into the Microsoft service (as they should). However, a notification is still pushed to the phone. This confuses the users with unnecessary push notifications. It's been 6 months since I brought this up on a previous thread and there's been no movement. This is a blocker for us to adoption.
3) It is easy for a user to stumble into enabling passwordless experience in the app. There is no way to disable it in the app, however. It turns out you have to delete the authenticator connection from the device and website (2 step process) and re-create from scratch. This is cumbersome.
These should all be resolved. Please open a support case if you are still experiencing issues.