Azure wants 6 digits code but Authenticator generates 8 digits

Question

Azure wants 6 digits code but Authenticator generates 8 digits

Scott Friedman 0

I'm trying to login into my Azure account but it wants a 6-digit code from Microsoft Authenticator but Authenticator generates a 8-digit code. I tried to remove my account from Authenticator, remove and create password, turn on and off 2-factor authentication but nothing worked. I still can't login to Azure. I can login everywhere else like Outlook, Microsoft 365 Copilot but not Azure.

I can login to my Azure account via the Azure CLI - which is strange.

How to resolve this?

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-23T04:54:44.3733333+00:00

Hello Scott Friedman

Based on your description, it seems that you are unable to verify your custom domain in your Entra ID tenant, even after correctly adding the TXT records in your domain provider side.

This issue often occurs when the domain has already been verified in another Entra directory, as explained in the following document: Common verification issues

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: Customer service phone numbers - Microsoft Support.

If it doesn't work for you, please don’t worry—let us know, we are happy to assist you further!
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-24T07:31:03.1733333+00:00

Hello Scott Friedman Following up to see if you were able to create the support ticket, otherwise please let us know, we are happy to assist you further!

1 answer

Your answer

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-23T04:54:44.3733333+00:00

Hello Scott Friedman

Based on your description, it seems that you are unable to verify your custom domain in your Entra ID tenant, even after correctly adding the TXT records in your domain provider side.

This issue often occurs when the domain has already been verified in another Entra directory, as explained in the following document: Common verification issues

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: Customer service phone numbers - Microsoft Support.

If it doesn't work for you, please don’t worry—let us know, we are happy to assist you further!
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-24T07:31:03.1733333+00:00

Hello Scott Friedman Following up to see if you were able to create the support ticket, otherwise please let us know, we are happy to assist you further!

Answer 1

The 8‑digit codes in Microsoft Authenticator indicate that the account is configured with an incompatible or stale MFA/sign‑in method for Azure Portal, even though it still works for other services. The Azure MFA profile for this account is likely stuck and must be reset from the tenant side so that new, correct methods (including 6‑digit codes or push notifications) can be registered.

Resolution requires an administrator in the tenant to reset the MFA registration for this user, then the user signs in again and reconfigures MFA:

A Global Administrator (or another admin) signs in to the Microsoft Entra admin center.
Go to Identity → Users → All users.
Select the affected user account.
Open Authentication methods.
Select Require re-register multifactor authentication.
Save the change.

After this, sign in to the Azure Portal again with the affected account. The sign‑in flow will prompt to set up MFA from scratch (for example, re‑adding Microsoft Authenticator or a phone method). This will register a fresh, compatible MFA configuration so that the correct verification options (including 6‑digit codes or push/prompt) are used for Azure sign‑in.

If the affected account is a guest in another tenant, an admin in that tenant must perform the same Require re-register multifactor authentication step on that guest user object.

If there is no other admin and this is the only admin account, create or use another admin account (as was done in the referenced scenario) to perform the reset, then reconfigure MFA for the original account.

References: