Personal Outlook.com account stuck in old Azure AD tenant (AADSTS500200)

Question

Personal Outlook.com account stuck in old Azure AD tenant (AADSTS500200)

Brian Polley 0

My personal Outlook.com account has been incorrectly linked to an old employer’s Azure AD tenant. I have not worked for that company in over a decade, yet Azure/Entra is still routing me through their old organization. Because of this, I receive AADSTS500200 on any Microsoft service that uses Azure AD. I can sign in to my Microsoft account normally, but anything that touches Azure/Entra fails.

This is not a password problem.

This is not a sign‑in problem.

This is not something I can fix through the consumer login flow.

The issue is that my personal MSA is still attached to a long‑defunct organization’s Azure directory, and I cannot remove myself because the login system routes me incorrectly. The “Organizations” page will not load, and every Microsoft support path forces me to sign in — which loops me back into the same routing error.

I have now spent hours attempting to reach support. Every path I attempted — phone, chat, consumer support pages, business support pages, Azure help, Entra login — either refused to help without signing in or redirected me to the sign‑in helper, which is irrelevant and only risks locking me out. Several chats closed automatically while I was actively trying to explain this issue.

This should not be this complicated.

I have had this account since Outlook.com launched.

I pay for Microsoft services.

The fact that my account can be stuck in an old Azure tenant without any clear or safe way to get help is extremely disappointing. It makes me question whether I can trust this identity system for future business use.

I need this corrected at the directory level.

Please escalate this to the Azure AD B2B Identity team and remove my personal Outlook.com MSA from all Azure AD tenants it is associated with. I cannot access the normal tenant removal tools because the misrouting prevents them from loading.

I am asking for an identity engineer to clean up the backend tenant link so my Microsoft account can function normally again.

I spent even longer just trying to find the right stupid tag to get this to the right place, I finally just picked this even though I know it’s not correct. I need someone to route this to the proper place because I cannot find what I’m looking for. This is crazy.

Thank you.

VEMULA SRISAI 9,265 Reputation points Microsoft External Staff Moderator

2026-02-26T20:38:50.0533333+00:00
Hello Brian Polley,

Thank you for the detailed explanation — and you are correct on the core diagnosis.

This is not a password or consumer sign‑in issue. What you’re encountering is a stale backend association between a personal Microsoft Account (MSA) and a legacy Azure AD (Microsoft Entra ID) directory, most commonly created years ago when Outlook.com / Hotmail addresses were implicitly added to an organization as member or guest identities.

When this association becomes corrupted or the tenant is defunct, Entra’s home‑realm discovery can incorrectly route authentication attempts to that old directory, resulting in AADSTS500200 / tenant routing failures across any service that touches Entra — even though the MSA itself is healthy and can sign in via consumer endpoints.

You are also correct that:

The Organizations page failing to load is a symptom, not the cause

Normal self‑service tenant removal tools cannot load because authentication is misrouted

Consumer Microsoft Account support cannot fix this, because the issue lives in Entra’s directory layer

Repeated sign‑in attempts or “account recovery” flows do not resolve this and can increase lockout risk

This scenario requires backend cleanup by Microsoft identity engineering to: Please share the details in private message.