Skip to content

Commit 7471c19

Browse files
committed
added new info
1 parent 08a6cb8 commit 7471c19

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

defender-xdr/defender-experts-scoped-coverage.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,11 @@ Currently, we do not offer support to rename this group nor have the option to s
4141
> [!IMPORTANT]
4242
> The device group must also be in the highest order of priority for the devices under it to be considered in scope. This is a known product limitation.
4343
44-
To set up scoped coverage, in the Microsoft Defender XDR portal, we will create a pre-defined Microsoft Defender for Endpoint (MDE) device group or Microsoft Entra ID user group. The default name assigned to a device or user group is **Defender_Experts_Scoped_Coverage_.**. It is recommended that you do not change the name of the user/device group.
44+
To set up scoped coverage, in the Microsoft Defender XDR portal, we will create a pre-defined Microsoft Defender for Endpoint (MDE) device group or Microsoft Entra ID user group. The default name assigned to a device or user group is **Defender_Experts_Scoped_Coverage_**.
45+
46+
:::image type="content" source="media/defender_scoped_devices.png" alt-text="Screenshot of Defender Experts Scoped devices." lightbox="media/defender_scoped_devices.png":::
47+
48+
You require the **System Administrator** permissions to create such device and user groups, however it is recommended that you do not change the name of the user/device group created by Defender Experts.
4549

4650
The following section lists down questions that you or your SOC team might have regarding scoped coverage.
4751

262 KB
Loading

0 commit comments

Comments
 (0)