From a9289ad95f211dd7021eb3f3fa63244fb52db5f9 Mon Sep 17 00:00:00 2001 From: v-chodges <96920257+v-chodges@users.noreply.github.com> Date: Fri, 31 Dec 2021 10:49:56 -0600 Subject: [PATCH] Edit Notes: ADMX_MicrosoftDefenderAntivirus/SignatureUpdate_ASSignatureDue It is recommended not to set the value below 2 days to avoid machines to go out of date. --- .../mdm/policy-csp-admx-microsoftdefenderantivirus.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md index ea7d8bca47..fba7c6f419 100644 --- a/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md +++ b/windows/client-management/mdm/policy-csp-admx-microsoftdefenderantivirus.md @@ -3693,6 +3693,8 @@ 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. + 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. If you disable or do not configure this setting, spyware security intelligence will be considered out of date after the default number of days have passed without an update.