AADSTS5000225 – Tenant blocked due to inactivity, need reactivation for Visual Studio Marketplace publisher

Ben Gao 0 Reputation points
2026-05-26T04:38:53.71+00:00

Hello,

I am unable to access my Azure tenant and related services. When attempting to sign in to Azure DevOps (to generate a PAT for VS Code extension publishing), I receive the following error:

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: 7e150926-bbc0-4aeb-a728-49edbcba2a00 Correlation ID: 019e6265-36e9-7ad7-862c-e276e1bbf2a8 Timestamp: 2026-05-26 03:47:41Z

This tenant is now actively used as the identity provider for my publisher account on the Visual Studio Marketplace. As a result:

  • I cannot access Azure DevOps to generate a Personal Access Token
  • I am unable to publish updates to my VS Code extensions via the CLI
  • My extensions may become unavailable if I cannot push updates

I did not receive any notification or warning prior to this.

Request: Please assist in reactivating my Azure AD tenant so I can resume managing my VS Code Marketplace publisher and extensions.

If any verification or additional information is required, I am ready to provide it.

Thank you for your help.

Azure Cloud Services
Azure Cloud Services

An Azure platform as a service offer that is used to deploy web and cloud applications.


1 answer

Sort by: Most helpful
  1. AI answer

    2026-05-26T04:39:08.7466667+00:00

    The error AADSTS5000225: This tenant has been blocked due to inactivity means the Microsoft Entra (Azure AD) tenant backing the Azure DevOps and Visual Studio Marketplace identity has been put into an inactive state and sign‑in is blocked.

    Key points from the tenant lifecycle behavior:

    • When a tenant is marked inactive, sign‑ins are blocked and the error AADSTS5000225 is expected.
    • Administrators can request reactivation only within 20 days of the tenant entering the inactive state.
    • After 20 days in this blocked state, the tenant is permanently deleted and cannot be recovered.

    To proceed:

    1. Determine whether reactivation is still possible
      Reactivation is only possible if the tenant has been blocked for less than 20 days. If it has been longer than 20 days, the tenant and its identities cannot be restored.
    2. If within 20 days: contact Microsoft to request reactivation
      As the tenant admin, open a support case with Microsoft to request tenant reactivation:
      • Use the official global support phone numbers listed in the tenant‑inaccessible documentation.
      • Provide details such as the tenant ID or tenant domain (for example, yourtenant.onmicrosoft.com), the error code AADSTS5000225, and that this tenant is used as the identity provider for a Visual Studio Marketplace publisher.
      • Do not submit multiple requests for the same issue; wait for the decision on the initial case before opening another.
    3. Sign in using a tenant‑specific endpoint (if directed by support)
      If support provides the tenant ID or confirms it is still present, sign in with a tenant‑specific URL such as:
      • https://portal.azure.com/<TenantId>
      • or https://portal.azure.com/<yourTenantName>.onmicrosoft.com
        This can sometimes allow access to the portal for further actions once the block is lifted.
    4. If the tenant is already deleted (blocked > 20 days)
      • The tenant cannot be recovered.
      • A new tenant must be created and used going forward.
      • For Visual Studio Marketplace and Azure DevOps, this would require re‑establishing identities and, if supported by those services, re‑linking or recreating publisher accounts under the new tenant.
    5. Avoid repeated auth attempts while blocked
      Application owners and developers should minimize authentication requests against the blocked tenant until it is reactivated, and avoid submitting multiple assistance requests in parallel.

    Because Visual Studio subscriptions and Marketplace publishing rely on Microsoft Entra identities, regaining access to the tenant (if still within the 20‑day window) via Microsoft support is the only path to restore the ability to sign in, generate PATs, and manage extensions under the existing publisher identity.


    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.