From 6c06b13cc6a967e5433763155a6be0ab5da6acc4 Mon Sep 17 00:00:00 2001 From: jcaparas Date: Mon, 25 Nov 2019 14:39:33 -0800 Subject: [PATCH] Update configure-endpoints-vdi.md --- .../microsoft-defender-atp/configure-endpoints-vdi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md index 1ec1a8e920..5a8e0475ca 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md @@ -34,7 +34,7 @@ Microsoft Defender ATP supports non-persistent VDI session onboarding. There mig - Instant early onboarding of a short-lived sessions, which must be onboarded to Microsoft Defender ATP prior to the actual provisioning. - The machine name is typically reused for new sessions. -VDI machines can appear in MDATP portal as either: +VDI machines can appear in Microsoft Defender ATP portal as either: - Single entry for each machine. Note that in this case, the *same* machine name must be configured when the session is created, for example using an unattended answer file.