Skip to content

Commit 1a46ee2

Browse files
authored
Merge pull request #5412 from MicrosoftDocs/poliveria-ah-cd
Update advanced hunting doc for Defender XDR
2 parents b5061df + acbc1a1 commit 1a46ee2

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

defender-xdr/advanced-hunting-microsoft-defender.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ms.topic: concept-article
2323
appliesto:
2424
- Microsoft Defender XDR
2525
- Microsoft Sentinel in the Microsoft Defender portal
26-
ms.date: 09/08/2025
26+
ms.date: 10/30/2025
2727
---
2828

2929
# Advanced hunting with Microsoft Sentinel data in Microsoft Defender portal
@@ -88,10 +88,8 @@ In the unified portal, in addition to viewing the schema column names and descri
8888
- The Microsoft Sentinel `SecurityAlert` table is replaced by `AlertInfo` and `AlertEvidence` tables, which both contain all the data on alerts. While SecurityAlert isn't available in the schema tab, you can still use it in queries using the advanced hunting editor. This provision is made so as not to break existing queries from Microsoft Sentinel that use this table.
8989
- Guided hunting mode and take actions capabilities are supported for Defender XDR data only.
9090
- Custom detections have the following limitations:
91-
- Custom detections aren't available for KQL queries that don't include Defender XDR data.
9291
- Near real-time detection frequency isn't available for detections that include Microsoft Sentinel data.
9392
- Custom functions that were created and saved in Microsoft Sentinel aren't supported.
94-
- Defining entities from Sentinel data isn't yet supported in custom detections.
9593
- Bookmarks aren't supported in the advanced hunting experience. They're supported in the **Microsoft Sentinel > Threat management > Hunting** feature. Alternatively, you can use the [Link to incident](advanced-hunting-defender-results.md#link-query-results-to-an-incident) feature to link query results to new or existing incidents.
9694
- If you're streaming Defender XDR tables to Log Analytics, there might be a difference between the`Timestamp` and `TimeGenerated` columns. In case the data arrives to Log Analytics after 48 hours, it's being overridden upon ingestion to `now()`. Therefore, to get the actual time the event happened, we recommend relying on the `Timestamp` column.
9795
- When prompting [Security Copilot](advanced-hunting-security-copilot.md) for advanced hunting queries, you might find that not all Microsoft Sentinel tables are currently supported. However, support for these tables can be expected in the future.

0 commit comments

Comments
 (0)