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/plan-conditional-access.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Planning your Conditional Access deployment is critical to achieving your organi
23
23
24
24
With this evaluation and enforcement, Conditional Access defines the basis of [Microsoft’s Zero Trust security posture management](https://www.microsoft.com/security/business/zero-trust).

27
27
28
28
Microsoft provides [security defaults](../fundamentals/concept-fundamentals-security-defaults.md) that ensure a basic level of security enabled in tenants that don't have Azure AD Premium. With Conditional Access, you can create policies that provide the same protection as security defaults, but with granularity. Conditional Access and security defaults aren't meant to be combined as creating Conditional Access policies will prevent you from enabling security defaults.

189
189
190
190
A descriptive name helps you to keep an overview of your Conditional Access implementation. The Sequence Number is helpful if you need to reference a policy in a conversation. For example, when you talk to an administrator on the phone, you can ask them to open policy CA01 to solve an issue.
191
191
@@ -263,7 +263,7 @@ If a user has an issue with a Conditional Access policy, collect the following i
263
263
264
264
If the user received a message with a More details link, they can collect most of this information for you.
265
265
266
-

266
+

267
267
268
268
Once you've collected the information, See the following resources:
Copy file name to clipboardExpand all lines: articles/active-directory/identity-protection/how-to-deploy-identity-protection.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title:
3
-
description:
2
+
title: Plan an Azure AD Identity Protection deployment
3
+
description: Deploy Azure Active Directory Identity Protection
4
4
5
5
services: active-directory
6
6
ms.service: active-directory
@@ -45,15 +45,15 @@ When technology projects fail, they typically do so due to mismatched expectatio
45
45
46
46
### Communication plan
47
47
48
-
Communication is critical to the success of any new functionality. You should proactively communicate with your users how their experience will change, when it will change, and how to get support if they experience issues.
48
+
Communication is critical to the success of any new functionality. You should proactively communicate with your users how their [experience](concept-identity-protection-user-experience.md) will change, when it will change, and how to get support if they experience issues.
49
49
50
50
## Step 1: Review existing reports
51
51
52
-
It's important to understand your current Identity Protection reports before deploying risk based Conditional Access policies. This is to give you an understanding of your environment, investigate suspicious behavior you may have missed and to dismiss or confirm safe user who you have determined aren't at risk. We recommend allowing users to self-remediate through policies that will be discussed in [Step 3](#step-3-configure-your-policies).
52
+
It's important to understand your current Identity Protection reports before deploying risk based Conditional Access policies. This review is to give you an understanding of your environment, investigate suspicious behavior you may have missed and to dismiss or confirm safe user who you have determined aren't at risk. We recommend allowing users to self-remediate through policies that will be discussed in [Step 3](#step-3-configure-your-policies).
53
53
54
54
### Existing risk detections
55
55
56
-
If your users haven't been remediating risk, then they may have accumulated risk. Users who reset their password on-premises don't remediate risk. Make sure before you dismiss risks, you've determined they aren't really at risk by [investigating risk detections](howto-identity-protection-investigate-risk.md). After investigating you can remediate user risk by following the steps in the article, [Remediate risks and unblock users](howto-identity-protection-remediate-unblock.md). Make bulk changes to user risk by following the samples in the article, [Azure Active Directory Identity Protection and the Microsoft Graph PowerShell](howto-identity-protection-graph-api.md).
56
+
If your users haven't been remediating risk, then they may have accumulated risk. Users who reset their password on-premises don't remediate risk. Make sure before you dismiss risks, you've determined they aren't really at risk by [investigating risk detections](howto-identity-protection-investigate-risk.md). After investigating, you can remediate user risk by following the steps in the article, [Remediate risks and unblock users](howto-identity-protection-remediate-unblock.md). Make bulk changes to user risk by following the samples in the article, [Azure Active Directory Identity Protection and the Microsoft Graph PowerShell](howto-identity-protection-graph-api.md).
57
57
58
58
## Step 2: Plan for Conditional Access risk policies
59
59
@@ -77,11 +77,11 @@ Plan your Azure Active Directory Multi-Factor Authentication deployment with Con
77
77
78
78
### Known network locations
79
79
80
-
It's important to configure named locations in Conditional Access and add your VPN ranges to Defender for Cloud Apps. Sign-ins from named locations, marked as trusted or known, improve the accuracy of Azure AD Identity Protection's risk calculation. These sign-ins lower a user's risk when they authenticate from a location marked as trusted or known. This will reduce false positives for some detections in your environment.
80
+
It's important to configure named locations in Conditional Access and add your VPN ranges to Defender for Cloud Apps. Sign-ins from named locations, marked as trusted or known, improve the accuracy of Azure AD Identity Protection's risk calculation. These sign-ins lower a user's risk when they authenticate from a location marked as trusted or known. This practice will reduce false positives for some detections in your environment.
81
81
82
82
### Report only mode
83
83
84
-
Report-only mode is a Conditional Access policy state that allows administrators to evaluate the impact of Conditional Access policies before enforcing them in their environment.
84
+
Report-only mode is a Conditional Access policy state that allows administrators to evaluate the effect of Conditional Access policies before enforcing them in their environment.
85
85
86
86
## Step 3: Configure your policies
87
87
@@ -93,13 +93,13 @@ Use the Identity Protection multifactor authentication registration policy to he
93
93
94
94
Most users have a normal behavior that can be tracked, when they fall outside of this norm it could be risky to allow them to just sign in. You may want to block that user or maybe just ask them to perform multi-factor authentication to prove that they're really who they say they are. You may want to start by scoping these policies to admins only.
95
95
96
-
The guidance in the article [Common Conditional Access policy: Sign-in risk-based multifactor authentication](../conditional-access/howto-conditional-access-policy-risk.md) provides guidance to create a sign-in risk policy.
96
+
The article [Common Conditional Access policy: Sign-in risk-based multifactor authentication](../conditional-access/howto-conditional-access-policy-risk.md) provides guidance to create a sign-in risk policy.
97
97
98
98
### Conditional Access user risk
99
99
100
100
Microsoft works with researchers, law enforcement, various security teams at Microsoft, and other trusted sources to find leaked username and password pairs. When these vulnerable users are detected, we recommend requiring users perform multifactor authentication then reset their password.
101
101
102
-
The guidance in the article [Common Conditional Access policy: User risk-based password change](../conditional-access/howto-conditional-access-policy-risk-user.md) provides guidance to create a user risk policy that requires password change.
102
+
The article [Common Conditional Access policy: User risk-based password change](../conditional-access/howto-conditional-access-policy-risk-user.md) provides guidance to create a user risk policy that requires password change.
103
103
104
104
### Migrating from older Identity Protection policies
105
105
@@ -116,22 +116,22 @@ For more information, see the section [Migrate risk policies from Identity Prote
116
116
117
117
### Enable notifications
118
118
119
-
Enable notifications so you can respond when a user is flagged as at risk so you can start investigating immediately. You can also set up weekly digest emails giving you an overview of risk for that week in your tenant.
119
+
[Enable notifications](howto-identity-protection-configure-notifications.md) so you can respond when a user is flagged as at risk so you can start investigating immediately. You can also set up weekly digest emails giving you an overview of risk for that week.
120
120
121
121
### Monitor and investigate
122
122
123
-
Investigate risk with Identity Protection Alerts (in DRAFT)
124
-
Identity Protection workbook to help monitor and look for patterns in your tenant. Monitor this workbook for trends and also Conditional Access Report Only mode results to see if there are any tweaks that need to be made, for example, additions to named locations.
123
+
The [Identity Protection workbook](../reports-monitoring/workbook-risk-analysis.md) can help monitor and look for patterns in your tenant. Monitor this workbook for trends and also Conditional Access Report Only mode results to see if there are any changes that need to be made, for example, additions to named locations.
125
124
126
-
How to investigate anomaly detection with Defender for Cloud App Security Alerts
127
-
You can also use the Identity Protection APIs to export the risk to your SIEM tool so your security team can monitor and alert on risk events.
125
+
Microsoft Defender for Cloud Apps provides an investigation framework organizations can use as a starting point. For more information, see the article [How to investigate anomaly detection alerts] (/defender-cloud-apps/investigate-anomaly-alerts).
128
126
129
-
During this testing time, you might want to simulate some threats Identity Protection protects against so you can see some of these risks.
127
+
You can also use the Identity Protection APIs to [export risk information](howto-export-risk-data.md) to other tools, so your security team can monitor and alert on risk events.
128
+
129
+
During testing, you might want to [simulate some threats](howto-identity-protection-simulate-risk.md) to test your investigation processes.
130
130
131
131
## Step 5: Enable Conditional Access policies
132
132
133
133
After you've completed all your analysis, evaluated policies in report only mode, and you have your stakeholders on board it's time to turn on your Conditional Access risk policies.
134
134
135
135
## Next steps
136
136
137
-
137
+
[What is risk?](concept-identity-protection-risks.md)
Identity Protection uses the learnings Microsoft has acquired from their position in organizations with Azure Active Directory, the consumer space with Microsoft Accounts, and in gaming with Xbox to protect your users. Microsoft analyses trillions of signals per day to identify and protect customers from threats. Identity Protection allows organizations to accomplish three key tasks:
20
+
Identity Protection allows organizations to accomplish three key tasks:
21
21
22
22
-[Automate the detection and remediation of identity-based risks](howto-identity-protection-configure-risk-policies.md).
23
23
-[Investigate risks](howto-identity-protection-investigate-risk.md) using data in the portal.
24
24
-[Export risk detection data to other tools](howto-export-risk-data.md).
Identity Protection uses the learnings Microsoft has acquired from their position in organizations with Azure Active Directory, the consumer space with Microsoft Accounts, and in gaming with Xbox to protect your users. Microsoft analyses trillions of signals per day to identify and protect customers from threats.
29
+
26
30
The signals generated by and fed to Identity Protection, can be further fed into tools like Conditional Access to make access decisions, or fed back to a security information and event management (SIEM) tool for further investigation.
27
31
28
32
## Why is automation important?
@@ -110,8 +114,4 @@ More information on these rich reports can be found in the article, [How To: Inv
0 commit comments