Azure authenicator issues on personal account

Question

Azure authenicator issues on personal account

Vadim 20

I have a personal and work Azure account using the same email. I have an Azure subscription, which I am using for storage on my personal account.

Starting a few weeks ago, I have been unable to sign in to the Azure portal using my personal account. The Azure login screen is entering Authenicator request mode and expects a 6-digit code for a personal account. Requesting approval doesn't do anything either. I am the only person on that subscription. What can I do?

Sridevi Machavarapu 22,120 Reputation points Microsoft External Staff Moderator

2026-02-09T02:15:47.4566667+00:00
Hello Vadim,

To assist you further and forward this to Microsoft’s Data Protection Team, we need some additional information. As this involves Personally Identifiable Information (PII), please share the following details with us via private message only (do not post publicly):

Contact phone number (including country code)

Contact Email address

Email address (affected account)

Country

Time zone

Tenant domain name (e.g., contoso.onmicrosoft.com or verified custom domain)

Tenant ID

Azure subscription ID or billing information associated with the tenant (this helps confirm ownership)

Language

Once we receive this information, we will forward it to Microsoft’s Data Protection Team for further assistance.
Mukesh D 30 Reputation points

2026-02-09T02:23:51.5833333+00:00
This sounds like one of those situations where Azure gets confused because the same email exists as both a personal Microsoft account and a work (Entra ID) account. I’ve seen this happen before, and usually the login ends up trying to authenticate against the wrong account or MFA setup.

A few things you could try first:

When you enter your email, make sure you explicitly select Personal account if Azure gives you the choice. Sometimes it silently defaults to the work account.

Try signing in using an incognito/private browser window or a different browser altogether. Cached sessions can cause the Authenticator request to go to the wrong identity.

Check your personal account at account.microsoft.com and confirm that the Authenticator app is still linked correctly and that MFA methods are up to date.

When the Authenticator prompt appears, choose use another verification method and enter the 6-digit code manually instead of waiting for approval.

If none of that works, you may need to contact Microsoft support as the subscription owner, because they can reset MFA or help untangle the personal vs work account issue on the backend. Unfortunately, once MFA gets stuck in this loop, it’s not always something you can fix from the user side alone.

Answer accepted by question author

0 additional answers

Your answer

Sridevi Machavarapu 22,120 Reputation points Microsoft External Staff Moderator

2026-02-09T02:15:47.4566667+00:00

Hello Vadim,

To assist you further and forward this to Microsoft’s Data Protection Team, we need some additional information. As this involves Personally Identifiable Information (PII), please share the following details with us via private message only (do not post publicly):

Contact phone number (including country code)

Contact Email address

Email address (affected account)

Country

Time zone

Tenant domain name (e.g., contoso.onmicrosoft.com or verified custom domain)

Tenant ID

Azure subscription ID or billing information associated with the tenant (this helps confirm ownership)

Language

Once we receive this information, we will forward it to Microsoft’s Data Protection Team for further assistance.
Mukesh D 30 Reputation points

2026-02-09T02:23:51.5833333+00:00

This sounds like one of those situations where Azure gets confused because the same email exists as both a personal Microsoft account and a work (Entra ID) account. I’ve seen this happen before, and usually the login ends up trying to authenticate against the wrong account or MFA setup.

A few things you could try first:

When you enter your email, make sure you explicitly select Personal account if Azure gives you the choice. Sometimes it silently defaults to the work account.

Try signing in using an incognito/private browser window or a different browser altogether. Cached sessions can cause the Authenticator request to go to the wrong identity.

Check your personal account at account.microsoft.com and confirm that the Authenticator app is still linked correctly and that MFA methods are up to date.

When the Authenticator prompt appears, choose use another verification method and enter the 6-digit code manually instead of waiting for approval.

If none of that works, you may need to contact Microsoft support as the subscription owner, because they can reset MFA or help untangle the personal vs work account issue on the backend. Unfortunately, once MFA gets stuck in this loop, it’s not always something you can fix from the user side alone.

Answer 1

Sridevi Machavarapu 22,120 Microsoft External Staff Moderator

Hello Vadim,

The issue pertains to a tenant lockout, where no other global admin in the tenant has the necessary permissions to login and make changes in your tenant.

To resolve this, we have engaged our Data Protection team through a support ticket. They will reach out to you via email or phone to help restore access to the tenant and assist in resolving the issue.

Share via

Azure authenicator issues on personal account

0 additional answers

Your answer