Azure "Sing-in failed" (tenant has been blocked due to inactivity)

Fabián Alarcón 0 Reputation points
2025-11-12T21:32:07.88+00:00

Hi,

I‘ve got „Sign-in failed“ error.

Error code: AADSTS5000225

Error message: AADSTS5000225: This tenant has been blocked due to inactivity. To learn more about tenant lifecycle policies, see https://aka.ms/TenantLifecycle Trace ID: 801fee8b-1d23-427f-a552-da6d9e013a00 Correlation ID: 087ce7a4-5b37-480a-8fd3-f36c8267673c Timestamp: 2025-11-12 21:28:44Z

tenant id: <PII REMOVED>

client id: <PII REMOVED>

email: <PII REMOVED>

Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} votes

2 answers

Sort by: Most helpful
  1. Shubham Sharma 3,830 Reputation points Microsoft External Staff Moderator
    2025-11-12T21:43:20.75+00:00

    Hello Fabián Alarcón

    Thank you for reaching out to Microsoft Q&A.

    The error message you encountered indicates that your tenant has been inactive for over 200 days past the billing cycle, triggering Microsoft’s effort to remove inactive tenants. When a tenant remains inactive for this period, the OMS commerce system imposes a login block (AADSTS5000225). Twenty days after the login block is applied, the tenant is permanently deleted.

    Tenant inaccessible due to inactivity

    To assist you further, we need some additional information. As this involves Personally Identifiable Information (PII), please share the following details with us via private message only (do not post publicly):

    • Tenant ID or affected user's mail
    • Correlation ID from the recent failure
    • Timestamp from the recent failure
    • Business impact and justification for restoring the tenant, and an explanation of the impact if the tenant cannot be restored

    Note: If it's a test tenant, please re-create a new tenant for testing purposes.

    QuickStart: https://learn.microsoft.com/en-us/entra/fundamentals/create-new-tenant

    Do let me know if you have any queries, we are happy to assist you further.

    0 comments No comments

  2. Shubham Sharma 3,830 Reputation points Microsoft External Staff Moderator
    2025-11-20T15:27:23.2533333+00:00

    Hello Fabián Alarcón

    This issue will be resolved by signing in using the tenant-specific Azure portal URL and the tenant ID I have provided over the private messages tab:

    HTTP

    https://portal.azure.com/<tenant-ID>
    

    Once you accessed the portal through the tenant-scoped URL, the tenant became active again and you will be able to manage resources without further issues.

    And the tenant will be restored successfully.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful, which may help members with similar questions. If you have any other questions, let me know in the “comments” and I would be happy to help you

    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.