Share via

Cannot login into Azure (Visual Studio Enterprise) using Microsoft Authenticator due to broken MFA

Yue Xie 20 Reputation points
2026-03-05T13:50:23.6566667+00:00

Hello Support,

I am locked out of my personal Azure account (MSA) that is backed by my Visual Studio Enterprise (MSDN) benefit, and I need assistance resetting Azure MFA.

Issue Summary

  • Personal Microsoft account (MSA), used for Visual Studio Enterprise
  • Unable to complete Azure MFA
  • Microsoft Authenticator app shows 8 digit codes, but Azure is prompting for a 6 digit code
  • Push notifications never arrive
  • The "use another verification option" link does not appear
  • I can sign into my Microsoft account for non-Azure services, but Azure Portal login fails at MFA
  • The MFA reset page only works for Work/School accounts and does not apply here

Impact

  • I cannot access the Azure Portal
  • I cannot manage subscriptions/resources

Based on similar cases, this appears to be a tenant lockout / broken Azure MFA state for a personal Azure tenant where there is no alternate Global Admin.

Request

Please assist with resetting Azure MFA for this personal account or engage the Data Protection team to restore access.

Microsoft Security | Microsoft Entra | Microsoft Entra ID

Answer accepted by question author
  1. VEMULA SRISAI 11,330 Reputation points Microsoft External Staff Moderator
    2026-03-20T17:09:53.8433333+00:00

    Hello Yue Xie,

    We engaged our Microsoft Data Protection team by raising a support ticket, and the issue has now been resolved by them. Could you please check and confirm whether you are now able to sign in successfully?

    If the issue is confirmed as resolved, kindly revisit this thread and click “Accept Answer”, as this may help other community members facing similar issues.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-05T13:50:43.28+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    For a personal Microsoft account (MSA) used with Azure where Microsoft Authenticator is in a broken state and there is no alternate admin or MFA method, self-service recovery is not available. Resetting or clearing MFA for that account requires intervention from Microsoft support and, specifically, the Data Protection/Tenant Recovery team.

    Actions to take:

    1. Because this is an MSA-backed Azure tenant with no other Global Administrator and no working MFA method, treat this as a tenant lockout scenario.
    2. Contact Microsoft support by phone and request that a support case be opened with the Data Protection team (sometimes referred to as Data Protection/Tenant Recovery) to:
      • Verify ownership of the personal account and associated Azure subscription, and
      • Reset or clear the Azure MFA registration for that account.
    3. When speaking with support, clearly state:
      • The account is a personal Microsoft account (MSA) with Visual Studio Enterprise/ MSDN benefits.
      • Azure sign-in fails at MFA because the Authenticator app only shows 8‑digit codes while Azure is prompting for 6‑digit codes, push notifications do not arrive, and there is no “use another verification option” link.
      • There is no alternate MFA method and no other Global Administrator on the tenant.
      • This is a tenant lockout and you need escalation to the Data Protection team to reset MFA.
    4. Be prepared to provide any ownership and identity verification information that support requests (billing details, subscription information, identity documents, etc.), as the Data Protection team must confirm that the requester is the legitimate owner before resetting MFA.

    The behavior described (no alternate verification options, no other admin, and broken Authenticator flow) matches the lockout scenarios in which moderators and support engineers escalate to the Data Protection team to restore access and reset MFA.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.