Microsoft Entra ID: Seamless SSO on Hybrid Azure AD-Joined Devices
Question details
The user wants to understand which single sign-on mechanism applies to domain-joined, Azure AD-joined, and hybrid Azure AD-joined devices.

- Product
- Microsoft Entra ID (formerly Azure Active Directory) Seamless Single Sign-On
- Device & OS
- not provided
- Scenario
- Determine whether Seamless SSO is used on hybrid Azure AD-joined devices and distinguish it from Primary Refresh Token-based SSO.
- Observed behavior
- Traditional domain-joined devices can use Seamless SSO, while Azure AD-joined and hybrid Azure AD-joined devices normally use a Primary Refresh Token for single sign-on.
Distinguish the device's join state from the user's sign-in method. If checking a Windows device, run the device-status command from the affected user's session so the user-specific token status is relevant.
Identify the device join state and its expected SSO mechanism
Use this comparison to understand why hybrid Azure AD-joined devices normally rely on a Primary Refresh Token rather than Seamless SSO.
Azure AD is now called Microsoft Entra ID. Seamless SSO is designed for traditional Active Directory domain-joined devices and uses Kerberos to provide automatic sign-in when its requirements are met.
Microsoft Entra-joined and hybrid Microsoft Entra-joined devices normally use Primary Refresh Token (PRT)-based SSO. Seamless SSO can remain enabled in a tenant that also has hybrid-joined devices, but it is not the normal SSO mechanism for those devices.
On the Windows device you want to inspect, open Command Prompt in the signed-in user's session and run dsregcmd /status. Locate the Device State section.
Read AzureAdJoined and DomainJoined. AzureAdJoined: NO with DomainJoined: YES indicates a traditional domain-joined device; AzureAdJoined: YES with DomainJoined: NO indicates a Microsoft Entra-joined device; both values set to YES indicate a hybrid Microsoft Entra-joined device.
For a Microsoft Entra-joined or hybrid-joined device, locate AzureAdPrt in the SSO State section of the command output. AzureAdPrt: YES indicates that the current user has a PRT. For a traditional domain-joined device, ask the identity administrator to verify that Seamless SSO is enabled and that the device meets its domain-connectivity and browser requirements.

Use WPS Office for Local Document Work While Microsoft Sign-In Is Investigated
WPS Office is a free, lightweight alternative for everyday document editing, with a familiar interface and Microsoft Office format compatibility for easy migration. It can help you continue working with accessible local files, but it does not repair Microsoft Entra ID, Seamless SSO, or PRT issues.

Frequently Asked Questions
Can Seamless SSO and hybrid Azure AD join exist in the same tenant?
Yes. Seamless SSO can be enabled in a tenant that contains hybrid-joined devices. However, hybrid Microsoft Entra-joined devices normally use PRT-based SSO, not Seamless SSO.
Why does a hybrid-joined device use a PRT if it is also domain-joined?
Hybrid join gives the device both an on-premises Active Directory identity and a Microsoft Entra identity. Its Microsoft Entra single sign-on normally uses the user's Primary Refresh Token; domain membership alone does not make Seamless SSO the expected mechanism.
How can I check whether my Windows device is hybrid Azure AD-joined?
Open Command Prompt and run dsregcmd /status. In Device State, AzureAdJoined: YES and DomainJoined: YES indicate a hybrid Microsoft Entra-joined device. To check the current user's PRT, run the command in that user's session and inspect AzureAdPrt under SSO State.
Does AzureAdPrt: YES guarantee that every Office app will sign in without a prompt?
No. It indicates that the current user has a PRT, but application support, account selection, Conditional Access requirements, and session policies can still cause prompts. If prompts persist, record the affected app and sign-in error and ask your identity administrator to review the Microsoft Entra sign-in logs.




