Consecutive OR rows are grouped in parentheses; AND starts a new where clause.
Assemble valid KQL for Microsoft Sentinel (Log Analytics) or Defender XDR Advanced Hunting — stage by stage, with the right schema, the right time column, joins, time-series buckets, and type-aware operators. Builds queries; never runs them.
Consecutive OR rows are grouped in parentheses; AND starts a new where clause.
KQL (Kusto Query Language) is the query language used by Microsoft Sentinel (Log Analytics) and Microsoft Defender XDR Advanced Hunting to search and analyze security telemetry.
Yes. You pick the environment and the builder uses the correct schema and time column — TimeGenerated for Sentinel / Log Analytics, Timestamp for Defender XDR Advanced Hunting — plus the right table names for each.
Yes. A dedicated join stage correlates two tables (inner, leftouter, semi, anti, and more) with match keys and an optional time filter on the right table, and the aggregate stage supports bin() time buckets with render timechart for time-series hunts.
No. It only assembles valid KQL text for you to copy into Sentinel or Defender. It never connects to your tenant or executes anything, and it runs entirely in your browser.
Yes. Copy a shareable deep-link that rebuilds the exact query in someone else's browser, or export the query as a Microsoft Sentinel scheduled analytics rule (YAML) or a Defender XDR custom detection.
Yes — 38 MITRE ATT&CK-tagged templates spanning twelve tactics cover common hunts so you can start from a working query and adapt it to your environment.