Skip to content

Commit fcc2112

Browse files
authored
Merge pull request #216818 from shlipsey3/reports-quickstarts-updates-110122
quickstarts-overview-metadata
2 parents e24185c + 930c93b commit fcc2112

10 files changed

+83
-122
lines changed

articles/active-directory/reports-monitoring/overview-flagged-sign-ins.md

Lines changed: 18 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,14 @@
33
title: What are flagged sign-ins in Azure Active Directory?
44
description: Provides a general overview of flagged sign-ins in Azure Active Directory.
55
services: active-directory
6-
documentationcenter: ''
7-
author: MarkusVi
6+
author: shlipsey3
87
manager: amycolannino
9-
editor: ''
10-
11-
ms.assetid: e2b3d8ce-708a-46e4-b474-123792f35526
128
ms.service: active-directory
139
ms.topic: overview
14-
ms.tgt_pltfrm: na
1510
ms.workload: identity
1611
ms.subservice: report-monitor
17-
ms.date: 08/26/2022
18-
ms.author: markvi
12+
ms.date: 11/01/2022
13+
ms.author: sarahlipsey
1914
ms.reviewer: tspring
2015

2116
# Customer intent: As an Azure AD administrator, I want a tool that gives me the right level of insights into the sign-in activities in my system so that I can easily diagnose and solve problems when they occur.
@@ -28,16 +23,13 @@ As an IT admin, when a user failed to sign-in, you want to resolve the issue as
2823

2924
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.
3025

31-
32-
33-
34-
## What it is
26+
## What are flagged sign-ins?
3527

3628
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.
3729

38-
Flagged Sign-ins is a feature intended to increase the signal to noise ratio for user sign-ins requiring help. The functionality is intended to empower users to raise awareness about sign-in errors they want help with and, for admins and help desk workers, make finding the right events faster and more efficient. Flagged Sign-in events contain the same information as other sign-in events contain with one addition: they also indicate that a user flagged the event for review by admins.
30+
Flagged Sign-ins is a feature intended to increase the signal to noise ratio for user sign-ins requiring help. The functionality is intended to empower users to raise awareness about sign-in errors they want help with. Admins and help desk workers also benefit from finding the right events more efficiently. Flagged Sign-in events contain the same information as other sign-in events contain with one addition: they also indicate that a user flagged the event for review by admins.
3931

40-
Flagged sign-ins gives the user the ability to enable flagging when an error is seen on a sign-in page and then reproduce that error. The error event will then appear as “Flagged for Review” in the Azure AD Reporting blade for Sign-ins.
32+
Flagged sign-ins gives the user the ability to enable flagging when an error is seen on a sign-in page and then reproduce that error. The error event will then appear as “Flagged for Review” in the Azure AD sign-ins log.
4133

4234
In summary, you can use flagged sign-ins to:
4335

@@ -54,23 +46,22 @@ Flagged sign-ins gives you the ability to enable flagging when signing in using
5446
### User: How to flag an error
5547

5648
1. The user receives an error during sign-in.
57-
2. The user clicks **View details** in the error page.
58-
3. In **Troubleshooting details**, click **Enable Flagging**. The text changes to **Disable Flagging**. Flagging is now enabled.
49+
2. The user selects **View details** in the error page.
50+
3. In **Troubleshooting details**, select **Enable Flagging**. The text changes to **Disable Flagging**. Flagging is now enabled.
5951
4. Close the browser window.
60-
5. Open a new browser window (in the same browser application) and attempt the same sign in that failed.
52+
5. Open a new browser window (in the same browser application) and attempt the same sign-in that failed.
6153
6. Reproduce the sign-in error that was seen before.
6254

63-
After enabling flagging, the same browser application and client must be used or the events will not be flagged.
55+
With flagging enabled, the same browser application and client must be used or the events won't be flagged.
6456

6557

6658
### Admin: Find flagged events in reports
6759

68-
1. In the Azure AD portal, select **Sign-in logs** in the left-hand pane.
69-
2. Click **Add Filters**.
70-
3. In the filter menu titled **Pick a field**, select **Flagged for review**, and click **Apply**.
71-
4. All events that were flagged by users are shown.
72-
5. If needed, apply additional filters to refine the event view.
73-
6. Select the event to review what happened.
60+
1. In the Azure AD portal, go to **Sign-in logs** > **Add Filters**.
61+
1. From the **Pick a field** menu, select **Flagged for review** and **Apply**.
62+
1. All events that were flagged by users are shown.
63+
1. If needed, apply more filters to refine the event view.
64+
1. Select the event to review what happened.
7465

7566

7667
### Admin or Developer: Find flagged events using MS Graph
@@ -80,7 +71,7 @@ You can find flagged sign-ins with a filtered query using the sign-ins reporting
8071
Show all Flagged Sign-ins:
8172
`https://graph.microsoft.com/beta/auditLogs/signIns?&$filter=flaggedforReview eq true`
8273

83-
Flagged Sign-ins query for specific user by UPN (e.g.: [email protected]):
74+
Flagged Sign-ins query for specific user by UPN (for example: [email protected]):
8475
`https://graph.microsoft.com/beta/auditLogs/signIns?&$filter=flaggedforReview eq true and userPrincipalname eq '[email protected]'`
8576

8677
Flagged Sign-ins query for specific user and date greater than:
@@ -100,7 +91,7 @@ Any user signing into Azure AD via web page can use flag sign-ins for review. Me
10091
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)
10192

10293

103-
To flag sign-in failures, you don't need additional permissions.
94+
To flag sign-in failures, you don't need extra permissions.
10495

10596

10697
## What you should know
@@ -116,4 +107,4 @@ While the names are similar, **flagged sign-ins** and **risky sign-ins** are dif
116107
## Next steps
117108

118109
- [Sign-in logs in Azure Active Directory](concept-sign-ins.md)
119-
- [Sign in diagnostics for Azure AD scenarios](concept-sign-in-diagnostics-scenarios.md)
110+
- [Sign-in diagnostics for Azure AD scenarios](concept-sign-in-diagnostics-scenarios.md)

articles/active-directory/reports-monitoring/overview-monitoring.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,14 @@
33
title: What is Azure Active Directory monitoring? | Microsoft Docs
44
description: Provides a general overview of Azure Active Directory monitoring.
55
services: active-directory
6-
documentationcenter: ''
7-
author: MarkusVi
6+
author: shlipsey3
87
manager: amycolannino
9-
editor: ''
10-
11-
ms.assetid: e2b3d8ce-708a-46e4-b474-123792f35526
128
ms.service: active-directory
139
ms.topic: overview
14-
ms.tgt_pltfrm: na
1510
ms.workload: identity
1611
ms.subservice: report-monitor
17-
ms.date: 08/26/2022
18-
ms.author: markvi
12+
ms.date: 11/01/2022
13+
ms.author: sarahlipsey
1914
ms.reviewer: dhanyahk
2015

2116
# Customer intent: As an Azure AD administrator, I want to understand what monitoring solutions are available for Azure AD activity data and how they can help me manage my tenant.
@@ -40,7 +35,7 @@ Currently, you can route the logs to:
4035

4136
## Licensing and prerequisites for Azure AD reporting and monitoring
4237

43-
You'll need an Azure AD premium license to access the Azure AD sign in logs.
38+
You'll need an Azure AD premium license to access the Azure AD sign-in logs.
4439

4540
For detailed feature and licensing information in the [Azure Active Directory pricing guide](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
4641

articles/active-directory/reports-monitoring/overview-reports.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,14 @@
33
title: What are Azure Active Directory reports? | Microsoft Docs
44
description: Provides a general overview of Azure Active Directory reports.
55
services: active-directory
6-
documentationcenter: ''
7-
author: MarkusVi
6+
author: shlipsey3
87
manager: amycolannino
9-
editor: ''
10-
11-
ms.assetid: 6141a333-38db-478a-927e-526f1e7614f4
128
ms.service: active-directory
139
ms.topic: overview
14-
ms.tgt_pltfrm: na
1510
ms.workload: identity
1611
ms.subservice: report-monitor
17-
ms.date: 08/22/2022
18-
ms.author: markvi
12+
ms.date: 11/01/2022
13+
ms.author: sarahlipsey
1914
ms.reviewer: sarbar
2015

2116
# Customer intent: As an Azure AD administrator, I want to understand what Azure AD reports are available and how I can use them to gain insights into my environment.
@@ -55,7 +50,7 @@ The [audit logs report](concept-audit-logs.md) provides you with records of syst
5550

5651
#### What Azure AD license do you need to access the audit logs report?
5752

58-
The audit logs report is available for features for which you have licenses. If you have a license for a specific feature, you also have access to the audit log information for it. A detailed feature comparison as per [different types of licenses](../fundamentals/active-directory-whatis.md#what-are-the-azure-ad-licenses) can be seen on the [Azure Active Directory pricing page](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing). For more details, see [Azure Active Directory features and capabilities](../fundamentals/active-directory-whatis.md#which-features-work-in-azure-ad).
53+
The audit logs report is available for features for which you have licenses. If you have a license for a specific feature, you also have access to the audit log information for it. A detailed feature comparison as per [different types of licenses](../fundamentals/active-directory-whatis.md#what-are-the-azure-ad-licenses) can be seen on the [Azure Active Directory pricing page](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing). For more information, see [Azure Active Directory features and capabilities](../fundamentals/active-directory-whatis.md#which-features-work-in-azure-ad).
5954

6055
### Sign-ins report
6156

@@ -71,7 +66,7 @@ To access the sign-ins activity report, your tenant must have an Azure AD Premiu
7166

7267
## Programmatic access
7368

74-
In addition to the user interface, Azure AD also provides you with [programmatic access](concept-reporting-api.md) to the reports data, through a set of REST-based APIs. You can call these APIs from a variety of programming languages and tools.
69+
In addition to the user interface, Azure AD also provides you with [programmatic access](concept-reporting-api.md) to the reports data, through a set of REST-based APIs. You can call these APIs from various programming languages and tools.
7570

7671
## Next steps
7772

articles/active-directory/reports-monitoring/overview-service-health-notifications.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,14 @@
22
title: What are Service Health notifications in Azure Active Directory? | Microsoft Docs
33
description: Learn how Service Health notifications provide you with a customizable dashboard that tracks the health of your Azure services in the regions where you use them.
44
services: active-directory
5-
documentationcenter: ''
6-
author: MarkusVi
5+
author: shlipsey3
76
manager: amycolannino
8-
editor: ''
9-
10-
ms.assetid: 1c5002e4-079e-4c28-a4e8-a5841942030a6
117
ms.service: active-directory
128
ms.topic: overview
13-
ms.tgt_pltfrm: na
149
ms.workload: identity
1510
ms.subservice: report-monitor
16-
ms.date: 08/26/2022
17-
ms.author: markvi
11+
ms.date: 11/01/2022
12+
ms.author: sarahlipsey
1813
ms.reviewer: davey
1914

2015

@@ -53,7 +48,7 @@ Most of the built-in admin roles will have access to see these notifications. Fo
5348

5449
## What you should know
5550

56-
Service Health events allow the addition of alerts and notifications to be applied to subscription events. Currently, this isn't yet supported with tenant events, but will be coming soon.
51+
Service Health events allow the addition of alerts and notifications to be applied to subscription events. This feature isn't yet supported with tenant events, but will be coming soon.
5752

5853

5954

articles/active-directory/reports-monitoring/overview-sign-in-diagnostics.md

Lines changed: 13 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,14 @@
33
title: What is the sign-in diagnostic for Azure Active Directory?
44
description: Provides a general overview of the sign-in diagnostic in Azure Active Directory.
55
services: active-directory
6-
documentationcenter: ''
7-
author: MarkusVi
6+
author: shlipsey3
87
manager: amycolannino
9-
editor: ''
10-
11-
ms.assetid: e2b3d8ce-708a-46e4-b474-123792f35526
128
ms.service: active-directory
139
ms.topic: overview
14-
ms.tgt_pltfrm: na
1510
ms.workload: identity
1611
ms.subservice: report-monitor
17-
ms.date: 08/26/2022
18-
ms.author: markvi
12+
ms.date: 11/01/2022
13+
ms.author: sarahlipsey
1914
ms.reviewer: tspring
2015

2116
# Customer intent: As an Azure AD administrator, I want a tool that gives me the right level of insights into the sign-in activities in my system so that I can easily diagnose and solve problems when they occur.
@@ -33,7 +28,7 @@ This article gives you an overview of what the diagnostic is and how you can use
3328

3429
In Azure AD, sign-in attempts are controlled by:
3530

36-
- **Who** - The user performing a sign in attempt.
31+
- **Who** - The user performing a sign-in attempt.
3732
- **How** - How a sign-in attempt was performed.
3833

3934
For example, you can configure conditional access policies that enable administrators to configure all aspects of the tenant when they sign in from the corporate network. But the same user might be blocked when they sign into the same account from an untrusted network.
@@ -61,9 +56,9 @@ To start and complete the diagnostic process, you need to:
6156
The diagnostic allows two methods to find events to investigate:
6257

6358
- Sign-in failures users have [flagged for assistance](overview-flagged-sign-ins.md).
64-
- Search for specific events by the user and additional criteria.
59+
- Search for specific events by the user and other criteria.
6560

66-
Flagged sign-ins are automatically presented in a list of up to 100. You can run a diagnostics on an event immediately by clicking it.
61+
Flagged sign-ins are automatically presented in a list of up to 100. You can run diagnostics on an event immediately by clicking it.
6762

6863
You can search a specific event by selecting the search tab even when flagged sign-ins are present.
6964
When searching for specific events, you can filter based on the following options:
@@ -96,7 +91,7 @@ You can change the content displayed in the columns based on your preference. Ex
9691

9792
### Take action
9893

99-
For the selected sign-in event, you get a diagnostic results. Read through the results to identify action that you can take to fix the problem. These results add recommended steps and shed light on relevant information such as the related policies, sign-in details, and supportive documentation. Because it's not always possible to resolve issues without more help, a recommended step might be to open a support ticket.
94+
For the selected sign-in event, you get a diagnostic result. Read through the results to identify action that you can take to fix the problem. These results add recommended steps and shed light on relevant information such as the related policies, sign-in details, and supportive documentation. Because it's not always possible to resolve issues without more help, a recommended step might be to open a support ticket.
10095

10196

10297
![Screenshot showing the diagnostic results.](./media/overview-sign-in-diagnostics/diagnostic-results.png)
@@ -105,7 +100,7 @@ For the selected sign-in event, you get a diagnostic results. Read through the r
105100

106101
## How to access it
107102

108-
To use the diagnostic, you must be signed into the tenant as a global admin or a global reader. If you do not have this level of access, use [Privileged Identity Management, PIM](../privileged-identity-management/pim-resource-roles-activate-your-roles.md), to elevate your access to global admin/reader within the tenant. This will allow you to have temporary access to the diagnostic.
103+
To use the diagnostic, you must be signed into the tenant as a Global Administrator or a Global Reader.
109104

110105
With the correct access level, you can find the diagnostic in various places:
111106

@@ -116,14 +111,9 @@ With the correct access level, you can find the diagnostic in various places:
116111

117112
1. Open **Azure Active Directory AAD or Azure AD Conditional Access**.
118113

119-
2. From the main menu, click **Diagnose & Solve Problems**.
120-
121-
3. Under the **Troubleshooters**, there is a sign-in diagnostic tile.
122-
123-
4. Click **Troubleshoot** button.
124-
125-
114+
1. From the main menu, select **Diagnose & Solve Problems**.
126115

116+
1. From the **Troubleshooters** section, select the **Troubleshoot** button from the sign-in diagnostic tile.
127117

128118

129119
**Option B**: Sign-in Events
@@ -137,11 +127,11 @@ With the correct access level, you can find the diagnostic in various places:
137127

138128
2. On the main menu, in the **Monitoring** section, select **Sign-ins**.
139129

140-
3. From the list of sign-ins, select a sign in with a **Failure** status. You can filter your list by Status to make it easier to find failed sign-ins.
130+
3. From the list of sign-ins, select a sign-in with a **Failure** status. You can filter your list by Status to make it easier to find failed sign-ins.
141131

142-
4. The **Activity Details: Sign-ins** tab will open for the selected sign-in. Click on dotted icon to view more menu icons. Select the **Troubleshooting and support** tab.
132+
4. The **Activity Details: Sign-ins** tab will open for the selected sign-in. Select the dotted icon to view more menu icons. Select the **Troubleshooting and support** tab.
143133

144-
5. Click the link to **Launch the Sign-in Diagnostic**.
134+
5. Select the link to **Launch the Sign-in Diagnostic**.
145135

146136

147137

0 commit comments

Comments
 (0)