Very High Increase in CPU activity after Update Microsoft Defender for Identity sensor
All our servers that are running this sensor (DCs, Certificate servers, AD Connect servers) showed a massive increase in average CPU utilization from virtually straight after the sensor was automatically updated to version 2.254.19112.470 (late night UK time). Two of our DCs are sitting on 100% CPU today and we can't find anything to resolve it. Has anyone else seen this since running this version and if so what actions did you take ? How would we go back to rolling back to the previous version when it appears it will just be automatically updated soon after ? This is our monitoring of CPU utilization from one of the majorly affected DCs but every server with the sensor had the exact same graph showing a major increase in CPU at the same date and time i.e. just after the sensor was updated.
Defender for Identity documentation refreshed
Hi everyone, Just an informational note for our fantastic community of MDI advocates... Our incredible technical content developers have just concluded a mammoth exercise in updating all Defender for Identity documentation to reflect MDI's new home in Microsoft 365 Defender. aka.ms/MDIDocs For those still transitioning from using the classic MDI portal, don't worry - the documentation for that experience still exists and is accessible from the table of contents on the left of the screen. For anybody who has pages bookmarked, they should redirect without any issues. Thanks!
Missing remediation actions
Hi everyone, Remediation actions such as Disable/Enable user in AD, Force password reset are currently not available through the Defender portal (user page, advanced hunting). Anyone aware of this change? https://learn.microsoft.com/en-us/defender-for-identity/remediation-actions#supported-actions
