Our Azure reference focuses on ARM deployment failures, Entra ID authentication and authorization errors, and storage/runtime service exceptions. Each guide maps provider messages to actionable checks across tenant, subscription, resource group, and policy layers used in real operations.
Showing 1-15 of 63.
Microsoft Entra or Microsoft Graph returns group-not-found responses when the target group object cannot be resolved in the current tenant directory.
Microsoft Entra or Microsoft Graph returns `AADServicePrincipalNotFound` when the requested service principal object cannot be resolved in the active tenant.
Azure AADSTS50011 is a security mismatch error indicating that the Redirect URI (Reply URL) sent by the application does not exactly match any of the URIs registered in the Microsoft Entra app registration.
Azure AADSTS50012 is a client-authentication failure indicating that the supplied client secret, certificate, or JWT assertion is invalid, expired, or does not match the application registration in Microsoft Entra ID.
Azure AADSTS50020 is a directory boundary error. It occurs when a valid user attempts to sign in to an application, but their account does not exist as a member or invited guest in the specific Microsoft Entra tenant hosting the app.
Azure AADSTS50034 is a directory lookup failure indicating that the user account does not exist in the targeted Microsoft Entra tenant. The identity cannot be resolved because the username (UPN) is incorrect or the user is not provisioned in that specific directory.
Azure AADSTS50053 is a defensive security block. It indicates that a sign-in attempt was rejected because the account is temporarily locked (Smart Lockout) or the source IP address has been flagged for suspicious or malicious activity.
Azure AADSTS50055 indicates that the user's password has reached the maximum age allowed by the tenant or directory policy. Microsoft Entra ID requires a password reset before it will issue new authentication tokens or allow session renewal.
Azure AADSTS50056 indicates that Microsoft Entra ID received a password-based sign-in request, but the targeted user account does not have a valid password configured in the cloud or the password was not supplied in the request.
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.