Skip to content

Commit 7609cc2

Browse files
committed
Update configure-extension-file-exclusions-microsoft-defender-antivirus.md
1 parent 202d80c commit 7609cc2

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

defender-endpoint/configure-extension-file-exclusions-microsoft-defender-antivirus.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Exclude files from Microsoft Defender Antivirus scans based on thei
44
ms.service: defender-endpoint
55
ms.subservice: ngp
66
ms.localizationpriority: medium
7-
ms.date: 04/03/2024
7+
ms.date: 09/10/2024
88
author: siosulli
99
ms.author: siosulli
1010
ms.topic: conceptual
@@ -189,6 +189,7 @@ See [Add exclusions in the Windows Security app](microsoft-defender-security-cen
189189
## Use wildcards in the file name and folder path or extension exclusion lists
190190

191191
You can use the asterisk `*`, question mark `?`, or environment variables (such as `%ALLUSERSPROFILE%`) as wildcards when defining items in the file name or folder path exclusion list. You can mix and match `*` and `?` and environment variables into a single exclusion. The way these wildcards are interpreted differs from their usual usage in other apps and languages. Make sure to read this section to understand their specific limitations.
192+
192193
> [!IMPORTANT]
193194
> There are key limitations and usage scenarios for these wildcards:
194195
> - Environment variable usage is limited to machine variables and those applicable to processes running as an NT AUTHORITY\SYSTEM account.

0 commit comments

Comments
 (0)