AADSTS50020 Severity: High User account from identity provider does not exist in tenant
The classic multi-org login error: your account from another identity provider (personal or another tenant) does not exist in the tenant you are signing into.
Affected systems
Symptoms
- AADSTS50020 with the hint about 'identity provider'
- Message 'User account from identity provider X does not exist in tenant Y'
- Clicking a meeting link from a different organization fails
- Guest invite leads to the error page
Possible causes
- You sign in with a personal Microsoft account into a corporate tenant
- You were invited as a guest, but the guest account is not yet activated
- Your email address changed, the old reference in the foreign tenant is dead
- Tenant admin removed your guest account
Solutions
1.Sign in with the correct account
-
Check the exact email address the organizer used in the invite.
-
If you use personal (live.com / outlook.com) and work with the same address, explicitly pick 'Work account' on the MS login screen.
-
If the picker does not appear, sign in from a private browser window to avoid stale cookies.
2.Request a fresh guest invite
-
Ask the person who invited you to confirm you are listed as a guest in the foreign tenant.
-
If not, request a new invite, accept it from your inbox, complete the prompts.
-
Only then will sign-in to the foreign tenant succeed.
3.Verify in a browser
-
Open https://myapps.microsoft.com in a private window with the account in question.
-
If the foreign tenant does not show in the list, your account really has no access there.
-
Send the correlation ID from the error page to the IT of the foreign organization.
AADSTS50020 is the most common multi-org pitfall. Anyone who works for customers across tenants hits it regularly. The fix is almost always a combination of correct account choice and clean guest registration.