The red no sign pops up when I’m trying to do the two factor authentication, why? What can I do to fix this?

The red “no” sign and “something went wrong” during MFA usually mean the current verification method is blocked or failing, often due to unusual activity, too many attempts, or a problem with the specific method (SMS/email/app) rather than your password.

Try these steps in order:

1. Wait and avoid repeated attempts

• Multiple failed or repeated MFA attempts can trigger a temporary security block where codes are not sent or accepted.
• Stop trying for a while and do not keep resending codes; this can extend the block.
• If you’ve already tried many times, wait up to 24 hours before trying again.

2. Try another verification method

• On the MFA prompt, look for an option like “Sign in another way” or “Try another verification method”.
• If available, choose a different method than the one failing (for example, use email instead of SMS, or use the Authenticator app instead of SMS/email).
• If you don’t see any alternative method, it usually means no backup method was set up; in that case, contact your organization’s IT/admin.

3. Check for common code‑delivery issues If you’re using SMS or email codes:

• Make sure the phone number or email shown (masked) is correct.
• For SMS:
  • Confirm the phone is on, has signal, and can receive texts.
  • Ensure the number is a mobile number, not VOIP; VOIP numbers cannot be used for verification codes.
  • Check that the device is not blocking texts from unknown senders.
• For email:
  • Check junk/spam for messages from @accountprotection.microsoft.com.
  • Mark @accountprotection.microsoft.com as a trusted sender.

4. If you see messages like “We cannot send a text message to this number” or “Try another verification method”

• This usually indicates:
  • Temporary block due to unusual activity or high volume of requests, or
  • Issues with your region/network.
• Actions:
  • Switch network (e.g., from Wi‑Fi to mobile data or to a different Wi‑Fi).
  • Use a different verification method already configured on the account (Authenticator app, alternate email, office phone, etc.).
  • Wait at least a day without repeated attempts if the block persists.

5. If you don’t have your phone or the Authenticator app anymore

• If the phone with the Authenticator app is unavailable and no alternative method is configured, the only resolution is through your organization’s IT help desk or admin.
• Ask them to reset your MFA settings in Microsoft Entra so that you can register MFA again on your current device.

6. If nothing works and you still can’t sign in

• For work or school accounts: contact your organization’s help desk or Microsoft 365/Entra administrator and ask them to check sign‑in logs and reset your MFA methods.
• For personal Microsoft accounts: use the sign‑in helper and support options described in the verification-code troubleshooting article.

References:

• Common problems with two-step verification for a work or school account
• Use a screen reader to set up and troubleshoot multifactor authentication
• Troubleshoot Microsoft verification code issues
• Microsoft Curate - Troubleshoot Multi-Factor Authentication (MFA)
• 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
• Authenticator app not sending code to my email - Microsoft Q&A
• Having problems getting text codes to confirm my account - Microsoft Q&A
• Microsoft authenticator sending me into a spiral - Microsoft Q&A