Skip to content

Commit 31973dc

Browse files
authored
Merge pull request #104020 from MicrosoftGuyJFlo/SecurityDefaultsUpdates
[Azure AD] - Security defaults update from PM
2 parents e8802e5 + 18742a1 commit 31973dc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 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: 01/14/2020
9+
ms.date: 02/11/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -71,7 +71,7 @@ To give your users easy access to your cloud apps, Azure AD supports a variety o
7171

7272
Today, the majority of compromising sign-in attempts come from legacy authentication. Legacy authentication does not support Multi-Factor Authentication. Even if you have a Multi-Factor Authentication policy enabled on your directory, an attacker can authenticate by using an older protocol and bypass Multi-Factor Authentication.
7373

74-
After security defaults are enabled in your tenant, all authentication requests made by an older protocol will be blocked. Security defaults don't block Exchange ActiveSync.
74+
After security defaults are enabled in your tenant, all authentication requests made by an older protocol will be blocked. Security defaults blocks Exchange Active Sync basic authentication.
7575

7676
> [!WARNING]
7777
> Before you enable security defaults, make sure your administrators aren't using older authentication protocols. For more information, see [How to move away from legacy authentication](concept-fundamentals-block-legacy-authentication.md).

0 commit comments

Comments
 (0)