- Removed Windows 10 mobile from Applies to across all pages

This commit is contained in:
Mike Stephens 2018-05-11 07:59:13 -07:00
parent 1a8e1da573
commit f84d8e60a5
14 changed files with 26 additions and 7 deletions

View File

@ -13,6 +13,9 @@ ms.date: 03/20/2018
---
# Multifactor Unlock
**Applies to:**
- Windows 10
**Requirements:**
* Windows Hello for Business deployment (Hybrid or On-premises)
* Azure AD joined device (Cloud and Hybrid deployments)

View File

@ -15,7 +15,6 @@ ms.date: 07/27/2017
**Applies to**
- Windows 10
- Windows 10 Mobile
When you set up Windows Hello, the PIN or biometric gesture that you use is specific to that device. You can set up Hello for the same account on multiple devices. If the PIN or biometric is configured as part of Windows Hello for Business, changing the account password will not impact sign-in or unlock with these gestures since it uses a key or certificate. However, if Windows Hello for Business is not deployed and the password for that account changes, you must provide the new password on each device to continue to use Hello.

View File

@ -14,8 +14,8 @@ ms.date: 07/27/2017
---
# Windows Hello biometrics in the enterprise
**Applies to:**
**Applies to:**
- Windows 10
Windows Hello is the biometric authentication feature that helps strengthen authentication and helps to guard against potential spoofing through fingerprint matching and facial recognition.

View File

@ -15,7 +15,7 @@ ms.date: 11/08/2017
**Applies to**
- Windows 10
- Windows 10 Mobile
> This guide only applies to Windows 10, version 1703 or higher.

View File

@ -14,6 +14,9 @@ ms.date: 3/5/2018
---
# Windows Hello for Business Features
**Applies to:**
- Windows 10
Consider these additional features you can use after your organization deploys Windows Hello for Business.
* [Conditional access](#conditional-access)

View File

@ -12,6 +12,9 @@ ms.date: 05/05/2018
---
# Windows Hello for Business and Authentication
**Applies to:**
- Windows 10
Windows Hello for Business authentication is passwordless, two-factor authentication. Authenticating with Windows Hello for Business provides a convenient sign-in experience that authenticates the user to both Azure Active Directory and Active Directory resources.<br>
Azure Active Directory joined devices authenticate to Azure during sign-in and can optional authenticate to Active Directory. Hybrid Azure Active Directory joined devices authenticate to Active Directory during sign-in, and authenticate to Azure Active Directory in the background.<br>

View File

@ -11,6 +11,10 @@ localizationpriority: high
ms.date: 05/05/2018
---
# Windows Hello for Business and Device Registration
**Applies to:**
- Windows 10
Device Registration is a prerequisite to Windows Hello for Business provisioning. Device registration occurs regardless of a cloud, hybrid, or on-premises deployments. For cloud and hybrid deployments, devices register with Azure Active Directory. For on-premises deployments, devices registered with the enterprise device registration service hosted by Active Directory Federation Services (AD FS).
[Azure AD joined in Managed environments](#Azure-AD-joined-in-Managed-environments)<br>

View File

@ -11,6 +11,10 @@ localizationpriority: high
ms.date: 05/05/2018
---
# Windows Hello for Business Provisioning
**Applies to:**
- Windows 10
Windows Hello for Business provisioning enables a user to enroll a new, strong, two-factor credential that they can use for passwordless authentication. Provisioning experience vary based on:
- How the device is joined to Azure Active Directory
- The Windows Hello for Business deployment type

View File

@ -12,6 +12,10 @@ localizationpriority: high
ms.date: 05/05/2018
---
# Technical Deep Dive
**Applies to:**
- Windows 10
Windows Hello for Business authentication works through collection of components and infrastructure working together. You can group the infrastructure and components in three categories:
- [Registration](#Registration)
- [Provisioning](#Provisioning)

View File

@ -12,6 +12,9 @@ ms.date: 05/05/2018
---
# Technology and Terms
**Applies to:**
- Windows 10
- [Attestation Identity Keys](#Attestation-Identity-Keys)
- [Azure AD Joined](#Azure-AD-Joined)
- [Azure AD Registered](#Azure-AD-Registered)

View File

@ -17,7 +17,6 @@ ms.date: 10/18/2017
**Applies to**
- Windows 10
- Windows 10 Mobile
You can create a Group Policy or mobile device management (MDM) policy that will implement Windows Hello on devices running Windows 10.

View File

@ -16,7 +16,6 @@ ms.date: 05/05/2018
**Applies to**
- Windows 10
In Windows 10, Windows Hello for Business replaces passwords with strong two-factor authentication on PCs and mobile devices. This authentication consists of a new type of user credential that is tied to a device and uses a biometric or PIN.
>[!NOTE]

View File

@ -17,7 +17,6 @@ ms.date: 07/27/2017
**Applies to**
- Windows 10
- Windows 10 Mobile
When you set a policy to require Windows Hello for Business in the workplace, you will want to prepare people in your organization by explaining how to use Hello.

View File

@ -17,7 +17,6 @@ ms.date: 10/23/2017
**Applies to**
- Windows 10
- Windows 10 Mobile
Windows Hello in Windows 10 enables users to sign in to their device using a PIN. How is a PIN different from (and better than) a password?
On the surface, a PIN looks much like a password. A PIN can be a set of numbers, but enterprise policy might allow complex PINs that include special characters and letters, both upper-case and lower-case. Something like **t758A!** could be an account password or a complex Hello PIN. It isn't the structure of a PIN (length, complexity) that makes it better than a password, it's how it works.