Skip to content

Commit 2a7f3d3

Browse files
committed
expanded CA info
1 parent 2bc8ca0 commit 2a7f3d3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/external-identities/authentication-conditional-access.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 06/07/2022
9+
ms.date: 06/30/2022
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -76,7 +76,7 @@ Organizations can enforce Conditional Access policies for external B2B collabora
7676

7777
In an Azure AD cross-tenant scenario, the resource organization can create Conditional Access policies that require MFA or device compliance for all guest and external users. Generally, a B2B collaboration user accessing a resource is then required to set up their Azure AD MFA with the resource tenant. However, Azure AD now offers the ability to trust MFA claims from other Azure AD tenants. Enabling MFA trust with another tenant streamlines the sign-in process for B2B collaboration users and enables access for B2B direct connect users.
7878

79-
If you've configured your inbound trust settings to accept MFA claims from a B2B collaboration or B2B direct connect user's home tenant, Azure AD checks the user's credentials during authentication. If the credentials contain a claim indicating that MFA policies have already been met in the user's home tenant, the user is granted seamless sign-on to your shared resource.
79+
If you've configured your inbound trust settings to accept MFA claims from a B2B collaboration or B2B direct connect user's home tenant, Azure AD checks the user's authentication session. If the session contains a claim indicating that MFA policies have already been met in the user's home tenant, the user is granted seamless sign-on to your shared resource.
8080

8181
If MFA trust isn't enabled, the user experience is different for B2B collaboration users and B2B direct connect users:
8282

@@ -138,7 +138,7 @@ Organizations can use Conditional Access policies to require users' devices to b
138138

139139
However, you can use device trust settings to unblock external users while still requiring managed devices. In your cross-tenant access settings, you can choose to trust claims from an external user's home tenant about whether the user's device meets their device compliance policies or is [hybrid Azure AD joined](../conditional-access/howto-conditional-access-policy-compliant-device.md). You can set device trust settings for all Azure AD organizations or individual organizations.
140140

141-
When device trust settings are enabled, Azure AD checks a user's credentials during authentication for a device ID to determine if the policies have already been met in the user's home tenant. If so, the external user is granted seamless sign-on to your shared resource.
141+
When device trust settings are enabled, Azure AD checks a user's authentication session for a device claim. If the session contains a device claim indicating that the policies have already been met in the user's home tenant, the external user is granted seamless sign-on to your shared resource.
142142

143143
>[!Important]
144144
>

0 commit comments

Comments
 (0)