SubscriptionNotFound: The subscription 'x' could not be found
The subscription ID doesn’t exist in the current tenant or the identity has no access to it.
Exact message you may see
The subscription could not be found
Seen on:
Azure
Meaning
Logging in to the wrong tenant, using a subscription ID from another environment, or a service principal without any role on the subscription.
Common causes
- Wrong tenant in az login
- Subscription ID typo or from another directory
- No role assignment for the identity
- Subscription disabled/cancelled
⚡ Quick fix
- az account list --all to see accessible subscriptions
- az login --tenant <id>
- Assign a role on the subscription to the principal
Detailed fix by platform
Azure CLI
- bash
az account list --all -o table az login --tenant <tenant-id> az account set --subscription <id>
How to diagnose
- Tenant — Current tenant
- Access — Role assignments
- State — Enabled?
🔧 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
- AADSTS50053 AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- AADSTS50173 AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 15 Oct 2026