Skip to content

Commit cf35f63

Browse files
committed
Update configure-exclusions-microsoft-defender-antivirus.md
1 parent bbb6774 commit cf35f63

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Custom exclusions apply to [scheduled scans](schedule-antivirus-scans.md), [on-d
4040

4141
| Setting | Description | Default value |
4242
| -------- | -------- | -------- |
43-
|**Configure if exclusions are visible to Local Admins** | - **Disabled (Default)**: If you disable or do not configure this setting, Local Admins will be able to see exclusions in the Windows Security App or via PowerShell. <br> - **Enabled**: If this setting is enabled, Local Admins will no longer be able to see the exclusion list in Windows Security App or via PowerShell. <br> - Please note that applying this setting will not remove exclusions, it will only prevent them from being visible to Local Admins. This is reflected in Get-MpPreference. <br> | Disabled |
43+
|**Configure if exclusions are visible to Local Admins** | - **Disabled (Default)**: If you disable or don't configure this setting, Local Admins are able to see exclusions in the Windows Security App or via PowerShell. <br> - **Enabled**: If this setting is enabled, Local Admins no longer see the exclusion list in Windows Security App or via PowerShell. <br> - Please note that applying this setting won't remove exclusions, it prevents them from being visible to Local Admins. This is reflected in Get-MpPreference. <br> | Disabled |
4444
|**Configure whether exclusions are visible to local users** | - Use this policy setting to configure whether or not exclusions are visible to Local Admins (HideExclusionsFromLocalAdmins). | Disabled |
4545

4646
## Configure and validate exclusions
@@ -123,7 +123,7 @@ Remember these important points:
123123

124124
## Audit antivirus exclusions on Exchange systems
125125

126-
Microsoft Exchange has supported integration with the Antimalware Scan Interface (AMSI) since the June 2021 Quarterly Updates for Exchange (see [Running Windows antivirus software on Exchange servers](/exchange/antispam-and-antimalware/windows-antivirus-software)). It's highly recommended to install these updates and make sure that AMSI is working properly. See [Microsoft Defender Antivirus security intelligence and product updates](microsoft-defender-antivirus-updates.md).
126+
Microsoft Exchange has supported integration with the anti-malware Scan Interface (AMSI) since the June 2021 Quarterly Updates for Exchange (see [Running Windows antivirus software on Exchange servers](/exchange/antispam-and-antimalware/windows-antivirus-software)). It's highly recommended to install these updates and make sure that AMSI is working properly. See [Microsoft Defender Antivirus security intelligence and product updates](microsoft-defender-antivirus-updates.md).
127127

128128
Many organizations exclude the Exchange directories from antivirus scans for performance reasons. Microsoft recommends auditing Microsoft Defender Antivirus exclusions on Exchange systems and assessing whether exclusions can be removed without impacting performance in your environment to ensure the highest level of protection. Exclusions can be managed by using Group Policy, PowerShell, or systems management tools like Microsoft Intune.
129129

0 commit comments

Comments
 (0)