Skip to content

Commit 78272fc

Browse files
authored
Update mto-advanced-hunting.md
1 parent 4f0f0bd commit 78272fc

File tree

1 file changed

+12
-18
lines changed

1 file changed

+12
-18
lines changed

unified-secops-platform/mto-advanced-hunting.md

Lines changed: 12 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -3,18 +3,18 @@ title: Advanced hunting in Microsoft Defender multitenant management
33
description: Learn about advanced hunting in Microsoft Defender multitenant management
44
search.appverid: met150
55
ms.service: unified-secops-platform
6-
ms.author: deniseb
7-
author: denisebmsft
6+
ms.author: bagol
7+
author: batamig
88
ms.localizationpriority: medium
9-
manager: dansimp
9+
manager: orspodek
1010
audience: ITPro
1111
ms.collection:
1212
- m365-security
1313
- highpri
1414
- tier1
1515
- usx-security
1616
ms.topic: article
17-
ms.date: 05/02/2025
17+
ms.date: 07/07/2025
1818
appliesto:
1919
- Microsoft Defender XDR
2020
- Microsoft Sentinel in the Microsoft Defender portal
@@ -23,18 +23,15 @@ appliesto:
2323
# Advanced hunting in Microsoft Defender multitenant management
2424

2525
Advanced hunting in Microsoft Defender multitenant management allows you to proactively hunt for intrusion attempts and breach activity in email, data, devices, and accounts across multiple tenants and workspaces at the same time. If you have multiple tenants with Microsoft Sentinel workspaces onboarded to the Microsoft Defender portal, search for security information and event management (SIEM) data together with extended detection and response (XDR) data across multiple tenants and workspaces.
26-
2726

2827
Multiple workspaces per tenant are supported in multitenant Advanced hunting as preview.
2928

30-
3129
## Quotas
3230

3331
In multitenant environments, advanced hunting queries can return a maximum of 50,000 records in total. The result set from each individual tenant is capped at 50,000 divided by the number of tenants queried.
3432

3533
For more information about service limits in advanced hunting, read [Understand advanced hunting quotas](/defender-xdr/advanced-hunting-limits#understand-advanced-hunting-quotas-and-usage-parameters).
3634

37-
3835
## Run cross-tenant queries
3936

4037
You can run any query that you already have access to in the multitenant management **Advanced hunting** page.
@@ -68,11 +65,15 @@ You can run any query that you already have access to in the multitenant managem
6865
| take 10
6966
```
7067

68+
To learn more about advanced hunting in Microsoft Defender XDR, read [Proactively hunt for threats with advanced hunting in Microsoft Defender XDR](/defender-xdr/advanced-hunting-overview).
7169

72-
> [!NOTE]
73-
> If you have tables with the same name but different schemas in multiple workspaces and want to use them in the same query, you should use the workspace operator to uniquely identify the table that you need.
70+
### Use adx(x) operator for Azure Data Explorer queries carefully
7471

75-
To learn more about advanced hunting in Microsoft Defender XDR, read [Proactively hunt for threats with advanced hunting in Microsoft Defender XDR](/defender-xdr/advanced-hunting-overview).
72+
Consider carefully before using the `adx(x)` operator for queries on multiple tenants. Advanced hunting in the multitenant portal sends each query to each of the selected tenants in parallel. The tenants returns the results, which are then aggregated and sent back to the portal. Using the `adx(x)` operator in your queries effectively queries ADX multiple times, once for each tenant, and the returned and aggregated data might include duplicate information.
73+
74+
We recommend using the `adx(x)` operator with multiple tenants only when you want to join results from each tenant with ADX data.
75+
76+
For more information, see [Use Microsoft Sentinel functions, saved queries, and custom rules](/defender-xdr/advanced-hunting-defender-use-custom-rules#use-adx-operator-for-azure-data-explorer-queries).
7677

7778
## Run cross-workspace queries
7879

@@ -100,16 +101,14 @@ For more information, see [Query multiple workspaces](/azure/sentinel/extend-sen
100101
101102
## View schema tables
102103

103-
You can view the [advanced hunting schema tables](/defender-xdr/advanced-hunting-schema-tables) in the left pane inside the advanced hunting page under the **Schema** tab.
104+
View the [advanced hunting schema tables](/defender-xdr/advanced-hunting-schema-tables) in the left pane inside the advanced hunting page under the **Schema** tab.
104105

105106
The schema list is a unified view of all tables from all your tenants regardless of the tenant selected in the upper right tenant selector.
106107

107108
This could mean that some tables that appear here might only be available for query in some tenants, like custom Microsoft Sentinel tables.
108109

109-
110110
## View and manage custom detection rules
111111

112-
113112
You can also manage custom detection rules from multiple tenants in the custom detection rules page.
114113

115114
### View custom detection rules by tenant
@@ -138,11 +137,6 @@ To manage detection rules:
138137

139138
1. Select **Open detection rules** to view this rule in a new tab for the specific tenant in the [Microsoft Defender portal](https://security.microsoft.com). To learn more, see [Custom detection rules](/defender-xdr/custom-detection-rules).
140139

141-
142-
143-
144-
145-
146140
## Related content
147141

148142
- [Set up Microsoft Defender multitenant management](mto-requirements.md)

0 commit comments

Comments
 (0)