Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | AADSTS50130: The claim value 'http://schemas.microsoft.com/claims/authmethods' cannot be interpreted as a known authentication method. | Event Viewer - Windows Logs - Application | -> Event ID 4294967295 |
| Affected OS build range | Windows 11 22H2 | ||
| Registry key involved | HKLM\SOFTWARE\Microsoft\WindowsSelfHost\Applicability\{guid}\PolicyPath | Registry Editor | -> Check for OMA-URI |
| Relevant service/endpoint URL | https://login.microsoftonline.com/<tenant_id>/oauth2/v2.0/token | ||
| Log line signature | AADSTS50130: The claim value 'http://schemas.microsoft.com/claims/authmethods' cannot be interpreted as a known authentication method. | Event Viewer - Windows Logs - Security | -> Event ID 4624 |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtxC:\Windows\System32\winevt\Logs\Security.evtx
What This Error Actually Means
The error code AADSTS50130 is raised by Microsoft Entra ID when a multi-factor authentication (MFA) claim is present but the Authentication Methods Reference (AMR) value is not recognized or accepted according to the Conditional Access policies configured in your tenant. The AMR value, which should be 'http://schemas.microsoft.com/claims/authmethods', indicates that an MFA method was used during authentication, but the specific method does not match any of the methods listed as acceptable by the policy. This error typically occurs when there is a mismatch between the MFA policies defined in Entra ID and the actual MFA methods being employed on devices attempting to authenticate. The claim value 'http://schemas.microsoft.com/claims/authmethods' signifies that an authentication method was used, but it does not align with what your Conditional Access policy expects.Affected Versions and Scope
This error is observed specifically in Windows 11 build 22H2, where the operating system's interaction with Entra ID for authentication purposes has a specific configuration that can trigger this issue. The affected range includes all devices running Windows 11 22H2 that are enrolled and managed through Microsoft Intune or similar endpoint management solutions. The error does not affect other OS builds unless they use the same version of the Microsoft identity platform (MSAL) library for authentication, which is unlikely outside of this specific build. It also doesn't impact devices running older versions of Windows 10 that might be using different MFA mechanisms or configurations.Where To Look First: Logs and Event IDs
To diagnose AADSTS50130, start by examining the Application.evtx and Security.evtx logs located at C:\Windows\System32\winevt\Logs. The exact log line to look for is:AADSTS50130: The claim value 'http://schemas.microsoft.com/claims/authmethods' cannot be interpreted as a known authentication method.
This error can also be found in the Event Viewer under Windows Logs > Application and Security logs, with an associated Event ID of 4769. Additionally, check the registry key HKLM\SOFTWARE\Microsoft\WindowsSelfHost\Applicability\{guid}\PolicyPath to ensure that the policy path is correctly set for your tenant.
Root Causes
Mismatch Between MFA Policy and Authentication Methods
This occurs when a Conditional Access policy in Entra ID mandates specific authentication methods (like phone call, SMS, or app notification), but the actual method used by the device is not recognized. For instance, if a user tries to authenticate using an older version of the Microsoft Authenticator app that doesn't support all MFA methods defined in your policy.Incorrect Configuration of Authentication Methods
Sometimes, the configuration for authentication methods might be incorrect or outdated. This can happen due to misconfigurations during updates or changes made without proper validation. Ensure that the AMR values are correctly mapped and accepted by Conditional Access policies.Be cautious when making changes to authentication methods as it could affect all enrolled devices.
Registry Configuration Issues
The registry key HKLM\SOFTWARE\Microsoft\WindowsSelfHost\Applicability\{guid}\PolicyPath might be incorrectly set or missing, leading to issues with policy enforcement. This can cause the system to fail in interpreting MFA claims correctly.Fix Procedure
To resolve AADSTS50130, follow these steps:- Update Conditional Access Policy: Navigate to Entra ID > Conditional Access > Policies and ensure that all required authentication methods are included in the policy. Use the OMA-URI string
./Device/Vendor/MSFT/MAM/ConditionalAccessPolicyto configure this setting. - Check Registry Configuration: Open the registry editor and verify the PolicyPath value under HKLM\SOFTWARE\Microsoft\WindowsSelfHost\Applicability\{guid}. Ensure it correctly points to your tenant's policy configuration.
- Validate Authentication Methods: Use PowerShell cmdlets like
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"andInvoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices"to validate the authentication methods used by devices. - Review Event Logs: Use cmdlets like
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50and review logs for any discrepancies between expected and actual authentication methods.
Use the Event ID 4769 to quickly locate relevant entries in Security.evtx for troubleshooting.
Error Code Variants
| Error Code | Description |
|---|---|
| AADSTS50130 | MFA claim present but amr value not in accepted methods list. |
| AADSTS50129 | The authentication method is not supported or the user has not been assigned to use this method. |
| AADSTS50131 | The claim value 'http://schemas.microsoft.com/claims/authmethods' cannot be interpreted as a known authentication method due to policy misconfiguration. |
Verification
After applying the fixes, verify that the issue is resolved by checking if the error no longer appears in Event Viewer logs. Additionally, confirm that devices are now able to authenticate without encountering AADSTS50130 errors. You can also use PowerShell cmdlets likedsregcmd /status to check the status of device registration and ensure it aligns with your MFA policies.