KQL data limit

[Phoenixstar]

Adios Defenders,

Does anyone know how to bypass the data limit of 10000 rows

[#2]

You can use the api to get 100k rows? https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/run-advanced-query-api?vie... Typically you'd only use more than a few 100's of rows if you plan to export the data, to make it human readable (much less than 10k), try the summarize or where operators : https://docs.microsoft.com/en-gb/azure/data-explorer/kusto/query/summarizeoperator and https://docs.microsoft.com/en-gb/azure/data-explorer/kusto/query/whereoperator

[#3 · Accepted solution]

As far as I am aware, the limit is fixed. The trick is to get your query down beneath the limit by imposing criteria in the most efficient order. You can view a shorter period of time, a more limited group of devices or simply remove data irrelevant to the threat you are hunting. I cannot be more specific as I typically work with EXO, but even then our tenancy is big enough to slam straight into the limits if I tried to eat everything.

[#4]

Will implement this Thanks !!

[#5]

This is the most updated AH API : https://docs.microsoft.com/en-us/microsoft-365/security/defender/api-advanced-hunting?view=o365-worl...

You can leverage it to get up to 100K records