Hybrid Entra Join: AzureAdPrt NO / WamDefaultSet NO despite successful M365 authentication

Jeff Onofreychuk 0 Reputation points
2026-11-20T16:36:40.88+00:00

We have a Windows 11 Hybrid Microsoft Entra joined device where the device registration appears healthy:

  • AzureAdJoined: YES
  • DomainJoined: YES
  • DeviceAuthStatus: SUCCESS
  • TpmProtected: YES
  • KeySignTest: PASSED

However, the affected user's state shows:

  • WamDefaultSet: NO
  • AzureAdPrt: NO

AcquirePrtDiagnostics repeatedly shows:

  • 0xc000006a
  • Credential Type: Password
  • HTTP 400
  • invalid_grant
  • AADSTS50126: Error validating credentials due to invalid username or password

The user has different on-premises and cloud UPNs by design. Entra shows the correct mapping:

  • Entra UPN: user@cloud-domain
  • onPremisesUserPrincipalName: user@onprem-domain
  • OnPremisesSyncEnabled: True

The user recently changed the password, signed out of Windows and back in with the new password, and can manually authenticate to Microsoft 365 in Chrome with the cloud UPN and new password.

A later dsregcmd /status also shows:

  • RefreshPrtDiagnostics: PRESENT
  • Attempt Status: 0xc0070057
  • User Identity: NULL
  • Credential Type: unknown

We're trying to determine whether this points to corrupted/stale CloudAP/WAM/PRT state rather than a device registration or password-sync issue.

Before we reset WAM/BrokerPlugin state or use dsregcmd /leave, what is Microsoft's recommended remediation sequence for this scenario?We have a Windows 11 Hybrid Microsoft Entra joined device where the device registration appears healthy:

  • AzureAdJoined: YES
  • DomainJoined: YES
  • DeviceAuthStatus: SUCCESS
  • TpmProtected: YES
  • KeySignTest: PASSED

However, the affected user's state shows:

  • WamDefaultSet: NO
  • AzureAdPrt: NO

AcquirePrtDiagnostics repeatedly shows:

  • 0xc000006a
  • Credential Type: Password
  • HTTP 400
  • invalid_grant
  • AADSTS50126: Error validating credentials due to invalid username or password

The user has different on-premises and cloud UPNs by design. Entra shows the correct mapping:

  • Entra UPN: user@cloud-domain
  • onPremisesUserPrincipalName: user@onprem-domain
  • OnPremisesSyncEnabled: True

The user recently changed the password, signed out of Windows and back in with the new password, and can manually authenticate to Microsoft 365 in Chrome with the cloud UPN and new password.

A later dsregcmd /status also shows:

  • RefreshPrtDiagnostics: PRESENT
  • Attempt Status: 0xc0070057
  • User Identity: NULL
  • Credential Type: unknown

We're trying to determine whether this points to corrupted/stale CloudAP/WAM/PRT state rather than a device registration or password-sync issue.

Before we reset WAM/BrokerPlugin state or use dsregcmd /leave, what is Microsoft's recommended remediation sequence for this scenario?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-11-20T16:37:05.49+00:00

    For this scenario, the supported remediation sequence is:

    1. Verify PRT state from the affected user session.
      • Open Command Prompt in the signed-in user context.
      • Run dsregcmd /status.
      • Confirm the device remains hybrid joined and focus on SSO State.
      • If AzureAdPrt is NO, continue with PRT troubleshooting.
    2. If the password was recently changed, allow synchronization to complete before resetting device state.
      • For hybrid-joined devices with password hash sync, AADSTS50126 can occur when the new password has not yet synchronized to Microsoft Entra ID.
      • The documented remediation is to wait for Microsoft Entra synchronization to finish so a fresh PRT can be acquired with the new credentials.
    3. If AzureAdPrtUpdateTime is older than four hours, force a PRT refresh first.
      • Lock and unlock the device.
      • Run dsregcmd /status again and check whether the time updates.
    4. Retrieve the exact PRT acquisition failure from logs.
      • In Event Viewer, go to Applications and Services Log > Microsoft > Windows > AAD.
      • Review analytics and operational logs.
      • Event 1006 marks the start of PRT acquisition and Event 1007 marks the end.
      • Event 1007 contains the final error code.
      • For AADSTS50126, also check Event 1144 in the Microsoft Entra analytic logs to see the UPN that was provided during authentication.
    5. Validate the documented causes for AADSTS50126 and AADSTS50034 before any reset.
      • AADSTS50126 is documented for incorrect username/password, or for a recent password change on a hybrid-joined device before password sync completes.
      • AADSTS50034 is documented when Microsoft Entra ID cannot find the user account in the tenant. In hybrid scenarios, this can happen when the Windows client sends a SAM account name instead of a properly formatted UPN, often alongside lack of communication with an on-premises domain controller.
      • Since different on-premises and cloud UPNs are in use, confirming the UPN captured in Event 1144 is the key supported check.
    6. If network or federation is involved, check for service access issues.
      • For WinHTTP network errors, review Event 1022 and 1084 for the accessed URL.
      • If an outbound proxy is required, ensure the device computer account can discover and silently authenticate to the proxy.
      • In federated environments, STATUS_LOGON_FAILURE, STATUS_WRONG_PASSWORD, or STATUS_REQUEST_NOT_ACCEPTED can reflect HTTP 400 responses from Microsoft Entra authentication or the WS-Trust endpoint. Event 1081 and 1088 contain the server error code and description.
      • A documented accepted resolution for a federated environment with missing PRT is to verify with the third-party IdP team that required endpoints and ports are open and available for device login token issuance.
    7. Only after the above checks, consider re-registration actions.
      • Microsoft documentation in related device-state troubleshooting mentions that in some cases dsregcmd.exe /leave, reboot, and registration again might help.
      • This is not the first documented step for PRT failures and should follow verification of password sync, UPN used, logs, and connectivity.
      • Risk: dsregcmd /leave removes the current device registration state and should be treated as a disruptive step.
    8. If the issue persists, collect logs and contact Support.
      • Regular logs: use the diagnostic tool from https://aka.ms/icesdptool, reproduce the issue, and provide the latest .cab file to Support.
      • Network traces: run netsh trace start scenario=internetClient_dbg capture=yes persistent=yes, reproduce by locking/unlocking, then run netsh trace stop and share nettrace.cab.
      • Important: do not use Fiddler during network trace collection.

    Based on the documented sequence, the recommended order is:

    • confirm dsregcmd /status
    • wait for password sync if the password changed recently
    • force refresh by lock/unlock
    • inspect Event Viewer for Event 1007 and Event 1144
    • verify UPN actually used during PRT acquisition
    • verify proxy/federation endpoint access if applicable
    • only then consider dsregcmd /leave
    • collect logs for Support if unresolved

    The provided documentation does not recommend resetting WAM/BrokerPlugin state as the standard first remediation for this PRT failure pattern.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.