Skip to content

Commit

Permalink
Update prevent-changes-to-security-settings-with-tamper-protection.md
Browse files Browse the repository at this point in the history
added information around co-managed devices not being supported for exclusion tamper protection from what I can tell
  • Loading branch information
andrewjohnporter authored Oct 7, 2024
1 parent 256542f commit 4a989b7
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ When tamper protection is turned on, these tamper-protected settings can't be ch
- Automatic actions are taken on detected threats.
- Notifications are visible in the Windows Security app on Windows devices.
- Archived files are scanned.
- [Exclusions cannot be modified or added ](manage-tamper-protection-intune.md#tamper-protection-for-antivirus-exclusions) (Applies to Intune or Configuration Manager)
- [Exclusions cannot be modified or added ](manage-tamper-protection-intune.md#tamper-protection-for-antivirus-exclusions) (Applies to devices managed by Intune only or by Configuration Manager only. Co-Managed devices are not supported)

*As of signature release `1.383.1159.0`, due to confusion around the default value for "Allow Scanning Network Files", tamper protection no longer locks this setting to its default value. In managed environments, the default value is `enabled`.*

Expand Down

0 comments on commit 4a989b7

Please sign in to comment.