A cloud-based identity and access management service for securing user authentication and resource access
For this scenario, the supported remediation sequence is:
- 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
AzureAdPrtisNO, continue with PRT troubleshooting.
- If the password was recently changed, allow synchronization to complete before resetting device state.
- For hybrid-joined devices with password hash sync,
AADSTS50126can 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.
- For hybrid-joined devices with password hash sync,
- If
AzureAdPrtUpdateTimeis older than four hours, force a PRT refresh first.- Lock and unlock the device.
- Run
dsregcmd /statusagain and check whether the time updates.
- 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.
- Validate the documented causes for
AADSTS50126andAADSTS50034before any reset.-
AADSTS50126is documented for incorrect username/password, or for a recent password change on a hybrid-joined device before password sync completes. -
AADSTS50034is 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.
-
- 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, orSTATUS_REQUEST_NOT_ACCEPTEDcan 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.
- 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 /leaveremoves the current device registration state and should be treated as a disruptive step.
- Microsoft documentation in related device-state troubleshooting mentions that in some cases
- 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.cabfile to Support. - Network traces: run
netsh trace start scenario=internetClient_dbg capture=yes persistent=yes, reproduce by locking/unlocking, then runnetsh trace stopand sharenettrace.cab. - Important: do not use Fiddler during network trace collection.
- Regular logs: use the diagnostic tool from
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: