There was an issue looking up your account - Microsoft Authenticator App

Marcelo Leiva 0 Reputation points
2026-06-30T22:32:45.4166667+00:00

Hello,

I have just done a reset to my phone, and I used to have the Microsoft Authenticator app. After doing the reset, I have tried several times to access the app.

However, when logging in and placing my email from Hotmail the logging interface gives an error saying

"There was an issue looking up your account. Tap next to try again".

Have tried different ways, but none works. Have someone had a similar issue? And by any chance do you know how to fix this problem?

#microsoftsecurity #microsoftauthenticator #outlook #outlook.com

1000008215

Microsoft Security | Microsoft Authenticator

1 answer

Sort by: Oldest
  1. AI answer

    2026-06-30T22:33:10.0233333+00:00

    The error in the Authenticator sign‑in screen is a generic account lookup issue, but the underlying problem after a phone reset is usually with the Authenticator setup or your account’s verification methods rather than the email itself.

    Try these steps in order:

    1. Confirm the Microsoft account and domain
      Make sure the address being entered is exactly the one used before (for example, ******@hotmail.com vs ******@outlook.com, and correct spelling of the name). If the address is wrong or belongs to a different domain, the service may not find the account and will show lookup errors. If the correct address still cannot be used to sign in anywhere, start account recovery from the Microsoft account page.
    2. Update Authenticator and device settings
      On the reset phone:
      • Install the latest version of Microsoft Authenticator. Microsoft does not support versions older than 12 months. Use Settings → App updates in Authenticator and make sure updates are enabled.
      • Ensure the phone’s Date & time are correct and set to automatic.
      • Turn off battery optimization for Authenticator and confirm Settings → Notification Settings → Show notifications is on.
      • If using VPN, disconnect and try again.
        These steps address common causes where authentication or account checks fail.
    3. Check for network or notification issues
      • Switch between Wi‑Fi and mobile data to rule out network problems.
      • Make sure the phone is not in Do Not Disturb/Quiet mode and that other apps can receive notifications.
        Network or notification issues can cause sign‑in or verification to fail and lead to messages like “Authentication did not complete.”
    4. Use another verification method to get back into the account
      If Authenticator cannot be set up directly on the reset phone, sign in to the Microsoft account using another method (SMS, email code, etc.) and then re‑add Authenticator:
      • Go to the Microsoft account security page: account.microsoft.com/security.
      • Open Security info or Advanced security options.
      • If Authenticator is listed but not working, remove it.
      • Select Add a new way to sign in or verify → Use an app → Authenticator app and follow the steps to set it up again on the reset phone.
    5. If authentication still does not complete
      When seeing messages like “Authentication did not complete,” check:
      • Authenticator is unlocked (not protected by a lock screen that blocks prompts).
      • The app version is current.
      • Network connectivity is stable.
      • Device date/time are correct.
        If the password itself is forgotten, use the Reset your password option from the sign‑in page.

    If none of these steps work and the account cannot be recovered with alternate verification methods, contact Microsoft Support and use the sign‑in helper or account recovery options referenced in the documentation.


    References:

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

    Was this answer helpful?

    1 person found 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.