Skip to content

Commit f0c5ef5

Browse files
authored
Merge pull request #799 from MicrosoftDocs/main
Publish main to live, Tuesday 3:30PM PDT, 06/25
2 parents f804a4f + 5157f38 commit f0c5ef5

29 files changed

+331
-315
lines changed

defender-endpoint/api/device-health-api-methods-properties.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: defender-endpoint
55
ms.author: siosulli
66
author: siosulli
77
ms.localizationpriority: medium
8-
ms.date: 05/15/2024
8+
ms.date: 06/25/2024
99
manager: deniseb
1010
ms.reviewr: mkaminska
1111
audience: ITPro
@@ -50,7 +50,7 @@ Data that is collected using either '_JSON response_ or _via files_' is the curr
5050
> [!IMPORTANT]
5151
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](../configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
5252
>
53-
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft 365 Security dashboard, see: [Device health and antivirus report in Microsoft Defender for Endpoint](../device-health-reports.md).
53+
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft Defender portal, see: [Device health and antivirus report in Microsoft Defender for Endpoint](../device-health-reports.md).
5454
5555
### 1.1 Export device antivirus health details API methods
5656

@@ -128,4 +128,5 @@ Data that is collected using either '_JSON response_ or _via files_' is the curr
128128
[Export device antivirus health report](device-health-export-antivirus-health-report-api.md)
129129

130130
[Device health and compliance reporting](../device-health-reports.md)
131+
131132
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../../includes/defender-mde-techcommunity.md)]

defender-endpoint/api/device-health-export-antivirus-health-report-api.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: defender-endpoint
55
ms.author: siosulli
66
author: siosulli
77
ms.localizationpriority: medium
8-
ms.date: 11/03/2022
8+
ms.date: 06/25/2024
99
manager: deniseb
1010
audience: ITPro
1111
ms.collection:
@@ -46,19 +46,13 @@ This API has two methods to retrieve Microsoft Defender Antivirus device antivir
4646

4747
Data that is collected using either '_JSON response_ or _via files_' is the current snapshot of the current state. It doesn't contain historic data. To collect historic data, customers must save the data in their own data storages. See [Export device health details API methods and properties](device-health-api-methods-properties.md).
4848

49-
> [!IMPORTANT]
50-
>
51-
> Currently, only the **Antivirus Health JSON Response** is generally available. **Antivirus Health API via files** is currently only available in public preview.
52-
>
53-
> **Advanced Hunting custom query** is currently only available in public preview, even if the queries are still visible.
54-
5549
> [!IMPORTANT]
5650
>
5751
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](../configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
5852
5953
> [!NOTE]
6054
>
61-
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft 365 Security dashboard, see: [Device health and antivirus compliance report in Microsoft Defender for Endpoint](../device-health-reports.md).
55+
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft Defender portal, see: [Device health and antivirus compliance report in Microsoft Defender for Endpoint](../device-health-reports.md).
6256
>
6357
6458
## 1 Export health reporting (JSON response)

defender-endpoint/assign-portal-access.md

Lines changed: 19 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection:
1313
- m365-security
1414
- tier2
1515
ms.topic: conceptual
16-
ms.date: 3/30/2023
16+
ms.date: 06/25/2024
1717
---
1818

1919
# Assign user access
@@ -32,19 +32,26 @@ ms.date: 3/30/2023
3232
3333
Defender for Endpoint supports two ways to manage permissions:
3434

35-
- **Basic permissions management**: Set permissions to either full access or read-only.
35+
- **Basic permissions management**: Set permissions to either full access or read-only. See [Use basic permissions to access the portal](basic-permissions.md).
36+
3637
- **Role-based access control (RBAC)**: Set granular permissions by defining roles, assigning Microsoft Entra user groups to the roles, and granting the user groups access to device groups. For more information on RBAC, see [Manage portal access using role-based access control](rbac.md).
3738

38-
> [!NOTE]
39-
> If you have already assigned basic permissions, you may switch to RBAC anytime. Consider the following before making the switch:
40-
> - Users with full access (users that are assigned the Global Administrator or Security Administrator directory role in Microsoft Entra ID), are automatically assigned the default Defender for Endpoint administrator role, which also has full access. Additional Microsoft Entra user groups can be assigned to the Defender for Endpoint administrator role after switching to RBAC. Only users assigned to the Defender for Endpoint administrator role can manage permissions using RBAC.
41-
> - Users that have read-only access (Security Readers) will lose access to the portal until they are assigned a role. Note that only Microsoft Entra user groups can be assigned a role under RBAC.
42-
> - After switching to RBAC, you will not be able to switch back to using basic permissions management.
43-
>
44-
> Device group creation is supported in Defender for Endpoint Plan 1 and Plan 2.
39+
## Change from basic permissions to RBAC
40+
41+
If you have already assigned basic permissions, you can switch to RBAC anytime. Consider the following before making the switch:
42+
43+
- Users who have full access (users who are assigned the Global Administrator or Security Administrator directory role in Microsoft Entra ID), are automatically assigned the default Defender for Endpoint administrator role, which also has full access.
44+
- Other Microsoft Entra user groups can be assigned to the Defender for Endpoint administrator role after switching to RBAC.
45+
- Only users who are assigned the Defender for Endpoint administrator role can manage permissions using RBAC.
46+
- Users who have read-only access (Security Readers) lose access to the portal until they are assigned a role. Only Microsoft Entra user groups can be assigned a role under RBAC.
47+
- After switching to RBAC, you can't switch back to using basic permissions management.
48+
49+
> [!IMPORTANT]
50+
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
51+
52+
## Related articles
4553

46-
## Related topics
54+
- [Create and manage device groups](machine-groups.md)
55+
- [Zero Trust with Microsoft Defender for Endpoint](zero-trust-with-microsoft-defender-endpoint.md)
4756

48-
- [Use basic permissions to access the portal](basic-permissions.md)
49-
- [Manage portal access using RBAC](rbac.md)
5057
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/attack-surface-reduction-rules-report.md

Lines changed: 10 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier2
1717
- mde-asr
18-
ms.date: 03/27/2023
18+
ms.date: 06/25/2024
1919
search.appverid: met150
2020
---
2121

@@ -33,9 +33,6 @@ search.appverid: met150
3333

3434
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
3535

36-
> [!IMPORTANT]
37-
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
38-
3936
The attack surface reduction rules report provides information about the _attack surface reduction rules_ that are applied to devices in your organization. This report also provides information about:
4037

4138
- detected threats
@@ -47,39 +44,31 @@ Additionally, this report provides an easy-to-use interface that enables you to:
4744
- View threat detections
4845
- View the configuration of the ASR rules
4946
- Configure (add) exclusions
50-
- Easily activate _basic protection_ by enabling the three most recommended ASR rules with a single toggle
5147
- Drill down to gather detailed information
5248

5349
For more information about individual attack surface reduction rules, see [Attack surface reduction rules reference](attack-surface-reduction-rules-reference.md).
5450

5551
## Prerequisites
5652

5753
> [!IMPORTANT]
58-
> To access the **Attack surface reduction rules report**, read permissions are required for the Microsoft Defender portal. Access to this report granted by Microsoft Entra roles, such as Security Global Admin or Security role, is being deprecated and will be removed in April 2023.
59-
> For Windows Server 2012 R2 and Windows Server 2016 to appear in the **Attack surface reduction rules report**, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
54+
> To access the attack surface reduction rules report, read permissions are required for the Microsoft Defender portal.
55+
> For Windows Server 2012 R2 and Windows Server 2016 to appear in the attack surface reduction rules report, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
6056
6157
## Report access permissions
6258

63-
To access the **Attack surface reduction rules report** in the Microsoft 365 Security dashboard, the following permissions are required:
59+
To access the attack surface reduction rules report in the Microsoft Defender portal, the following permissions are required:
6460

6561
| Permission type | Permission | Permission display name |
6662
|:---|:---|:---|
67-
| Application | Machine.Read.All | 'Read all machine profiles' |
68-
|Delegated (work or school account) | Machine.Read | 'Read machine information' |
69-
70-
To assign these permissions:
63+
| Application | `Machine.Read.All` | `Read all machine profiles` |
64+
| Delegated (work or school account) | `Machine.Read` | `Read machine information` |
7165

72-
1. Sign in to <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft Defender XDR</a> using account with Security administrator or Global administrator role assigned.
73-
1. In the navigation pane, select **Settings** \> **Endpoints** \> **Roles** (under **Permissions**).
74-
1. Select the role you'd like to edit.
75-
1. Select **Edit**.
76-
1. In **Edit role**, on the **General** tab, in **Role name**, type a name for the role.
77-
1. In **Description** type a brief summary of the role.
78-
1. In **Permissions**, select **View Data**, and under **View Data** select **Attack surface reduction**.
66+
You can assign permissions by using Microsoft Entra ID or the Microsoft Defender portal.
7967

80-
For more information about user role management, see [Create and manage roles for role-based access control](user-roles.md).
68+
- To use Microsoft Entra ID, see [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal)
69+
- To use the Microsoft Defender portal, see [Assign user access](assign-portal-access.md).
8170

82-
## Navigation
71+
## Navigate to the attack surface reduction rules report
8372

8473
To navigate to the summary cards for the attack surface reduction rules report
8574

defender-endpoint/basic-permissions.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
ms.topic: conceptual
1818
search.appverid: met150
19-
ms.date: 02/21/2024
19+
ms.date: 06/25/2024
2020
---
2121

2222
# Use basic permissions to access the portal
@@ -31,14 +31,7 @@ ms.date: 02/21/2024
3131

3232
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-basicaccess-abovefoldlink)
3333
34-
Refer to the instructions below to use basic permissions management.
35-
36-
You can use either of the following solutions:
37-
38-
- Microsoft Graph PowerShell
39-
- Azure portal
40-
41-
For granular control over permissions, [switch to role-based access control](rbac.md).
34+
If you want to use basic permissions management for the Microsoft Defender portal, keep in mind that permissions are set to either full access or read only. For granular control over permissions, [use role-based access control](rbac.md).
4235

4336
## Assign user access using Microsoft Graph PowerShell
4437

@@ -57,6 +50,7 @@ You can assign users with one of the following levels of permissions:
5750
- Connect to your Microsoft Entra ID. For more information, see [Connect-MgGraph](/powershell/microsoftgraph/authentication-commands).
5851

5952
- **Full access**: Users with full access can log in, view all system information and resolve alerts, submit files for deep analysis, and download the onboarding package. Assigning full access rights requires adding the users to the "Security Administrator" or "Global Administrator" Microsoft Entra built-in roles.
53+
6054
- **Read-only access**: Users with read-only access can log in, view all alerts, and related information.
6155

6256
They will not be able to change alert states, submit files for deep analysis or perform any state changing operations.
@@ -93,11 +87,10 @@ Use the following steps to assign security roles:
9387

9488
For more information, see [Add or remove group members using Microsoft Entra ID](/azure/active-directory/fundamentals/active-directory-groups-members-azure-portal).
9589

96-
## Assign user access using the Azure portal
97-
98-
For more information, see [Assign administrator and non-administrator roles to users with Microsoft Entra ID](/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
9990

100-
## Related topic
91+
## Related articles
10192

93+
- [Assign Microsoft Entra roles to users](/entra/identity/role-based-access-control/manage-roles-portal)
10294
- [Manage portal access using RBAC](rbac.md)
95+
10396
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

0 commit comments

Comments
 (0)