From 2dc2268c019bdb0149a52d722eda51febef0be96 Mon Sep 17 00:00:00 2001
From: Brock Walters <153771548+nonpunctual@users.noreply.github.com>
Date: Wed, 29 Oct 2025 11:08:33 -0400
Subject: [PATCH] Clarify SCEP challenge string requirements for Windows
 (#34916)

Modified to include base64 warning.
---
 articles/connect-end-user-to-wifi-with-certificate.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/connect-end-user-to-wifi-with-certificate.md b/articles/connect-end-user-to-wifi-with-certificate.md
index 5282fcc201..8c2fdf0a53 100644
--- a/articles/connect-end-user-to-wifi-with-certificate.md
+++ b/articles/connect-end-user-to-wifi-with-certificate.md
@@ -517,7 +517,7 @@ Custom SCEP proxy:
 
 * NDES SCEP proxy is currently supported for macOS devices via Apple config profiles. Support for DDM (Declarative Device Management) is coming soon, as is support for iOS, iPadOS, Windows, and Linux.
 * Fleet server assumes a one-time challenge password expiration time of 60 minutes.
-* On Windows, special characters in SCEP challenge strings such as `! @ # $ % ^ & * _ ()` should not be used. 
+* On Windows, SCEP challenge strings should NOT include `base64` encoding or special characters such as `! @ # $ % ^ & * _ ()` 
 
 ## How to deploy certificates to a user's login keychain