A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
During sign-in, Microsoft Authenticator sends the push notification to the device where the app was last actively used for that account. If the app is still active on the old phone, notifications can continue going there instead of the new phone, even though the account is visible on the new device.
For the college account, there is an additional complication: the phone number used for MFA (calls/SMS) is still the old one. Until the security info is updated, verification prompts that use phone (text/call) will go to the old number, not the new one.
To address this:
- If possible, use the old phone once more
- Open Microsoft Authenticator on the old phone and approve a sign-in request.
- After signing in, go to the account’s security/MFA settings and remove the old phone as an authentication method.
- Reconfigure MFA so that the new phone (Authenticator app and/or new phone number) is added as the primary method.
- If the old phone is unavailable or unusable
- Use any other verification method offered at sign-in (for example SMS to a working number, or email, if configured) to get into the account.
- Once signed in, update the security info so that the new phone number and the Authenticator app on the new phone are set up.
- For a work or school (college) account
- If no alternative method works and the old phone cannot be used, contact the college’s IT/helpdesk and ask them to reset MFA for the account. They can clear the old methods so the Authenticator app and new phone number can be registered again.
Going forward, when changing phones or numbers, remove the Authenticator app and old phone number from the account’s security info and add the new phone/number so that notifications and codes are sent only to the new device.
References: