A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The symptoms indicate an issue with the browser-based sign-in/MFA experience rather than with the account or Azure itself, since Azure CLI sign-in works.
Try these steps in order:
- Clear browser sign-in state
- Sign out of all Microsoft accounts in the browser.
- Clear cookies and site data for Microsoft/Azure sign-in pages (for example,
login.microsoftonline.com,portal.azure.com,microsoft.com). - Close all browser windows and reopen the browser.
- Try signing in to the Azure portal again.
- Check for browser security/HSTS issues
- If using Microsoft Edge and you see security warnings (for example, “The connection for this site isn't secure”) when Azure CLI or other tools try to open sign-in pages, remove any HSTS policy for
localhost:- In Edge, go to
edge://net-internals/#hsts. - Under Delete domain security policy, enter
localhostand select Delete.
- In Edge, go to
- Then retry the browser sign-in.
- If using Microsoft Edge and you see security warnings (for example, “The connection for this site isn't secure”) when Azure CLI or other tools try to open sign-in pages, remove any HSTS policy for
- Align MFA method and prompt
- The “Enter a code” prompt expects a specific type of code (for example, a 6‑digit TOTP code or a number match) that must match the method configured for the sign-in.
- If the prompt is expecting a shorter code than what Authenticator shows, cancel that attempt and explicitly choose Sign in another way, then select the method that matches what Authenticator is configured for (for example, push approval/number match rather than code entry).
- Since push approvals are not arriving, focus on getting a clean sign-in session (steps 1–2) so that the correct MFA prompt is shown.
- Use a different browser or in-private session
- Try signing in from a different browser (or an InPrivate/Incognito window) on the same machine. If it works there, the issue is with cached state or extensions in the original browser.
- If Conditional Access/MFA policies are involved
- If the tenant has Conditional Access policies requiring MFA, ensure that MFA is enforced at sign-in and not only at resource access. Misalignment can cause repeated or mismatched MFA prompts.
- If errors mention “Interactive authentication is needed” or “MFA is required,” follow the guidance to ensure MFA is satisfied at sign-in.
If none of the above resolves the issue, an administrator can temporarily reset MFA registration for the account from the Microsoft Entra admin center so that MFA methods can be re-registered cleanly.
References: