Update RDP sign-in requirements with Microsoft

Intune deployment instructions
This commit is contained in:
Paolo Matarazzo
2023-12-08 15:05:41 -05:00
parent 256dd9895c
commit 808afc0f07

View File

@ -43,9 +43,12 @@ Here's a list of requiremets to enable RDP sign-in with Windows Hello for Busine
> * A PKI infrastructure based on AD CS or third-party > * A PKI infrastructure based on AD CS or third-party
> * Windows Hello for Business deployed to the clients > * Windows Hello for Business deployed to the clients
> * If you plan to support Microsoft Entra joined devices, the domain controllers must have a certificate, which serves as a *root of trust* for the clients. The certificate ensures that clients don't communicate with rogue domain controllers > * If you plan to support Microsoft Entra joined devices, the domain controllers must have a certificate, which serves as a *root of trust* for the clients. The certificate ensures that clients don't communicate with rogue domain controllers
> * If you plan to deploy certificates using Microsoft Intune:
> * Ensure you have the required infrastructure to support either [SCEP][MEM-1] or [PKCS][MEM-2] deployments If you plan to deploy certificates using Microsoft Intune, here are additional requiremets:
> * Deploy the root CA certificate (and any other intermediate certificate authority certificates) to Microsoft Entra joined Devices using a *Trusted root certificate* policy with Intune. For guidance, refer to [Create trusted certificate profiles in Microsoft Intune][MEM-5]
> [!div class="checklist"]
> * Ensure you have the infrastructure to support either [SCEP][MEM-1] or [PKCS][MEM-2] deployment
> * Deploy the root CA certificate and any other intermediate certificate authority certificates to Microsoft Entra joined Devices using a [Trusted root certificate policy][MEM-5]
## Create a Windows Hello for Business certificate template ## Create a Windows Hello for Business certificate template