How to Move Microsoft Authenticator to a New Phone (Change Your MFA Phone Number)
You picked up a new phone and now Microsoft 365 sign-in prompts never arrive. The Approve sign-in request screen sits waiting while the notification goes to a phone in a drawer or traded in. In the worst version, the old phone was wiped first and the user is locked out of email entirely.
This affects anyone who upgrades a phone or changes a mobile number while using Microsoft Authenticator for multifactor authentication (MFA) with Microsoft Entra ID (formerly Azure AD). It is one of the most common help desk tickets in Microsoft 365.
Why This Happens
An Authenticator registration belongs to one device, not to the user. Scanning the QR code during setup stores a credential in Entra ID tied to that specific phone. A new phone has no such credential until you register it, so Entra ID keeps pushing notifications to the only device it knows.
Backup and restore is designed for personal accounts. Authenticator backs up to iCloud on iPhone or to a personal Microsoft account on Android. Personal accounts come back, but work or school accounts return flagged as needing action and must be re-added with a fresh QR code, and passwordless phone sign-in is never restored.
Phone number methods are separate from the app. A number registered for SMS or voice is its own method, and changing numbers leaves a dead fallback. Cyber insurers and frameworks such as CMMC increasingly expect app-based or phishing-resistant MFA rather than SMS.
How to Fix It
Method 1: You still have the old phone (the clean path)
Do this before wiping the old device.
- On a computer, open https://mysignins.microsoft.com/security-info (short link
aka.ms/mysecurityinfo), sign in with your work account, and approve the prompt on the old phone one last time. - Install Microsoft Authenticator from the App Store or Google Play on the new phone.
- Click Add sign-in method and choose Microsoft Authenticator. Click Next until a QR code appears.
- In Authenticator on the new phone, tap the plus sign, choose Work or school account, then Scan a QR code, and scan the screen.
- Click Next on the computer. A test notification shows a two-digit number; type it into the app and approve. Number matching is enforced on every push.
- Find the old phone in the list (it shows the device name), click Delete, and confirm. If your number changed, click Change next to the Phone entry and verify the new number.
- Click Change next to Default sign-in method and select Microsoft Authenticator, notification.
- If you use passwordless phone sign-in, open the account in Authenticator and choose Set up phone sign-in; it never carries over.
Method 2: Old phone is gone but you have another method
Open the security info page and sign in. At the push prompt, choose I can’t use my Microsoft Authenticator app right now (or Sign in another way) and pick your phone number, security key, or passkey. Then follow steps 2 through 7 of Method 1.
Method 3: Locked out, administrator required
If Authenticator was the only method, an administrator with the Authentication Administrator role (Privileged Authentication Administrator for admin accounts) handles it in the Microsoft Entra admin center at entra.microsoft.com.
- Verify the person first. MFA reset requests are a top social engineering vector; a widely reported 2023 casino breach began with a call to a help desk. Call the user back on a number already on file, confirm on video, or get their manager to confirm. Never reset MFA from an inbound call alone.
- Go to Identity > Users > All users, open the user, and select Authentication methods.
- Delete the stale Microsoft Authenticator entry.
- Issue a Temporary Access Pass (TAP). TAP must first be enabled under Protection > Authentication methods > Policies > Temporary Access Pass and targeted to the user or a group. Then click Add authentication method on the user’s page, choose Temporary Access Pass, set a short lifetime (one hour is typical) and One-time use, and click Add. Read the pass to the user over the verified channel, never by email.
- The user signs in at the security info page, enters the TAP in place of a push approval, and completes steps 2 through 7 of Method 1.
- If TAP is not enabled, click Require re-register multifactor authentication instead; the user registers fresh methods at next sign-in.
Prevent the next lockout by requiring a second method per user, ideally a passkey or security key, and restricting the Register security information user action with Conditional Access.
How to Verify the Fix Worked
- In a private browser window, sign in to office.com and confirm the number-matching prompt arrives on the new phone.
- On the security info page, only the new device appears under Microsoft Authenticator and the default method points to it.
- Admins: Identity > Monitoring & health > Sign-in logs shows MFA satisfied by Microsoft Authenticator from the expected location.
If It Still Isn’t Working
The QR scan fails or says the account is already added. Remove the work account from Authenticator on the new phone, delete the half-registered entry on the security info page, and scan again. Confirm the phone sets its clock automatically; time drift breaks one-time codes.
Notifications never arrive. Check that Authenticator has notification permission and a data connection, or open the app and approve the request manually. If a Conditional Access policy blocks registration from that location or device, register from a managed device in the office.
Signs of compromise. If an unfamiliar device was added recently or sign-in logs show approvals from places the user never was, this is not a phone swap. Reset the password, revoke sessions, remove all methods, and follow an account compromise procedure first.
How Capital Techies Handles This for Managed Clients
Capital Techies treats an MFA device change as a verified identity event, not a casual reset. Our help desk runs a scripted identity check before touching authentication methods, issues one-time Temporary Access Passes over a verified channel, and requires every user to hold a backup method. Conditional Access on security info registration and Microsoft Defender alerts on unusual MFA registrations are standard in our Microsoft 365 configuration.
The result is staff back to work in minutes, no opening for help desk impersonation, and MFA practices that hold up to cyber insurance, HIPAA, and CMMC review. Learn more about our Microsoft 365 services or contact Capital Techies.
Frequently Asked Questions
Does Microsoft Authenticator cloud backup move my work account to the new phone?
Not reliably. Backup and restore carries personal Microsoft accounts and third-party codes, but work or school accounts come back flagged as needing action and must be re-added with a new QR code, and passwordless phone sign-in is never restored. Register the work account on the new phone from the security info page instead.
I already wiped my old phone and I am locked out. What now?
If you have a second method such as a phone number, security key, or passkey, sign in with that and add Authenticator on the new phone. If Authenticator was your only method, contact IT. An administrator can issue a Temporary Access Pass or require you to re-register MFA after confirming your identity.
Why does MFA still prompt my old phone after I set up the new one?
Both phones stay registered until you remove the old one, and the old device may still be your default sign-in method. On the security info page, delete the old Authenticator entry, update any changed phone number, and set the new device as default.