From 9d93b1f9da96d49263654fc185e43ce24d686f11 Mon Sep 17 00:00:00 2001 From: v-chodges <96920257+v-chodges@users.noreply.github.com> Date: Mon, 3 Jan 2022 08:49:56 -0600 Subject: [PATCH] Update windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../mdm/policy-csp-admx-microsoftdefenderantivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md index fba7c6f419..e8f77fefa1 100644 --- a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md +++ b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md @@ -3693,7 +3693,7 @@ ADMX Info: This policy setting allows you to define the number of days that must pass before spyware security intelligence is considered out of date. If security intelligence is determined to be out of date, this state may trigger several additional actions, including falling back to an alternative update source or displaying a warning icon in the user interface. By default, this value is set to 14 days. -It is recommended not to set the value below 2 days to avoid machines to go out of date. +We do not recommend setting the value below two days to avoid machines going out of date. If you enable this setting, spyware security intelligence will be considered out of date after the number of days specified have passed without an update.