Unable to login due to Length of Verification code in the Authenticator app and azure login screen does not match

The sign-in prompt and the Microsoft Authenticator app must use the same MFA method and code format. A mismatch between an 8‑digit code in the app and a 6‑digit field in the Azure sign-in page indicates that the wrong verification method or registration is being used, or the sign-in flow is stuck.

Use these steps to resolve:

1. Restart the sign-in and pick the correct method
   • On the Azure sign-in page, when asked for a verification code, choose Other verification options (or similar) if available.
   • Select the method that matches what is configured for the account (for example, push notification approval in Authenticator instead of code, or SMS code instead of app code).
2. Check for blocks or verification issues
   • If the page shows messages like Try another verification method or codes are not accepted, the account may be temporarily blocked due to unusual activity or too many attempts. In that case:
     • Try another verification method linked to the account (alternate email or phone).
     • Avoid repeated attempts; wait up to 24 hours before trying again.
   • See the guidance under How to fix "Try another verification method" error message and I'm not getting my Microsoft account verification code for behavior when verification fails or codes are not delivered.
3. Verify security info and update backup methods
   • Sign in to the Microsoft account security page from a device where access is still available (for example, an already signed-in browser session).
   • Confirm that the phone number/email and sign-in methods are correct.
   • If backup info is outdated or inaccessible, select I don't have any of these during sign-in and follow the prompts to update security info.
4. If still blocked from signing in
   • Use the Microsoft sign-in helper to diagnose sign-in issues and see available recovery options.
   • If no verification method works and access is completely lost, follow the account recovery flow starting from I don't have any of those and complete the recovery process.

If none of the available verification methods match the code format requested on the page, and the account cannot be recovered using the built-in flows, direct support from Microsoft may be required using the sign-in helper and support contact options.

References:

• "We did not receive the expected response" error message when you try to sign in by using Azure Multi-Factor Authentication
• Troubleshoot problems with Microsoft Authenticator
• Troubleshoot Microsoft verification code issues
• Microsoft Invest - Troubleshoot Multi-Factor Authentication (MFA)