Microsoft Entra ID
Fundamentals

Primary Refresh Token

In brief

The article was revised in sections covering registered device PRTs, WS-Trust requirements, WAM and browser SSO, PRT validity and renewal, and device-signing-key issuance.

What Entra admins need to know

Use the updated guidance when troubleshooting PRT issuance and Windows or Android browser SSO. No administrator action is specified.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

At a high level, there are two different types of PRT artifacts.

  • Registered device PRTs are bound to a device that has an associated Microsoft Entra identity.
  • Unregistered device PRTs are bound to a device that doesn't have a Microsoft Entra identity, which is associated with an on-device cryptographic key pair generated by the client.

Clients always attempt to use "registered device PRTs" whenever possible. PRTs only satisfy device registration policies if they're issued for registered devices. Unregistered device PRTs are used in scenarios where the device doesn't have a Microsoft Entra identity, such as when a user signs in to a browser on a personal device or when a user signs in to an app that doesn't support device registration. The list of supported browsers is available here: Supported Browsers

A PRT is used by two key components in Windows:

  • Microsoft Entra CloudAP plugin: During Windows sign in, the Microsoft Entra CloudAP plugin requests a PRT from Microsoft Entra ID using the credentials provided by the user. It also caches the PRT to enable cached sign in when the user doesn't have access to an internet connection.
  • Microsoft Entra WAM plugin: When users try to access applications, the Microsoft Entra WAM plugin uses the PRT to enable SSO on Windows 10 or newer. Microsoft Entra WAM plugin uses the PRT to request refresh and access tokens for applications that rely on WAM for token requests. It also enables SSO on browsers by injecting the PRT into browser requests. Browser SSO in Windows 10 or newer is supported on Microsoft Edge (natively), Chrome (via the Microsoft Single Sign On extension) and Mozilla Firefox v91+ (Firefox Windows SSO setting).

Android

For Android, only Microsoft Edge is supported for Browser SSO.

Linux

Linux

A PRT is valid for 90 days and is renewed every 4 hours if the user actively uses the device.

Android

  • A PRT is valid for 90 days and is continuously renewed as long as the user actively uses the device.
  • A PRT is only issued and renewed during native app authentication. A PRT isn't renewed or issued during a browser session.
  • It's possible to obtain a PRT without the need for device registration (Workplace Join) and enable SSO.
  • PRTs obtained without device registration can't satisfy the authorization criteria for Conditional Access that relies on the device's status or compliance.

A Primary Refresh Token (PRT) is securely bound to the device on which the user signs in. Microsoft Entra ID and macOS enforce this protection through several mechanisms:

The PRT is issued only after a request is signed using a secure enclave–backed Device Signing Key, which is cryptographically generated during device registration. If the signature from this key can't be validated, the PRT won't be issued.

For macOS where Platform SSO is used, it will use hardware binding by default.

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…