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-endpoint/microsoft-defender-endpoint-linux.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,8 +85,11 @@ In general you need to take the following steps:
85
85
- Red Hat Enterprise Linux 9.x
86
86
- CentOS 6.7 or higher (In preview)
87
87
- CentOS 7.2 or higher
88
-
- Ubuntu 16.04 LTS or higher LTS
89
-
- Debian 9 - 12
88
+
- Ubuntu 16.04 LTS
89
+
- Ubuntu 18.04 LTS
90
+
- Ubuntu 20.04 LTS
91
+
- Ubuntu 22.04 LTS
92
+
- Debian 9 - 12
90
93
- SUSE Linux Enterprise Server 12 or higher
91
94
- SUSE Linux Enterprise Server 15 or higher
92
95
- Oracle Linux 7.2 or higher
@@ -105,9 +108,10 @@ In general you need to take the following steps:
105
108
> MDE Linux version 101.23082.0011 is the last MDE Linux release supporting RHEL 6.7 or higher versions (does not expire before June 30, 2024). Customers are advised to plan upgrades to their RHEL 6 infrastructure aligned with guidance from Red Hat.
106
109
107
110
- List of supported kernel versions
108
-
> [!NOTE]
109
-
> Microsoft Defender for Endpoint on Red Hat Enterprise Linux and CentOS - 6.7 to 6.10 is a Kernel based solution. You must verify that the kernel version is supported before updating to a newer kernel version.
110
-
> Microsoft Defender for Endpoint for all other supported distributions and versions is kernel-version-agnostic. With a minimal requirement for the kernel version to be at or greater than 3.10.0-327.
111
+
112
+
> [!NOTE]
113
+
> Microsoft Defender for Endpoint on Red Hat Enterprise Linux and CentOS - 6.7 to 6.10 is a Kernel based solution. You must verify that the kernel version is supported before updating to a newer kernel version.
114
+
> Microsoft Defender for Endpoint for all other supported distributions and versions is kernel-version-agnostic. With a minimal requirement for the kernel version to be at or greater than 3.10.0-327.
111
115
112
116
- The `fanotify` kernel option must be enabled
113
117
- Red Hat Enterprise Linux 6 and CentOS 6:
@@ -249,5 +253,6 @@ High I/O workloads from certain applications can experience performance issues w
249
253
-[Protect your endpoints with Defender for Cloud's integrated EDR solution: Microsoft Defender for Endpoint](/azure/defender-for-cloud/integration-defender-for-endpoint)
250
254
-[Connect your non-Azure machines to Microsoft Defender for Cloud](/azure/defender-for-cloud/quickstart-onboard-machines)
251
255
-[Turn on network protection for Linux](network-protection-linux.md)
256
+
252
257
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
Copy file name to clipboardExpand all lines: defender-endpoint/migrate-devices-streamlined.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.collection:
13
13
- tier1
14
14
ms.topic: how-to
15
15
ms.subservice: onboard
16
-
ms.date: 05/08/2024
16
+
ms.date: 05/09/2024
17
17
---
18
18
19
19
# Migrate devices to use the streamlined connectivity method
@@ -33,6 +33,7 @@ In most cases, full device offboarding isn't required when reonboarding. You can
33
33
> [!IMPORTANT]
34
34
> Limitations and known issues:
35
35
>
36
+
> - We found a back-end issue with populating the `ConnectivityType` column in the `DeviceInfo table` in advanced hunting so that you can track migration progress. We aim to resolve this issue as soon as possible.
36
37
> - For device migrations (reonboarding): Offboarding is not required to switch over to streamlined connectivity method. Once the updated onboarding package is run, a full device reboot is required for Windows devices and a service restart for macOS and Linux. For more information, see the details included in this article.
37
38
> - Windows 10 versions 1607, 1703, 1709, and 1803 do not support reonboarding. Offboard first and then onboard using the updated package. These versions also require a longer URL list.
38
39
> - Devices running the MMA agent are not supported and must continue using the MMA onboarding method.
Copy file name to clipboardExpand all lines: defender-endpoint/threat-protection-integration.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
@@ -58,7 +58,7 @@ Suspicious activities are processes running under a user context. The integratio
58
58
59
59
### Microsoft Defender for Office
60
60
61
-
[Defender for Office 365]/defender-office-365/mdo-about helps protect your organization from malware in email messages or files through Safe Links, Safe Attachments, advanced Anti-Phishing, and spoof intelligence capabilities. The integration between Microsoft Defender for Office 365 and Microsoft Defender for Endpoint enables security analysts to go upstream to investigate the entry point of an attack. Through threat intelligence sharing, attacks can be contained and blocked.
61
+
[Defender for Office 365](/defender-office-365/mdo-about) helps protect your organization from malware in email messages or files through Safe Links, Safe Attachments, advanced Anti-Phishing, and spoof intelligence capabilities. The integration between Microsoft Defender for Office 365 and Microsoft Defender for Endpoint enables security analysts to go upstream to investigate the entry point of an attack. Through threat intelligence sharing, attacks can be contained and blocked.
62
62
63
63
> [!NOTE]
64
64
> Defender for Office 365 data is displayed for events within the last 30 days. For alerts, Defender for Office 365 data is displayed based on first activity time. After that, the data is no longer available in Defender for Office 365.
Copy file name to clipboardExpand all lines: defender-office-365/advanced-delivery-policy-configure.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
@@ -59,7 +59,7 @@ Messages that are identified by the advanced delivery policy aren't security thr
59
59
- To connect to Exchange Online PowerShell, see [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell).
60
60
61
61
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
62
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Core Security settings (manage)** or **Authorization and settings/Security settings/Core Security settings (read)**.
62
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Core Security settings (manage)** or **Authorization and settings/Security settings/Core Security settings (read)**.
63
63
-[Email & collaboration permissions in the Microsoft Defender portal](mdo-portal-permissions.md) and [Exchange Online permissions](/exchange/permissions-exo/permissions-exo):
64
64
-_Create, modify, or remove configured settings in the advanced delivery policy_: Membership in the **Security Administrator** role groups in Email & collaboration RBAC <u>and</u> membership in the **Organization Management** role group in Exchange Online RBAC.
65
65
-_Read-only access to the advanced delivery policy_: Membership in the **Global Reader** or **Security Reader** role groups in Email & collaboration RBAC.
Copy file name to clipboardExpand all lines: defender-office-365/air-about.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
@@ -101,7 +101,7 @@ Microsoft 365 provides many built-in alert policies that help identify Exchange
101
101
102
102
You need to be assigned permissions to use AIR. You have the following options:
103
103
104
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (Affects the Defender portal only, not PowerShell):
104
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
105
105
-_Start an automated investigation_ or _Approve or reject recommended actions_: **Security Operator/Email advanced remediation actions (manage)**.
106
106
-[Email & collaboration permissions in the Microsoft Defender portal](mdo-portal-permissions.md):
107
107
-_Set up AIR features_: Membership in the **Organization Management** or **Security Administrator** role groups.
Copy file name to clipboardExpand all lines: defender-office-365/air-user-automatic-feedback-response.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,6 @@ appliesto:
15
15
16
16
# Automatic user notifications for user reported phishing results in AIR
17
17
18
-
> [!NOTE]
19
-
> The features described in this article are currently in Public Preview, aren't available in all organizations, and are subject to change.
20
-
21
18
In Microsoft 365 organizations with Exchange Online mailboxes, admins can configure the backend for messages that users report as malicious or not malicious in Outlook (send to Microsoft, send to a reporting mailbox, or both), and configure the various notification options for user reported messages. For more information, see [User reported settings](submissions-user-reported-messages-custom-mailbox.md).
22
19
23
20
In Microsoft 365 organizations with Microsoft Defender for Office 365 Plan 2, when a user reports a message as phishing, an investigation is automatically created in [automated investigation and response (AIR)](air-about.md). Admins can configure the user reported message settings to send an email notification to the user who reported the message based on the verdict from AIR. This notification is also known as _automatic feedback response_.
Copy file name to clipboardExpand all lines: defender-office-365/alert-policies-defender-portal.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
@@ -35,7 +35,7 @@ In Microsoft 365 organizations with mailboxes in Exchange Online, alert policies
35
35
## What do you need to know before you begin?
36
36
37
37
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
38
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (Affects the Defender portal only, not PowerShell):
38
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
39
39
-_Read only access to the Alert policies page_: **Security operations / Security data / Security data basics (read)**.
Copy file name to clipboardExpand all lines: defender-office-365/anti-malware-policies-configure.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
@@ -47,7 +47,7 @@ You can configure anti-malware policies in the Microsoft Defender portal or in P
47
47
- To connect to Exchange Online PowerShell, see [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). To connect to standalone EOP PowerShell, see [Connect to Exchange Online Protection PowerShell](/powershell/exchange/connect-to-exchange-online-protection-powershell).
48
48
49
49
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
50
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Core Security settings (manage)** or **Authorization and settings/Security settings/Core Security settings (read)**.
50
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Core Security settings (manage)** or **Authorization and settings/Security settings/Core Security settings (read)**.
0 commit comments