Skip to content

Commit fe6ae52

Browse files
authored
Merge pull request #52983 from John-Gallagher-JPG/patch-1
Update overview.md
2 parents d57d2be + a141a50 commit fe6ae52

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/active-directory/devices/overview.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,9 @@ To get a device in Azure AD, you have multiple options:
5252

5353
![Devices displayed in Azure AD Devices blade](./media/overview/azure-active-directory-devices-all-devices.png)
5454

55+
> [!NOTE]
56+
> A hybrid state refers to more than just the state of a device. For a hybrid state to be valid, a valid Azure AD user also is required.
57+
5558
## Device management
5659

5760
Devices in Azure AD can be managed using Mobile Device Management (MDM) tools like Microsoft Intune, Microsoft Endpoint Configuration Manager, Group Policy (hybrid Azure AD join), Mobile Application Management (MAM) tools, or other third-party tools.
@@ -63,6 +66,8 @@ Registering and joining devices to Azure AD gives your users Seamless Sign-on (S
6366
> [!NOTE]
6467
> Device-based Conditional Access policies require either hybrid Azure AD joined devices or compliant Azure AD joined or Azure AD registered devices.
6568
69+
The primary refresh token (PRT) contains information about the device and is required for SSO. If you have a device-based Conditional Access policy set on an application, without the PRT, access is denied. Hybrid Conditional Access policies require a hybrid state device and a valid user who is signed in.
70+
6671
Devices that are Azure AD joined or hybrid Azure AD joined benefit from SSO to your organization's on-premises resources as well as cloud resources. More information can be found in the article, [How SSO to on-premises resources works on Azure AD joined devices](azuread-join-sso.md).
6772

6873
## Device security

0 commit comments

Comments
 (0)