Personal account closure blocked by disabled University Tenant (Error AADSTS5000225) - Need help!! Engineers, please help!

Question

Personal account closure blocked by disabled University Tenant (Error AADSTS5000225) - Need help!! Engineers, please help!

Jo Lee 0

Hello,

I am facing a critical issue where I am completely unable to close my personal Microsoft account because it is trapped in an inactive Azure AD / Microsoft Entra ID tenant belonging to my former university.

The issue: When I attempt to close my personal account via the standard closure link (account.live.com/closeaccount.aspx), the system blocks me with the message: "Before we can take any action, you must leave your work organization." However, I cannot leave the organization because the university tenant is disabled/inactive, throwing error code AADSTS5000225 upon any login attempt.

What has already been done (with Microsoft Support guidance):

Changed Primary Alias: Guided by Microsoft Consumer Support, I successfully added a new @outlook.com alias (******@outlook.com), set it as Primary, and completely removed my original email address (******@inbox.ru) from the account aliases.

Attempted Account Closure: Even after switching to the clean @outlook.com primary alias and logging in fresh, the account closure process is still blocked by the same university directory relationship.

Official Support Reference: I spent weeks in discussion with Microsoft Support. The last agent (Raizen) confirmed via a secure Quick Assist screen-sharing session that this is a known backend issue where the tenant cleanup wasn't fully completed on the server side, leaving a "stuck" relationship cache. My official Microsoft Support case number for this issue is 7103992240.

The bottleneck: Consumer Support stated they lack the directory tools to interact with Azure/Entra ID tenants. At the same time, I cannot open an official Azure Support ticket because I am an individual user without a paid Azure Support plan or access to the university's Entra ID admin center.

Could a Microsoft Employee or an MVP please escalate this case to the Entra ID / Identity Engineering team? The backend directory association between my personal account (******@outlook.com) and the inactive university tenant needs to be forcefully purged so I can finally close my account.

Thank you.

Jo Lee 0 Reputation points

2026-06-09T22:38:33.96+00:00

The tenant is already fully deleted, but the system left an orphaned cache link in my personal MSA. This is a system bug, please escalate to a human engineer.
Shubham Sharma 17,915 Reputation points Microsoft External Staff Moderator

2026-06-10T03:12:08.13+00:00

Jo Lee

Thank you for reaching out to Microsoft Q&A.

The error message you encountered indicates that your tenant has been inactive for over 200 days past the billing cycle, triggering Microsoft’s effort to remove inactive tenants. When a tenant remains inactive for this period, the OMS commerce system imposes a login block (AADSTS5000225). Twenty days after the login block is applied, the tenant is permanently deleted.

Tenant inaccessible due to inactivity

If you plan to unblock your inactive tenant, it’s essential that it has been blocked for less than 20 days. After the 20-day period, the tenant is permanently deleted and cannot be recovered.

If it has been less than 20 days since the block, please provide the requested details for further assistance via private message: -
Jo Lee 0 Reputation points

2026-06-11T16:13:45.8333333+00:00

Thank you for opening this communication channel.

Regarding the 20-day window you mentioned for tenant reactivation: this period has definitely already passed. The university tenant itself is fully deleted and inactive.

I have just received the official response from my former university's IT Helpdesk (TalTech). They performed a full administrative check on their Microsoft Entra ID tenant and confirmed the following:

My account does not exist in their tenant as an active, guest, or even deleted user.

There is no remaining account object or organizational relationship left for them to manage or remove from their side.

They officially confirmed that this error (AADSTS5000225) is caused by a historical association trapped within Microsoft’s own account/identity system backend rather than within the university environment.

This perfectly aligns with my recent session with Microsoft Consumer Support. The support agent (Raizen) guided me through a secure Quick Assist screen-sharing session (Case #7103992240). Under his guidance, we successfully changed the primary alias of my Microsoft Account to a clean @outlook.com address and completely cleaned up the alias page. However, even after these changes, the account closure process remains blocked by the exact same error.

Since the university tenant has no record of my account, and the tenant itself is long past the 20-day deletion cycle, this is purely an orphaned relationship bug in the Microsoft Account (MSA) identity database.

Could you please escalate these findings directly to the Entra ID / Identity Engineering team so they can manually clear this ghost association from my current @outlook.com account backend? This is the only way I can exercise my right to close my personal account.

Thank you.
Shubham Sharma 17,915 Reputation points Microsoft External Staff Moderator

2026-06-12T03:59:54.99+00:00

Jo Lee

Thank you for your reply.

We have requested few details over private message. Kindly provide the details in private message to proceed further.

1 answer

Your answer

Jo Lee 0 Reputation points

2026-06-09T22:38:33.96+00:00

The tenant is already fully deleted, but the system left an orphaned cache link in my personal MSA. This is a system bug, please escalate to a human engineer.
Shubham Sharma 17,915 Reputation points Microsoft External Staff Moderator

2026-06-10T03:12:08.13+00:00

Jo Lee

Thank you for reaching out to Microsoft Q&A.

The error message you encountered indicates that your tenant has been inactive for over 200 days past the billing cycle, triggering Microsoft’s effort to remove inactive tenants. When a tenant remains inactive for this period, the OMS commerce system imposes a login block (AADSTS5000225). Twenty days after the login block is applied, the tenant is permanently deleted.

Tenant inaccessible due to inactivity

If you plan to unblock your inactive tenant, it’s essential that it has been blocked for less than 20 days. After the 20-day period, the tenant is permanently deleted and cannot be recovered.

If it has been less than 20 days since the block, please provide the requested details for further assistance via private message: -
Jo Lee 0 Reputation points

2026-06-11T16:13:45.8333333+00:00

Thank you for opening this communication channel.

Regarding the 20-day window you mentioned for tenant reactivation: this period has definitely already passed. The university tenant itself is fully deleted and inactive.

I have just received the official response from my former university's IT Helpdesk (TalTech). They performed a full administrative check on their Microsoft Entra ID tenant and confirmed the following:

My account does not exist in their tenant as an active, guest, or even deleted user.

There is no remaining account object or organizational relationship left for them to manage or remove from their side.

They officially confirmed that this error (AADSTS5000225) is caused by a historical association trapped within Microsoft’s own account/identity system backend rather than within the university environment.

This perfectly aligns with my recent session with Microsoft Consumer Support. The support agent (Raizen) guided me through a secure Quick Assist screen-sharing session (Case #7103992240). Under his guidance, we successfully changed the primary alias of my Microsoft Account to a clean @outlook.com address and completely cleaned up the alias page. However, even after these changes, the account closure process remains blocked by the exact same error.

Since the university tenant has no record of my account, and the tenant itself is long past the 20-day deletion cycle, this is purely an orphaned relationship bug in the Microsoft Account (MSA) identity database.

Could you please escalate these findings directly to the Entra ID / Identity Engineering team so they can manually clear this ghost association from my current @outlook.com account backend? This is the only way I can exercise my right to close my personal account.

Thank you.
Shubham Sharma 17,915 Reputation points Microsoft External Staff Moderator

2026-06-12T03:59:54.99+00:00

Jo Lee

Thank you for your reply.

We have requested few details over private message. Kindly provide the details in private message to proceed further.

Answer 1

Jo Lee 0

@Shubham Sharma
Hi Shubham, I am trying to go in private message, but the private message thread has expired and is no longer accessible. Could you please initiate a new private message session so I can share the information? Also, if this issue is too difficult or complex to resolve, please do not block or suspend my account. Thank you!

0 comments