Error code lookup
Start with the exact code your system showed. 43 entries across 4 technologies; Entra ID and Intune entries are based on Microsoft's documentation, with the source links and the date they were checked. Each gives the cause, the fix and how to confirm it.
43 error codes
AADSTS50011: redirect URI doesn't match the app registration
Sign-in fails because the redirect URI the app sent doesn't match any redirect URI registered for the app in Microsoft Entra ID.
AADSTS700016: application not found in the directory
Entra ID can't find the application named in the sign-in request in the tenant the request was sent to.
AADSTS53003: blocked by Conditional Access
A Conditional Access policy blocked token issuance for this sign-in. The sign-in log records which policy applied and why.
AADSTS50076: multifactor authentication required
The user must complete multifactor authentication to reach the resource, because of a Conditional Access policy, per-user MFA or a new location.
AADSTS50126: invalid username or password
Entra ID couldn't validate the credentials because the username or password was wrong. Some of these are expected in any tenant's logs.
AADSTS50053: account locked or sign-in blocked
The account is locked after too many failed sign-ins, or the sign-in was blocked because it came from an IP address with malicious activity.
AADSTS50158: external security challenge not satisfied
The user was sent to satisfy an extra requirement, such as terms of use or a third-party MFA provider. On its own this code isn't a failure.
AADSTS53000: device not compliant
A Conditional Access policy requires a compliant device and the device signing in isn't marked compliant.
AADSTS65001: consent not granted for the application
Neither the user nor an administrator has consented to the application using the permissions it asked for.
AADSTS700082: refresh token expired due to inactivity
The app's refresh token expired because it wasn't used for too long, so the user has to sign in interactively again.
AADSTS90072: external account doesn't exist in the tenant
The external account the user signed in with doesn't exist in the tenant, so the user can't satisfy that tenant's MFA requirements.
AADSTS50020: user from another identity provider doesn't exist in the tenant
A user from another identity provider tried to sign in to a tenant where their account doesn't exist, typically a guest or multitenant sign-in problem.
AADSTS7000215: invalid client secret
The app tried to authenticate to Entra ID with a client secret that isn't valid, so it can't get a token.
AADSTS500011: resource principal not found
The app asked for a token to a resource (an API or service) that Entra ID can't find in the tenant.
0x80180014: your organization does not support this version of Windows
Windows enrollment is refused, either because Windows MDM enrollment is blocked by a platform restriction or because an Autopilot device is being reused.
80180018: enrollment fails with Something went wrong
Windows enrollment in Intune or another MDM fails with 80180018, usually because of the user's licence or their number of enrolled devices.
8018000a: the device is already enrolled
Enrollment fails because a different user has already enrolled the device in Intune or joined it to Microsoft Entra ID.
0x8007064c: the machine is already enrolled
Enrollment fails because the computer still holds enrollment state from a previous enrollment, a cloned image, or an old account certificate.
80180026: Something went wrong joining Microsoft Entra ID
Joining a Windows computer to Microsoft Entra ID fails because MDM automatic enrollment is on and the old Intune PC software client is installed.
0x8018002b: Auto MDM Enroll failed (Group Policy enrollment)
Automatic MDM enrollment through Group Policy fails with event 76, because of the user's UPN suffix or because MDM user scope is None.
0x80180022: Autopilot enrollment fails on Windows Home
Autopilot enrollment fails because the device is running Windows Home edition, which this enrollment doesn't support.
0x80070774: hybrid Autopilot can't reach or join the domain
A hybrid join Autopilot deployment fails because the device can't reach a domain controller or has been put in a state that can't join the domain.
Kubernetes CrashLoopBackOff
A container repeatedly starts and exits, so the kubelet applies an increasing delay before trying again.
Kubernetes ImagePullBackOff
The node cannot retrieve a container image and is delaying subsequent pull attempts.
Kubernetes OOMKilled
The container exceeded available memory at its cgroup or node boundary and was killed.
Kubernetes FailedScheduling: insufficient resources
The scheduler cannot find a node that satisfies the Pod's resource requests and placement constraints.
Kubernetes FailedMount
Kubernetes could not attach, prepare or mount one or more volumes required by the Pod.
Kubernetes RBAC forbidden
The request was authenticated, but the active authoriser did not permit the requested verb, resource and scope.
Kubernetes context deadline exceeded
A Kubernetes operation did not complete before its caller's deadline expired, indicating latency or unavailability somewhere in the request path.
Kubernetes readiness probe connection refused
The kubelet reached the Pod network but no process accepted the readiness probe connection at the configured address and port.
Kubernetes Pod evicted by node pressure
The kubelet terminated a Pod to reclaim a constrained node resource such as memory, filesystem space or inodes.
Kubernetes Node NotReady
The control plane no longer considers a node healthy enough to host normal workload traffic.
Kubernetes Service has no endpoints
A Kubernetes Service currently has no ready backend addresses to receive traffic, even though its virtual IP and DNS name may still exist.
PostgreSQL too_many_connections
PostgreSQL rejected a new session because the server has reached its usable connection limit.
PostgreSQL deadlock_detected
PostgreSQL found a cycle of sessions waiting on one another and aborted one transaction to break it.
PostgreSQL unique_violation
An INSERT or UPDATE attempted to create a value combination already protected by a unique constraint or index.
PostgreSQL foreign_key_violation
A write would leave a child row referencing a parent key that does not exist, or a parent change would orphan dependent rows.
PostgreSQL serialization_failure
A serializable or repeatable-read transaction could not complete without violating the isolation guarantee.
PostgreSQL admin_shutdown
The server terminated the client connection because PostgreSQL was stopped, restarted, promoted, or explicitly instructed to end sessions.
PostgreSQL lock_not_available
A statement configured not to wait, or constrained by lock_timeout, could not acquire its required lock.
PostgreSQL undefined_table
PostgreSQL could not resolve a referenced table, view, sequence, materialized view, or other relation in the active namespace.
PostgreSQL invalid_password
The server selected a password-based authentication rule and could not validate the supplied credentials.
PostgreSQL connection_failure
An established PostgreSQL connection failed while the client was using it, leaving the current operation interrupted or uncertain.
Browse by technology
Get practical engineering references
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.