Microsoft 365, AD and Windows · #28
Online dsregcmd Output Analyzer
Extracts the join type, PRT state and diagnostic codes from dsregcmd /status output and produces a masked copy for sharing.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
For conditional access, Intune enrollment or SSO problems, the first thing to look at is the dsregcmd /status output, but it has over 60 lines and it is not always clear which value is the problem. The tool determines the join type and highlights whether there is a PRT (Primary Refresh Token) in the user context, the device authentication status and diagnostic error codes.
How to use it
- On the affected device, open Command Prompt in the affected user's session (not as administrator) and run
dsregcmd /status. - Paste the whole output and press Calculate. Use the masked copy for sharing.
Fields
- dsregcmd /status output
- Full output taken in the user's session. Data does not leave your browser.
Worked example
| Input | Value |
|---|---|
| dsregcmd /status output | |
Expected result: Hybrid join indicator (AzureAdJoined and DomainJoined YES); DeviceAuthStatus SUCCESS but AzureAdPrt NO; diagnostic entries AttemptStatus 0xc000006d and ClientErrorCode 0x80070057.
The device is registered and healthy in Entra, but no PRT was obtained for the user. 0xc000006d usually points to wrong credentials or a federation/password sync issue; the first steps are signing out and in with the new password and checking reachability of the corporate network (DC).
Method and assumptions
Key : Value lines are read (frame lines are skipped). Join type: AzureAdJoined and DomainJoined YES → hybrid; only AzureAdJoined → Entra joined; only DomainJoined → domain only; WorkplaceJoined YES → registered.
AzureAdPrt is read from the SSO section; AttemptStatus, ClientErrorCode, ServerErrorCode and descriptions from diagnostics. MdmUrl only shows that an MDM discovery URL is configured in the tenant; it does not prove Intune enrollment.
The masked copy partially hides GUIDs, email addresses and tenant/device names.
Using the result and troubleshooting
If AzureAdPrt is NO: sign in again as the user, look up the diagnostic code in Microsoft's dsregcmd troubleshooting article, and for hybrid devices check DC reachability and Entra Connect sync.
If only DomainJoined is YES, the device is not yet hybrid joined: check device sync in Entra Connect, the SCP configuration and the Automatic-Device-Join scheduled task. Compare Intune and Entra records with the Intune Device Inventory Reconciliation.
Limits and common mistakes
- Not all error codes are explained; the codes are highlighted with a first check.
- Output taken as administrator lacks the user-context SSO fields.
Frequently asked questions
MdmUrl is filled in — is the device in Intune?
Not necessarily. MdmUrl is the tenant's MDM discovery address. Confirm enrollment in the Intune portal or on the device under Settings › Accounts › Access work or school.
Related tools and service
- Intune Device Inventory ReconciliationMatches device records from three sources; name similarity is never treated as a certain match.
- Entra Connect Sync Inventory DiffMatches on-premises AD and Entra user lists by source anchor; shows attribute differences and unmatched objects.
Related service: Microsoft 365, Azure, AWS and Google Cloud Services