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: articles/defender-for-cloud/integration-defender-for-endpoint.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,9 @@ You'll deploy Defender for Endpoint to your Linux machines in one of these ways,
162
162
-[Enable for multiple subscriptions in the Azure portal dashboard](#enable-for-multiple-subscriptions-in-the-azure-portal-dashboard)
163
163
- Enable for multiple subscriptions with a PowerShell script
164
164
165
+
> [!NOTE]
166
+
> When you enable automatic deployment, Defender for Endpoint for Linux installation will abort on machines with pre-existing security solutions using [fanotify](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux#system-requirements).
167
+
> After you validate potential compatibility issues, we recommend that you manually install Defender for Endpoint on these servers.
165
168
166
169
##### Existing users with Defender for Cloud's enhanced security features enabled and Microsoft Defender for Endpoint for Windows
167
170
@@ -190,7 +193,6 @@ If you've already enabled the integration with **Defender for Endpoint for Windo
190
193
Microsoft Defender for Cloud will:
191
194
192
195
- Automatically onboard your Linux machines to Defender for Endpoint
193
-
- Ignore any machines that are running other fanotify-based solutions (see details of the `fanotify` kernel option required in [Linux system requirements](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux#system-requirements))
194
196
- Detect any previous installations of Defender for Endpoint and reconfigure them to integrate with Defender for Cloud
195
197
196
198
Microsoft Defender for Cloud will automatically onboard your machines to Microsoft Defender for Endpoint. Onboarding might take up to 12 hours. For new machines created after the integration has been enabled, onboarding takes up to an hour.
@@ -226,7 +228,6 @@ If you've never enabled the integration for Windows, endpoint protection enables
226
228
Microsoft Defender for Cloud will:
227
229
228
230
- Automatically onboard your Windows and Linux machines to Defender for Endpoint
229
-
- Ignore any Linux machines that are running other fanotify-based solutions (see details of the `fanotify` kernel option required in [Linux system requirements](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux#system-requirements))
230
231
- Detect any previous installations of Defender for Endpoint and reconfigure them to integrate with Defender for Cloud
0 commit comments