From 75874148779327438bc3ba32954fc82565d28704 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Mon, 9 Nov 2020 11:10:38 -0800 Subject: [PATCH] pencil edit --- .../threat-protection/microsoft-defender-atp/machine-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/machine-groups.md b/windows/security/threat-protection/microsoft-defender-atp/machine-groups.md index 554b5877df..3b19a5d4f9 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/machine-groups.md +++ b/windows/security/threat-protection/microsoft-defender-atp/machine-groups.md @@ -30,7 +30,7 @@ ms.topic: article In an enterprise scenario, security operation teams are typically assigned a set of devices. These devices are grouped together based on a set of attributes such as their domains, computer names, or designated tags. -In Defender for Endpoint, you can create device groups and use them to: +In Microsoft Defender for Endpoint, you can create device groups and use them to: - Limit access to related alerts and data to specific Azure AD user groups with [assigned RBAC roles](rbac.md) - Configure different auto-remediation settings for different sets of devices - Assign specific remediation levels to apply during automated investigations