From e82efe9be8ea6fde8d48c296169a03764d8de90d Mon Sep 17 00:00:00 2001
From: Sriraman M S <45987684+msbemba@users.noreply.github.com>
Date: Wed, 23 Nov 2022 17:00:33 +0530
Subject: [PATCH] Update hello-deployment-rdp-certs.md

Made changes to Subject Alternative Name

fixes #https://github.com/MicrosoftDocs/windows-itpro-docs/issues/11053
---
 .../hello-for-business/hello-deployment-rdp-certs.md          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md b/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md
index 282264de1e..62a2a4eb41 100644
--- a/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md
+++ b/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md
@@ -139,7 +139,7 @@ This section describes how to configure a SCEP policy in Intune. Similar steps c
     | --- | --- |
     |*Certificate Type*| User |
     |*Subject name format* | `CN={{UserPrincipalName}}` |
-    |*Subject alternative name* |From the dropdown, select **User principal name (UPN)** with a value of `CN={{UserPrincipalName}}`
+    |*Subject alternative name* |From the dropdown, select **User principal name (UPN)** with a value of `{{UserPrincipalName}}`
     |*Certificate validity period* | Configure a value of your choosing|
     |*Key storage provider (KSP)* | **Enroll to Windows Hello for Business, otherwise fail (Windows 10 and later)**
     |*Key usage*| **Digital Signature**|
@@ -198,4 +198,4 @@ After obtaining a certificate, users can RDP to any Windows devices in the same
 [MEM-5]: /mem/intune/protect/certificates-trusted-root
 [MEM-6]: /mem/intune/protect/certificate-authority-add-scep-overview
 
-[HTTP-1]: https://www.powershellgallery.com/packages/Generate-CertificateRequest
\ No newline at end of file
+[HTTP-1]: https://www.powershellgallery.com/packages/Generate-CertificateRequest