Inactive tenant blocking personal account (Error AADSTS5000225) - Need internal escalation

Question

Hi, my Azure tenant has been blocked due to inactivity (Error AADSTS5000225). It is not deleting automatically as promised by the lifecycle policy, and it is now blocking my personal Microsoft account login. I am completely locked out and cannot manage or delete it myself.

Could a Microsoft moderator please escalate this internally to the Product Group / Data Protection team for a manual deprovisioning? I have all the details ready to share via private message, such as Tenant ID, ".onmicrosoft.com" Domain, Trace ID, Correlation ID.

Thank you! /Filip

Answer 1

Waiting for them to contact me here. It has been more than 20 days, the tenant has been deactivated for several years.

Answer 2

Hello Filip R,

Greetings! Thanks for raising this question in the Q&A forum.

This behavior matches Microsoft's tenant lifecycle policy for inactive tenants. When a tenant has had no sign-in or billing activity for a long period, the OMS commerce backend applies a login block and returns AADSTS5000225. Normally the tenant is then automatically deleted 20 days after the block is first applied. If you are past that 20 day window and the tenant still has not been removed, and it is also blocking sign-in for your personal Microsoft account in other places, that does need a manual look from the backend team since there is no self-service way to force deletion or reactivation once you are locked out.

1. Confirm the timeline first Check the exact date the block first appeared if you still have any record of it, for example from an earlier sign-in error screenshot or email notification. This matters because the next step depends on whether you are inside or past the 20 day window.
2. If it has been less than 20 days since the block appeared You can request reactivation. Since you cannot sign in to open a support request through the Azure portal, use the Microsoft global support phone numbers instead, since phone support does not require portal sign-in:

      https://support.microsoft.com/contactus
   

   Tell the agent the tenant is blocked with AADSTS5000225 and that you want to request reactivation within the lifecycle policy window, not deletion.
3. If it has been more than 20 days since the block appeared The expected behavior is that the tenant is deleted and the block on your personal account clears on its own. If that has not happened, this is a backend cleanup that did not complete on schedule, and only Microsoft's internal Product Group or Data Protection team can force it through manually. This is not something that can be fixed from the admin side even if you could sign in.
4. Since you cannot log in to raise a ticket yourself, use the moderator escalation path on this thread This is the correct place to ask for that, since Microsoft Q&A moderators can take your Tenant ID, domain, Trace ID and Correlation ID privately and forward them to the internal team for manual deprovisioning. Watch for a private message request on this thread and reply there rather than posting the IDs publicly, since this is a public forum.
5. While waiting, avoid repeated sign-in attempts Minimize further authentication attempts against the blocked tenant. Repeated attempts do not speed anything up and the guidance from Microsoft is to let the existing case run its course once it is opened.
6. Avoid opening a second request for the same tenant If a moderator has already asked for your details privately, keep all follow-up in this same thread. Opening a duplicate question for the same Tenant ID can slow things down since it splits the case history.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.