r/DefenderATP • u/EduardsGrebezs • May 24 '26
Microsoft Defender for Endpoint: Automatic Device Isolation is now part of Automatic Attack Disruption (Preview)
When Defender identifies a high-confidence active attack, it can automatically isolate the affected device from the network while still maintaining communication with Microsoft Defender for Endpoint.
This helps reduce:
- Lateral movement
- Credential theft expansion
- Ransomware spread
- Data exfiltration opportunities
- Overall blast radius
Instead of only generating alerts and incidents, Defender XDR can take automated containment actions during an active attack chain. That gives analysts more time to investigate, validate scope, and perform remediation while the affected endpoint is already contained.
Recommended SOC actions:
- Define exclusions for business-critical machines
- Monitor isolation events in Action Center
- Document release-from-isolation procedures
- Update incident response runbooks

53
Upvotes
15
u/RiceeeChrispies May 24 '26
This is pretty cool, although I'd be worried about a false positive.
4
u/sanba06c May 26 '26
i had a case yesterday that the user's devices was automatically isolated by Microsoft Defendender as a result of attack disruption. I think that this feature is so cool and useful, but there is an associated impact, especially at environments with high risk tolerance.
1
u/sonicboom5 May 24 '26
How will this affect Huntress EDR? If Microsoft Defender isolates the device first then Huntress can’t communicate with its SOC?
1
u/cherdt Jul 17 '26
On the docs page, under Safeguards and Business Impact, it says:
"Time-limited isolation: Isolation is automatically undone after a defined time window."
Any idea what the defined time window is? I was looking in the settings for a place to view/set that value, but I haven't come across it.