Account locked in 2FA verification loop – phone verification fails – Case --PII REMOVED--

Hi LinuxDistroX64,

Since this is a public forum, we will hide your personal identifiable information, and I have sent that image of yours containing your personal identifiable information in a private message so we can work together to resolve the issue. Also, please check your private message in case you want to share another screenshot to avoid leaking your PII by click on the Private Message button right under your first post.

I really wish I could assist you directly on this issue. However, the behavior you're experiencing is tied to back‑end systems and service functionality, and unfortunately, we don't have the authority or access required to investigate or make changes at that level.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

Given these limitations, I have to say sorry that we do not have the answer for your concern. Since you have already submitted a ticket, please be patient.

Thank you for your understanding, and I hope the support team can resolve this for you soon.

The described behavior matches known conditions where Microsoft’s verification and multifactor authentication protections temporarily block sign-in or specific verification methods after repeated attempts or unusual activity.

From the available information, the following points are relevant:

1. Repeated/blocked MFA attempts
   • Microsoft Entra multifactor authentication and Microsoft account security systems detect unusual activity such as multiple sign-in or verification attempts and can temporarily block further attempts or specific methods. This can surface as errors like “temporary problem with the service” or “Try another verification method,” and can result in a loop where no method succeeds.
   • Guidance in this situation is to:
     • Wait before trying again (the block is often temporary), and
     • Use a different MFA method if one is available.
   References:
   • For work/school accounts, repeated attempts can trigger protection and require waiting or using another MFA method:

     “Microsoft Entra multifactor authentication detects unusual activity like repeated sign-in attempts, and may prevent additional attempts to counter security threats. If you've mistakenly made many sign-in attempts, wait until you can try again, or use a different MFA method for sign-in.”

   • For Microsoft accounts, blocks can occur due to unusual activity, high volume of requests, or other risk signals, and can lead to “Try another verification method” or blocked code delivery.
2. “Try another verification method” and method-specific blocks
   • The “Try another verification method” message is explicitly documented as a symptom of a block tied to a particular verification method:
     • Unusual activity, high volume of requests, or compromised traffic from a region can cause a temporary block on sending or accepting verification codes.
     • Recommended actions:
       1. Try another verification method already configured on the account (for example, switch from SMS to email or vice versa, or to an authenticator app if configured).
       2. Try another network (switch between Wi‑Fi and mobile data, or use a different Wi‑Fi network).
       3. Wait (often at least 24 hours, up to several days) without repeated attempts, because repeated attempts can reset the time lock.
       4. Use the sign-in helper tool to identify the problem and available support options.
3. “Account verification system is having trouble” and invalid responses
   • For work/school accounts with Azure/Microsoft Entra MFA, a similar error (“Sorry, our account verification system is having trouble…”) can be caused by invalid input to the MFA prompt (for example, not pressing # on a phone call, or entering an incorrect code). In those cases, resolution is to:
     • Ensure the correct response is provided (press # on calls, enter the exact code from SMS), and
     • If possible, choose Other verification options and use a different configured method, verifying that phone numbers and other security info are correct in the account settings.
4. When self-service and front-line support are exhausted
   • For consumer Microsoft accounts, support agents are explicitly limited:
     • They cannot send verification codes on behalf of the user.
     • They cannot bypass verification or directly change account security details.
     • If codes are not being received or methods are blocked, the documented options are:
       • Use another verification method already on the account.
       • Wait for temporary blocks to clear (without excessive retries).
       • Use the sign-in helper and standard support channels.
   • For work/school (Microsoft Entra ID / Azure AD) tenants where an administrator is locked out and is the only admin, escalation to specialized internal teams (such as the Microsoft Data Protection team) is used to verify identity and restore access. This is done via a support request and may require phone-based interaction and identity verification. That process is not something the user or forum can perform directly; it is handled by Microsoft support and backend teams.
5. What typically resolves similar cases
   Based on the documented patterns and Q&A examples:
   • Many cases where users see “Try another verification method” or blocked codes resolve after:
     • Waiting long enough for the risk-based block to expire (sometimes a day or more), and
     • Then successfully receiving a code again via phone or email and completing sign-in, after which they add additional verification methods to avoid future lockouts.
   • For administrators of work/school tenants who are fully locked out and are the only admin, resolution occurs through:
     • A support case that is escalated beyond front-line agents to internal teams who can verify identity and restore access.
   • For consumer accounts, when all self-service and normal support options are exhausted and verification still fails, there is no documented mechanism for agents to override MFA or manually grant access; the system’s security model relies on successful verification or the expiration of temporary blocks.

Given that there is already an open and escalated case number, the documented path is to continue working through that support case. For work/school accounts where the user is an admin and locked out, support can escalate to the appropriate internal team (such as the Data Protection team) for backend verification and recovery. For consumer accounts, resolution typically depends on the temporary block clearing and successful use of one of the configured verification methods; agents cannot bypass MFA.

References:

• "Account verification system is having trouble" error message when you try to sign in by using a work or school account
• Common problems with two-step verification for a work or school account
• Troubleshoot Microsoft verification code issues
• 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
• My Microsoft account is blocked. - Microsoft Q&A
• I need to speak with a real person and it seems impossible. - Microsoft Q&A
• I need to reset my mfa methods - Microsoft Q&A