Authenticator App accounts/e-mails (urgent matter)

Jonas Bjarnøe 0 Reputation points
2026-03-27T10:50:50.6133333+00:00

Hi there

I have an old iPhone 12 with the Autenticator app working. At least it dit until yesterday. But cant figure out what's going on now.
Now I bought an iPhone 17 and in the app I can see all the accounts, but I'm not able to login.

This is quite urgent!

Thanks

Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-03-27T10:51:12.6766667+00:00

    Follow these steps to get Microsoft Authenticator working on the new iPhone and regain sign-in access.

    1. Verify the old iPhone still works for MFA
      • If the old iPhone 12 still has Authenticator working, use it to approve any current sign-in prompts while fixing the new phone.
      • Do not erase or reset the old phone or remove Authenticator until sign-in works reliably on the new phone.
    2. Check why sign-ins are failing on the new iPhone Common causes when accounts show in the app but sign-in fails:
      • Push notifications are not arriving or not alerting.
      • The app is out of date.
      • Device/network settings are blocking Authenticator.
      On the new iPhone:
      1. Make sure the device has a working internet connection (try switching between Wi‑Fi and mobile data).
      2. Open Authenticator → Settings:
        • Ensure App updates are enabled and that the app is updated to the latest version.
        • Turn off battery optimization (if available in Settings) to improve sync and notification performance.
        • Go to Notification Settings and confirm Show notifications is turned on.
      3. In iOS Settings → Notifications → Authenticator, confirm alerts, sounds, and badges are allowed.
      4. Ensure the device Date & time are set automatically and correctly.
    3. If push notifications are going to the wrong device
      • When registering or approving a credential, the push may still be sent to the old iPhone if that was the last device used.
      • On the old iPhone, open Authenticator and check if an approval prompt is waiting there.
      • After gaining access, follow the FAQ steps ("How do I make sure notifications don't go to an old device?") to remove the old device from the account security settings so new prompts go only to the new iPhone.
    4. If the backup did not restore correctly on the new iPhone If the accounts appear but do not work, or some are missing, re-check the backup/restore setup: On the old iPhone 12:
      1. Turn on iCloud Drive.
      2. Turn on iCloud Keychain.
      3. Turn on iCloud Backup and, in the Saved to iCloud list, ensure Authenticator is enabled.
      4. Make sure Authenticator is version 6.8.33 or later.
      5. Open Authenticator at least once (to ensure the latest backup is written).
      On the new iPhone 17:
      1. Uninstall Microsoft Authenticator.
      2. Reinstall Microsoft Authenticator from the App Store.
      3. Sign in with the same iCloud/Apple ID and recovery account used on the old phone.
      4. Open Authenticator and check for the backup; restore it when prompted.
      Note: Backups cannot be moved between Android and iOS; they must both be iPhones using the same iCloud account.
    5. If sign-in still fails for specific accounts
      • For work/school accounts: the organization may require re-registration of MFA. Use the old iPhone to approve a sign-in, then go to the account’s security/MFA setup page and re-add the account to Authenticator on the new phone using a QR code.
      • For personal Microsoft accounts: if verification codes or notifications are not working, use the guidance in the verification-code troubleshooting article linked from the FAQ.
    6. If completely locked out and no method works
      • For personal accounts: follow the account recovery and verification-code troubleshooting guidance referenced in the Authenticator FAQ.
      • For work/school tenants where there is only one global admin and that admin is locked out, a Data Protection team case via Microsoft Support is required. This is done by calling the regional Microsoft support number and asking to open a ticket for MFA reset/tenant lockout so the Data Protection team can verify identity and reset the admin’s authentication methods.

    For an urgent business/tenant lockout where no admin can sign in, the documented resolution path is to:

    • Contact Microsoft Support by phone (Global Customer Service phone numbers) and clearly state that this is a tenant admin MFA lockout and there is no other global admin.
    • The frontline agent escalates to the Data Protection team, who will verify identity and reset MFA for at least one admin account.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.