Skip to content

Commit a921c12

Browse files
authored
Merge pull request #5219 from MicrosoftDocs/poliveria-entraid-10072025
Add EntraIdSignInEvents and EntraIdSpnSignInEvents tables
2 parents 935c00c + 7c26338 commit a921c12

6 files changed

+214
-15
lines changed

defender-xdr/advanced-hunting-aadsignineventsbeta-table.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ ms.service: defender-xdr
66
ms.subservice: adv-hunting
77
f1.keywords:
88
- NOCSH
9-
ms.author: maccruz
10-
author: schmurky
9+
ms.author: pauloliveria
10+
author: poliveria
1111
ms.localizationpriority: medium
12-
manager: dansimp
12+
manager: orspodek
1313
audience: ITPro
1414
ms.collection:
1515
- m365-security
@@ -21,19 +21,26 @@ appliesto:
2121
- Microsoft Defender XDR
2222
- Microsoft Sentinel in the Microsoft Defender portal
2323
ms.topic: reference
24-
ms.date: 03/28/2025
24+
ms.date: 11/04/2025
2525
---
2626

2727
# AADSignInEventsBeta
2828

2929

3030

3131
> [!IMPORTANT]
32-
> The `AADSignInEventsBeta` table is currently in beta and is being offered on a short-term basis to allow you to hunt through Microsoft Entra sign-in events. Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table. All sign-in schema information will eventually move to the `IdentityLogonEvents` table.
32+
> On December 9, 2025, the `AADSignInEventsBeta` table will be replaced by [`EntraIdSignInEvents`](advanced-hunting-entraidsigninevents-table.md). This change will be made to remove the former's preview status and to align it with the existing product branding.
33+
>
34+
>The `EntraIdSignInEvents` table is already available. To ensure a smooth transition, make sure that you update your queries that use the `AADSignInEventsBeta` table to use `EntraIdSignInEvents` before the previously mentioned date.
35+
36+
>[!IMPORTANT]
37+
> The `AADSignInEventsBeta` table is currently in beta and is being offered on a short-term basis to allow you to hunt through Microsoft Entra sign-in events. Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table.
3338
3439
The `AADSignInEventsBeta` table in the advanced hunting schema contains information about Microsoft Entra interactive and non-interactive sign-ins. Learn more about sign-ins in [Microsoft Entra sign-in activity reports - preview](/azure/active-directory/reports-monitoring/concept-all-sign-ins).
3540

36-
Use this reference to construct queries that return information from the table. For information on other tables in the advanced hunting schema, see the [advanced hunting reference](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-reference).
41+
Use this reference to construct queries that return information from the table.
42+
43+
For information on other tables in the advanced hunting schema, see the [advanced hunting reference](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-reference).
3744

3845
<br>
3946

defender-xdr/advanced-hunting-aadspnsignineventsbeta-table.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ ms.service: defender-xdr
66
ms.subservice: adv-hunting
77
f1.keywords:
88
- NOCSH
9-
ms.author: maccruz
10-
author: schmurky
9+
ms.author: pauloliveria
10+
author: poliveria
1111
ms.localizationpriority: medium
12-
manager: dansimp
12+
manager: orspodek
1313
audience: ITPro
1414
ms.collection:
1515
- m365-security
@@ -21,14 +21,18 @@ appliesto:
2121
- Microsoft Defender XDR
2222
- Microsoft Sentinel in the Microsoft Defender portal
2323
ms.topic: reference
24-
ms.date: 03/28/2025
24+
ms.date: 11/04/2025
2525
---
2626

2727
# AADSpnSignInEventsBeta
2828

29-
3029
> [!IMPORTANT]
31-
> The `AADSpnSignInEventsBeta` table is currently in beta and is being offered on a short-term basis to allow you to hunt through Microsoft Entra sign-in events. Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table. Microsoft will eventually move all sign-in schema information to the `IdentityLogonEvents` table.
30+
> On December 9, 2025, the `AADSpnSignInEventsBeta` table will be replaced by [`EntraIdSpnSignInEvents`](advanced-hunting-entraidspnsigninevents-table.md). This change will be made to remove the former's preview status and to align it with the existing product branding.
31+
>
32+
>The `EntraIdSpnSignInEvents` table is already available. To ensure a smooth transition, make sure that you update your queries that use the `AADSpnSignInEventsBeta` table to use `EntraIdSpnSignInEvents` before the previously mentioned date.
33+
34+
>[!IMPORTANT]
35+
>The `AADSpnSignInEventsBeta` table is currently in beta and is being offered on a short-term basis to allow you to hunt through Microsoft Entra sign-in events. Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table.
3236
3337
The `AADSpnSignInEventsBeta` table in the advanced hunting schema contains information about Microsoft Entra service principal and managed identity sign-ins. You can learn more about the different kinds of sign-ins in [Microsoft Entra sign-in activity reports - preview](/azure/active-directory/reports-monitoring/concept-all-sign-ins).
3438

@@ -54,7 +58,7 @@ For information on other tables in the advanced hunting schema, see [the advance
5458
|`ResourceId`|`string`|Unique identifier of the resource accessed|
5559
|`ResourceTenantId`|`string`|Unique identifier of the tenant of the resource accessed|
5660
|`IPAddress`|`string`|IP address assigned to the endpoint and used during related network communications|
57-
|`Country`|`string`|Two-letter code indicating the country where the client IP address is geolocated|
61+
|`Country`|`string`|Two-letter code indicating the country/region where the client IP address is geolocated|
5862
|`State`|`string`|State where the sign-in occurred, if available|
5963
|`City`|`string`|City where the account user is located|
6064
|`Latitude`|`string`|The north to south coordinates of the sign-in location|
Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
---
2+
title: EntraIdSignInEvents table in the advanced hunting schema (preview)
3+
description: Learn about the Microsoft Entra sign-in events table of the advanced hunting schema.
4+
search.appverid: met150
5+
ms.service: defender-xdr
6+
ms.subservice: adv-hunting
7+
f1.keywords:
8+
- NOCSH
9+
ms.author: pauloliveria
10+
author: poliveria
11+
ms.localizationpriority: medium
12+
manager: orspodek
13+
audience: ITPro
14+
ms.collection:
15+
- m365-security
16+
- tier3
17+
ms.custom:
18+
- cx-ti
19+
- cx-ah
20+
appliesto:
21+
- Microsoft Defender XDR
22+
- Microsoft Sentinel in the Microsoft Defender portal
23+
ms.topic: reference
24+
ms.date: 11/04/2025
25+
---
26+
27+
# EntraIdSignInEvents (Preview)
28+
29+
30+
31+
> [!IMPORTANT]
32+
> On December 9, 2025, the `EntraIdSignInEvents` table will replace [`AADSignInEventsBeta`](advanced-hunting-aadsignineventsbeta-table.md). This change will be made to remove the latter's preview status and to align it with the existing product branding. Both tables will coexist until `AADSignInEventsBeta` is deprecated after the said date.
33+
>
34+
>To ensure a smooth transition, make sure that you update your queries that use the `AADSignInEventsBeta` table to use `EntraIdSignInEvents` before the previously mentioned date. Your custom detections will be updated automatically and won't require any changes.
35+
36+
> [!IMPORTANT]
37+
> Some information relates to prereleased product that may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
38+
>
39+
> Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table.
40+
41+
The `EntraIdSignInEvents` table in the advanced hunting schema contains information about Microsoft Entra interactive and non-interactive sign-ins. Learn more about sign-ins in [Microsoft Entra sign-in activity reports - preview](/azure/active-directory/reports-monitoring/concept-all-sign-ins).
42+
43+
Use this reference to construct queries that return information from the table.
44+
45+
For information on other tables in the advanced hunting schema, see the [advanced hunting reference](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-reference).
46+
47+
48+
49+
50+
|Column name|Data type|Description|
51+
|---|---|---|
52+
|`Timestamp`|`datetime`|Date and time when the record was generated|
53+
|`Application`|`string`|Application that performed the recorded action|
54+
|`ApplicationId`|`string`|Unique identifier for the application|
55+
|`LogonType`|`string`|Type of logon session, specifically interactive, remote interactive (RDP), network, batch, and service|
56+
|`ErrorCode`|`int`|Contains the error code if a sign-in error occurs. To find a description of a specific error code, visit <https://aka.ms/AADsigninsErrorCodes>.|
57+
|`CorrelationId`|`string`|Identifier of the sign-in event|
58+
|`SessionId`|`string`|Unique number assigned to a user by a website's server for the duration of the visit or session|
59+
|`AccountDisplayName`|`string`|Name displayed in the address book entry for the account user. This is usually a combination of the given name, middle initial, and surname of the user.|
60+
|`AccountObjectId`|`string`|Unique identifier for the account in Microsoft Entra ID|
61+
|`AccountUpn`|`string`|User principal name (UPN) of the account|
62+
|`IsExternalUser`|`int`|Indicates if the user that signed in is external. Possible values: -1 (not set), 0 (not external), 1 (external).|
63+
|`IsGuestUser`|`boolean`|Indicates whether the user that signed in is a guest in the tenant|
64+
|`AlternateSignInName`|`string`|On-premises user principal name (UPN) of the user signing in to Microsoft Entra ID|
65+
|`LastPasswordChangeTimestamp`|`datetime`|Date and time when the user that signed in last changed their password|
66+
|`ResourceDisplayName`|`string`|Display name of the resource accessed. The display name can contain any character.|
67+
|`ResourceId`|`string`|Unique identifier of the resource accessed|
68+
|`ResourceTenantId`|`string`|Unique identifier of the tenant of the resource accessed|
69+
|`DeviceName`|`string`|Fully qualified domain name (FQDN) of the device|
70+
|`EntraIdDeviceId`|`string`|Unique identifier for the device in Microsoft Entra ID|
71+
|`OSPlatform`|`string`|Platform of the operating system running on the device. Indicates specific operating systems, including variations within the same family, such as Windows 11, Windows 10, and Windows 7.|
72+
|`DeviceTrustType`|`string`|Indicates the trust type of the device that signed in. For managed device scenarios only. Possible values are Workplace, AzureAd, and ServerAd.|
73+
|`IsManaged`|`int`|Indicates whether the device that initiated the sign-in is a managed device (1) or not a managed device (0)|
74+
|`IsCompliant`|`int`|Indicates whether the device that initiated the sign-in is compliant (1) or non-compliant (0)|
75+
|`AuthenticationProcessingDetails`|`string`|Details about the authentication processor|
76+
|`AuthenticationRequirement`|`string`|Type of authentication required for the sign-in. Possible values: multiFactorAuthentication (MFA was required) and singleFactorAuthentication (no MFA was required).|
77+
|`TokenIssuerType`|`int`|Indicates if the token issuer is Microsoft Entra ID (0) or Active Directory Federation Services (1)|
78+
|`RiskLevelAggregated`|`int`|Aggregated risk level during sign-in. Possible values: 0 (aggregated risk level not set), 1 (none), 10 (low), 50 (medium), or 100 (high).|
79+
|`RiskDetails`|`int`|Details about the risky state of the user that signed in|
80+
|`RiskState`|`int`|Indicates risky user state. Possible values: 0 (none), 1 (confirmed safe), 2 (remediated), 3 (dismissed), 4 (at risk), or 5 (confirmed compromised).|
81+
|`UserAgent`|`string`|User agent information from the web browser or other client application|
82+
|`ClientAppUsed`|`string`|Indicates the client app used|
83+
|`Browser`|`string`|Details about the version of the browser used to sign in|
84+
|`ConditionalAccessPolicies`|`string`|Details of the conditional access policies applied to the sign-in event|
85+
|`ConditionalAccessStatus`|`int`|Status of the conditional access policies applied to the sign-in. Possible values are 0 (policies applied), 1 (attempt to apply policies failed), or 2 (policies not applied).|
86+
|`IPAddress`|`string`|IP address assigned to the device during communication|
87+
|`Country`|`string`|Two-letter code indicating the country/region where the client IP address is geolocated|
88+
|`State`|`string`|State where the sign-in occurred, if available|
89+
|`City`|`string`|City where the account user is located|
90+
|`Latitude`|`string`|The north to south coordinates of the sign-in location|
91+
|`Longitude`|`string`|The east to west coordinates of the sign-in location|
92+
|`NetworkLocationDetails`|`string`|Network location details of the authentication processor of the sign-in event|
93+
|`RequestId`|`string`|Unique identifier of the request|
94+
|`ReportId`|`string`|Unique identifier for the event|
95+
|`EndpointCall`|`string`|Information about the Microsoft Entra ID endpoint that the request was sent to and the type of request sent during sign in.|
96+
97+
## Related articles
98+
99+
- [EntraIdSpnSignInEvents](./advanced-hunting-aadspnsignineventsbeta-table.md)
100+
- [Advanced hunting overview](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-overview)
101+
- [Learn the query language](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-query-language)
102+
- [Understand the schema](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-schema-reference)
103+
104+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]
Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: EntraIdSpnSignInEvents table in the advanced hunting schema (preview)
3+
description: Learn about information associated with Microsoft Entra service principal and managed identity sign-in events table.
4+
search.appverid: met150
5+
ms.service: defender-xdr
6+
ms.subservice: adv-hunting
7+
f1.keywords:
8+
- NOCSH
9+
ms.author: pauloliveria
10+
author: poliveria
11+
ms.localizationpriority: medium
12+
manager: orspodek
13+
audience: ITPro
14+
ms.collection:
15+
- m365-security
16+
- tier3
17+
ms.custom:
18+
- cx-ti
19+
- cx-ah
20+
appliesto:
21+
- Microsoft Defender XDR
22+
- Microsoft Sentinel in the Microsoft Defender portal
23+
ms.topic: reference
24+
ms.date: 11/04/2025
25+
---
26+
27+
# EntraIdSpnSignInEvents (Preview)
28+
29+
30+
> [!IMPORTANT]
31+
> On December 9, 2025, the `EntraIdSpnSignInEvents` table will replace [`AADSpnSignInEventsBeta`](advanced-hunting-aadspnsignineventsbeta-table.md). This change will be made to remove the latter's preview status and to align it with the existing product branding. Both tables will coexist until `AADSpnSignInEventsBeta` is deprecated after the said date.
32+
>
33+
>To ensure a smooth transition, make sure that you update your queries that use the `AADSpnSignInEventsBeta` table to use `EntraIdSpnSignInEvents` before the previously mentioned date. Your custom detections will be updated automatically and won't require any changes.
34+
35+
> [!IMPORTANT]
36+
> Some information relates to prereleased product that may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
37+
>
38+
> Customers need to have a Microsoft Entra ID P2 license to collect and view activities for this table.
39+
40+
The `EntraIdSpnSignInEvents` table in the advanced hunting schema contains information about Microsoft Entra service principal and managed identity sign-ins. You can learn more about the different kinds of sign-ins in [Microsoft Entra sign-in activity reports - preview](/azure/active-directory/reports-monitoring/concept-all-sign-ins).
41+
42+
Use this reference to construct queries that return information from the table.
43+
44+
For information on other tables in the advanced hunting schema, see [the advanced hunting reference](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-reference).
45+
46+
47+
|Column name|Data type|Description|
48+
|-----------|---------|-----------|
49+
|`Timestamp`|`datetime`|Date and time when the record was generated|
50+
|`Application`|`string`|Application that performed the recorded action|
51+
|`ApplicationId`|`string`|Unique identifier for the application|
52+
|`IsManagedIdentity`|`boolean`|Indicates whether the sign-in was initiated by a managed identity|
53+
|`ErrorCode`|`int`|Contains the error code if a sign-in error occurs. To find a description of a specific error code, visit <https://aka.ms/AADsigninsErrorCodes>.|
54+
|`CorrelationId`|`string`|Unique identifier of the sign-in event|
55+
|`ServicePrincipalName`|`string`|Name of the service principal that initiated the sign-in|
56+
|`ServicePrincipalId`|`string`|Unique identifier of the service principal that initiated the sign-in|
57+
|`ResourceDisplayName`|`string`|Display name of the resource accessed. The display name can contain any character.|
58+
|`ResourceId`|`string`|Unique identifier of the resource accessed|
59+
|`ResourceTenantId`|`string`|Unique identifier of the tenant of the resource accessed|
60+
|`IPAddress`|`string`|IP address assigned to the endpoint and used during related network communications|
61+
|`Country`|`string`|Two-letter code indicating the country/region where the client IP address is geolocated|
62+
|`State`|`string`|State where the sign-in occurred, if available|
63+
|`City`|`string`|City where the account user is located|
64+
|`Latitude`|`string`|The north to south coordinates of the sign-in location|
65+
|`Longitude`|`string`|The east to west coordinates of the sign-in location|
66+
|`RequestId`|`string`|Unique identifier of the request|
67+
|`ReportId`|`string`|Unique identifier for the event|
68+
69+
## Related articles
70+
71+
- [EntraIdSignInEvents](./advanced-hunting-aadsignineventsbeta-table.md)
72+
- [Advanced hunting overview](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-overview)
73+
- [Learn the query language](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-query-language)
74+
- [Understand the schema](/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-schema-reference)
75+
76+
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

defender-xdr/advanced-hunting-schema-changes.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ appliesto:
2121
- Microsoft Defender XDR
2222
- Microsoft Sentinel in the Microsoft Defender portal
2323
ms.topic: reference
24-
ms.date: 05/28/2025
24+
ms.date: 11/04/2025
2525
---
2626

2727
# Advanced hunting schema - Naming changes
@@ -37,6 +37,12 @@ Naming changes are automatically applied to queries that are saved in Microsoft
3737
- Queries that are run using the API
3838
- Queries that are saved elsewhere outside Microsoft Defender XDR
3939

40+
## November 2025
41+
42+
The [`AADSignInEventsBeta`](advanced-hunting-aadspnsignineventsbeta-table.md) and [`AADSignInEventsBeta`](advanced-hunting-aadspnsignineventsbeta-table.md) tables are being replaced by [`EntraIdSignInEvents`](advanced-hunting-entraidsigninevents-table.md) and [`EntraIdSpnSignInEvents`](advanced-hunting-entraidspnsigninevents-table.md), respectively. These changes are being made to remove the former tables' preview status and to align them with the existing product branding.
43+
44+
The `EntraIdSignInEvents` and `EntraIdSpnSignInEvents` tables are now available. The legacy `AADSignInEventsBeta`and `AADSignInEventsBeta` tables will remain in the schema for 30 days to allow time for updating your queries. Your custom detections will be updated automatically and won't require any changes. On December 9, 2025, `AADSignInEventsBeta`and `AADSignInEventsBeta` will be removed from the schema.
45+
4046
## September 2025
4147

4248
In the [AADSignInEventsBeta](./advanced-hunting-aadspnsignineventsbeta-table.md) table, the `AadDeviceId` column is being replaced with a new column, called `EntraIdDeviceId`, to align with current product branding. The legacy `AadDeviceId` column will remain in the schema for 30 days to allow time for updating in your queries. After this period of 30 days, `AadDeviceId` will be removed from the schema.

0 commit comments

Comments
 (0)