Skip to content

Commit a8bf39b

Browse files
authored
Merge pull request #101158 from MicrosoftGuyJFlo/SecurityDefaultsUpdate
[Azure AD] Security Defaults - Update from PG
2 parents 5e3f5a6 + 370e0bc commit a8bf39b

File tree

2 files changed

+12
-7
lines changed

2 files changed

+12
-7
lines changed

articles/active-directory/conditional-access/concept-conditional-access-policy-common.md

Lines changed: 7 additions & 5 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: 12/10/2019
9+
ms.date: 01/14/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -30,15 +30,17 @@ More information about emergency access accounts and why they are important can
3030

3131
## Typical policies deployed by organizations
3232

33-
* [Require MFA for administrators](howto-conditional-access-policy-admin-mfa.md)
34-
* [Require MFA for Azure management](howto-conditional-access-policy-azure-management.md)
35-
* [Require MFA for all users](howto-conditional-access-policy-all-users-mfa.md)
36-
* [Block legacy authentication](howto-conditional-access-policy-block-legacy.md)
33+
* [Require MFA for administrators](howto-conditional-access-policy-admin-mfa.md)\*
34+
* [Require MFA for Azure management](howto-conditional-access-policy-azure-management.md)\*
35+
* [Require MFA for all users](howto-conditional-access-policy-all-users-mfa.md)\*
36+
* [Block legacy authentication](howto-conditional-access-policy-block-legacy.md)\*
3737
* [Risk-based Conditional Access (Requires Azure AD Premium P2)](howto-conditional-access-policy-risk.md)
3838
* [Require trusted location for MFA registration](howto-conditional-access-policy-registration.md)
3939
* [Block access by location](howto-conditional-access-policy-location.md)
4040
* [Require compliant device](howto-conditional-access-policy-compliant-device.md)
4141

42+
\* These four policies when configured together, would mimic functionality enabled by [security defaults](../fundamentals/concept-fundamentals-security-defaults.md).
43+
4244
## Next steps
4345

4446
- [Simulate sign in behavior using the Conditional Access What If tool.](troubleshoot-conditional-access-what-if.md)

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

Lines changed: 5 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: 12/06/2019
9+
ms.date: 01/14/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -25,7 +25,10 @@ Microsoft is making security defaults available to everyone. The goal is to ensu
2525

2626
![Screenshot of the Azure portal with the toggle to enable security defaults](./media/concept-fundamentals-security-defaults/security-defaults-azure-ad-portal.png)
2727

28-
The following security configurations will be turned on in your tenant.
28+
> [!TIP]
29+
> If your tenant was created on or after October 22nd, 2019, it’s possible you are experiencing the new secure-by-default behavior and already have security defaults enabled in your tenant. In an effort to protect all of our users, security defaults is being rolled out to all new tenants created.
30+
31+
More details on why security defaults are being made available can be found in Alex Weinert's blog post, [Introducing security defaults](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/introducing-security-defaults/ba-p/1061414).
2932

3033
## Unified Multi-Factor Authentication registration
3134

0 commit comments

Comments
 (0)