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/reports-monitoring/overview-flagged-sign-ins.md
+24-7Lines changed: 24 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,20 @@
2
2
3
3
title: What are flagged sign-ins in Azure Active Directory?
4
4
description: Provides a general overview of flagged sign-ins in Azure Active Directory.
5
+
services: active-directory
6
+
documentationcenter: ''
5
7
author: MarkusVi
6
8
manager: karenhoran
9
+
editor: ''
10
+
7
11
ms.assetid: e2b3d8ce-708a-46e4-b474-123792f35526
8
12
ms.service: active-directory
13
+
ms.devlang: na
9
14
ms.topic: overview
15
+
ms.tgt_pltfrm: na
10
16
ms.workload: identity
11
17
ms.subservice: report-monitor
12
-
ms.date: 10/27/2021
18
+
ms.date: 11/12/2021
13
19
ms.author: markvi
14
20
ms.reviewer: tspring
15
21
@@ -24,6 +30,8 @@ As an IT admin, when a user failed to sign-in, you want to resolve the issue as
24
30
This article gives you an overview of a feature that significantly improves the time it takes to resolve user sign-in problems by making the related problems easy to find.
25
31
26
32
33
+
34
+
27
35
## What it is
28
36
29
37
Azure AD sign-in events are critical to understanding what went right or wrong with user sign-ins and the authentication configuration in a tenant. However, Azure AD processes over 8 billion authentications a day, which can result in so many sign-in events that admins may find it difficult to find the ones which matter. In other words, the sheer number of sign-in events can make the signal of users who need assistance get lost in the volume of a large number of events.
@@ -35,7 +43,9 @@ Flagged sign-ins gives the user the ability to enable flagging when an error is
35
43
In summary, you can use flagged sign-ins to:
36
44
37
45
-**Empower** users to indicate the sign-in errors they need their tenant admins help on.
46
+
38
47
-**Simplify** the process of locating the sign-in errors a user needs to be resolved.
48
+
39
49
-**Enable** help desk personal find the problems users want help with proactively- without the end user having to do anything other than flag the event.
40
50
41
51
## How it works
@@ -66,20 +76,27 @@ After enabling flagging, the same browser application and client must be used or
66
76
67
77
### Admin or Developer: Find flagged events using MS Graph
68
78
69
-
You can find flagged sign-ins with a filtered query using the sign-ins reporting API. A sample query is:
For more information on using the sign-ins Graph API, see [signIn resource type](/graph/api/resources/signin?view=graph-rest-1.0&preserve-view=true).
84
+
Flagged Sign-ins query for specific user by UPN (e.g.: [email protected]):
85
+
`https://graph.microsoft.com/beta/auditLogs/signIns?&$filter=flaggedforReview eq true and userPrincipalname eq '[email protected]'`
86
+
87
+
Flagged Sign-ins query for specific user and date greater than:
88
+
`https://graph.microsoft.com/beta/auditLogs/signIns?&$filter=flaggedforReview eq true and createdDateTime ge 2021-10-01 and userPrincipalname eq '[email protected]'`
89
+
90
+
For more information on using the sign-ins Graph API, see [signIn resource type](https://docs.microsoft.com/graph/api/resources/signin?view=graph-rest-1.0&preserve-view=true).
74
91
75
92
76
93
77
94
78
-
## Who can create it?
95
+
## Who can create flagged sign-ins?
79
96
80
97
Any user signing into Azure AD via web page can use flag sign-ins for review. Member and guest users alike can flag sign-in errors for review.
81
98
82
-
## Who can review it?
99
+
## Who can review flagged sign-ins?
83
100
84
101
Reviewing flagged sign-in events requires permissions to read the Sign-in Report events in the Azure AD portal. For more information, see [who can access it?](concept-sign-ins.md#who-can-access-it)
0 commit comments