Skip to content

Commit 1e453cf

Browse files
Merge pull request #210930 from SanDeo-MSFT/patch-111
Update concept-fundamentals-security-defaults.md
2 parents 37006a4 + bb49b47 commit 1e453cf

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/active-directory/fundamentals/concept-fundamentals-security-defaults.md

Lines changed: 6 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: conditional-access
88
ms.topic: conceptual
9-
ms.date: 04/07/2022
9+
ms.date: 09/12/2022
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -91,6 +91,9 @@ After these attackers gain access, they can request access to privileged informa
9191

9292
One common method to improve protection for all users is to require a stronger form of account verification, such as Multi-Factor Authentication, for everyone. After users complete Multi-Factor Authentication registration, they'll be prompted for another authentication whenever necessary. Azure AD decides when a user will be prompted for Multi-Factor Authentication, based on factors such as location, device, role and task. This functionality protects all applications registered with Azure AD including SaaS applications.
9393

94+
> [!NOTE]
95+
> In case of [B2B direct connect](https://docs.microsoft.com/azure/active-directory/external-identities/b2b-direct-connect-overview) users, any Multi-Factor Authentication requirment due to security defaults enabled by resource tenant will need to be satisfied, including Multi-Factor Authentication registration by the direct connect user in their home tenant.
96+
9497
### Block legacy authentication protocols
9598

9699
To give your users easy access to your cloud apps, Azure AD supports various authentication protocols, including legacy authentication. *Legacy authentication* is a term that refers to an authentication request made by:
@@ -175,9 +178,9 @@ You may choose to [disable password expiration](../authentication/concept-sspr-p
175178

176179
For more detailed information about emergency access accounts, see the article [Manage emergency access accounts in Azure AD](../roles/security-emergency-access.md).
177180

178-
### B2B guest users
181+
### B2B users
179182

180-
Any B2B Guest users that access your directory will be subject to the same controls as your organization's users.
183+
Any [B2B guest](https://docs.microsoft.com/azure/active-directory/external-identities/what-is-b2b) users or [B2B direct connect](https://docs.microsoft.com/azure/active-directory/external-identities/b2b-direct-connect-overview) users that access your directory will be subject to the same controls as your organization's users.
181184

182185
### Disabled MFA status
183186

0 commit comments

Comments
 (0)