From 50a4e9303061ab47668c79d23eb2125b86896da7 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 7 May 2019 15:55:45 -0700 Subject: [PATCH] update version for airs --- ...estigations-windows-defender-advanced-threat-protection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection.md b/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection.md index 8968b3b2cf..8ff29cf968 100644 --- a/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection.md +++ b/windows/security/threat-protection/windows-defender-atp/automated-investigations-windows-defender-advanced-threat-protection.md @@ -34,8 +34,8 @@ The Automated investigations list shows all the investigations that have been in Entities are the starting point for Automated investigations. When an alert contains a supported entity for Automated investigation (for example, a file) that resides on a machine that has a supported operating system for Automated investigation then an Automated investigation can start. >[!NOTE] ->Currently, Automated investigation only supports Windows 10, version 1803 or later. ->Some investigation playbooks, like memory investigations, require Windows 10, version 1809 or later. +>Currently, Automated investigation only supports Windows 10, version 1709 or later. +>Some investigation playbooks, like memory investigations, require Windows 10, version 1709 or later. The alerts start by analyzing the supported entities from the alert and also runs a generic machine playbook to see if there is anything else suspicious on that machine. The outcome and details from the investigation is seen in the Automated investigation view.