Update considerations-known-issues.md

Changed "NTLM classic (NTLMv1)" clarification.
This commit is contained in:
zwhitt-microsoft 2024-06-19 15:33:32 -07:00 committed by GitHub
parent 8a1c3f19ca
commit 3f58cdd5fa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -22,7 +22,7 @@ Upgrades to Windows 11, 22H2 and Windows Server 2025 (preview) will have Credent
## Wi-fi and VPN considerations ## Wi-fi and VPN considerations
When Credential Guard is enabled, you can no longer use NTLM classic authentication for single sign-on. You'll be forced to enter your credentials to use these protocols and can't save the credentials for future use. When Credential Guard is enabled, you can no longer use NTLM classic authentication (NTLMv1) for single sign-on. You'll be forced to enter your credentials to use these protocols and can't save the credentials for future use.
If you're using WiFi and VPN endpoints that are based on MS-CHAPv2, they're subject to similar attacks as for NTLMv1. If you're using WiFi and VPN endpoints that are based on MS-CHAPv2, they're subject to similar attacks as for NTLMv1.