Skip to content

Commit 9b0820e

Browse files
committed
Update defender-experts-scoped-coverage.md
1 parent 9dec335 commit 9b0820e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Devices and users that are out of scope won't be supported by Defender Experts.
3636

3737
You can create a predefined Microsoft Defender for Endpoint device group or a Microsoft Entra ID user group in the Microsoft Defender portal to which you can add devices and users, respectively. The default name assigned to the created device or user group is:
3838

39-
- **Defender_Experts_Scoped_Coverage_Devices**.
39+
- **Defender_Experts_Scoped_Coverage_Devices**
4040
- **Defender_Experts_Scoped_Coverage_Users**
4141

4242
:::image type="content" source="media/defender_scoped_devices.png" alt-text="Screenshot of Defender Experts Scoped devices." lightbox="media/defender_scoped_devices.png":::
@@ -47,7 +47,7 @@ The devices and users you add to these groups are then considered as the set of
4747
> Defender Experts need **Security admin** permissions to create the device and user groups. [Learn more about granting permissions to our experts](get-started-xdr.md#grant-permissions-to-our-experts)
4848
4949
> [!TIP]
50-
> The device group must should be in the highest order of priority for the devices under it, to be considered in scope. This is a known product limitation.
50+
> The device group should be in the highest order of priority for the devices under it, to be considered in scope. This is a known product limitation.
5151
5252
Currently, the service doesn't offer support to rename these predefined groups, so we recommend that you don't rename the created device or user group. It also doesn't support nested groups. The devices and users would have to be added individually to the groups created.
5353

0 commit comments

Comments
 (0)