Can someone help me fix this kind of issue. Microsoft Authenticator app displays an 8-digit code instead of a 6-digit one,

For Azure sign-in, a work or school account protected by Microsoft Entra multifactor authentication must use the exact MFA method that was configured for that account. If the sign-in prompt expects a 6‑digit one-time password (OTP) but the Microsoft Authenticator app is showing an 8‑digit code, that code is not the correct factor for the Azure sign-in being attempted and will not work.

When the configured MFA method does not match what is available on the device (for example, wrong OTP format, wrong account entry, or missing OTP at all), the only supported way to fix access for a work or school account is to have the MFA registration reset from the directory side and then re-register the app.

For a work or school (Microsoft Entra ID) account, the supported paths are:

1. If another global admin exists in the tenant:
   • A global admin can require re-registration of MFA for the affected user so that the Microsoft Authenticator app can be set up again from scratch with the correct OTP format and method. This is done in the user’s authentication settings as described in the “manage user authentication options” documentation referenced in the context.
2. If there is no other global admin and the only global admin is locked out:
   • This is treated as a tenant lockout scenario. In such cases, Microsoft support must escalate to the Data Protection team. That team verifies tenant ownership using business documentation and then resets the MFA configuration from their side so that the admin can regain access and reconfigure Microsoft Authenticator correctly.
   • The documented resolution pattern for similar cases is: open a support ticket, have it escalated specifically to the Data Protection team, and work with them to restore access and reset MFA. Frontline support or standard queues cannot bypass MFA or provide codes; only the Data Protection team can reset MFA after identity verification.
3. If the Microsoft Authenticator app itself appears to malfunction (for example, not showing the expected OTP type for a configured account):
   • Logs can be sent from the app to Microsoft support, and an incident ID obtained:
     1. Open Microsoft Authenticator.
     2. Tap Send feedback in the top menu.
     3. Select Having trouble?.
     4. Fill out the form and select Send.
     5. Note the incident ID and provide it to support so they can correlate logs with the support case.

If support cases are being closed without resolution while access to Azure resources is still blocked, the next step is to open a new support request and explicitly request escalation to the Data Protection team for an MFA reset/tenant lockout scenario, providing any prior incident IDs and the Authenticator incident ID from the app.

Once MFA is reset by an admin or the Data Protection team, sign in again, follow the MFA setup prompts, and re-add the work/school account in Microsoft Authenticator so that the correct OTP (6‑digit or push approval, depending on policy) is generated for Azure sign-in.

References:

• Common problems with two-step verification for a work or school account
• Send Microsoft Authenticator logs and get an incident ID
• I need to reset my mfa methods - Microsoft Q&A
• Severity A Situation - Locked out of global admin account (MFA) - business down - Microsoft Q&A