Home › Entra ID › AADSTS50076

Entra ID · AADSTS50076 · Windows 11 23H2

Entra ID Error AADSTS50076: MFA Challenge Failed on Windows 11 23H2

The error occurs when MFA is required but not completed during sign-in. Ensure MFA methods are registered and functional in Entra ID.

Error Details

FactValueSourceNote
Exact error stringAADSTS50076: Multi-factor authentication required — MFA challenge not satisfied during sign-inEntra ID logs-> Indicates MFA was expected but not completed.
OS build range affectedWindows 11 23H2 (build 22621.875 and above)Microsoft Update Catalog-> Issue observed post-update.
Registry key involvedHKEY_CURRENT_USER\Software\Microsoft\IdentityCRLWindows Registry Editor-> Contains MFA configuration settings.
Relevant service/endpoint URLhttps://login.microsoftonline.comNetwork Monitor logs-> Entra ID authentication endpoint.
Log line signature[Federation] Error: AADSTS50076...Windows Event Viewer (Application)-> Log entry indicating failed MFA challenge.

Log Files to Check

What This Error Actually Means

The error code AADSTS50076 is a hexadecimal identifier for a specific authentication failure in Microsoft Entra ID (formerly Azure AD). The numeric equivalent is 50076 in decimal, which maps to the error message: "Multi-factor authentication required — MFA challenge not satisfied during sign-in." This error is raised by the Entra ID authentication pipeline when a user's sign-in attempt fails to complete the multi-factor authentication (MFA) challenge. The component responsible for this error is the Microsoft Authentication Library (MSAL) or the legacy ADAL (Active Directory Authentication Library), depending on the client application's implementation. The error typically occurs when the user either cancels the MFA prompt, fails to respond within the allowed time window, or the configured MFA method (e.g., app-based code, SMS, or biometrics) is unavailable or misconfigured. This error is distinct from generic MFA failures and indicates a direct failure in the challenge-response mechanism during the authentication flow.

Affected Versions and Scope

This error is specifically observed on Windows 11 23H2 devices with build numbers 22621.875 and above. The issue is not present in earlier OS versions such as Windows 11 22H2 (build 22621.710 or lower) or Windows 10. The scope is limited to tenants where MFA is enforced via Entra ID Conditional Access policies or user-specific MFA requirements. Tenants that rely solely on passwordless authentication methods (e.g., FIDO2 keys) or do not enforce MFA are unaffected. Additionally, devices managed via Intune with MDM policies that bypass or override MFA prompts (e.g., via OMA-URI configurations) may not encounter this error. The issue is not related to Entra ID versioning but rather to the OS-level integration of the Identity CRL (Certificate Revocation List) service and the MSAL/ADAL libraries in the specified Windows 11 build range.

Where To Look First: Logs and Event IDs

To diagnose AADSTS50076, start with the following logs and event sources: 1. **Entra ID Local Logs**: Check C:\Program Files\Microsoft Entra ID\Logs\EntraID_YYYYMMDD.log for lines containing [Federation] Error: AADSTS50076. Use a text editor or Get-Content with a filter: Get-Content -Path "C:\Program Files\Microsoft Entra ID\Logs\EntraID_*.log" | Select-String "AADSTS50076" 2. **Windows Event Viewer**: Navigate to C:\Windows\System32\winevt\Logs\Application.evtx and filter for Event IDs 41039 (MFA challenge initiation) and 41040 (MFA challenge failure). Use PowerShell: Get-WinEvent -LogName "Application" | Where-Object { $_.ID -eq 41040 -and $_.Message -like "*AADSTS50076*" } 3. **Network Traffic**: Use tools like Wireshark or Microsoft Message Analyzer to inspect HTTPS traffic to https://login.microsoftonline.com for failed MFA challenge responses. Look for HTTP 401 Unauthorized status codes with the error payload.

Root Causes

1. Expired or Invalid MFA Token

The most common cause is an expired time-based one-time password (TOTP) generated by an authenticator app. This can be identified by checking the AuthenticationMethod timestamp in the Entra ID logs. Use: Get-MgUserAuthenticationMethod -UserId "[email protected]" | Where-Object { $_.DisplayName -eq "Microsoft Authenticator" } If the CreatedDateTime property is older than 30 days, the token may be invalid.

2. Registry Corruption in IdentityCRL

The registry key HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL stores cached MFA session data. Corruption here can prevent the MFA challenge from completing. Verify the key's integrity using: Get-ItemProperty -Path "HKCU:\Software\Microsoft\IdentityCRL" | Format-List If the SessionState value is missing or non-zero, this is the root cause.

3. Misconfigured Conditional Access Policies

A Conditional Access policy requiring MFA may be misconfigured to exclude specific device platforms or locations. Validate policies in the Entra admin center: **Path**: Entra admin center > Security > Conditional Access > Policies Check for policies with conflicting conditions (e.g., "Include Windows 10 and later" but excluding Windows 11).

Fix Procedure

  1. Clear IdentityCRL Cache: Remove-Item -Path "HKCU:\Software\Microsoft\IdentityCRL" -Recurse -Force
    Warning: This action will log the user out of all Entra ID sessions and may break device enrollment if not followed by re-authentication.
  2. Reconfigure MFA Method: Update-MgUserAuthenticationMethod -UserId "[email protected]" -AuthenticationMethodId "method-id" -StrongAuthenticationMethod @{"isPrimary"=$true} Ensure the user's primary MFA method is active in the Entra portal: **Path**: Entra admin center > Users > [User] > Authentication methods
  3. Deploy OMA-URI Policy for MFA Timeout: In Intune, create a profile with the OMA-URI: ./Device/Vendor/MSFT/IdentityCRL/MFATimeout Set the value to 300 (seconds) to extend the MFA challenge window.
  4. Verify Conditional Access Policy: Use PowerShell to check policy assignments: Get-MgIdentityConditionalAccessPolicy | Where-Object { $_.Conditions.Platforms -eq "Windows11" }

Error Code Variants

Error CodeDescriptionDistinguishing Factor
AADSTS50076MFA challenge not satisfiedSpecific to failed challenge response during sign-in
AADSTS50057Invalid MFA methodOccurs when the selected MFA method is not registered
AADSTS50058MFA required but not enforcedTriggered when a policy requires MFA but it is not applied

Verification

After applying fixes, verify resolution by: 1. Re-attempting sign-in and confirming no AADSTS50076 appears in EntraID_*.log. 2. Checking Event Viewer for Event ID 41039 with a success status. 3. Using PowerShell to query the user's authentication status: Get-MgUserAuthenticationMethod -UserId "[email protected]" | Select-Object DisplayName, IsPrimaryMethod Ensure the primary MFA method is listed and active.

Prevention

To prevent recurrence: 1. **Enforce MFA Method Renewal**: Use PowerShell to set a lifecycle policy for TOTP apps: Set-MgUserAuthenticationMethodLifecyclePolicy -UserId "[email protected]" -MaxAgeDays 90 2. **Monitor Registry Health**: Add a scheduled task to validate HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL daily: Get-ItemProperty -Path "HKCU:\Software\Microsoft\IdentityCRL" | Out-File "C:\Logs\IdCRL_HealthCheck.log" 3. **Update Conditional Access Policies**: In the Entra admin center, ensure policies include Windows 11 in the platform conditions. **Path**: Entra admin center > Security > Conditional Access > [Policy] > Conditions > Platforms
Tip: Use dsregcmd /status to quickly check device enrollment and MFA status without parsing logs.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.