A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Notifications are still going to the old device because the Authenticator app on that phone is still the last one registered for push approvals.
To use the new phone while away from the old one, try these options:
- Use an alternate verification method (if configured)
- On the sign-in screen where the notification is requested, choose “Use a different verification method” (such as SMS or another method) and complete sign-in that way.
- Once signed in, go to your account security/MFA settings and add or reconfigure the new Authenticator app as an approved method.
- If alternate methods are not available or fail
- You must wait until you have access to the old device again, open Microsoft Authenticator on that device, and approve the sign-in.
- After signing in, remove the old device from your account security settings and re-register the Authenticator app on the new phone so future notifications go only to the new device.
- Prevent this in the future
- Before switching phones, remove Authenticator from old devices in your account security settings.
- Keep the device list up to date in your account security settings.
If you are not receiving any notifications at all on the new phone even after it is correctly registered, also check:
- Device notification settings
- Ensure the phone is not in Do Not Disturb/Quiet mode.
- Confirm notifications are enabled for Microsoft Authenticator in the phone’s Settings (including sound/vibration if desired).
- General notification and network health
- Verify other apps can receive notifications.
- If not, troubleshoot the phone’s network connection or the Android/Apple notification channel (may require help from the mobile provider).
- Per-account issues
- If some accounts in Authenticator receive notifications but others do not, remove the problematic account from the app, add it again, and allow notifications during setup.
References: