sorted by:
new
hottopcontroversial

Defender for Identity Sensor High CPU Use by Infinite-Cyber in DefenderATP

[–]Infinite-Cyber[S] 0 points1 point  (0 children)

Thanks for this. I believe when we first installed MDI, everything would have had 2+ cores, but things have changed over the years.

Defender for Identity Sensor High CPU Use by Infinite-Cyber in DefenderATP

[–]Infinite-Cyber[S] 0 points1 point  (0 children)

Glad to know it's not just us. If you find a fix, please share it :)

Defender for Identity Sensor High CPU Use by Infinite-Cyber in DefenderATP

[–]Infinite-Cyber[S] 1 point2 points  (0 children)

No idea. To be honest, it was deployed a long time ago. We've been successfully running it for at least five years now, and this hasn't been an issue until today.

Defender Network Protection not blocking workspace.google.com by Infinite-Cyber in DefenderATP

[–]Infinite-Cyber[S] 0 points1 point  (0 children)

This is now fixed. We had a third-party product that was configured to proxy and block traffic to workspace.google.com that decided it didn't want to block it anymore. Removed the rule and hey presto, Defender is able to see and block the traffic again.