Skip to content

Commit a302e11

Browse files
authored
Merge pull request #5878 from MicrosoftDocs/poliveria-schema-edit-12102025
Update schema change dates in documentation
2 parents 11a84a6 + 2ad1404 commit a302e11

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
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: 11/27/2025
24+
ms.date: 12/10/2025
2525
---
2626

2727
# Advanced hunting schema - Naming changes
@@ -38,7 +38,7 @@ Naming changes are automatically applied to queries that are saved in Microsoft
3838
- Queries that are saved elsewhere outside Microsoft Defender XDR
3939

4040
## November 2025
41-
- The Boolean field values in advanced hunting results will change from numeric (`1` and `0`) to textual (`True` and `False`) on January 25, 2026. While your queries and custom detection rules won't be affected by this change, you might want to update your automated processes (for example, scripts, playbooks, or integrations) parsing these values.
41+
- The Boolean field values in advanced hunting results will change from numeric (`1` and `0`) to textual (`True` and `False`) on February 25, 2026. While your queries and custom detection rules won't be affected by this change, you might want to update your automated processes (for example, scripts, playbooks, or integrations) parsing these values.
4242

4343

4444
- The [`AADSignInEventsBeta`](advanced-hunting-aadsignineventsbeta-table.md) and [`AADSpnSignInEventsBeta`](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.

0 commit comments

Comments
 (0)