Skip to content

Commit 1cbabe2

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/defender-docs-pr into WI473943-account-view-manual-account-correlation
2 parents 2bd7292 + a8373fd commit 1cbabe2

File tree

117 files changed

+298
-227
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

117 files changed

+298
-227
lines changed

.openpublishing.redirection.defender-endpoint.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -165,5 +165,10 @@
165165
"redirect_url": "/defender-xdr/contact-defender-support",
166166
"redirect_document_id": false
167167
},
168+
{
169+
"source_path": "defender-endpoint/install-defender-endpoint-linux.md",
170+
"redirect_url": "/defender-endpoint/mde-linux-prerequisites",
171+
"redirect_document_id": false
172+
}
168173
]
169174
}

defender-endpoint/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -263,7 +263,7 @@
263263
items:
264264
- name: Prerequisites
265265
href: mde-linux-prerequisites.md
266-
- name: Choose a deployment method
266+
- name: Choose a deployment method
267267
items:
268268
- name: Enabling deployment to a custom location
269269
href: linux-custom-location-installation.md

defender-endpoint/configure-proxy-internet.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Configure your devices to connect to the Defender for Endpoint service us
33
description: Learn how to configure your devices to enable communication with the cloud service using a proxy.
44
search.appverid: met150
55
ms.service: defender-endpoint
6-
ms.author: bagol
7-
author: batamig
6+
ms.author: painbar
7+
author: paulinbar
88
ms.localizationpriority: medium
99
manager: bagol
1010
audience: ITPro
@@ -13,12 +13,12 @@ ms.collection:
1313
- tier1
1414
ms.topic: how-to
1515
ms.subservice: onboard
16-
ms.date: 07/01/2024
16+
ms.date: 11/09/2025
1717
appliesto:
1818
- Microsoft Defender for Endpoint Plan 1
1919
- Microsoft Defender for Endpoint Plan 2
20-
2120
---
21+
2222
# STEP 2: Configure your devices to connect to the Defender for Endpoint service using a proxy
2323

2424

@@ -126,7 +126,9 @@ Configure the static proxy using the Group Policy available in Administrative Te
126126
>
127127
> For resiliency purposes and the real-time nature of cloud-delivered protection, Microsoft Defender Antivirus caches the last known working proxy. Ensure your proxy solution does not perform SSL inspection, as that breaks the secure cloud connection.
128128
>
129-
> Microsoft Defender Antivirus doesn't use the static proxy to connect to Windows Update or Microsoft Update for downloading updates. Instead, it uses a system-wide proxy if configured to use Windows Update, or the configured internal update source according to the [configured fallback order](manage-protection-updates-microsoft-defender-antivirus.md). If necessary, you can use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define proxy auto-config (.pac)** for connecting to the network. If you need to set up advanced configurations with multiple proxies, use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define addresses to bypass proxy server** and prevent Microsoft Defender Antivirus from using a proxy server for those destinations.
129+
> Microsoft Defender Antivirus doesn't use the static proxy to connect to Windows Update or Microsoft Update for downloading updates. Instead, it uses a system-wide proxy if configured to use Windows Update, or the configured internal update source according to the [configured fallback order](manage-protection-updates-microsoft-defender-antivirus.md).
130+
>
131+
> If necessary, you can use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define proxy auto-config (.pac)** for connecting to the network. If you need to set up advanced configurations with multiple proxies, use **Administrative Templates > Windows Components > Microsoft Defender Antivirus > Define addresses to bypass proxy server** and prevent Microsoft Defender Antivirus from using a proxy server for those destinations.
130132
>
131133
> You can use PowerShell with the `Set-MpPreference` cmdlet to configure these options:
132134
> - `ProxyBypass`

defender-endpoint/mde-linux-prerequisites.md

Lines changed: 45 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: Prerequisites for Microsoft Defender for Endpoint on Linux
33
ms.reviewer: gopkr, pahuijbr, megphapriya
44
description: Describes the requirements needed to install and use Microsoft Defender for Endpoint on Linux.
@@ -15,20 +15,19 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 10/27/2025
18+
ms.date: 11/11/2025
1919
---
2020

2121
# Prerequisites for Microsoft Defender for Endpoint on Linux
2222

2323
> [!TIP]
2424
> Microsoft Defender for Endpoint on Linux now extends support for Arm64-based Linux servers in GA.
2525
26-
2726
This article lists hardware and software requirements for Defender for Endpoint on Linux. For more information about Defender for Endpoint on Linux, such as what's included in this offering, see the following articles:
2827

29-
- [Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
28+
- [Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
3029

31-
- [What's new in Defender for Endpoint on Linux](linux-whatsnew.md)
30+
- [What's new in Defender for Endpoint on Linux](linux-whatsnew.md)
3231

3332
[!INCLUDE [side-by-side-scenarios](includes/side-by-side-scenarios.md)]
3433

@@ -70,56 +69,59 @@ For detailed licensing information, see [Product Terms: Microsoft Defender for E
7069

7170
The following Linux server distributions and x64 (AMD64/EM64T) versions are supported:
7271

73-
- Red Hat Enterprise Linux 7.2 and higher
74-
- Red Hat Enterprise Linux 8.x
75-
- Red Hat Enterprise Linux 9.x
76-
- CentOS 7.2 and higher, excluding CentOS Stream
72+
- Red Hat Enterprise Linux 7.2 and higher
73+
- Red Hat Enterprise Linux 8.x
74+
- Red Hat Enterprise Linux 9.x
75+
- Red Hat Enterprise Linux 10.x
76+
- CentOS 7.2 and higher, excluding CentOS Stream
7777
- CentOS 8.x
78-
- Ubuntu 16.04 LTS
79-
- Ubuntu 18.04 LTS
80-
- Ubuntu 20.04 LTS
81-
- Ubuntu 22.04 LTS
82-
- Ubuntu 24.04 LTS
83-
- Debian 9 - 12
84-
- SUSE Linux Enterprise Server 12.x
85-
- SUSE Linux Enterprise Server 15.x
86-
- Oracle Linux 7.2 and higher
87-
- Oracle Linux 8.x
88-
- Oracle Linux 9.x
89-
- Amazon Linux 2
90-
- Amazon Linux 2023
78+
- Ubuntu 16.04 LTS
79+
- Ubuntu 18.04 LTS
80+
- Ubuntu 20.04 LTS
81+
- Ubuntu 22.04 LTS
82+
- Ubuntu 24.04 LTS
83+
- Debian 9 - 12
84+
- SUSE Linux Enterprise Server 12.x
85+
- SUSE Linux Enterprise Server 15.x
86+
- Oracle Linux 7.2 and higher
87+
- Oracle Linux 8.x
88+
- Oracle Linux 9.x
89+
- Amazon Linux 2
90+
- Amazon Linux 2023
9191
- Fedora 33-42
92-
- Rocky 8.7 and higher
93-
- Rocky 9.2 and higher
94-
- Alma 8.4 and higher
95-
- Alma 9.2 and higher
96-
- Mariner 2
92+
- Rocky 8.7 and higher
93+
- Rocky 9.2 and higher
94+
- Alma 8.4 and higher
95+
- Alma 9.2 and higher
96+
- Mariner 2
9797

9898
**The following Linux server distributions on ARM64 are now GA:**
9999

100-
- Ubuntu 20.04 ARM64
101-
- Ubuntu 22.04 ARM64
100+
- Ubuntu 20.04 ARM64
101+
- Ubuntu 22.04 ARM64
102102
- Ubuntu 24.04 ARM64
103103
- Debian 11, 12 ARM64
104-
- Amazon Linux 2 ARM64
105-
- Amazon Linux 2023 ARM64
104+
- Amazon Linux 2 ARM64
105+
- Amazon Linux 2023 ARM64
106106
- RHEL 8.x ARM64
107107
- RHEL 9.x ARM64
108+
- RHEL 10.x ARM64
108109
- Oracle Linux 8.x ARM64
109110
- Oracle Linux 9.x ARM64
110111
- SUSE Linux Enterprise Server 15 (SP5, SP6) ARM64
111112

112113
> [!NOTE]
113-
> Distributions and versions that aren't explicitly listed above, and custom operating systems, are unsupported (even if they're derived from the officially supported distributions).
114-
> Microsoft Defender for Endpoint is kernel-version agnostic for all other supported distributions and versions. The minimal requirement for the kernel version is`3.10.0-327`or later.
114+
> Distributions and versions that aren't explicitly listed above, and custom operating systems, are unsupported (even if they're derived from the officially supported distributions).
115+
> Microsoft Defender for Endpoint is kernel-version agnostic for all other supported distributions and versions. The minimal requirement for the kernel version is `3.10.0-327` or later.
115116
116117
> [!WARNING]
117118
> Running Defender for Endpoint on Linux alongside other fanotify-based security solutions is not supported and may lead to unpredictable behavior, including system hangs.
118119
> If any applications use fanotify in blocking mode, they will appear in the conflicting_applications field of the mdatp health command output.
119-
> You can still safely take advantage of Defender for Endpoint on Linux by setting antivirus enforcement level to passive. See [Configure security settings in Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-preferences).> **EXCEPTION:** The Linux `FAPolicyD` feature, which also uses Fanotify in blocking mode, is supported with Defender for Endpoint in active mode on RHEL and Fedora platforms, provided that mdatp health reports a healthy status. This exception is based on validated compatibility specific to these distributions.
120-
>
121-
>
122-
## Supported filesystems for real-time protection and quick, full, and custom scans
120+
> You can still safely take advantage of Defender for Endpoint on Linux by setting antivirus enforcement level to passive. See [Configure security settings in Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-preferences).> **EXCEPTION:** The Linux `FAPolicyD` feature, which also uses Fanotify in blocking mode, is supported with Defender for Endpoint in active mode on RHEL and Fedora platforms, provided that mdatp health reports a healthy status. This exception is based on validated compatibility specific to these distributions.
121+
>
122+
>
123+
124+
## Supported filesystems for real-time protection and quick, full, and custom scans
123125

124126
|Real-time protection and quick/full scans|Custom scans|
125127
|---|---|
@@ -141,7 +143,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
141143
|`xfs`|
142144

143145
> [!NOTE]
144-
> To scan NFS v3 mount points, make sure to set the`no_root_squash`export option. Without this option, scanning NFS v3 can potentially fail due to lack of permissions.
146+
> To scan NFS v3 mount points, make sure to set the `no_root_squash` export option. Without this option, scanning NFS v3 can potentially fail due to lack of permissions.
145147
146148
## Verify if devices can connect to Defender for Endpoint cloud services
147149

@@ -150,16 +152,16 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
150152
2. Connect Defender for Endpoint on Linux through a proxy server by using the following discovery methods:
151153

152154
- Transparent proxy
153-
- [Manual static proxy configuration](/defender-endpoint/linux-static-proxy-configuration#installation-time-configuration)
155+
- [Manual static proxy configuration](/defender-endpoint/linux-static-proxy-configuration#installation-time-configuration)
154156

155157
3. Permit anonymous traffic in the previously listed URLs, if a proxy or firewall blocks traffic.
156158

157-
> [!NOTE]
159+
> [!NOTE]
158160
> Configuration for transparent proxies isn't needed for Defender for Endpoint. See [Manual Static Proxy Configuration.](/defender-endpoint/linux-static-proxy-configuration)
159161
160162
> [!WARNING]
161-
> PAC, WPAD, and authenticated proxies aren't supported.
162-
> Use only static or transparent proxies.
163+
> PAC, WPAD, and authenticated proxies aren't supported.
164+
> Use only static or transparent proxies.
163165
> SSL inspection and intercepting proxies aren't supported for security reasons.
164166
> Configure an exception for SSL inspection and your proxy server to allow direct data pass-through from Defender for Endpoint on Linux to the relevant URLs without interception.
165167
> Adding your interception certificate to the global store doesn't enable interception.
@@ -183,7 +185,6 @@ If the Microsoft Defender for Endpoint installation fails due to missing depende
183185
> - For DEBIAN, the mdatp package requires `auditd`.
184186
> - For Mariner, the mdatp package requires `audit`.
185187
186-
187188
## Installation instructions
188189

189190
There are several methods and tools that you can use to deploy Microsoft Defender for Endpoint on Linux (applicable to AMD64 and ARM64 Linux servers):
@@ -219,4 +220,4 @@ If you experience any installation issues, self-troubleshooting resources are av
219220
- [Install Defender for Endpoint on Linux to a custom path](linux-custom-location-installation.md)
220221

221222
> [!TIP]
222-
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)
223+
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)

defender-endpoint/microsoft-defender-endpoint-linux.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ appliesto:
2121
- Microsoft Defender for Endpoint Plan 2
2222

2323
---
24+
2425
# Microsoft Defender for Endpoint on Linux
2526

2627

@@ -143,4 +144,4 @@ If you're using non-Microsoft applications, also see their documentation regardi
143144
- [Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md)
144145

145146
> [!TIP]
146-
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)
147+
> Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/category/microsoft-defender-for-endpoint/discussions/microsoftdefenderatp)

defender-endpoint/microsoft-defender-offline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ Starting with Windows 10, version 1607 or newer, and Windows 11, Microsoft Defen
128128
> [!NOTE]
129129
> In Windows 10, version 1607, the offline scan can be run from **Windows Settings > Update & security > Windows Defender** or from the Windows Defender client.
130130
131-
1. On your Windows device, open the Windows Security app, and then **Scan options**.
131+
1. On your Windows device, open the **Windows Security** app. Select **Virus & threat protection**, and then choose **Scan options**.
132132

133133
2. Select the radio button **Microsoft Defender Offline scan** and select **Scan now**.
134134

defender-endpoint/respond-machine-alerts.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: defender-endpoint
55
ms.author: painbar
66
author: paulinbar
77
ms.localizationpriority: medium
8-
ms.date: 11/05/2025
8+
ms.date: 11/11/2025
99
manager: bagol
1010
audience: ITPro
1111
ms.collection:
@@ -363,7 +363,9 @@ When an identity in your network might be compromised, you must prevent that ide
363363
> Blocking incoming communication with a "contained" user is supported on onboarded Microsoft Defender for Endpoint Windows 10 and 11 devices (Sense version 8740 and higher), Windows Server 2019+ devices, and Windows Servers 2012R2 and 2016 with the modern agent.
364364
365365
> [!IMPORTANT]
366-
> Once a **Contain user** action is enforced on a domain controller, it starts a GPO update on the Default Domain Controller policy. A change of a GPO starts a sync across the domain controllers in your environment. This is expected behavior, and if you monitor your environment for AD GPO changes, you may be notified of such changes. Undoing the **Contain user** action reverts the GPO changes to their previous state, which will then start another AD GPO synchronization in your environment. Learn more about [merging of security policies on domain controllers](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj966251(v=ws.11)#merging-of-security-policies-on-domain-controllers).
366+
> As part of the active protection provided by Microsoft Defender for Endpoint, a distributed mechanism can apply LSA Policy to prevent compromised users from accessing machines in your organization. Currently, when this policy is applied on domain controllers, it may cause Group Policy synchronization activity across domain controllers.
367+
>
368+
> We are gradually rolling out a new solution by integrating with new OS APIs. This deployment will be phased and thoroughly tested to ensure stability and security. During this rollout, LSA Policy enforcement on your servers will be temporarily removed to prevent potential GPO sync. This change will remain in effect until the rollout is complete.
367369
368370
### How to contain a user
369371

0 commit comments

Comments
 (0)