From bec466912b57ad98ec41d5dac242ebcf3dccce78 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Tue, 27 Dec 2022 19:57:47 +0530
Subject: [PATCH] added windows 11

after reading this article, i confirmed windows 11 is supported
---
 .../access-credential-manager-as-a-trusted-caller.md             | 1 +
 1 file changed, 1 insertion(+)

diff --git a/windows/security/threat-protection/security-policy-settings/access-credential-manager-as-a-trusted-caller.md b/windows/security/threat-protection/security-policy-settings/access-credential-manager-as-a-trusted-caller.md
index 1c67b647de..5ac230e0ed 100644
--- a/windows/security/threat-protection/security-policy-settings/access-credential-manager-as-a-trusted-caller.md
+++ b/windows/security/threat-protection/security-policy-settings/access-credential-manager-as-a-trusted-caller.md
@@ -20,6 +20,7 @@ ms.technology: itpro-security
 # Access Credential Manager as a trusted caller
 
 **Applies to**
+-   Windows 11
 -   Windows 10
 
 This article describes the recommended practices, location, values, policy management, and security considerations for the **Access Credential Manager as a trusted caller** security policy setting.