Article

Primary Refresh Token Missing: Diagnosing AzureAdPrt NO on Windows

How to read dsregcmd /status when the Primary Refresh Token is missing, find the likely cause, and apply fixes from the least to the most invasive.

Editorial note: This article was drafted with AI assistance and reviewed for technical clarity, accuracy, and practical relevance before publication.

When a user on a Windows device is asked to sign in again and again to Microsoft 365, or Conditional Access says the device is not compliant although Intune shows it as managed, the first thing to check is the Primary Refresh Token. In dsregcmd /status, the symptom is a single line: AzureAdPrt : NO.

This article explains what the Primary Refresh Token is, how to read the relevant dsregcmd fields, which causes are most common, and which fixes to try first. It also shows where Smart Device Registration Tool helps support teams collect the same evidence without asking users to read command output.

What the Primary Refresh Token does

The Primary Refresh Token (PRT) is a key artifact of Microsoft Entra ID authentication on Windows. It is issued to a user on a specific device when the user signs in to Windows on a Microsoft Entra joined or Microsoft Entra hybrid joined device. Windows then uses it to provide single sign-on to applications and services protected by Microsoft Entra ID.

  • The PRT is bound to the device. When the device has a usable TPM, the keys that protect it are stored in the TPM.
  • It carries device claims, which Conditional Access uses to check that the request comes from a joined, compliant, or hybrid joined device.
  • Windows renews it in the background while the user is signed in and connected.

Without a PRT, users still work, but they get repeated sign-in prompts, browsers do not pass device identity, and device-based Conditional Access policies can block access.

Run dsregcmd in the right context

Run dsregcmd /status in a normal command prompt opened by the affected user. The SSO State section describes the user who runs the command: if a support technician runs it from another account or with another user's credentials, the result says nothing about the affected user's token.

+----------------------------------------------------------------------+
| Device State                                                         |
+----------------------------------------------------------------------+
             AzureAdJoined : YES
          EnterpriseJoined : NO
              DomainJoined : YES
                DomainName : WORKPLACECLOUDHUB
+----------------------------------------------------------------------+
| SSO State                                                            |
+----------------------------------------------------------------------+
                AzureAdPrt : NO
       AzureAdPrtAuthority :

Read the fields that matter

Start with the device, then the user.

Section Field What to look for
Device State AzureAdJoined YES on a Microsoft Entra joined or hybrid joined device. NO means the device is not registered yet, and no PRT can be issued.
Device State DomainJoined YES together with AzureAdJoined : YES indicates hybrid join.
Device Details DeviceAuthStatus SUCCESS when the device object is usable. A failure usually means the device object is disabled or deleted in Microsoft Entra ID.
Device Details TpmProtected Whether the device keys are protected by the TPM.
SSO State AzureAdPrt YES when the signed-in user has a PRT.
SSO State AzureAdPrtUpdateTime When the token was last renewed. An old value on a connected device points to a renewal problem.
Diagnostic Data Attempt Status, Server Error Code The result of the last token request and, when the service answered, its error code.

The Diagnostic Data section appears when the last attempt failed. Look up the server error code in Microsoft's documentation before acting: for example, AADSTS50155 indicates that device authentication failed, while AADSTS50126 indicates an invalid user name or password.

Common causes

The device is not joined yet

On a hybrid joined device, the PRT depends on a completed device registration. Registration needs the computer object to be in the synchronization scope of Microsoft Entra Connect, a successful synchronization, and the Automatic-Device-Join scheduled task under Microsoft\Windows\Workplace Join to run again after the user signs in. A recently imaged or recently moved computer often shows AzureAdJoined : NO simply because these steps are not finished.

The device object is stale, disabled, or duplicated

A device that was deleted or disabled in Microsoft Entra ID, or that was reimaged and registered again under the same name, can keep local registration data that no longer matches a usable object. DeviceAuthStatus and the DeviceId shown by dsregcmd help compare the local state with the object in the Microsoft Entra admin center.

The device cannot reach Microsoft Entra ID

Token requests are sent from the device to Microsoft Entra ID endpoints such as login.microsoftonline.com. An authenticating proxy, TLS inspection, a missing firewall rule, or a device that only reaches the network after sign-in can all prevent the token from being issued. Check the proxy configuration used by the system, not only the user's browser.

The password changed or the account does not match

After a password change, the PRT may not be renewed until the user signs in again with the new password while the device can reach Microsoft Entra ID. An on-premises account that is not synchronized, or that maps to a different cloud account, also prevents token issuance.

TPM or clock problems

A TPM in a bad state can block the use of the device keys, and a large clock difference between the device and the service can make authentication fail. Check the TPM status in Windows Security or with Get-Tpm, and check time synchronization before changing anything else.

Where to look in the event logs

Two Windows event logs give more detail than dsregcmd:

  • Applications and Services Logs > Microsoft > Windows > AAD > Operational: token requests and their errors for the signed-in user.
  • Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin: device registration and join attempts.

Correlate the time of each error with the user sign-in, the last network change, and the AzureAdPrtUpdateTime value.

Fixes, from the least to the most invasive

  1. Lock and unlock, or sign out and in again, while the device is connected to the corporate network or the internet. This gives Windows a fresh chance to request the token.
  2. Request a renewal of the token for the current user with dsregcmd /refreshprt, then run dsregcmd /status again and compare AzureAdPrtUpdateTime.
  3. Fix the cause you identified: proxy or firewall rules, time synchronization, the user's password or synchronized account, or the TPM state.
  4. Check the device object in the Microsoft Entra admin center: enabled, not duplicated, and, for hybrid join, in the synchronization scope.
  5. Run the Automatic-Device-Join task again on a hybrid joined device after the computer object is synchronized.
  6. Leave and join again only as a last resort, with administrator rights and a clear plan: dsregcmd /leave removes the local registration, the device object may need cleanup, and Intune enrollment and compliance must be checked again afterwards.

Do not clear the TPM to fix a missing PRT without a BitLocker recovery plan: clearing it can trigger BitLocker recovery and removes keys that other components rely on.

How Smart Device Registration Tool helps

Smart Device Registration Tool gives support teams the same evidence in a form users can share:

  • The User view runs without administrator rights and summarizes the work account, the organization connection, and the device management detected locally. Evidence that cannot be confirmed stays unconfirmed.
  • Renew my work connection requests a renewal of the current session's Primary Refresh Token after the user confirms, then runs the check again. It never joins, leaves, or re-enrolls the device, and a renewal stays unconfirmed until a newer token is observed.
  • An optional Microsoft Graph check reads the signed-in user's own assigned licenses. The Microsoft Graph authentication module is installed separately.
  • Admin mode keeps guarded repair actions for support: dsregcmd leave or join workflows, removal of stale MDM enrollment traces, triggering Intune auto-enrollment, and starting the Automatic-Device-Join task.

When the token is present but Intune enrollment or the Intune Management Extension still fails, continue with How to Troubleshoot Intune Device Enrollment Failures and analyze the device diagnostics with Smart Endpoint Diagnostics Analyzer.

Checklist

Step Check Expected result
1 Run dsregcmd /status as the affected user Output collected in the user's context
2 Device State AzureAdJoined : YES
3 Device Details DeviceAuthStatus : SUCCESS
4 SSO State AzureAdPrt : YES with a recent update time
5 Diagnostic Data No error, or a server error code you can explain
6 Event logs AAD Operational and User Device Registration Admin reviewed
7 Network and time Microsoft Entra ID endpoints reachable, clock synchronized
8 Device object Enabled, unique, and in the synchronization scope

Boundaries

AzureAdPrt : YES shows that the signed-in user holds a token on this device at the time of the check. It does not prove that Intune enrollment is healthy, that the device is compliant, that Conditional Access will allow a given application, or that the user's licenses are active. Smart Device Registration Tool reports local evidence; confirm management, compliance, and licensing in the Microsoft Intune and Microsoft Entra admin centers. Its exports and support bundles are not anonymized: they can contain user, device, tenant, and event-log details, so review and protect them before sharing.

Frequently asked questions

What does AzureAdPrt NO mean in the dsregcmd output?

It means that the user who ran the command has no Primary Refresh Token on this device at the time of the check. Single sign-on to Microsoft Entra ID resources and device claims for Conditional Access are then unavailable for that user. Check the device join state first, then the Diagnostic Data section.

Does a hybrid joined device have a PRT before a user signs in?

No. The Primary Refresh Token is issued to a user when that user signs in to Windows on a joined or hybrid joined device. A device can be correctly hybrid joined while no user on it holds a token yet.

How can I force a PRT renewal?

Lock and unlock the session, or sign out and in again, while the device can reach Microsoft Entra ID. You can also run dsregcmd /refreshprt as the affected user, then compare AzureAdPrtUpdateTime in dsregcmd /status before and after.

Does AzureAdPrt YES prove that the device is healthy?

No. It shows that the signed-in user holds a token on this device at the time of the check. It does not prove Intune enrollment health, compliance, Conditional Access results, or license activation.