Personal account, AADSTS5000225: This tenant has been blocked due to inactivity.

Question

Want to use my personal account to publish visual studio code extensions, but I seem to have some old blocked tenant connected to my account, and I do not have permissions to do anything about it since it a RESTRICTED ACCOUNT. Can it be removed from my account?

Account: [Moderator note: personal info removed] @gmail.com

Primary blocked tenant: [Moderator note: personal info removed]

(Looks like i got other blocked as well, [Moderator note: personal info removed])

-Best regards, Sigurd

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: [Moderator note: personal info removed] Correlation ID: [Moderator note: personal info removed]
Timestamp: 2026-04-08 10:46:57Z

Answer 1

Hi @Sigurd Hansen,

Please understand that our forum is a public platform, and we will modify your question to cover your personal information including your organization domain name in the description. Please notice to hide these personal or organization information next time you post error or some information to protect personal data.    

I have moved the information to the Private message if you need to add any more privacy information please add it in there.

Regarding your issue, the error message: AADSTS5000225: "This tenant has been blocked due to inactivity." likely means that your Azure Active Directory (AAD) tenant has been automatically disabled by Microsoft because it was inactive for a prolonged period. This is part of Microsoft’s Tenant Lifecycle Policy, which helps manage unused tenants. For more information, please see: Troubleshoot inaccessible tenants    

If the tenant was blocked less than 20 days ago, you can request reactivation:    

The tenant administrator should contact Microsoft Support. Please refer to the global support phone numbers: Customer service phone numbers

• Depending on your country or region. For some countries, when calling the support number, although there are about 30 seconds opening as something "you can visit the link...." But you can ignore this opening and wait until the option, then "1" as a business email user, "1" again for technical help.  
• Then you can follow the automated hotline flow to request a support ticket. 

Please provide the following details to the support team:   

• Tenant ID  
• Email address used to sign in  
• Correlation ID from the login failure  
• Timestamp of the failure  
• Business impact and reason for restoring the tenant  

If this is a test or non-critical tenant, you can create a new one using this instruction: Quickstart: Create a new tenant in Microsoft Entra ID  

Hopefully it clears thing up and if you have any other questions or need further assistance, feel free to ask.  

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The error AADSTS5000225 means the associated Microsoft Entra tenant is blocked due to inactivity. Blocked tenants cannot be managed or used until reactivated, and after 20 days in this state they are permanently deleted and cannot be recovered.

Because this is a tenant/identity lifecycle issue, it cannot be fixed directly from the Visual Studio Code publishing side or by actions in the Azure portal when the tenant is blocked. The only supported path in this situation is:

1. If any of the blocked tenants have been inactive for less than 20 days:
   • The administrator of that tenant must contact Microsoft using the global support phone numbers to request reactivation.
   • Only a tenant administrator can make this request; end users without admin rights cannot unblock or remove the tenant themselves.
   • While a support case is open, no additional assistance requests should be submitted for the same tenant.
2. If the tenants have been blocked for more than 20 days:
   • After 20 days in the blocked state, the tenant is deleted and is not recoverable.
   • In this case, the blocked tenants cannot be reactivated or “removed” in a way that restores access; they simply age out of the system per the tenant lifecycle.
3. For using the personal account to publish VS Code extensions going forward:
   • Use a tenant that is active and accessible with the account, or
   • Create/use a new active tenant (for example, via Microsoft Entra ID) and associate the publishing workflow with that active tenant instead of the blocked ones.

If the blocked tenants are preventing sign-in flows or causing prompts in tools like Visual Studio, one mitigation is to filter out unwanted tenants in Visual Studio so they are not used for authentication. In Visual Studio 2019 16.6 and later this can be done from File > Account Settings… > Account options, using the tenant filtering options. This does not delete the tenants but avoids authenticating against them from Visual Studio.

For removal or cleanup of the relationship between a personal Microsoft account and old tenants beyond these documented mechanisms, direct support from the appropriate Microsoft support channel (Azure/Entra for tenants, Outlook/consumer support for the personal account) is required; it cannot be completed self-service when the tenant is blocked and the account is not an administrator.

---

References:

• Tenant inaccessible due to inactivity
• Sign in to Visual Studio with accounts that require multifactor authentication (MFA)
• Troubleshooting suggestions for signing in to Visual Studio subscriptions
• NuGet.org frequently-asked questions