Microsoft Defender XDR
Hunting and detection

Advanced Hunting Query Builder Details

In brief

The page updates its date, clarifies when the EventType filter is available, and improves descriptions of EventType, sample-size, Edit in KQL, and generated KQL screenshots. It also specifies the file-name and SHA256 example when describing narrowed Emails & collaboration queries.

What Defender admins need to know

Administrators get clearer guidance when using and interpreting Query Builder examples; no action is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Screenshot showing smart auto-complete support

Use EventType

You can even look for specific event types like all failed logons, file modification events, or successful network connections by using the EventType filter in any section where itthe EventType filter is applicable.available.

For instance, if you want to add a condition that looks for registry value deletions, you can go to the Registry Events section and select EventType.

Screenshot of the Registry Events EventType list showing available registry event values

Selecting EventType under Registry Events allows you to choose from different registry events, including the one you're hunting for, RegistryValueDeleted.

Screenshot of the Registry Events filter with EventType set to RegistryValueDeleted

Test your query with a smaller sample size

If you're still working on your query and would like to see its performance and some sample results quickly, adjust the number of records to return by picking a smaller set through the Sample size dropdown menu.

Screenshot of the Sample size dropdown used to limit returned records while testing a query

The sample size is set to 10,000 results by default, which is the maximum number of records that can be returned in hunting. However, we highly recommend lowering the sample size to 10 or 100 to quickly test your query, as doing so consumes less resources while you're still working on improving the query.

Switch to advanced mode after building a query

You can click on Edit in KQL to view the KQL query generated by your selected conditions. Editing in KQL opens a new tab in advanced mode, with the corresponding KQL query:

Screenshot of guided mode showing the Edit in KQL control used to open the generated query in advanced mode

Screenshot of the generated KQL query in advanced mode for a guided query searching file name and SHA256 across all relevant tables

In the file-name and SHA256 query example shown in the previous screenshot, the selected view is All, so the KQL query searches all tables that have file properties of name and SHA256, and in all the relevant columns covering these properties.

If you change the view to Emails & collaboration, the KQL query generated for the file-name and SHA256 example is narrowed down to:

Screenshot of the generated KQL query in advanced mode narrowed to Emails & collaboration tables for the file-name and SHA256 example

Related content