fairfax / Sign-in errors / AADSTS90002
AADSTS90002: InvalidTenantName
Microsoft Entra ID can't find the tenant on the host you asked. Microsoft says this often happens because a cross-cloud app was used against the wrong cloud: a GCC High, DoD or Azure Government tenant doesn't exist on login.microsoftonline.com.
How to fix it
Check the tenant ID, then sign in through the host of the cloud that tenant lives in.
| Your tenant or subscription | Sign-in host |
|---|---|
| Commercial Microsoft 365 and Azure, and GCC tenants | login.microsoftonline.com |
| GCC High and DoD tenants, and Azure Government | login.microsoftonline.us |
What Microsoft says
“AADSTS90002 | InvalidTenantName - The tenant name wasn't found in the data store. Check to make sure you have the correct tenant ID. The application developer will receive this error if their app attempts to sign into a tenant that we cannot find. Often, this is because a cross-cloud app was used against the wrong cloud, or the developer attempted to sign in to a tenant derived from an email address, but the domain isn't registered.”
Source: Microsoft Entra authentication and authorization error codes, page updated 2026-06-15, checked 2026-10-12.
- “Microsoft Entra ID for US Government | https://login.microsoftonline.us” (National clouds)
Decode it from the command line
pip install fairfax
fairfax explain AADSTS90002 --tenant gcchigh # or paste the whole error message
To find the commercial sign-in host in your code before it fails, run
fairfax scan src/ --tenant gcchigh --azure government.
Other cross-cloud sign-in errors
- AADSTS50049: NoSuchInstanceForDiscovery
- AADSTS90038: NationalCloudTenantRedirection
- AADSTS90051: InvalidNationalCloudId
- AADSTS700016: UnauthorizedClient_DoesNotMatchRequest
- AADSTS900382: Confidential Client isn't supported in Cross Cloud request
- AADSTS900432: Confidential Client isn't supported in Cross Cloud request
- AADSTS900439: USGClientNotSupportedOnPublicEndpoint
- AADSTS1000104: XCB2BResourceCloudNotAllowedOnIdentityTenant