You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/conditional-access/baseline-protection.md
+1-12Lines changed: 1 addition & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ This article provides you with an overview of baseline protection in Azure Activ
31
31
32
32
Users with access to privileged accounts have unrestricted access to your environment. Due to the power these accounts have, you should treat them with special care. One common method to improve the protection of privileged accounts is to require a stronger form of account verification when they are used to sign-in. In Azure Active Directory, you can get a stronger account verification by requiring multi-factor authentication (MFA).
33
33
34
-
**Require MFA for admins** is a baseline policy that requires MFA for the following directory roles:
34
+
**Require MFA for admins** is a baseline policy that requires MFA for the following directory roles:
35
35
36
36
* Global administrator
37
37
* SharePoint administrator
@@ -46,12 +46,8 @@ Users with access to privileged accounts have unrestricted access to your enviro
46
46
47
47
This baseline policy provides you with the option to exclude users. You might want to exclude one *[emergency-access administrative account](../users-groups-roles/directory-emergency-access.md)* to ensure you are not locked out of the tenant.
48
48
49
-
50
49
## Enable a baseline policy
51
50
52
-
While baseline policies are in preview, they are by default not activated. You need to manually enable a policy if you want to activate it. If you explicitly enable the baseline policies at the preview stage, they will remain active when this feature reaches general availability. The planned behavior change is the reason why, in addition to activate and deactivate, you have a third option to set the state of a policy: **Automatically enable policy in the future**. By selecting this option, you can leave the policies disabled during preview, but have Microsoft enable them automatically when this feature reaches general availability. If you do not explicitly enable baseline policies now, and do not select the **Automatically enable policy in the future** option, the policies will remain disabled when this feature reaches general availability.
53
-
54
-
55
51
**To enable a baseline policy:**
56
52
57
53
1. Sign in to the [Azure portal](https://portal.azure.com) as global administrator, security administrator, or conditional access administrator.
@@ -69,9 +65,6 @@ While baseline policies are in preview, they are by default not activated. You n
69
65
5. To enable the policy, click **Use policy immediately**.
70
66
71
67
6. Click **Save**.
72
-
73
-
74
-
75
68
76
69
## What you should know
77
70
@@ -83,14 +76,10 @@ If you have privileged accounts that are used in your scripts, you should replac
83
76
84
77
Baseline policies apply to legacy authentication flows like POP, IMAP, older Office desktop client.
85
78
86
-
87
-
88
-
89
79
## Next steps
90
80
91
81
For more information, see:
92
82
93
83
-[Five steps to securing your identity infrastructure](https://docs.microsoft.com/azure/security/azure-ad-secure-steps)
94
84
95
85
-[What is conditional access in Azure Active Directory?](overview.md)
0 commit comments