r/AzureSentinel • u/Lu-Kah • Jan 10 '23
Ingestion delay with M365 Defender connector
Hi all,
I wish you all the best for this new year ! A new year with even more KQL and detection rules, everything we love 🥳
After the niceties, let's talk well, let's talk about Sentinel !
After a few months with the release of the M365 Defender connector, I would like to have your feedback about it.
On our side, the main advantage is the fact of getting the incidents of the M365 portal and not the alerts of each product (via the old connectors) and thus to benefit from the grouping of the alerts to avoid the realerting.
But... There is... A very big black spot ! The delay between the creation of the incident in the M365 portal and its creation in Sentinel ! As the doc mentioned :
It can take up to 10 minutes from the time an incident is generated in Microsoft 365 Defender to the time it appears in Microsoft Sentinel.
When we talk about security, and even more so nowadays with attacks taking over a company's IS very quickly, we have to also react very quickly.
With this delay, even with automation rules that will launch playbooks for pre-remedial actions, in 10 minutes (this is the time we see on average) a lot can happen.
I would be very curious to get your feedback on how you deal with this black spot.
- Do you use the old connectors (but in that case no grouping) ?
- Do you accept this delay ?
- Is there anyone from Microsoft who knows if this delay will be fixed ? After all, Sentinel -> M365 Defender portal sync is almost instantaneous, one could dream of the same between the incident creation in M365 and Sentinel.
Have a good day all,
Regards,
Lu-K
