From a900fbebad45e7ab3ba1197e3d769be0f3c1b846 Mon Sep 17 00:00:00 2001 From: Jeff Borsecnik <36546697+jborsecnik@users.noreply.github.com> Date: Mon, 28 Nov 2022 09:39:08 -0800 Subject: [PATCH] Update hello-deployment-rdp-certs.md --- .../hello-for-business/hello-deployment-rdp-certs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 82e591ddb6..af71e186d2 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 @@ -55,7 +55,7 @@ Follow these steps to create a certificate template: | *Compatibility* | | | *General* | | | *Extensions* | Verify the **Application Policies** extension includes **Smart Card Logon**| - | *Subject Name* |
**Note:** If you deploy certificates via Intune, select **Supply in the request** instead of *Build from this Active Directory*| + | *Subject Name* |
**Note:** If you deploy certificates via Intune, select **Supply in the request** instead of *Build from this Active Directory*.| |*Request Handling*|| |*Cryptography*|| |*Security*|Add the security group that you want to give **Enroll** access to. For example, if you want to give access to all users, select the **Authenticated** users group, and then select Enroll permissions for them|