AADSTS90002: Tenant 'x' not found
The tenant ID or domain in the authority URL doesn’t exist — or isn’t in the cloud you’re calling (public vs government/China).
Seen on:
Azure
Meaning
A typo in the tenant ID, using an unverified domain name, a deleted tenant, or using login.microsoftonline.com for a sovereign-cloud tenant all return 90002.
Common causes
- Typo or wrong tenant ID/domain
- Domain not verified in the tenant
- Tenant deleted
- Sovereign cloud tenant called on the public endpoint
⚡ Quick fix
- Copy the Directory (tenant) ID from the portal
- Use the tenant GUID instead of a domain
- Use the correct cloud authority
Detailed fix by platform
Azure CLI
- bash
az account show --query tenantId -o tsv curl -s https://login.microsoftonline.com/contoso.com/v2.0/.well-known/openid-configuration | jq .issuer
How to diagnose
- Tenant — ID in config vs portal
- Cloud — Public, US Gov, China?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Azure
- AADSTS50076 Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- App Service Application Error Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026