Skip to content

Commit d20c370

Browse files
authored
edit identity-protection-investigate-risk.md
1 parent 125f40b commit d20c370

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory-b2c/identity-protection-investigate-risk.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Azure AD B2C Premium P2 is required for some Identity Protection features. If ne
6666

6767
With the information provided by the risky users report, administrators can find:
6868

69-
- Which users are at risk, have had risk remediated, or have had risk dismissed?
69+
- The **Risk state**, showing which users are **At risk**, have had risk **Remediated**, or have had risk **Dismissed**
7070
- Details about detections
7171
- History of all risky sign-ins
7272
- Risk history
@@ -79,7 +79,7 @@ Administrators can then choose to take action on these events. Administrators ca
7979
- Block user from signing in
8080
- Investigate further using Azure ATP
8181

82-
**Dismissed** is an operation that is perform by an administrator to dismiss a risk. The administrator dismisses the risk through the Azure portal, or programmatically through the Microsoft Graph API [Dismiss User Risk](https://docs.microsoft.com/graph/api/riskyusers-dismiss?view=graph-rest-beta&preserve-view=true). The **Dismissed** is considered a privileged action as conducted by an administrator. The **Remediated** is an action performers by the risky user, or by an administrator, on behalf of a user to remediate the risk. For example, password reset.
82+
An administrator can choose to dismiss a user's risk in the Azure portal or programmatically through the Microsoft Graph API [Dismiss User Risk](https://docs.microsoft.com/graph/api/riskyusers-dismiss?view=graph-rest-beta&preserve-view=true). Administrator privileges are required to dismiss a user's risk. Remediating a risk can be performed by the risky user or by an administrator on the user's behalf, for example through a password reset.
8383

8484
### Navigating the risky users report
8585

@@ -120,4 +120,4 @@ Administrators can then choose to return to the user's risk or sign-ins report t
120120

121121
## Next steps
122122

123-
- [Add Conditional Access to a user flow](conditional-access-user-flow.md).
123+
- [Add Conditional Access to a user flow](conditional-access-user-flow.md).

0 commit comments

Comments
 (0)