Skip to content

Commit a7f535d

Browse files
authored
Merge pull request #178408 from cloudhandler/patch-67
Add risk analysis info
2 parents 3dbd1bd + 56665c4 commit a7f535d

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

articles/active-directory/reports-monitoring/howto-use-azure-monitor-workbooks.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Do you want to:
2727

2828
- Troubleshoot sign-in failures to get a better view of your organization's sign-in health and to resolve issues quickly?
2929

30+
- Understand risky users and risk detections trends in your tenant?
31+
3032
- Know who's using legacy authentications to sign in to your environment? (By [blocking legacy authentication](../conditional-access/block-legacy-authentication.md), you can improve your tenant's protection.)
3133

3234
- Do you need to understand the impact of Conditional Access policies in your tenant?
@@ -292,9 +294,25 @@ To help you troubleshoot sign-ins, Azure Monitor gives you a breakdown by the fo
292294
![Summary of sign-ins waiting on user action](./media/howto-use-azure-monitor-workbooks/54.png)
293295

294296

297+
## Identity Protection Risk Analysis
298+
299+
Use the **Identity Protection Risk Analysis** workbook in the **Usage** section to understand:
300+
301+
- Distribution in risky users and risk detections by levels and types
302+
- Opportunities to better remediate risk
303+
- Where in the world risk is being detected
304+
305+
You can filter the Risky Detections trends by:
306+
- Detection timing type
307+
- Risk level
295308

309+
Real-time risk detections are those that can be detected at the point of authentication. These detections can be challenged by risky sign-in policies using Conditional Access to require multi-factor authentication.
296310

311+
You can filter the Risky Users trends by:
312+
- Risk detail
313+
- Risk level
297314

315+
If you have a high number of risky users where "no action" has been taken, consider enabling a Conditional Access policy to require secure password change when a user is high risk.
298316

299317
## Next steps
300318

0 commit comments

Comments
 (0)