From 4a989b7c29b22f35935d267823af277b97acfe88 Mon Sep 17 00:00:00 2001
From: Andrew John Porter <53306271+andrewjohnporter@users.noreply.github.com>
Date: Mon, 7 Oct 2024 23:26:01 +0100
Subject: [PATCH] Update
 prevent-changes-to-security-settings-with-tamper-protection.md

added information around co-managed devices not being supported for exclusion tamper protection from what I can tell
---
 ...event-changes-to-security-settings-with-tamper-protection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md b/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md
index a864800546..eae20447d3 100644
--- a/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md
+++ b/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md
@@ -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`.*