Stuck in an infinite loop of needing to already be signed in to the Authenticator app to approve a sign in FOR the authenticator app.

Anonymous
2023-05-26T16:02:55+00:00

I can't sign in because my account says it need me to approve the sign on in the Authenticator app. HOWEVER, the sign on for the Authenticator app is ALSO saying I need to approve the sign on in the app. So I can't sign in to approve it without already being signed in. SO I am stuck in an infinite loop of it asking me to approve a sign in on my account in an app that I can't sign into without already being signed in!

Microsoft Teams | Microsoft Teams for business | Sign up and Sign in | Sign in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

42 answers

Sort by: Newest
  1. Anonymous
    2024-02-06T21:02:26+00:00

    So this "might" be a fix.

    However, when I tried to open the link in your message (mysignins.microsoft.com/security-info) from my desktop PC, it did ask me to sign into my account, and also approve my sign in on the Authenticator App, which if I was still stuck in the infinite loop, would not have worked. (my IT guy had previously been able to reset all my sign in devices on my account).

    Yet I tried the same web address from my mobile phone web browser and it did just ask me for my password but did not ask me to approve the sign in on the Authenticator App. I am not sure if that is because it only asks for the Authenticator app to be used on some devices, or if it didn't ask on my phone web browser because that is the same device that has the Authenticator App on it. But my desktop that I tried it on first is also already signed into the same Microsoft account on multiple office apps already.

    To further confuse things: My phone had an older password for my Microsoft account saved in the browser, and I had to change it to my current one. Also I had recently upgraded my phone just a week ago and had transferred all my apps and settings from my old phone to the new one, and had never actually opened the Authenticator App on my new phone ever before. So it is odd that the Desktop PC that is signed into multiple office apps and Windows with my current password was the one that asked mt to approve the sign in on the Authenticator, yet the week old mobile phone that had an outdated password saved and had never previously signed into that Microsoft account or into the Authenticator app, was not asked to approve the sign in with 2FA.

    So, way to go on that one Microsoft.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-06T20:16:37+00:00

    I had the same issue and found via my company's IT knowledgebase that one can go to mysignins.microsoft.com/security-info to view the sign-in methods you have listed. My old phone was in there, and I was able to delete it and choose Add Method to add and setup the account on my current phone. The Authenticator app and account had previously been moved over by the transfer when I got my current phone, which is what I think causes the loop issue. I think I did have to remove the account from Authenticator in the current phone before starting the Add Method process above.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-12-27T20:34:09+00:00

    Thanks!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-12-27T03:33:14+00:00

    Hi! I had the same nightmare and was able to call the service center, any MS service number will do. The key is to ask for "AZURE" help when prompted to specify an MS product. This took me directly to a person who was able to assist.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-12-12T19:01:38+00:00

    Redownloading ect did not work for me. I had to contact our service provider and have them fix the issue. 5 minutes and I was able to log in.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments