I miss the days when I could sign in with Google 2FA at work.

Now we are using Microsoft 2FA, and it is a fucking nightmare. Sessions get lost, half of the time the it refuses the login because of who knows why, and when it goes right it is even more cumbersome than Google's.

If your privacy settings are very good, this

"you failed to click on the buses click on these bicycles instead"

could go on for 6 (very slow) rounds and still fail and you have to start again. 🤣

oh, you didn't want to sign-up for the newsletter? Well too late, you're already subscribed.

Oh, you want to unsubscribe? That'll take 5-10 business days

"- would you like to see a list of our 847 partners we share your data with?"

"You can opt out by toggling them individually"

For me the most frustrating was logging into Microsoft Authenticator on a new phone. With no access to the old one.

- You have 2FA configured.
- You must use 2FA to login.
- Cannot use 2FA - Use alternative method.
- To use alternative method, you must login first.

Back to the start
- You have 2FA configured.
- You must use 2FA to login.
- Cannot use 2FA - Use alternative method.
- To use alternative method, you must login first.

Resetting 2FA didn't break the loop. Instead, they still expected me to use Microsoft Authenticator to login to Microsoft Authenticator.

The only way out of this loop was to use Google Authenticator.

Sign in using 2FA hardware token, receive email "We've received a suspicious login! Click here to confirm it's you"

ffs, I used my bleeding hardware 2FA token; yes, it's me.

@lichendust