Error map
Login failed for user '<token-identified principal>' Azure SQL: Login failed for user '<token-identified principal>' (Microsoft Entra / managed identity)
Azure · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
Azure SQL: Cannot open server 'x' requested by the login. Client with IP address 'y' is not allowed to access the server (Error 40615)
The Azure SQL server firewall doesn’t allow your client’s IP address.
AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
Too many failed sign-ins (or sign-ins from a malicious IP) triggered Entra Smart Lockout.
AADSTS50055: The password is expired
The user’s password expired under the tenant/on-prem password policy and must be changed before signing in.
DefaultAzureCredential failed to retrieve a token from the included credentials / ManagedIdentityCredential authentication unavailable
The Azure SDK tried every credential source (env vars, workload identity, managed identity, CLI…) and none worked.
AADSTS500113: No reply address is registered for the application
The app registration has no redirect URI for the platform being used, so Entra ID has nowhere to send the response.
AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application
The signed-in user belongs to another tenant (or is a personal Microsoft account) and isn’t a guest in the app’s tenant.
AADSTS50034: The user account does not exist in the directory
There’s no user with that sign-in name in the tenant.
Two steps away (21)
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
SQL Server: Login failed for user 'x'. (Error 18456)
SQL Server rejected the login — wrong password, wrong authentication mode, or a disabled/missing login.
driver failed programming external connectivity on endpoint: iptables: No chain/target/match by that name
Docker’s iptables rules were wiped (firewalld/ufw reload, iptables flush) while Docker was running, so it can’t publish ports.
Webhook signature verification failed (Stripe, Razorpay, GitHub…)
Your endpoint computed a different HMAC signature than the one the provider sent, so the webhook is rejected.
Error creating: pods is forbidden: violates PodSecurity "restricted:latest": allowPrivilegeEscalation != false ...
The namespace enforces a Pod Security Standard (baseline/restricted) and the pod spec breaks one of its rules.
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! (ssh host key changed)
The server’s SSH host key differs from the one saved in ~/.ssh/known_hosts — usually because the server was rebuilt or the IP was…
AADSTS50126: Error validating credentials due to invalid username or password
Microsoft Entra ID (Azure AD) rejected the sign-in because the username or password is wrong — or the flow can’t use passwords fo…
AADSTS65001: The user or administrator has not consented to use the application
The app needs permissions that haven’t been granted for this user or tenant.
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).
Git: Permission denied (publickey). fatal: Could not read from remote repository.
SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
OAuth 2.0 Error: invalid_grant
The authorization code, refresh token or credentials sent to the token endpoint are invalid, expired, already used or were issued…
OAuth Error: redirect_uri_mismatch
The redirect URI in your OAuth request doesn’t exactly match one registered for the client in the provider’s console.
OAuth 2.0 Error: invalid_client
The OAuth server couldn’t authenticate your application — wrong client ID/secret, wrong auth method, or the client doesn’t exist…
OAuth 2.0 Error: invalid_scope / insufficient_scope
The requested scope is unknown or not allowed for this client — or the token lacks the scope the API endpoint requires.
AADSTS53003: Access has been blocked by Conditional Access policies
Sign-in succeeded, but a Conditional Access policy blocked access — device, location, app or risk conditions weren’t met.
AADSTS50105: Your administrator has configured the application to block users unless they are specifically granted access
The enterprise app requires assignment (“Assignment required? Yes”) and the user isn’t assigned to it, directly or via a group.
AADSTS7000222: The provided client secret keys for app are expired
The app registration’s client secret has expired, so service-to-service authentication fails.
passwd: Authentication token manipulation error
passwd couldn’t update the password — the root filesystem is read-only, /etc/shadow has wrong permissions/attributes, or a PAM ru…
Failed to connect to bus: No such file or directory (systemctl --user / timedatectl)
The command needs the D-Bus/systemd bus, which isn’t available in this session — common over su, sudo -u, cron, containers or WSL.
AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed
The refresh token was revoked — usually because the user changed or reset their password, or an admin revoked sessions.
Map another error
Popular: 403500400TypeErrorCritical error0xC000007BNullPointerException404