diff --git a/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md b/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
index 00e6c568d8..6ae308d67b 100644
--- a/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
+++ b/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
@@ -42,6 +42,9 @@ The value of this policy setting indicates the number of users whose logon infor
 Users who access the server console will have their logon credentials cached on that server. A malicious user who is able to access the file system of the server can locate this cached information and use a brute-force attack to determine user passwords. Windows mitigates this type of attack by 
 encrypting the information and keeping the cached credentials in the system's registries, which are spread across numerous physical locations.
 
+> [!NOTE]
+> The cached account information does not expire, but can get overwritten, as described previously.
+
 ### Possible values
 
 -   A user-defined number from 0 through 50
@@ -107,4 +110,4 @@ member of the IT department has recently logged on to the device to perform syst
 
 ## Related topics
 
-- [Security Options](security-options.md)
\ No newline at end of file
+- [Security Options](security-options.md)