Microsoft Authenticator is asking me to authenticate using Microsoft Authenticator to use Microsoft Authenticator

Anonymous
2023-01-28T00:02:56+00:00

So first of all... Why is "microsoft Authenticator" not an option in the "Products" dropdown when choosing where this post should go? I'm just going to choose "Windows"... Sorry not sorry.

Also, I can't take a screenshot on the microsoft Authenticator app without it capturing a black image (thanks,) so here is an extremely low resolution webcam picture of my phone screen.

When I click "Passwords" section on the microsoft authenticator app, I see a button that says "Sign In".

So, I click the button, to sign in. Then, it asks me to authenticate using microsoft authenticator, but I am not signed in, and this is a "sensitive" page, so I have to enter the code displayed into microsoft authenticator, BUT I AM ON MICROSOFT AUTHENTICATOR ALREADY!!! Who designed this terrible app??? Cheap labor resources then you expect us to prefer microsoft edge over Chrome? LOL

Also, when I search my own question in "Bing", it doesn't come up, even if I type the title word for word. Does it go through some sort of not-mentioned approval process before my post becomes actually visible to the public, or is Bing just extremely bad at updating its search results in a timely manner?

Windows for home | Windows 11 | Security and privacy

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

138 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-18T12:16:30+00:00

    Same issue, I am logged out from my account (onedrive, outlook,..) and cant sign in because authentificator app does not receive any codes or aknowledgements. Deleting and reinstalling authentificator app did not help for my account. Installing 2 factor for another account on authentificator worked.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  2. Rob Koch 26,160 Reputation points Volunteer Moderator
    2023-01-28T06:31:37+00:00

    Since the original owner of this thread never selected an answer and it's grown into a mess, I'm modifying my initial post to include a general answer for new readers. It doesn't answer all possible questions as you'll see but does indicate the general problem and solution for Microsoft Personal account users.

    Every post in this thread that mentions a solution that works says exactly the same thing.

    To solve the problem, you need to log into the account using another method other than the authenticator (password or Windows Hello (biometric), or text/email a code, etc.), then delete the authenticator option titled 'Send sign-in notification' from the list of verification methods in the account security section.

    Once you've removed the old, invalid authenticator selection from your account the problem goes away, because it's no longer there to be used and you can set up the new phone's authenticator.

    The reason it happens is simple, you got a new phone and didn't take the time to find out first how to properly switch from one phone to another or couldn't because you lost the old phone.

    For an individual Microsoft Personal account user, the process to fix is as I described above.

    For anyone with either a Work or School account, the answer is similar, but varies depending on the way their account is managed.  The authenticator option, possibly titled; MFA, must either be deleted or disabled. Once this is done it will allow setting up a new authenticator to take its place.

    The problem with Work or School is really who needs to do this, since typically it's the administrator of the organization, who may be an IT department, but for small firms may be the account owner himself, which means they might need Microsoft Support's help if they can't get into the account without the old authenticator to fix it.

    I won't try to explain the Work or School possibilities here, since the answer is 'it depends'.  There's simply too many possible people and/or management interfaces involved and no one but you could possibly have that information, so it's pointless to try and answer in a single post.

    My only recommendation is simple, see your Administrator.  If you're the Admin, contact Microsoft Support. If you prefer, read through the other posts in this thread to see if someone else's situation sounds similar to yours.

    Rob


    All text below this point was from my initial post before we understood the above, which I'm leaving only to provide the history that supports some of the posts that follow. There's no reason to read it for most, since it's didn't truly fix the problem.

    <<<<<<<<<<<<<<<< Original text of post >>>>>>>>>>>>>>>

    Do you have a biometric login option set on your phone like your image or fingerprint reader?

    With that method enabled on my phone, I'm always prompted for my fingerprint each time I reopen the app, even if I just minimize it, but I can move between selections on the bottom bar without a new challenge while it's open. Been a couple years since I set mine up, but don't ever recall seeing an option to sign-in displayed.

    Also in Settings (3 vertical dots at top right of app) is a selection under Security called Screen Capture that allows apps to do that, I assume that would work for your purpose, though it's a security risk during normal operation.

    Don't know how fast the new threads are indexed, but typically they'll be on the top page for the better portion of a day, and you can always click the login option near the upper right of this screen and select 'My Profile' from the drop-down that appears to see a list of the threads you've posted to, including your own, as you scroll down that page. Few ever get here by search, so your questions will typically be answered by volunteers like me or contract workers with a Microsoft tag, so visibility via search is unimportant anyway.

    Rob

    < EDIT > Now that I think about it, you don't have your initial Microsoft account setup in Authenticator yet, which is why you're getting that prompt. If you're setting up a personal account like mine, here's the simple page for one of those.

    How to use the Microsoft Authenticator app - Microsoft Support

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-04-27T06:05:12+00:00

    I got a similar problem today when I got a new phone, because the old one crashed, and never came back from oblivion. On my new phone I installed the Authenticator app, but to login to that I have to confirm using the Authenticator app, which I no longer have access to on the old phone. There are NO other options for login. Just Authenticator, not email, not SMS, not anything..

    This is just ****.. and yes I should have backed up the old one to the cloud, but I didn't know that was an option before now..

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-04-26T02:20:43+00:00

    New person to the thread here. Having exact same issue. I am prompted by the Microsoft Authenticator app to authenticate via the same Authenticator app. Haven't seen any actual fixes in this thread... Any ideas how to fix?

    This is extremely poor design. Classic Microsoft.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-03-30T07:44:07+00:00

    Hey Rob,

    Thanks for your answer. I must say I was a bit salty yesterday, and maybe I was not the most diplomatic. In the meantime our admin has managed to stop 2FA.

    I also now understand why the issue happened. The user had an authenticator previously configured on another phone, but didn't remember it.

    But the message should be more clear. When I try to set up the authenticator, and it asks me for authenticator authorization, I feel like I am in the world of Kafka. It should have a different message in this case, so it does not feel like a bug. But anyway, it's solved on our end.

    Ben.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments