I'm afraid this is not at all likely to happen.
Unlike other authentication methods, this relies on making an API call to Microsoft's servers to verify your code. It can lock you out of our site if any network event beyond our control occurs. This will it only frustrate you but will increase the support load for us DevOps staff.
This API call has changed dramatically over the last three years which means that this is a high maintenance solution. Disruptions in the API stability will lock you out and create emergency events for DevOps which are not pertinent to our core business.
Moreover, the multi step setup process requires a lot of work to implement and creating an arbitrary endpoint on our server which we would rather. It have to do.
All these combined with the very limited popularity of this solution across our user base makes it an unattractive solution. In short, it will cost and cause disruption without any palpable benefit. Please use an alternative second step verification method. The six digit code is an actual Internet standard, there are universally available applications for all conceivable platforms, even the now dead Blackberry, and is even supported by Microsoft itself.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!