Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | AADSTS700011 | Entra ID portal blade | -> Error code |
| Affected OS build range | Windows 11 23H2 | System info | |
| Registry key involved | HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\FederatedCredentials | Registry Editor | -> Check for misconfigurations |
| Relevant service/endpoint URL | https://login.microsoftonline.com/common/oauth2/v2.0/token | Network trace | -> Token endpoint |
| Log line signature | AADSTS700011: The provided value for the input parameter is not valid. | Event Viewer -> Windows Logs -> Application |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtxC:\ProgramData\Microsoft\IdentityManager\Logs\IMLogging.log
What This Error Actually Means
The error code AADSTS700011 is raised by Microsoft's Entra ID (formerly Azure Active Directory) when a federated identity credential cannot be matched during an authentication attempt. Specifically, this occurs when the subject claim from an external Identity Provider (IdP) token does not align with any of the configured federated credentials within the application registration in Entra ID. This mismatch can prevent users or services from successfully authenticating and accessing resources that require a valid identity assertion. The error is part of a series of AADSTS codes, each indicating specific issues related to authentication and authorization failures. In this case, AADSTS700011 points towards misconfiguration in the federated identity credentials setup within Entra ID or an issue with the token being issued by the external IdP.Affected Versions and Scope
This error is observed on Windows 11 build 23H2, where workload identity federation (WIF) is enabled. The scope of this issue is limited to environments that rely heavily on federated identities for authentication purposes across multiple applications or services registered in Entra ID. It does not affect systems running older versions of Windows or those without WIF configured.Where To Look First: Logs and Event IDs
To diagnose the root cause, start by examining logs from both the system and application layers: - **System Log**: The primary location to check is theC:\Windows\System32\winevt\Logs\Application.evtx. Here, you will find entries related to authentication failures with Event ID 4625 (an account failed to log on) or Event ID 1078 (a user was denied access). These events often precede the AADSTS700011 error and provide context about which user or service is encountering issues.
- **Entra Identity Manager Log**: Another critical source of information is located at C:\ProgramData\Microsoft\IdentityManager\Logs\IMLogging.log. This file contains detailed logs from the Microsoft Identity Manager (MIM) service, which manages federated identity credentials. Look for entries that mention AADSTS700011 or related authentication errors.
- **Registry Key**: The Windows registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\FederatedCredentials may also hold clues about the configuration of federated credentials. Inspect this key for any discrepancies between expected and actual settings.
Root Causes
Incorrect Federated Credential Configuration in Entra ID
One common cause is an incorrect setup of federated credentials within the application registration in Entra ID. This can happen if the subject claim format or value does not match what is expected by the external IdP.External Identity Provider Token Mismatch
Another frequent issue arises from tokens issued by the external IdP that do not conform to expectations set up in Entra ID. For instance, changes in how the IdP formats subject claims can lead to mismatches.Outdated or Incomplete Federated Credential Information
Sometimes, federated credential information might be outdated due to delays in synchronization between systems or incomplete updates during configuration changes.Fix Procedure
To resolve this issue, follow these steps: 1. Verify the Federated Credentials Configuration: - Navigate to Entra ID > App Registrations > [Your Application] > Certificates & secrets > Federated credentials. - Ensure that all configured federated identities match exactly with what is expected from your external IdP. 2. Update Federated Credential Information in Entra ID: - Use the following PowerShell cmdlet to retrieve current managed devices and filter for those affected by this issue:Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
- Adjust federated credentials as necessary using the portal or scripts.
3. Validate Token Claims from External IdP:
- Use a tool like Postman to inspect tokens issued by your external IdP and ensure they match expected formats.
- Compare these claims against what is configured in Entra ID for consistency.
4. Update Registry Settings (if applicable):
- Modify the HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\FederatedCredentials registry key to correct any discrepancies found during inspection.
- Example: Use Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\FederatedCredentials" -Name "CredentialType" -Value "Federated"
5. Apply Group Policy or Intune Configuration:
- Ensure that group policies or Intune configurations are correctly set up to enforce consistent federated identity management across all devices.
- Example: Use Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\System" -Name "EnableFederatedCredentialUI" -Value 1
Be cautious when modifying registry settings, as incorrect changes can disrupt device enrollment and authentication processes.
Use the
dsregcmd /status command to quickly verify the status of federated credentials on a local machine without diving into logs or Entra ID portal.Error Code Variants
| Error Code | Description |
|---|---|
| AADSTS700011 | The provided value for the input parameter is not valid (federated identity credential mismatch). |
| AADSTS50029 | Invalid technical profile or API identifier. |
| AADSTS70011 | The provided value for the input parameter is not valid (generic validation error). |
Verification
After applying fixes, verify that the issue has been resolved by checking: - The application log fileC:\Windows\System32\winevt\Logs\Application.evtx for entries indicating successful authentication attempts.
- Entra ID portal logs and event viewer logs for any remaining error messages related to AADSTS700011.
Use the following PowerShell cmdlet to ensure that all affected devices have been updated correctly: Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"