You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-xdr/defender-experts-scoped-coverage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Currently, we do not offer support to rename this group nor have the option to s
41
41
> [!IMPORTANT]
42
42
> 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.
43
43
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_.**. It is recommended that you do not change the name of the user/device group.
45
45
46
46
The following section lists down questions that you or your SOC team might have regarding scoped coverage.
0 commit comments