SOLVED

Windows Hello for business queries

%3CLINGO-SUB%20id%3D%22lingo-sub-2595984%22%20slang%3D%22en-US%22%3EWindows%20Hello%20for%20business%20queries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2595984%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%20All%2C%3C%2FP%3E%3CP%3EI%E2%80%99m%20a%20complete%20newbie%20in%20Microsoft%20365%20security%20and%20need%20some%20guidance%20for%20a%20client%20who%20is%20look%20has%20Windows%20Hello%20for%20business%20queries.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EClient%20has%20Hybrid%20setup.%3C%2FLI%3E%3CLI%3EThey%20want%20to%20On-board%20%26nbsp%3Bto%20Windows%20Hello%20for%20Business.%3C%2FLI%3E%3CLI%3EThey%20looking%20for%20Pilot%20roll%20out%20of%2020%20or%20100%20users%20on%20Windows%20Hello%20for%20Business.%3C%2FLI%3E%3CLI%3EActive%20Directory%20Federation%20Service%20in%20place.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EQueries%20%3C%2FSTRONG%3E%26nbsp%3B%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3EWhat%20does%20it%20mean%20by%20%3CSTRONG%3Ekey%20trust%3C%2FSTRONG%3E%20and%20%3CSTRONG%3Ecertificate%20trust%3C%2FSTRONG%3E%3F%3CBR%20%2F%3E%3CSTRONG%3E%3CU%3EQuestion%3C%2FU%3E%3C%2FSTRONG%3E%3CU%3E%3A%3C%2FU%3E%20Could%20any%20key%20differences%20between%20%3CSTRONG%3Ekey%20trust%20%3C%2FSTRONG%3Eand%20%3CSTRONG%3Ecertificate%20trust%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSTRONG%3EI%20just%20tried%20use%20Microsoft%20docs%20to%20understand%20but%20cant%20figure%20out%20differences%3COL%3E%3CLI%3E%3CSTRONG%3EKey%20trust%3C%2FSTRONG%3E%20-%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-cert-trust-policy-settings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-cert-trust-policy-settings%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EWindows%20considers%20the%20deployment%20to%20use%20key-trust%20on-premises%20authentication%2C%20which%20requires%20a%20sufficient%20number%20of%20Windows%20Server%202016%20domain%20controllers%20to%20handle%20the%20Windows%20Hello%20for%20Business%20key-trust%20authentication%20requests.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3ECertificate%20trust%3C%2FSTRONG%3E%20-%3CBR%20%2F%3E%3CBR%20%2F%3EWindows%20Hello%20for%20Business%20replaces%20%3CSTRONG%3Eusername%20%3C%2FSTRONG%3Eand%20%3CSTRONG%3Epassword%3C%2FSTRONG%3E%20sign-in%20to%20Windows%20with%20strong%20user%20authentication%20based%20on%20asymmetric%20key%20pair.%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3BThe%20following%20deployment%20guide%20provides%20the%20information%20needed%20to%20successfully%20deploy%20%3CSTRONG%3EWindows%20Hello%20for%20Business%3C%2FSTRONG%3E%20in%20a%20hybrid%20certificate%20trust%20scenario.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-hybrid-cert-trust%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-hybrid-cert-trust%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3EFor%20%3CSTRONG%3Ehybrid%20deployment%3C%2FSTRONG%3E%2C%20do%20we%20have%20to%20check%20if%20the%20%3CSTRONG%3Eclient%3C%2FSTRONG%3E%20can%20meet%20the%20full%20list%20of%20requirements%20in%20the%20table%3F%3CBR%20%2F%3E%3CSTRONG%3E%3CU%3EQuestion%3C%2FU%3E%3C%2FSTRONG%3E%3A%20Does%20the%20client%20fits%20the%20hybrid%20deployment%20requirements%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fapc01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fwindows%252Fsecurity%252Fidentity-protection%252Fhello-for-business%252Fhello-identity-verification%26amp%3Bdata%3D04%257C01%257Climengtat%2540spgroup.com.sg%257C21b5aa29f36e44987d7b08d93f78ea3d%257C85541afe47e843a3bfa3cfafe05e6bd4%257C0%257C0%257C637610610848062519%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DR2lwAFeF9a6Njc04c7627AN4qHz0Z%252BLAUNMZhG8DZ8M%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EWindows%20Hello%20for%20Business%20Deployment%20Prerequisite%20Overview%20-%20Microsoft%20365%20Security%20%7C%20Microsoft%20Docs%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ArohShukla_0-1627634696107.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F299515iF805E47ACC8B104F%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ArohShukla_0-1627634696107.png%22%20alt%3D%22ArohShukla_0-1627634696107.png%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAny%20help%20would%20be%20highly%20appreciated.%20%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2597665%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Hello%20for%20business%20queries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597665%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F43548%22%20target%3D%22_blank%22%3E%40Aroh%20Shukla%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20would%20recommend%20you%20to%20start%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-planning-guide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPlanning%20a%20Windows%20Hello%20for%20Business%20Deployment%20-%20Microsoft%20365%20Security%20%7C%20Microsoft%20Docs%3C%2FA%3E.%20If%20you%20follow%20that%20guide%2C%20you%20should%20be%20able%20to%20answer%20your%20clients%20questions.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20quickly%20point%20out%20your%20specific%20questions%2C%20the%20difference%20between%20key%20trust%20and%20certificate%20trust%20are%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20deployment's%20trust%20type%20defines%20how%20each%20Windows%20Hello%20for%20Business%20client%20authenticates%20to%20the%20on-premises%20Active%20Directory.%20There%20are%20two%20trust%20types%3A%20key%20trust%20and%20certificate%20trust.%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20key%20trust%20type%20does%20not%20require%20issuing%20authentication%20certificates%20to%20end%20users.%20Users%20authenticate%20using%20a%20hardware-bound%20key%20created%20during%20the%20built-in%20provisioning%20experience.%20This%20requires%20an%20adequate%20distribution%20of%20Windows%20Server%202016%20or%20later%20domain%20controllers%20relative%20to%20your%20existing%20authentication%20and%20the%20number%20of%20users%20included%20in%20your%20Windows%20Hello%20for%20Business%20deployment.%20Read%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-adequate-domain-controllers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPlanning%20an%20adequate%20number%20of%20Windows%20Server%202016%20or%20later%20Domain%20Controllers%20for%20Windows%20Hello%20for%20Business%20deployments%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%20learn%20more.%3C%2FLI%3E%3CLI%3EThe%20certificate%20trust%20type%20issues%20authentication%20certificates%20to%20end%20users.%20Users%20authenticate%20using%20a%20certificate%20requested%20using%20a%20hardware-bound%20key%20created%20during%20the%20built-in%20provisioning%20experience.%20Unlike%20key%20trust%2C%20certificate%20trust%20does%20not%20require%20Windows%20Server%202016%20domain%20controllers%20(but%20still%20requires%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-hybrid-cert-trust-prereqs%23directories%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20Server%202016%20or%20later%20Active%20Directory%20schema%3C%2FA%3E).%20Users%20can%20use%20their%20certificate%20to%20authenticate%20to%20any%20Windows%20Server%202008%20R2%2C%20or%20later%2C%20domain%20controller.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EChoose%20a%20trust%20type%20that%20is%20best%20suited%20for%20your%20organizations.%20Remember%2C%20the%20trust%20type%20determines%20two%20things.%20Whether%20you%20issue%20authentication%20certificates%20to%20your%20users%20and%20if%20your%20deployment%20needs%20Windows%20Server%202016%20domain%20controllers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20trust%20model%20is%20not%20more%20secure%20than%20the%20other.%20The%20major%20difference%20is%20based%20on%20the%20organization%20comfort%20with%20deploying%20Windows%20Server%202016%20domain%20controllers%20and%20not%20enrolling%20users%20with%20end%20entity%20certificates%20(key-trust)%20against%20using%20existing%20domain%20controllers%20(Windows%20Server%202008R2%20or%20later)%20and%20needing%20to%20enroll%20certificates%20for%20all%20their%20users%20(certificate%20trust).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBecause%20the%20certificate%20trust%20types%20issues%20certificates%2C%20there%20is%20more%20configuration%20and%20infrastructure%20needed%20to%20accommodate%20user%20certificate%20enrollment%2C%20which%20could%20also%20be%20a%20factor%20to%20consider%20in%20your%20decision.%20Additional%20infrastructure%20needed%20for%20certificate-trust%20deployments%20includes%20a%20certificate%20registration%20authority.%20In%20a%20federated%20environment%2C%20you%20need%20to%20activate%20the%20Device%20Writeback%20option%20in%20Azure%20AD%20Connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20your%20organization%20wants%20to%20use%20the%20key%20trust%20type%2C%20write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Ekey%20trust%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ein%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E1b%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eon%20your%20planning%20worksheet.%20Write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EWindows%20Server%202016%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ein%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E4d%3C%2FSTRONG%3E.%20Write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EN%2FA%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ein%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E5b%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20your%20organization%20wants%20to%20use%20the%20certificate%20trust%20type%2C%20write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Ecertificate%20trust%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ein%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E1b%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eon%20your%20planning%20worksheet.%20Write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EWindows%20Server%202008%20R2%20or%20later%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ein%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E4d%3C%2FSTRONG%3E.%20In%20box%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E5c%3C%2FSTRONG%3E%2C%20write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Esmart%20card%20logon%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eunder%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ETemplate%20Name%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ecolumn%20and%20write%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Eusers%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eunder%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EIssued%20To%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ecolumn%20on%20your%20planning%20worksheet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ESource%3C%2FEM%3E%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fidentity-protection%2Fhello-for-business%2Fhello-planning-guide%23trust-types%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPlanning%20a%20Windows%20Hello%20for%20Business%20Deployment%20-%20Microsoft%20365%20Security%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20your%20client%26nbsp%3B%3CSPAN%3Efits%20the%20hybrid%20deployment%20requirements%2C%20depends%20on%20the%20trust%20type%20you%20choose.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2597468%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Hello%20for%20business%20queries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597468%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20somebody%20reply%20to%20my%20query%3F%20I%20will%20be%20grateful%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F44888%22%20target%3D%22_blank%22%3E%40Ryan%20Heffernan%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F108661%22%20target%3D%22_blank%22%3E%40Kartik%20Kanakasabesan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2614030%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Hello%20for%20business%20queries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2614030%22%20slang%3D%22en-US%22%3EThanks%20a%20million%20R_Gijsbers_Rademakers%20for%20your%20reply.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

 

Hello All,

I’m a complete newbie in Microsoft 365 security and need some guidance for a client who is look has Windows Hello for business queries.

 

  1. Client has Hybrid setup.
  2. They want to On-board  to Windows Hello for Business.
  3. They looking for Pilot roll out of 20 or 100 users on Windows Hello for Business.
  4. Active Directory Federation Service in place.

    Queries   

  5. What does it mean by key trust and certificate trust?
    Question: Could any key differences between key trust and certificate trust:

    I just tried use Microsoft docs to understand but cant figure out differences
    1. Key trust -
      https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-cert-...

      Windows considers the deployment to use key-trust on-premises authentication, which requires a sufficient number of Windows Server 2016 domain controllers to handle the Windows Hello for Business key-trust authentication requests.

    2. Certificate trust -

      Windows Hello for Business replaces username and password sign-in to Windows with strong user authentication based on asymmetric key pair.

       The following deployment guide provides the information needed to successfully deploy Windows Hello for Business in a hybrid certificate trust scenario.

      https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybri...

  6. For hybrid deployment, do we have to check if the client can meet the full list of requirements in the table?
    Question: Does the client fits the hybrid deployment requirements?

    Windows Hello for Business Deployment Prerequisite Overview - Microsoft 365 Security | Microsoft Doc...

    ArohShukla_0-1627634696107.png

     

Any help would be highly appreciated.  

3 Replies

Can somebody reply to my query? I will be grateful

 

@Ryan Heffernan  @Kartik Kanakasabesan 

best response confirmed by Trevor_Rusher (Community Manager)
Solution

@Aroh Shukla 

I would recommend you to start here: Planning a Windows Hello for Business Deployment - Microsoft 365 Security | Microsoft Docs. If you follow that guide, you should be able to answer your clients questions.

 

To quickly point out your specific questions, the difference between key trust and certificate trust are as follows:

 

A deployment's trust type defines how each Windows Hello for Business client authenticates to the on-premises Active Directory. There are two trust types: key trust and certificate trust.

  • The key trust type does not require issuing authentication certificates to end users. Users authenticate using a hardware-bound key created during the built-in provisioning experience. This requires an adequate distribution of Windows Server 2016 or later domain controllers relative to your existing authentication and the number of users included in your Windows Hello for Business deployment. Read the Planning an adequate number of Windows Server 2016 or later Domain Controllers for Windows Hello for... to learn more.
  • The certificate trust type issues authentication certificates to end users. Users authenticate using a certificate requested using a hardware-bound key created during the built-in provisioning experience. Unlike key trust, certificate trust does not require Windows Server 2016 domain controllers (but still requires Windows Server 2016 or later Active Directory schema). Users can use their certificate to authenticate to any Windows Server 2008 R2, or later, domain controller.

Choose a trust type that is best suited for your organizations. Remember, the trust type determines two things. Whether you issue authentication certificates to your users and if your deployment needs Windows Server 2016 domain controllers.

 

One trust model is not more secure than the other. The major difference is based on the organization comfort with deploying Windows Server 2016 domain controllers and not enrolling users with end entity certificates (key-trust) against using existing domain controllers (Windows Server 2008R2 or later) and needing to enroll certificates for all their users (certificate trust).

 

Because the certificate trust types issues certificates, there is more configuration and infrastructure needed to accommodate user certificate enrollment, which could also be a factor to consider in your decision. Additional infrastructure needed for certificate-trust deployments includes a certificate registration authority. In a federated environment, you need to activate the Device Writeback option in Azure AD Connect.

 

If your organization wants to use the key trust type, write key trust in box 1b on your planning worksheet. Write Windows Server 2016 in box 4d. Write N/A in box 5b.

 

If your organization wants to use the certificate trust type, write certificate trust in box 1b on your planning worksheet. Write Windows Server 2008 R2 or later in box 4d. In box 5c, write smart card logon under the Template Name column and write users under the Issued To column on your planning worksheet.

 

SourcePlanning a Windows Hello for Business Deployment - Microsoft 365 Security | Microsoft Docs

 

If your client fits the hybrid deployment requirements, depends on the trust type you choose. 

Thanks a million R_Gijsbers_Rademakers for your reply.