A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The 6‑digit vs 8‑digit mismatch means the Azure sign‑in page is expecting a different MFA method than the one currently configured in Microsoft Authenticator. Because portal access is blocked, resolution depends on whether there is another admin who can reset MFA for the account.
- If there is another admin in the tenant
- Ask a Global Administrator (or another cloud services admin) in the tenant to reset the MFA settings for the affected account.
- The admin signs in to the Azure portal and opens Microsoft Entra ID.
- Go to Users and select the locked‑out user account.
- Open Authentication methods and select Require re-register multifactor authentication.
- Save the change.
- Next time sign‑in is attempted, the account will be prompted to set up MFA again. During this re‑registration, configure a working method (Microsoft Authenticator push, correct OTP type, and/or phone number) and then use that method to complete sign‑in.
- If there is no other admin and this is a tenant lockout
- When the only Global Administrator is locked out and no one else can reset MFA, the case must be handled by Microsoft support/Data Protection.
- Open a support request from any channel that does not require the locked‑out account (for example, another tenant or a different Microsoft subscription) and clearly state that this is a tenant lockout / global admin locked out due to MFA so it can be escalated to the Data Protection / Tenant Recovery team.
- That team will verify tenant ownership (using business documentation and contact details) and then reset MFA registration for the locked‑out admin so access can be restored.
- If the phone or number was changed or lost
- If the issue started after losing the phone or changing the phone number, another cloud services admin must reset the MFA settings for the account so that contact methods can be re‑entered, as described above.
Until MFA is reset and re‑registered, sign‑in to review Azure Monitor alerts and payments will remain blocked. Support agents cannot send verification codes or directly change account details; they can only work through the formal tenant recovery/Data Protection process.
References:
- Can't use Azure Multi-Factor Authentication to sign in to cloud services after you lose your phone or the phone number changes
- Troubleshoot Azure Multi-Factor Authentication issues
- Troubleshoot Microsoft verification code issues
- "We did not receive the expected response" error message when you try to sign in by using Azure Multi-Factor Authentication
- Global Admin Locked out - Microsoft Q&A
- 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
- Azure has blocked myphone number for SMS verification due to a “bad reputation” flag - Microsoft Q&A