Update Windows Hello for Business deployment documentation

This commit is contained in:
Paolo Matarazzo 2023-12-27 17:14:03 -05:00
parent 6f5d0648c2
commit de91609bb9
4 changed files with 37 additions and 17 deletions

View File

@ -10,6 +10,11 @@ ms.topic: how-to
[!INCLUDE [requirements](includes/requirements.md)]
:ballot_box_with_check: Authentication to Microsoft Entra ID
:ballot_box_with_check: Multifactor authentication
:ballot_box_with_check: Device configuration
:ballot_box_with_check: Licensing for cloud services
## Introduction
When you Microsoft Entra join a device, the system attempts to automatically enroll you in Windows Hello for Business, by default. If you want to use Windows Hello for Business in a cloud-only environment, there's no additional configuration needed.

View File

@ -11,6 +11,20 @@ ms.topic: tutorial
[!INCLUDE [requirements](includes/requirements.md)]
:ballot_box_with_check: Deployment options
:ballot_box_with_check: Deploment models
:ballot_box_with_check: Trust types
:ballot_box_with_check: Authentication
:ballot_box_with_check: Device registration
:ballot_box_with_check: Key registration
:ballot_box_with_check: Directory synchronization
:ballot_box_with_check: Multifactor authentication
:ballot_box_with_check: Device configuration
:ballot_box_with_check: Public Key Infrastructure
:ballot_box_with_check: Licensing for cloud services
:ballot_box_with_check: Windows requirements
:ballot_box_with_check: Windows Server requirements
## Deployment steps
Once the prerequisites are met, deploying Windows Hello for Business consists of the following steps:

View File

@ -6,3 +6,5 @@ ms.topic: include
## Requirements
Before starting the deployment, review the requirements described in the [Plan a Windows Hello for Business Deployment](../index.md) article.
Ensure that the following requirements are met before you begin:

View File

@ -24,22 +24,21 @@ This guide removes the appearance of complexity by helping you make decisions on
Read this document and record your decisions. When finished, you should have all the necessary information to determine requirements and the next steps for your Windows Hello for Business deployment.
> [!div class="checklist"]
> There are 7 major categories to consider when planning a Windows Hello for Business deployment:
>
>- Deployment options
> - Deploment models
> - Trust types
>- Authentication
> - Device registration
> - Key registration
> - Directory synchronization
> - Multifactor authentication
>- Device configuration
>- Public Key Infrastructure
>- Licensing requirements for cloud services
>- Windows requirements
>- Windows Server requirements
There are 7 major categories to consider when planning a Windows Hello for Business deployment:
:ballot_box_with_check: Deployment options
:ballot_box_with_check: Deploment models
:ballot_box_with_check: Trust types
:ballot_box_with_check: Authentication
:ballot_box_with_check: Device registration
:ballot_box_with_check: Key registration
:ballot_box_with_check: Directory synchronization
:ballot_box_with_check: Multifactor authentication
:ballot_box_with_check: Device configuration
:ballot_box_with_check: Public Key Infrastructure
:ballot_box_with_check: Licensing for cloud services
:ballot_box_with_check: Windows requirements
:ballot_box_with_check: Windows Server requirements
## Deployment Options
@ -208,7 +207,7 @@ While cloud Kerberos trust is the only hybrid deployment option that doesn't req
| :black_square_button:|Hybrid| :black_square_button: **Cloud Kerberos trust**: not required <br> :black_square_button: **Key trust**: required <br> :black_square_button: **Certificate trust**: required|
| :black_square_button:|On-premises | required |
### Licensing requirements for cloud services
### Licensing for cloud services
Here are some considerations regarding licensing requirements for cloud services: