Authenticator demands code from itself to log into itself

Question

Authenticator demands code from itself to log into itself

G H S 26

I got a new iPhone and restored it from a backup of my old one. But Authenticator's data were not retained, so that's problem #1.

So I attempted to add my account to the app using my work log-in credentials. Upon my entry of them, I was told "Approve sign in request: Open your Microsoft Authenticator app and approve the request to sign-in."

Now... how is that supposed to work?

Even dumber is the link that says, "I can't use my Authenticator app to sign in right now,' which takes you to a page showing only two options:

Approve a request on my Microsoft Authenticator app
Use a verification code from my mobile app

What is the difference between those useless options, by the way?

Pathetic.

Anonymous

2022-02-16T18:58:55.067+00:00

I feel your pain. I have the same problem and have been trying to figure it out for two days. The instructions given don't make any sense and are impossible to implement. I think "pathetic" is a great word for this. It's like a dog chasing it's tail. I get that password code in the Microsoft Authenticator app and have no idea what to do with it. The account I set up in it is a "Personal Account." When I click on it to get into the app, the dog-chasing-tail begins with the dysfunctional password code request.

Sure would like something intuitive from Microsoft for resolving this confusing process.
G H S 26 Reputation points

2022-02-17T05:01:06.253+00:00

The stupidity continues.

It's bad enough that Authenticator fails to retain this information when it's backed up along with other applications' data, although I'm sure Microsoft's excuse for this would be security.

But the workaround is a sham. Authenticator allows you to turn on "iCloud backup." Notice that this says iCloud backup. But Microsoft, in another desperate attempt to get you to sign up for one of their BS accounts, blocks you from using your iCloud account until you do. Make no mistake: There's no technical excuse for this. I've written iOS applications that use iCloud to sync data across devices, and you most certainly do NOT need some janky third-party account.

"Pathetic" covers some of this, but to encompass all of Microsoft's failings here you need inexcusable.
Bridget a'Beckett 5 Reputation points

2024-02-13T00:31:22.45+00:00

I have been stuck in this loop for two weeks and can't get any support. It's ridiculous

Your answer

Anonymous

2022-02-16T18:58:55.067+00:00

I feel your pain. I have the same problem and have been trying to figure it out for two days. The instructions given don't make any sense and are impossible to implement. I think "pathetic" is a great word for this. It's like a dog chasing it's tail. I get that password code in the Microsoft Authenticator app and have no idea what to do with it. The account I set up in it is a "Personal Account." When I click on it to get into the app, the dog-chasing-tail begins with the dysfunctional password code request.

Sure would like something intuitive from Microsoft for resolving this confusing process.
G H S 26 Reputation points

2022-02-17T05:01:06.253+00:00

The stupidity continues.

It's bad enough that Authenticator fails to retain this information when it's backed up along with other applications' data, although I'm sure Microsoft's excuse for this would be security.

But the workaround is a sham. Authenticator allows you to turn on "iCloud backup." Notice that this says iCloud backup. But Microsoft, in another desperate attempt to get you to sign up for one of their BS accounts, blocks you from using your iCloud account until you do. Make no mistake: There's no technical excuse for this. I've written iOS applications that use iCloud to sync data across devices, and you most certainly do NOT need some janky third-party account.

"Pathetic" covers some of this, but to encompass all of Microsoft's failings here you need inexcusable.
Bridget a'Beckett 5 Reputation points

2024-02-13T00:31:22.45+00:00

I have been stuck in this loop for two weeks and can't get any support. It's ridiculous

Share via

Authenticator demands code from itself to log into itself

Your answer