Portal.Azure Authenticator

The issue is consistent with an Authenticator/MFA configuration problem rather than with portal.azure.com itself. Use the following steps to troubleshoot and recover access:

1. Verify Microsoft Authenticator basics
   • Ensure the app is fully up to date. Microsoft does not support versions older than 12 months. Use Settings → App updates and make sure updates are on, or reinstall from the store.
   • Confirm device date/time is set to automatic and correct, then restart the phone. Incorrect time can cause codes and notifications to fail.
   • In Authenticator Settings → Notification Settings, make sure Show notifications is turned on, and disable battery optimization for the app for better sync.
   • If using VPN on the phone or browser, disconnect and try again.
2. Fix “Approve a request” not appearing If the browser says “Approve a request on my Microsoft Authenticator app” but nothing appears:
   • Make sure the Authenticator app is unlocked and open when attempting to sign in.
   • Check that notifications are not silenced (no Do Not Disturb/Quiet mode) and that other apps can receive push notifications.
   • If only this account fails to receive prompts while others work, remove just this Azure account from Authenticator and re-add it using the portal’s MFA setup flow once access is restored (see step 4 for how to get help if you are locked out).
3. Handle the 6‑digit vs 8‑digit code mismatch
   • The 8‑digit “one-time password” in Authenticator is a TOTP code for one sign-in method; the portal is currently expecting a different method (likely a 6‑digit verification code or push approval) configured for Azure MFA.
   • When the portal prompts for a 6‑digit code but Authenticator only shows an 8‑digit OTP for that account, choose Other verification options on the sign-in page if available and try:
     • Use a verification code from my mobile app (then check if Authenticator shows a 6‑digit code entry for that account), or
     • Any alternate method (phone/SMS) if previously configured.
   • If you see the error “We did not receive the expected response,” ensure the correct code is entered and that Verify (not Cancel) is selected in the app.
4. If completely locked out of portal.azure.com
   • If there is another Global Administrator in the tenant, that admin should:
     1. Sign in to the Azure portal.
     2. Go to Microsoft Entra ID → Users → [your user] → Authentication methods.
     3. Select Require re-register multifactor authentication.
     4. You then sign in again and reconfigure Microsoft Authenticator from scratch.
   • If you are the only Global Administrator and cannot access any admin portal to reset MFA, the situation is a tenant lockout. In that case, contact Microsoft Support (Data Protection / Tenant Recovery) by phone so they can verify identity and reset MFA registration for the admin account. This is the supported path when no other admin can reset MFA and no alternate method is available.
5. After regaining access
   • Reconfigure MFA methods at https://aka.ms/MySecurityInfo:
     • Add Microsoft Authenticator (notification/code) and verify it shows the correct 6‑digit code if required.
     • Optionally add a phone call or SMS method as backup so that a future device change does not cause lockout.

Following these steps should restore working MFA with portal.azure.com and align the browser prompts with the codes/approvals in Microsoft Authenticator.

References:

• Troubleshoot problems with Microsoft Authenticator
• "We did not receive the expected response" error message when you try to sign in by using Azure Multi-Factor Authentication
• Authentication methods in Microsoft Entra ID - Microsoft Authenticator app
• Can't set up MFA because five devices are already registered to use an authenticator app
• I have a Micrsoft business account and I am the admin and the only user registered under this account. I can't log in because i have replaced my phone and the authenticator doesn't work. - Microsoft Q&A
• I need to reset my mfa methods - Microsoft Q&A
• Global Admin Locked out - Microsoft Q&A
• Severity A Situation - Locked out of global admin account (MFA) - business down - Microsoft Q&A