mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 09:17:25 +00:00
typos (git issues)
This commit is contained in:
parent
1a960fb91a
commit
99e85e4044
@ -75,7 +75,7 @@ If you do not have an existing public key infrastructure, please review [Certifi
|
|||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> For Azure AD joined device to authenticate to and use on-premises resources, ensure you:
|
> For Azure AD joined device to authenticate to and use on-premises resources, ensure you:
|
||||||
> * Install the root certificate authority certificate for your organization in the user's trusted root certifcate store.
|
> * Install the root certificate authority certificate for your organization in the user's trusted root certificate store.
|
||||||
> * Publish your certificate revocation list to a location that is available to Azure AD joined devices, such as a web-based url.
|
> * Publish your certificate revocation list to a location that is available to Azure AD joined devices, such as a web-based url.
|
||||||
|
|
||||||
### Section Review ###
|
### Section Review ###
|
||||||
@ -84,7 +84,7 @@ If you do not have an existing public key infrastructure, please review [Certifi
|
|||||||
> * Minimum Windows Server 2012 Certificate Authority.
|
> * Minimum Windows Server 2012 Certificate Authority.
|
||||||
> * Enterprise Certificate Authority.
|
> * Enterprise Certificate Authority.
|
||||||
> * Functioning public key infrastructure.
|
> * Functioning public key infrastructure.
|
||||||
> * Root certifcate authority certificate (Azure AD Joined devices).
|
> * Root certificate authority certificate (Azure AD Joined devices).
|
||||||
> * Highly available certificate revocation list (Azure AD Joined devices).
|
> * Highly available certificate revocation list (Azure AD Joined devices).
|
||||||
|
|
||||||
## Azure Active Directory ##
|
## Azure Active Directory ##
|
||||||
@ -131,7 +131,7 @@ Alternatively, you can configure Windows Server 2016 Active Directory Federation
|
|||||||
> * Review the overview and uses of Azure Multifactor Authentication.
|
> * Review the overview and uses of Azure Multifactor Authentication.
|
||||||
> * Review your Azure Active Directory subscription for Azure Multifactor Authentication.
|
> * Review your Azure Active Directory subscription for Azure Multifactor Authentication.
|
||||||
> * Create an Azure Multifactor Authentication Provider, if necessary.
|
> * Create an Azure Multifactor Authentication Provider, if necessary.
|
||||||
> * Configure Azure Multufactor Authentiation features and settings.
|
> * Configure Azure Multifactor Authentiation features and settings.
|
||||||
> * Understand the different User States and their effect on Azure Multifactor Authentication.
|
> * Understand the different User States and their effect on Azure Multifactor Authentication.
|
||||||
> * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server Active Directory Federation Services, if necessary.
|
> * Consider using Azure Multifactor Authentication or a third-party multifactor authentication provider with Windows Server Active Directory Federation Services, if necessary.
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ ms.date: 08/19/2018
|
|||||||
- Key trust
|
- Key trust
|
||||||
|
|
||||||
|
|
||||||
## Directory Syncrhonization
|
## Directory Synchronization
|
||||||
|
|
||||||
In hybrid deployments, users register the public portion of their Windows Hello for Business credential with Azure. Azure AD Connect synchronizes the Windows Hello for Business public key to Active Directory.
|
In hybrid deployments, users register the public portion of their Windows Hello for Business credential with Azure. Azure AD Connect synchronizes the Windows Hello for Business public key to Active Directory.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user