Unable to access existing Azure tenant – AADSTS5000224

Open a private browser window and sign in through the tenant-specific Azure portal URL; if AADSTS5000224 persists, only Microsoft Support can investigate and, if the tenant is eligible, restore backend access after verifying ownership.

1. Attempt tenant-scoped sign-in

A closely matched AADSTS5000224 case was resolved by using the tenant-specific portal URL, after which the existing tenant became accessible again.^1^

1. Open a new InPrivate/incognito window.
2. Enter this URL, replacing [tenant-id] with the tenant ID shown on your error page:

      https://portal.azure.com/[tenant-id]
   

3. Sign in with the Microsoft account associated with that directory.
4. If the portal opens, immediately verify:
   • Microsoft Entra ID → Overview shows the intended directory.
   • Subscriptions lists the expected subscriptions.
   • Resource groups contains the expected resources.

If the same AADSTS5000224 error appears, proceed to support escalation. Repeated browser clearing or creating another tenant will not recover this existing directory.

2. Request recovery of the existing tenant

Microsoft classifies AADSTS5000224 as NotAllowedTenantBlockedTenantFraud and explicitly directs affected users to Microsoft Support.^2^ This is not the documented inactivity error, which is AADSTS5000225; therefore, do not apply the inactivity tenant timelines to this case.^3^

Because the affected tenant cannot be used to open a portal case:

1. Contact Microsoft customer support using the public regional support channel.^4^
2. Request an Azure/Microsoft Entra tenant lockout and backend investigation.
3. State clearly:

   AADSTS5000224 prevents every sign-in to the existing home tenant. Tenant-scoped portal sign-in also fails. Please verify tenant ownership and route the case for backend investigation and possible re-enablement. The request is to restore access to the existing tenant and its Azure resources, not to create a new tenant.

Microsoft documents that, during tenant lockout, Support uses a high-assurance ownership-verification process and can help designated Global Administrators regain access to the existing tenant rather than issuing a replacement tenant.^5^ Restoration remains subject to the investigation, ownership verification, and the tenant’s eligibility.

3. Include this evidence in the case

Provide the following privately to Support, not in a public Q&A post:

• Tenant ID and the tenant’s .onmicrosoft.com domain, if known
• Sign-in account and any Global Administrator UPN
• Error code: AADSTS5000224
• Complete error screenshot
• Trace ID, correlation ID, and UTC timestamp from the newest failed attempt
• Azure subscription or billing identifiers and recent invoice details, if available
• Resource names or resource-group names that demonstrate prior control
• Business impact and why access to the existing resources is required
• Confirmation that tenant-specific sign-in was attempted and returned the same error

A matching recovery case required the tenant domain, tenant ID, correlation ID, timestamp, screenshot, and business-impact statement before engineering re-enabled authentication.^6^

Being a Microsoft employee does not replace tenant-ownership verification. Use public customer-support channels unless an existing internal support entitlement provides an approved customer-facing route. Once a case number exists, keep all follow-up under that case rather than opening duplicate requests.

References

1. Azure Sign-in failed with error code AADSTS5000224 - Microsoft Q&A
2. Microsoft Entra authentication and authorization error codes
3. Tenant inaccessible due to inactivity
4. Contact Microsoft customer support
5. Plan for tenant recoverability
6. AADSTS5000224: We are sorry, this resource is not available. - Microsoft Q&A