Share via

Azure Sign-in failed Error code: interaction_required

Jasmine 0 Reputation points
2026-03-12T02:51:28.0433333+00:00

Azure Sign-in failed Error code: interaction_required

  1. 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: 3aa0ed02-f043-483b-b5c7-8d0b391e1900 Correlation ID: 019cdfdc-1ae5-7502-acf9-cccf4555edcc Timestamp: 2026-03-12 02:24:30Z
  2. 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: a44ffe13-9c7d-4bd9-b97f-23deef7e0300 Correlation ID: 019cdfd1-2096-7227-8fc7-90bf96556154 Timestamp: 2026-03-12 02:12:30Z
  3. 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: c3d0835b-3b81-426a-a777-d6bfe8e30700 Correlation ID: 019cdfde-0177-749a-9205-a12606c6660a Timestamp: 2026-03-12 02:26:34Z
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

1 answer

Sort by: Most helpful
  1. AI answer

    2026-03-12T02:51:41.4533333+00:00

    The error interaction_required: AADSTS5000225: This tenant has been blocked due to inactivity means the Microsoft Entra (Azure AD) tenant backing the Azure subscription has been put into an inactive state and sign-ins are blocked.

    Key points from the tenant lifecycle behavior:

    • When a tenant is inactive past the allowed period, Microsoft blocks sign-in with error AADSTS5000225.
    • From the moment the tenant is made inaccessible, there is a 20‑day window during which a tenant administrator can request reactivation.
    • If the tenant remains inaccessible for more than 20 days, it is deleted and cannot be recovered.

    Recommended actions:

    1. Determine whether the tenant is within the 20‑day reactivation window
      • If the tenant has been blocked for less than 20 days, it is still eligible for reactivation.
      • If it has been blocked for more than 20 days, the tenant is permanently deleted and cannot be restored.
    2. If within 20 days and you are (or can reach) a tenant admin:
      • The tenant administrator must contact Microsoft support to request reactivation.
      • Use the published global support phone numbers to open a support case and reference the error AADSTS5000225 and the trace/correlation IDs from the failure.
      • Do not open multiple support requests for the same tenant; wait for the decision on the first case.
    3. If the tenant is past 20 days of inactivity:
      • The tenant is deleted and cannot be recovered.
      • Any associated environments and data are subject to Microsoft’s data protection and retention policies.
    4. If access to Azure Portal is blocked but the tenant is still active:
      • Try signing in directly with the tenant identifier in the portal URL, for example:
        • https://portal.azure.com/<TenantId> or
        • https://portal.azure.com/<yourTenantName>.onmicrosoft.com
      • If still blocked and within the 20‑day window, proceed with the support contact as above.
    5. If the tenant cannot be reactivated:
      • Create or use another active Microsoft Entra tenant.
      • For example, sign in to https://entra.microsoft.com/, go to Entra ID → Overview → Manage tenants, and create a new tenant.
      • Then access Azure with the new tenant context (for example, https://portal.azure.com/<newTenantName>.onmicrosoft.com) and configure any required services (including artifact signing) in that tenant.

    For application developers or automation that is failing with this error:

    • The interaction_required wrapper indicates the app cannot silently obtain tokens because the tenant is blocked.
    • Minimize authentication attempts against this tenant until it is reactivated or replaced.
    • Once a new or reactivated tenant is available, update configuration (tenant ID, authority, etc.) to point to the active tenant.

    If the tenant is confirmed deleted (blocked for more than 20 days), the only path forward is to use a different or newly created tenant and reconfigure Azure resources and artifact-signing workflows there.


    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.