Share via

Azure developer portal sign in failed

Rantu Biswas 0 Reputation points
2026-02-27T14:39:25.5733333+00:00

Sign-in failed Error code: interaction_required Error message: interaction_required: AADSTS5000225: This tenant has been blocked due to inactivity. To learn more about tenant lifecycle policies, see https://aka.ms/TenantLifecycle Trace ID: ebb73a5c-b614-44f1-ad55-262414dc0700 Correlation ID: 019c9f53-3391-79d8-852c-dcf05af82985 Timestamp: 2026-02-27 13:39:16Z Learn more about the error Try again Perform self diagnostics Go to Azure status page Sign out Contact support Debugging information Browser ID: 90260321-4d1c-46b6-b4fc-20d04879dfbe

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-02-27T14:39:38.14+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error AADSTS5000225: This tenant has been blocked due to inactivity means the Microsoft Entra tenant backing the Azure developer portal is in an inactive state and has been blocked.

    To resolve this, use one of the following approaches depending on the situation:

    1. If administrator access to that tenant exists and the tenant is still within 20 days of becoming inactive:
      • A tenant administrator must contact Microsoft support to request reactivation of the tenant. Use the global support phone numbers listed for Microsoft support. While the case is in progress, do not open additional support requests for the same issue.
      • If the tenant is successfully reactivated, sign-in to the Azure portal and the developer portal should start working again.
    2. If the tenant has been inactive for more than 20 days or reactivation is not requested:
      • After 20 days in the inaccessible state, the tenant is deleted and cannot be recovered.
      • In that case, create or use another active tenant to host the Azure developer portal and related resources.
    3. If sign-in to the Azure portal itself is failing with the same error:
      • Try signing in directly with the tenant identifier in the URL, for example:
        • https://portal.azure.com/<TenantId>
        • or https://portal.azure.com/<yourTenantName>.onmicrosoft.com
      • If access is still blocked and the tenant must be used, a tenant admin must follow the reactivation path via Microsoft support as above.

    Until the blocked tenant is reactivated (or a different active tenant is used), sign-in to services that rely on that tenant, including the Azure developer portal, will continue to fail with this error.


    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.