Hardware OATH tokens in Azure MFA in the cloud are now available

Michael McLaughlin , "Activating OATH doesn't change any credentials already registered for a user! It just sets OATH as their default MFA method"

Editing my comments (maybe something was fixed recently :) ) , I confirm importing MFA does not break SMS/Phone MFA method.

However, it is not setting OATH token as primary MFA method, after activating the token I still had the phone as my primary method (which is fine). Also, the login page asks for "mobile authenticator", although the OTP from the token was accepted with no issues.

On the figure below, what the page asks for is, in fact, a code from my token, not my app 

On the aka.ms/mfasetup page  the name of the profile is made of the token name and its serial number.

On the same page, users can change the default MFA method from phone to token, but again, the there is no "OATH token" in the list, it still says  "app"

It is also important to mention that multiple MFA devices work transparently fine, in addition to the hardware token I managed to add a mobile app profile (Google Authenticator) and it worked just fine, accepting both the hardware token and app-generated OTP without any issues.