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

Thanks for the reply with what you discovered Ben. It's likely that might aid some others experiencing the problem realize they also had authenticator configured on a previous phone as well.

As to why the message isn't clearer, as a past network administrator myself, I often experienced similar confusing messages when unexpected situations occur. I'm not trying to defend Microsoft here, just state that in some cases it's not possible for the app involved (i.e., authenticator) to properly identify what's causing it to fail.

That's when only someone who's managed to find the true problem like yourself can help others by telling them what the deeper issue might be.

Rob

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.

Yeah this is greaaaaat design. I immediately asked our admin if we can go back to google apps. Seriously, what's wrong with MS...

2FA is deactivated on our domain. Nobody should have this problem. It has been automatically forced for our company since today. Users are locked out of their account because the authenticator they just installed needs the code from the authenticator which is not set up to set up the authenticator.

Yeah this sentence almost doesn't mean anything with the stupid sh*t MS just sent our way.

Personnally I think we should go back to office 2016 and google apps, if microsoft can just shut down our access like this.

Ben Corr,

I haven't been clear that my aid here mostly relates to the consumer version of the Authenticator app, since this operates differently than when used with the Azure directory back-end used for Work or School accounts and as such, can cause confusion when discussed in these forums intended for consumers.

We can usually determine that Azure is involved when people mention they receive 6-digit rather than the 8-digit codes received by personal account holders, but obviously that's not been mentioned here due to the lack of functionality you're all experiencing.

Since it appears it's likely at least some of you have Work or School accounts, it's really the responsibility of admin or other IT support to deal with these issues, since they should either have some form of direct Microsoft support channel or at least a better idea how to access this than individual users like consumers.

The trouble-shooting for these is also different for the very reasons you've mentioned, so that's not something most here are aware of due to the fact that personal accounts are managed directly by the user himself in their online account profile.

Rob

Yeah this is greaaaaat design. I immediately asked our admin if we can go back to google apps. Seriously, what's wrong with MS...

2FA is deactivated on our domain. Nobody should have this problem. It has been automatically forced for our company since today. Users are locked out of their account because the authenticator they just installed needs the code from the authenticator which is not set up to set up the authenticator.

Yeah this sentence almost doesn't mean anything with the stupid things MS just sent our way.

Personnally I think we should go back to office 2016 and google apps, if microsoft can just shut down our access like this.

Same problem here. What a ludicrous situation for the app that is locking you out to require authentication from the very same app that is locking you out! Did anyone bother testing this app before they unleashed it on the public?!