Skip to content

Commit 1be0360

Browse files
authored
Merge pull request #213515 from shlipsey3/reports-monitoring-owner-updates-0908
Reports monitoring owner updates 0908
2 parents 514fad4 + 797c8db commit 1be0360

File tree

12 files changed

+115
-344
lines changed

12 files changed

+115
-344
lines changed

articles/active-directory/reports-monitoring/concept-activity-logs-azure-monitor.md

Lines changed: 5 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,17 @@
22
title: Azure Active Directory activity logs in Azure Monitor | Microsoft Docs
33
description: Introduction to Azure Active Directory activity logs in Azure Monitor
44
services: active-directory
5-
documentationcenter: ''
6-
author: MarkusVi
5+
author: shlipsey3
76
manager: amycolannino
8-
editor: ''
9-
10-
ms.assetid: 4b18127b-d1d0-4bdc-8f9c-6a4c991c5f75
117
ms.service: active-directory
128
ms.topic: conceptual
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: 10/03/2022
12+
ms.author: sarahlipsey
1813
ms.reviewer: besiler
19-
2014
ms.collection: M365-identity-device-management
2115
---
22-
2316
# Azure AD activity logs in Azure Monitor
2417

2518
You can route Azure Active Directory (Azure AD) activity logs to several endpoints for long term retention and data insights. This feature allows you to:
@@ -31,25 +24,21 @@ You can route Azure Active Directory (Azure AD) activity logs to several endpoin
3124

3225
> [!VIDEO https://www.youtube.com/embed/syT-9KNfug8]
3326
34-
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-log-analytics-rebrand.md)]
35-
3627
## Supported reports
3728

3829
You can route Azure AD audit logs and sign-in logs to your Azure Storage account, event hub, Azure Monitor logs, or custom solution by using this feature.
3930

4031
* **Audit logs**: The [audit logs activity report](concept-audit-logs.md) gives you access to information about changes applied to your tenant, such as users and group management, or updates applied to your tenant’s resources.
4132
* **Sign-in logs**: With the [sign-in activity report](concept-sign-ins.md), you can determine who performed the tasks that are reported in the audit logs.
4233

43-
44-
4534
## Prerequisites
4635

4736
To use this feature, you need:
4837

4938
* An Azure subscription. If you don't have an Azure subscription, you can [sign up for a free trial](https://azure.microsoft.com/free/).
5039
* Azure AD Free, Basic, Premium 1, or Premium 2 [license](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing), to access the Azure AD audit logs in the Azure portal.
5140
* An Azure AD tenant.
52-
* A user who's a **global administrator** or **security administrator** for the Azure AD tenant.
41+
* A user who's a **Global Administrator** or **Security Administrator** for the Azure AD tenant.
5342
* Azure AD Premium 1, or Premium 2 [license](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing), to access the Azure AD sign-in logs in the Azure portal.
5443

5544
Depending on where you want to route the audit log data, you need either of the following:
@@ -78,14 +67,6 @@ The following table contains a cost estimate of, depending on the size of the te
7867
| Sign-ins | 100,000 | 15 million | 1.7 TB | $35.41 | $424.92 |
7968

8069

81-
82-
83-
84-
85-
86-
87-
88-
8970
### Event Hub messages for activity logs
9071

9172
Events are batched into approximately five-minute intervals and sent as a single message that contains all the events within that timeframe. A message in the Event Hub has a maximum size of 256 KB, and if the total size of all the messages within the timeframe exceeds that volume, multiple messages are sent.
@@ -103,23 +84,12 @@ The following table contains estimated costs per month for a basic Event Hub in
10384

10485
### Azure Monitor logs cost considerations
10586

106-
107-
10887
| Log category | Number of users | Events per day | Events per month (30 days) | Cost per month in USD (est.) |
10988
|:-|--|--|--|-:|
11089
| Audit and Sign-ins | 100,000 | 16,500,000 | 495,000,000 | $1093.00 |
11190
| Audit | 100,000 | 1,500,000 | 45,000,000 | $246.66 |
11291
| Sign-ins | 100,000 | 15,000,000 | 450,000,000 | $847.28 |
11392

114-
115-
116-
117-
118-
119-
120-
121-
122-
12393
To review costs related to managing the Azure Monitor logs, see [Azure Monitor Logs pricing details](../../azure-monitor/logs/cost-logs.md).
12494

12595
## Frequently asked questions
@@ -174,7 +144,7 @@ This section answers frequently asked questions and discusses known issues with
174144

175145
**Q: What SIEM tools are currently supported?**
176146

177-
**A**: **A**: Currently, Azure Monitor is supported by [Splunk](./howto-integrate-activity-logs-with-splunk.md), IBM QRadar, [Sumo Logic](https://help.sumologic.com/Send-Data/Applications-and-Other-Data-Sources/Azure_Active_Directory), [ArcSight](./howto-integrate-activity-logs-with-arcsight.md), LogRhythm, and Logz.io. For more information about how the connectors work, see [Stream Azure monitoring data to an event hub for consumption by an external tool](../../azure-monitor/essentials/stream-monitoring-data-event-hubs.md).
147+
**A**: Currently, Azure Monitor is supported by [Splunk](./howto-integrate-activity-logs-with-splunk.md), IBM QRadar, [Sumo Logic](https://help.sumologic.com/Send-Data/Applications-and-Other-Data-Sources/Azure_Active_Directory), [ArcSight](./howto-integrate-activity-logs-with-arcsight.md), LogRhythm, and Logz.io. For more information about how the connectors work, see [Stream Azure monitoring data to an event hub for consumption by an external tool](../../azure-monitor/essentials/stream-monitoring-data-event-hubs.md).
178148

179149
---
180150

articles/active-directory/reports-monitoring/concept-all-sign-ins.md

Lines changed: 13 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -2,35 +2,28 @@
22
title: Sign-in logs in Azure Active Directory - preview | Microsoft Docs
33
description: Overview of the sign-in logs in Azure Active Directory including new features in preview.
44
services: active-directory
5-
documentationcenter: ''
6-
author: MarkusVi
5+
author: shlipsey3
76
manager: amycolannino
8-
editor: ''
9-
10-
ms.assetid: 4b18127b-d1d0-4bdc-8f9c-6a4c991c5f75
117
ms.service: active-directory
128
ms.topic: conceptual
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: 10/03/2022
12+
ms.author: sarahlipsey
1813
ms.reviewer: besiler
19-
2014
ms.collection: M365-identity-device-management
2115
---
2216
# Sign-in logs in Azure Active Directory - preview
2317

2418
As an IT administrator, you want to know how your IT environment is doing. The information about your system’s health enables you to assess whether and how you need to respond to potential issues.
2519

26-
To support you with this goal, the Azure Active Directory portal gives you access to three activity logs:
20+
To support you with this goal, the Azure Active Directory (Azure AD) portal gives you access to three activity logs:
2721

2822
- **[Sign-in](concept-sign-ins.md)** – Information about sign-ins and how your resources are used by your users.
29-
- **[Audit](concept-audit-logs.md)** – Information about changes applied to your tenant such as users and group management or updates applied to your tenant’s resources.
30-
- **[Provisioning](concept-provisioning-logs.md)** – Activities performed by the provisioning service, such as the creation of a group in ServiceNow or a user imported from Workday.
31-
23+
- **[Audit](concept-audit-logs.md)** – Information about changes applied to your tenant, such as users and group management or updates applied to your tenant’s resources.
24+
- **[Provisioning](concept-provisioning-logs.md)** – Activities performed by a provisioning service, such as the creation of a group in ServiceNow or a user imported from Workday.
3225

33-
The classic sign-in log in Azure Active Directory provides you with an overview of interactive user sign-ins. In addition, you now have access to three additional sign-in logs that are now in preview:
26+
The classic sign-in log in Azure AD provides you with an overview of interactive user sign-ins. Three additional sign-in logs are now in preview:
3427

3528
- Non-interactive user sign-ins
3629

@@ -40,8 +33,6 @@ The classic sign-in log in Azure Active Directory provides you with an overview
4033

4134
This article gives you an overview of the sign-in activity report with the preview of non-interactive, application, and managed identities for Azure resources sign-ins. For information about the sign-in report without the preview features, see [Sign-in logs in Azure Active Directory](concept-sign-ins.md).
4235

43-
44-
4536
## What can you do with it?
4637

4738
The sign-in log provides answers to questions like:
@@ -65,16 +56,13 @@ The sign-in log provides answers to questions like:
6556

6657
The sign-in activity report is available in [all editions of Azure AD](reference-reports-data-retention.md#how-long-does-azure-ad-store-the-data). If you have an Azure Active Directory P1 or P2 license, you also can access the sign-in activity report through the Microsoft Graph API. See [Getting started with Azure Active Directory Premium](../fundamentals/active-directory-get-started-premium.md) to upgrade your Azure Active Directory edition. It will take a couple of days for the data to show up in Graph after you upgrade to a premium license with no data activities before the upgrade.
6758

68-
69-
70-
7159
## Where can you find it in the Azure portal?
7260

7361
The Azure portal provides you with several options to access the log. For example, on the Azure Active Directory menu, you can open the log in the **Monitoring** section.
7462

75-
![Open sign-in logs](./media/concept-sign-ins/sign-ins-logs-menu.png)
63+
![Screenshot of the sign-in logs menu option.](./media/concept-sign-ins/sign-ins-logs-menu.png)
7664

77-
Additionally, you can get directly get to the sign-in log using this link: [https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/SignIns](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/SignIns)
65+
Additionally, you can access the sign-in log using this link: [https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/SignIns](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/SignIns)
7866

7967
On the sign-ins page, you can switch between:
8068

@@ -87,9 +75,7 @@ On the sign-ins page, you can switch between:
8775
- **Managed identities for Azure resources sign-ins** - Sign-ins by Azure resources that have secrets managed by Azure. For more information, see [What are managed identities for Azure resources?](../managed-identities-azure-resources/overview.md)
8876

8977

90-
![Sign-in log types](./media/concept-all-sign-ins/sign-ins-report-types.png)
91-
92-
78+
![Screenshot of the sign-in log types.](./media/concept-all-sign-ins/sign-ins-report-types.png)
9379

9480
Each tab on the sign-ins page shows the default columns below. Some tabs have additional columns:
9581

@@ -105,18 +91,13 @@ Each tab on the sign-ins page shows the default columns below. Some tabs have ad
10591

10692
- IP address of the device used for the sign-in
10793

108-
109-
11094
### Interactive user sign-ins
11195

112-
11396
Interactive user sign-ins are sign-ins where a user provides an authentication factor to Azure AD or interacts directly with Azure AD or a helper app, such as the Microsoft Authenticator app. The factors users provide include passwords, responses to MFA challenges, biometric factors, or QR codes that a user provides to Azure AD or to a helper app.
11497

11598
> [!NOTE]
11699
> This log also includes federated sign-ins from identity providers that are federated to Azure AD.
117100
118-
119-
120101
> [!NOTE]
121102
> The interactive user sign-in log used to contain some non-interactive sign-ins from Microsoft Exchange clients. Although those sign-ins were non-interactive, they were included in the interactive user sign-in log for additional visibility. Once the non-interactive user sign-in log entered public preview in November 2020, those non-interactive sign-in logs were moved to the non-interactive user sign in log for increased accuracy.
122103
@@ -139,24 +120,13 @@ In addition to the default fields, the interactive sign-in log also shows:
139120

140121
- Whether conditional access has been applied
141122

142-
143-
144123
You can customize the list view by clicking **Columns** in the toolbar.
145124

146-
![Interactive user sign-in columns](./media/concept-all-sign-ins/columns-interactive.png "Interactive user sign-in columns")
147-
148-
149-
150-
125+
![Screenshot of the interactive user sign-in columns that can be customized.](./media/concept-all-sign-ins/columns-interactive.png "Interactive user sign-in columns")
151126

152127
Customizing the view enables you to display additional fields or remove fields that are already displayed.
153128

154-
![All interactive columns](./media/concept-all-sign-ins/all-interactive-columns.png)
155-
156-
157-
158-
159-
129+
![Screenshot of all interactive columns.](./media/concept-all-sign-ins/all-interactive-columns.png)
160130

161131
### Non-interactive user sign-ins
162132

@@ -174,26 +144,18 @@ Non-interactive user sign-ins are sign-ins that were performed by a client app o
174144

175145
- A user signs in to a second Microsoft Office app while they have a session on a mobile device using FOCI (Family of Client IDs).
176146

177-
178-
179-
180147
In addition to the default fields, the non-interactive sign-in log also shows:
181148

182149
- Resource ID
183150

184151
- Number of grouped sign-ins
185152

186-
187-
188-
189153
You can't customize the fields shown in this report.
190154

191-
192-
![Disabled columns](./media/concept-all-sign-ins/disabled-columns.png "Disabled columns")
155+
![Screenshot of the disabled columns option.](./media/concept-all-sign-ins/disabled-columns.png "Disabled columns")
193156

194157
To make it easier to digest the data, non-interactive sign-in events are grouped. Clients often create many non-interactive sign-ins on behalf of the same user in a short time period, which share all the same characteristics except for the time the sign-in was attempted. For example, a client may get an access token once per hour on behalf of a user. If the user or client do not change state, the IP address, resource, and all other information is the same for each access token request. When Azure AD logs multiple sign-ins that are identical other than time and date, those sign-ins will be from the same entity are aggregated into a single row. A row with multiple identical sign-ins (except for date and time issued) will have a value greater than 1 in the # sign-ins column. You can expand the row to see all the different sign-ins and their different time stamps. Sign-ins are aggregated in the non-interactive users when the following data matches:
195158

196-
197159
- Application
198160

199161
- User
@@ -204,14 +166,8 @@ To make it easier to digest the data, non-interactive sign-in events are grouped
204166

205167
- Resource ID
206168

207-
208-
209-
210-
211169
The IP address of non-interactive sign-ins doesn't match the actual source IP of where the refresh token request is coming from. Instead, it shows the original IP used for the original token issuance.
212170

213-
214-
215171
## Service principal sign-ins
216172

217173
Unlike interactive and non-interactive user sign-ins, service principal sign-ins do not involve a user. Instead, they are sign-ins by any non-user account, such as apps or service principals (except managed identity sign-in, which are in included only in the managed identity sign-in log). In these sign-ins, the app or service provides its own credential, such as a certificate or app secret to authenticate or access resources.
@@ -257,10 +213,6 @@ To make it easier to digest the data in the service principal sign-in logs, serv
257213

258214
- Resource name or ID
259215

260-
261-
262-
263-
264216
## Managed identity for Azure resources sign-ins
265217

266218
Managed identity for Azure resources sign-ins are sign-ins that were performed by resources that have their secrets managed by Azure to simplify credential management.

0 commit comments

Comments
 (0)