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/linux-exclusions.md
+76-68Lines changed: 76 additions & 68 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 02/18/2025
18
+
ms.date: 02/19/2025
19
19
---
20
20
21
21
# Configure and validate exclusions for Microsoft Defender for Endpoint on Linux
@@ -181,105 +181,113 @@ Create a dynamic Microsoft Entra group that uses the operating system type to en
181
181
For more information refer: [Manage endpoint security policies in Microsoft Defender for Endpoint](/defender-endpoint/manage-security-policies#create-an-endpoint-security-policy).
182
182
183
183
### Using the command line
184
+
184
185
Run the following command to see the available switches for managing exclusions:
185
-
> [!NOTE]
186
-
> `--scope` is an optional flag with accepted value as `epp` or `global`. It provides the same scope used while adding the exclusion to remove the same exclusion. In the command line approach, if the scope isn't mentioned, the scope value is set as `epp`.
187
-
> Exclusions added through CLI before the introduction of `--scope` flag remain unaffected and their scope is considered `epp`.
188
186
189
187
```bash
190
188
mdatp exclusion
191
189
```
192
190
191
+
> [!NOTE]
192
+
> `--scope` is an optional flag with accepted value as `epp` or `global`. It provides the same scope used while adding the exclusion to remove the same exclusion. In the command line approach, if the scope isn't mentioned, the scope value is set as `epp`.
193
+
> Exclusions added through CLI before the introduction of `--scope` flag remain unaffected and their scope is considered `epp`.
194
+
193
195
> [!TIP]
194
196
> When configuring exclusions with wildcards, enclose the parameter in double-quotes to prevent globbing.
195
197
196
-
Examples:
198
+
This section includes several examples.
197
199
198
-
-Add an exclusion for a file extension*(Extension exclusion isn't supported for global exclusion scope)*:
200
+
#### Example 1: Add an exclusion for a file extension
199
201
200
-
```bash
201
-
mdatp exclusion extension add --name .txt
202
-
```
202
+
You can add an exclusion for a file extension. Keep in mind that extension exclusions aren't supported for the global exclusion scope.
203
203
204
-
```console
205
-
Extension exclusion configured successfully
206
-
```
204
+
```bash
205
+
mdatp exclusion extension add --name .txt
206
+
```
207
+
208
+
```console
209
+
Extension exclusion configured successfully
210
+
```
207
211
208
-
```bash
209
-
mdatp exclusion extension remove --name .txt
210
-
```
212
+
```bash
213
+
mdatp exclusion extension remove --name .txt
214
+
```
211
215
212
-
```console
213
-
Extension exclusion removed successfully
214
-
```
216
+
```console
217
+
Extension exclusion removed successfully
218
+
```
215
219
216
-
- Add or Remove an exclusion fora file *(File path should already be presentincase of adding or removing exclusion with global scope)*:
You can add or remove an exclusion for a file. The file path should already be present if you're adding or removing an exclusion with the global scope.
0 commit comments