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.
@@ -35,7 +35,7 @@ The following Windows components play a key role in requesting and using a Prima 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. +- **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.@@ -123,12 +123,12 @@ Linux - Microsoft Edge will pull the PRT from the broker into the browser' The list of supported browsers is available here: [Supported Browsers](../conditional-access/concept-conditional-access-conditions.md#supported-browsers) > [!NOTE]-> Customers who enable Entra federation with non-Microsoft Identity Providers must configure those Identity Providers to support WS-Trust protocol to enable PRT issuance on Windows 10 or newer devices. Without WS-Trust for federation cases, a PRT can't be issued to users on Microsoft Entra hybrid joined or Microsoft Entra joined devices. +> Customers who enable Entra federation with non-Microsoft Identity Providers must configure those Identity Providers to support WS-Trust protocol to enable PRT issuance on Windows 10 or newer devices. Without WS-Trust for federation cases, a PRT can't be issued to users on Microsoft Entra hybrid joined or Microsoft Entra joined devices. > [!NOTE] > For ADFS, `usernamemixed` endpoints are required. If `Smartcard/certificate` is used during Windows sign-in, then `certificatemixed` endpoints need to be configured on ADFS. `windowstransport` should be enabled as intranet facing endpoints only and **must NOT be exposed** as extranet facing endpoints through the Web Application Proxy. -> [!NOTE] +> [!NOTE] > Microsoft Entra Conditional Access policies aren't evaluated when PRTs are issued. > [!NOTE]@@ -141,8 +141,7 @@ The list of supported browsers is available here: [Supported Browsers](../condit 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-](https://chrome.google.com/webstore/detail/windows-10-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji?hl=en) extension) and Mozilla Firefox v91+ (Firefox [Windows SSO setting](https://support.mozilla.org/kb/windows-sso)).+- **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](https://chrome.google.com/webstore/detail/windows-10-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji?hl=en) extension) and Mozilla Firefox v91+ (Firefox [Windows SSO setting](https://support.mozilla.org/kb/windows-sso)). > [!NOTE] > In instances where a user has two accounts from the same Microsoft Entra tenant signed in to a browser application, the device authentication provided by the PRT of the primary account is automatically applied to the second account as well. As a result, the second account also satisfies any device-based Conditional Access policy on the tenant. @@ -158,7 +157,7 @@ For iOS, only Microsoft Edge and Safari are supported for Browser SSO. ### [Android](#tab/android-prt-used) -For Android, only Microsoft Edge is supported for Browser SSO. +For Android, only Microsoft Edge is supported for Browser SSO. ### [Linux](#tab/linux-prt-used) @@ -201,11 +200,11 @@ On iOS, there’s also an opportunistic update when device is charging, happenin ### [Linux](#tab/linux-prt-renewal) -A PRT is valid for 90 days and is renewed every 4 hours if the user actively uses the device. +A PRT is valid for 90 days and is renewed every 4 hours if the user actively uses the device. ### [Android](#tab/android-prt-renewal) -- A PRT is valid for 90 days and is continuously renewed as long as the user actively uses the device. +- 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](/windows-server/identity/ad-fs/operations/walkthrough--workplace-join-to-an-android-device)) 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.@@ -233,7 +232,7 @@ By securing these keys with the TPM, we enhance the security for PRT from malici 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. +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. 