Skip to content

Commit b01a3cd

Browse files
authored
Merge pull request #108071 from MicrosoftGuyJFlo/IdentityProtectionPerms
[Azure AD] Identity Protection - GitHub Issue 50281
2 parents 698f74b + eedf778 commit b01a3cd

File tree

1 file changed

+13
-4
lines changed

1 file changed

+13
-4
lines changed

articles/active-directory/identity-protection/overview-identity-protection.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: identity-protection
88
ms.topic: overview
9-
ms.date: 10/18/2019
9+
ms.date: 03/17/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -45,12 +45,12 @@ Identity Protection identifies risks in the following classifications:
4545

4646
| Risk detection type | Description |
4747
| --- | --- |
48-
| Atypical travel | Sign in from an atypical location based on the users recent sign-ins. |
48+
| Atypical travel | Sign in from an atypical location based on the user's recent sign-ins. |
4949
| Anonymous IP address | Sign in from an anonymous IP address (for example: Tor browser, anonymizer VPNs). |
50-
| Unfamiliar sign-in properties | Sign in with properties weve not seen recently for the given user. |
50+
| Unfamiliar sign-in properties | Sign in with properties we've not seen recently for the given user. |
5151
| Malware linked IP address | Sign in from a malware linked IP address |
5252
| Leaked Credentials | This risk detection indicates that the user's valid credentials have been leaked |
53-
| Azure AD threat intelligence | Microsofts internal and external threat intelligence sources have identified a known attack pattern |
53+
| Azure AD threat intelligence | Microsoft's internal and external threat intelligence sources have identified a known attack pattern |
5454

5555
More detail on these risks and how/when they are calculated can be found in the article, [What is risk](concept-identity-protection-risks.md).
5656

@@ -76,6 +76,15 @@ Information about integrating Identity Protection information with Azure Sentine
7676

7777
Identity Protection requires users be a Security Reader, Security Operator, Security Administrator, Global Reader, or Global Administrator in order to access.
7878

79+
| Role | Can do | Can't do |
80+
| --- | --- | --- |
81+
| Global administrator | Full access to Identity Protection | |
82+
| Security administrator | Full access to Identity Protection | Reset password for a user |
83+
| Security operator | View all Identity Protection reports and Overview blade <br><br> Dismiss user risk, confirm safe sign-in, confirm compromise | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts |
84+
| Security reader | View all Identity Protection reports and Overview blade | Configure or change policies <br><br> Reset password for a user <br><br> Configure alerts <br><br> Give feedback on detections |
85+
86+
Conditional Access administrators can also create policies that factor in sign-in risk as a condition, find more information in the article [Conditional Access: Conditions](../conditional-access/concept-conditional-access-conditions.md#sign-in-risk).
87+
7988
## License requirements
8089

8190
[!INCLUDE [Active Directory P2 license](../../../includes/active-directory-p2-license.md)]

0 commit comments

Comments
 (0)