With office phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the user is prompted to press # on their keypad. With phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the verification code provided is entered into the sign-in interface. With text message verification during SSPR or Azure AD Multi-Factor Authentication, an SMS is sent to the mobile phone number containing a verification code. Microsoft doesn't support short codes for countries / regions besides the United States and Canada. In the interest of our users, we may add or remove short codes at any time as we make route adjustments to improve SMS deliverability. Microsoft doesn't guarantee consistent SMS or voice-based Azure AD Multi-Factor Authentication prompt delivery by the same number. Administrators can see this information in the user's profile, but it's not published elsewhere. Instead, users should populate their Authentication Phone attribute via the combined security info registration at. If users don't want their mobile phone number to be visible in the directory but want to use it for password reset, administrators shouldn't populate the phone number in the directory. Mobile phone verificationįor Azure AD Multi-Factor Authentication or SSPR, users can choose to receive a text message with a verification code to enter in the sign-in interface, or receive a phone call. Even in the +1 4251234567X12345 format, extensions are removed before the call is placed.

Password reset and Azure AD Multi-Factor Authentication don't support phone extensions.

There needs to be a space between the country/region code and the phone number.

Ms authenticator change phone