Can't log into Azure portal. Had a case out for 47 days. Server has been down for two weeks. HELP!

Chad Vondra 0 Reputation points
2026-03-05T19:33:05.8333333+00:00

My problem is my azure account is under a @hotmail.com account. When attempting to login it asks for Authenticator code. For HOTMAIL accounts MS changed it to 8 digits. Azure ONLY takes 6 digits. When I try to use the alternative 'send a request to the authenticator app' I NEVER receive the message. Like I said I have paid for 'support' under a different account but am being told by the Data Protection Team that they can't help. The Azure support team told me I would receive a call back in 2 hours. That was 3 DAYS ago. Again I have had an open ticket for 48 days now and my linux VM is horked. I need to restore a backup. I keep getting charged for everything but NO ONE seems to be able to help me simply get into my account that I've had since the inception of Azure! I am business DOWN at this point. PLEASE HELP!

Microsoft Security | Microsoft Authenticator

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-03-05T19:33:29.5133333+00:00

    The issue is an account access and MFA problem that cannot be fully resolved with self-service steps in the provided context. The relevant supported options are:

    1. Confirm the correct account type and credentials
    • A single email (for example, ******@hotmail.com) can exist as both a personal Microsoft account and a work/school (Entra ID/Azure AD) account. When prompted, always choose the work/school account for Azure access, not the personal/Microsoft account.
    • If the domain is hosted in Azure, it cannot be used as a “Personal” account for Services Hub and related services. Use the work/school identity when accessing Azure resources.
    1. Use the sign-in helper and verification troubleshooting
    • For sign-in issues with Microsoft accounts, use the sign-in helper tool to diagnose common problems: Sign-in helper.
    • If verification codes are not arriving or are blocked, follow the guidance in “Troubleshoot Microsoft verification code issues,” including:
      • Try another verification method on the account (alternate email, SMS, or app notification) if available.
      • Try another network (switch between Wi‑Fi and cellular, or a different Wi‑Fi network).
      • Wait and avoid repeated attempts if there may be a temporary block due to unusual activity or high volume of requests.
      • Use the dedicated troubleshooter for sign-in issues: Start.
    1. When MFA/verification keeps failing (“having trouble verifying”)
    • If the error is similar to “Sorry, our account verification system is having trouble,” it can be caused by invalid MFA input. In that case:
      • If using phone call, ensure the # key is pressed when prompted.
      • If using SMS, ensure the exact verification code is entered.
      • If multiple verification options are configured, select Other verification options and try a different method, verifying that phone numbers and methods are correct in the account settings.
    1. When locked out and self-service is not working
    • For work/school or partner/tenant scenarios, the documented escalation path is via Microsoft Data Protection / Microsoft 365 Data Protection teams, who have tools to verify identity and restore access when an admin is locked out and no other admin exists.
    • If already working with the Data Protection team and Azure support and the case is open, do not open duplicate cases; wait for the existing case to be processed. If there is a phone support contract, use the published regional support numbers and reference the existing ticket to escalate severity, especially for production-down situations.
    • If the tenant is inaccessible due to inactivity (error AADSTS5000225), the tenant administrator must contact Microsoft via the global support phone numbers within the allowed reactivation window.
    1. If no portal access is possible to open or manage tickets
    • In similar cases where an admin is locked out and cannot open a ticket from the affected tenant, one documented workaround is to:
      • Create a separate trial Microsoft 365/Azure tenant.
      • Use that tenant’s admin center to open a support ticket explicitly stating that access is needed to a different, existing tenant where the admin is locked out by MFA.
      • Provide tenant ID, admin UPN, and error details so support can route the case to the Data Protection team.
    • This workaround does not restore access by itself; it only provides a channel to reach support when the original tenant is inaccessible.

    Given the context, recovery of access to the original Azure tenant and restoration of the Linux VM from backup requires direct action by Microsoft support/Data Protection. The documented path is to continue working with them via the existing ticket and, if necessary, via phone support using the published regional numbers, ensuring that the case is clearly marked as production/business down and that it is routed to the appropriate Data Protection or Azure support team for tenant/account recovery.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.