Transient outages, upstream faults, and service instability events.
Last reviewed: March 3, 2026|48 mapped errors|Page 2 of 4
Availability errors indicate that service execution failed or upstream dependencies could not complete in time for the current request path.
Provider-specific error pages mapped to this category (48 total). Showing 16-30.
Azure AADSTS50057 is an account-state error indicating that the user object exists in the target Microsoft Entra tenant but the accountEnabled property is set to false, blocking all authentication attempts.
Azure AADSTS50058 is a session-context error indicating that a silent authentication request (`prompt=none`) was sent, but Microsoft Entra ID could not find a valid SSO session or accessible identity cookies in the browser.
Azure AADSTS50059 is a tenant-routing failure that occurs when a sign-in request reaches Microsoft Entra ID without sufficient information, such as a tenant ID or domain, to determine which directory should process the request.
Azure AADSTS50074 is a high-assurance requirement signal. It indicates that the current authentication attempt or session context lacks the strong authentication claims required by the tenant’s security policy.
Azure AADSTS50076 is a step-up authentication requirement indicating that while the password was accepted, Microsoft Entra ID requires Multi-Factor Authentication (MFA) due to a Conditional Access policy or a detected risk signal.
Azure AADSTS50079 is an enrollment error indicating that the user’s credentials were accepted, but the sign-in cannot complete because the account has not yet registered the required Multi-Factor Authentication (MFA) methods.
Azure AADSTS53003 is a policy-based rejection. It indicates that while the user’s credentials were valid, the sign-in attempt was blocked by a specific Microsoft Entra Conditional Access policy due to untrusted location, non-compliant device, or high-risk signals.
Azure AADSTS65001 is a permission-grant failure indicating that the application is requesting API scopes, such as Microsoft Graph permissions, that have not yet been approved by the user or an administrator in the target tenant.
Azure AADSTS65004 is a consent-grant failure indicating that the user either explicitly declined the requested permissions or the consent flow was interrupted before the approval could be recorded in Microsoft Entra ID.
Azure returns `ImageNotFound` when the VM image reference cannot be resolved for the selected region, subscription, or source registry.
ARM returns `NotFound` when a deployment operation references a resource that is unavailable at evaluation time.
Azure Table service returns `TableNotFound` when the target table name does not exist in the addressed storage account endpoint.
Azure returns `VMOSDiskNotFound` when a VM deployment references an OS managed disk identifier that cannot be resolved in the active scope.
GCP INTERNAL means the service detected an internal invariant failure while handling the request.
GCP UNAVAILABLE means the service is temporarily unable to handle the request; safe clients should retry with backoff.
Compare Guide
Use 429 for caller-specific throttling and 503 for service-wide outages, so retry behavior, escalation paths, and incident ownership stay correct.
Compare Guide
Debug 500 vs 502 faster: use 500 for origin failures and 502 for invalid upstream responses at gateways, then route incidents to the right team.
Compare Guide
Fix upstream errors faster: use 502 when a gateway gets an invalid upstream response, and 504 when the upstream service exceeds your timeout budget.
Playbook
Use this playbook to separate invalid upstream responses from upstream wait expiration and deadline exhaustion, and apply timeout budgets, safe retries, and circuit-breaker controls safely.
Playbook
Use this playbook to separate origin-side 500 failures from temporary 503 dependency or capacity outages, then apply safe retry and escalation paths.
Playbook
Triage 500, gRPC UNKNOWN, and cloud InternalError fast: preserve correlation IDs, separate transient provider faults from app bugs, and apply safe retries.
500 indicates internal server failure, 502 indicates invalid upstream response, 503 indicates temporary unavailability, and 504 indicates upstream timeout.
Retries worsen outages when they are unbounded or synchronized, because they increase load on already degraded dependencies.
Sustained normalization of error rate and tail latency under representative traffic, not only short success bursts.