mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #1747 from MicrosoftDocs/seo-update-duplicate-meta-descriptions
Seo update duplicate meta descriptions - part 2
This commit is contained in:
Gary Moore
GitHub
commit
17a1707dfc
@ -2,7 +2,7 @@
|
||||
title: Windows Autopilot device guidelines
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
description: Learn all about hardware, firmware, and software best practices for Windows Autopilot deployment.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot for existing devices
|
||||
description: Windows Autopilot deployment
|
||||
description: Modern desktop deployment with Windows Autopilot enables you to easily deploy the latest version of Windows 10 to your existing devices.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot deployment
|
||||
description: Windows Autopilot deployment
|
||||
description: Discover resources for Windows Autopilot deployment with this guide.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Autopilot known issues
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
description: Inform yourself about known issues that may occur during Windows Autopilot deployment.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,48 +1,49 @@
|
||||
---
|
||||
title: Configure Autopilot profiles
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Configure Autopilot profiles
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
For each device that has been defined to the Windows Autopilot deployment service, a profile of settings needs to be applied that specifies the exact behavior of that device when it is deployed. For detailed procedures on how to configure profile settings and register devices, see [Registering devices](add-devices.md#registering-devices).
|
||||
|
||||
## Profile settings
|
||||
|
||||
The following profile settings are available:
|
||||
|
||||
- **Skip Cortana, OneDrive and OEM registration setup pages**. All devices registered with Autopilot will automatically skip these pages during the out-of-box experience (OOBE) process.
|
||||
|
||||
- **Automatically setup for work or school**. All devices registered with Autopilot will automatically be considered work or school devices, so this question will not be asked during the OOBE process.
|
||||
|
||||
- **Sign in experience with company branding**. Instead of presenting a generic Azure Active Directory sign-in page, all devices registered with Autopilot will automatically present a customized sign-in page with the organization’s name, logon, and additional help text, as configured in Azure Active Directory. See [Add company branding to your directory](https://docs.microsoft.com/azure/active-directory/customize-branding#add-company-branding-to-your-directory) to customize these settings.
|
||||
|
||||
- **Skip privacy settings**. This optional Autopilot profile setting enables organizations to not ask about privacy settings during the OOBE process. This is typically desirable so that the organization can configure these settings via Intune or other management tool.
|
||||
|
||||
- **Disable local admin account creation on the device**. Organizations can decide whether the user setting up the device should have administrator access once the process is complete.
|
||||
|
||||
- **Skip End User License Agreement (EULA)**. Starting in Windows 10 version 1709, organizations can decide to skip the EULA page presented during the OOBE process. This means that organizations accept the EULA terms on behalf of their users.
|
||||
|
||||
- **Disable Windows consumer features**. Starting in Windows 10 version 1803, organizations can disable Windows consumer features so that the device does not automatically install any additional Microsoft Store apps when the user first signs into the device. See the [MDM documentation](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience#experience-allowwindowsconsumerfeatures) for more details.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Profile download](troubleshooting.md#profile-download)
|
||||
[Registering devices](add-devices.md)
|
||||
---
|
||||
title: Configure Autopilot profiles
|
||||
description: Learn how to configure device profiles while performing a Windows Autopilot deployment.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Configure Autopilot profiles
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
For each device that has been defined to the Windows Autopilot deployment service, a profile of settings needs to be applied that specifies the exact behavior of that device when it is deployed. For detailed procedures on how to configure profile settings and register devices, see [Registering devices](add-devices.md#registering-devices).
|
||||
|
||||
## Profile settings
|
||||
|
||||
The following profile settings are available:
|
||||
|
||||
- **Skip Cortana, OneDrive and OEM registration setup pages**. All devices registered with Autopilot will automatically skip these pages during the out-of-box experience (OOBE) process.
|
||||
|
||||
- **Automatically setup for work or school**. All devices registered with Autopilot will automatically be considered work or school devices, so this question will not be asked during the OOBE process.
|
||||
|
||||
- **Sign in experience with company branding**. Instead of presenting a generic Azure Active Directory sign-in page, all devices registered with Autopilot will automatically present a customized sign-in page with the organization’s name, logon, and additional help text, as configured in Azure Active Directory. See [Add company branding to your directory](https://docs.microsoft.com/azure/active-directory/customize-branding#add-company-branding-to-your-directory) to customize these settings.
|
||||
|
||||
- **Skip privacy settings**. This optional Autopilot profile setting enables organizations to not ask about privacy settings during the OOBE process. This is typically desirable so that the organization can configure these settings via Intune or other management tool.
|
||||
|
||||
- **Disable local admin account creation on the device**. Organizations can decide whether the user setting up the device should have administrator access once the process is complete.
|
||||
|
||||
- **Skip End User License Agreement (EULA)**. Starting in Windows 10 version 1709, organizations can decide to skip the EULA page presented during the OOBE process. This means that organizations accept the EULA terms on behalf of their users.
|
||||
|
||||
- **Disable Windows consumer features**. Starting in Windows 10 version 1803, organizations can disable Windows consumer features so that the device does not automatically install any additional Microsoft Store apps when the user first signs into the device. See the [MDM documentation](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience#experience-allowwindowsconsumerfeatures) for more details.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Profile download](troubleshooting.md#profile-download)
|
||||
[Registering devices](add-devices.md)
|
||||
|
||||
@ -1,81 +1,82 @@
|
||||
---
|
||||
title: Windows Autopilot customer consent
|
||||
description: Windows Autopilot deployment
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot customer consent
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
This article describes how a cloud service provider (CSP) partner (direct bill, indirect provider, or indirect reseller) or an OEM can get customer authorization to register Windows Autopilot devices on the customer’s behalf.
|
||||
|
||||
## CSP authorization
|
||||
|
||||
CSP partners can get customer authorization to register Windows Autopilot devices on the customer’s behalf per the following restrictions:
|
||||
|
||||
<table>
|
||||
<tr><td>Direct CSP<td>Gets direct authorization from the customer to register devices.
|
||||
<tr><td>Indirect CSP Provider<td>Gets implicit permission to register devices through the relationship their CSP Reseller partner has with the customer. Indirect CSP Providers register devices through Microsoft Partner Center.
|
||||
<tr><td>Indirect CSP Reseller<td>Gets direct authorization from the customer to register devices. At the same time, their indirect CSP Provider partner also gets authorization, which mean that either the Indirect Provider or the Indirect Reseller can register devices for the customer. However, the Indirect CSP Reseller must register devices through the MPC UI (manually uploading CSV file), whereas the Indirect CSP Provider has the option to register devices using the MPC APIs.
|
||||
</table>
|
||||
|
||||
### Steps
|
||||
|
||||
For a CSP to register Windows Autopilot devices on behalf of a customer, the customer must first grant that CSP partner permission using the following process:
|
||||
|
||||
1. CSP sends link to customer requesting authorization/consent to register/manage devices on their behalf. To do so:
|
||||
- CSP logs into Microsoft Partner Center
|
||||
- Click **Dashboard** on the top menu
|
||||
- Click **Customer** on the side menu
|
||||
- Click the **Request a reseller relationship** link:
|
||||
|
||||
- Select the checkbox indicating whether or not you want delegated admin rights:
|
||||
|
||||
- NOTE: Depending on your partner, they might request Delegated Admin Permissions (DAP) when requesting this consent. You should ask them to use the newer DAP-free process (shown in this document) if possible. If not, you can easily remove their DAP status either from Microsoft Store for Business or the Office 365 admin portal: https://docs.microsoft.com/partner-center/customers_revoke_admin_privileges
|
||||
- Send the template above to the customer via email.
|
||||
2. Customer with global administrator privileges in Microsoft Store for Business (MSfB) clicks the link in the body of the email once they receive it from the CSP, which takes them directly to the following MSfB page:
|
||||
|
||||
|
||||
|
||||
NOTE: A user without global admin privileges who clicks the link will see a message similar to the following:
|
||||
|
||||
|
||||
|
||||
3. Customer selects the **Yes** checkbox, followed by the **Accept** button. Authorization happens instantaneously.
|
||||
4. The CSP will know that this consent/authorization request has been completed because the customer will show up in the CSP’s MPC account under their **customers** list, for example:
|
||||
|
||||
|
||||
|
||||
## OEM authorization
|
||||
|
||||
Each OEM has a unique link to provide to their respective customers, which the OEM can request from Microsoft via msoemops@microsoft.com.
|
||||
|
||||
1. OEM emails link to their customer.
|
||||
2. Customer with global administrator privileges in Microsoft Store for Business (MSfB) clicks the link once they receive it from the OEM, which takes them directly to the following MSfB page:
|
||||
|
||||
|
||||
|
||||
NOTE: A user without global admin privileges who clicks the link will see a message similar to the following:
|
||||
|
||||
|
||||
3. Customer selects the **Yes** checkbox, followed by the **Accept** button, and they’re done. Authorization happens instantaneously.
|
||||
|
||||
4. The OEM can use the Validate Device Submission Data API to verify the consent has completed. This API is discussed in the latest version of the API Whitepaper, p. 14ff [https://devicepartner.microsoft.com/assets/detail/windows-autopilot-integration-with-oem-api-design-whitepaper-docx](https://devicepartner.microsoft.com/assets/detail/windows-autopilot-integration-with-oem-api-design-whitepaper-docx). **Note**: this link is only accessible by Microsoft Device Partners. As discussed in this whitepaper, it’s a best practice recommendation for OEM partners to run the API check to confirm they’ve received customer consent before attempting to register devices, thus avoiding errors in the registration process.
|
||||
|
||||
## Summary
|
||||
|
||||
At this stage of the process, Microsoft is no longer involved; the consent exchange happens directly between the OEM and the customer. And, it all happens instantaneously - as quickly as buttons are clicked.
|
||||
|
||||
---
|
||||
title: Windows Autopilot customer consent
|
||||
description: Learn how a cloud service provider (CSP) partner or an OEM can get customer authorization to register Windows Autopilot devices on the customer’s behalf.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
# Windows Autopilot customer consent
|
||||
|
||||
**Applies to: Windows 10**
|
||||
|
||||
This article describes how a cloud service provider (CSP) partner (direct bill, indirect provider, or indirect reseller) or an OEM can get customer authorization to register Windows Autopilot devices on the customer’s behalf.
|
||||
|
||||
## CSP authorization
|
||||
|
||||
CSP partners can get customer authorization to register Windows Autopilot devices on the customer’s behalf per the following restrictions:
|
||||
|
||||
<table>
|
||||
<tr><td>Direct CSP<td>Gets direct authorization from the customer to register devices.
|
||||
<tr><td>Indirect CSP Provider<td>Gets implicit permission to register devices through the relationship their CSP Reseller partner has with the customer. Indirect CSP Providers register devices through Microsoft Partner Center.
|
||||
<tr><td>Indirect CSP Reseller<td>Gets direct authorization from the customer to register devices. At the same time, their indirect CSP Provider partner also gets authorization, which mean that either the Indirect Provider or the Indirect Reseller can register devices for the customer. However, the Indirect CSP Reseller must register devices through the MPC UI (manually uploading CSV file), whereas the Indirect CSP Provider has the option to register devices using the MPC APIs.
|
||||
</table>
|
||||
|
||||
### Steps
|
||||
|
||||
For a CSP to register Windows Autopilot devices on behalf of a customer, the customer must first grant that CSP partner permission using the following process:
|
||||
|
||||
1. CSP sends link to customer requesting authorization/consent to register/manage devices on their behalf. To do so:
|
||||
- CSP logs into Microsoft Partner Center
|
||||
- Click **Dashboard** on the top menu
|
||||
- Click **Customer** on the side menu
|
||||
- Click the **Request a reseller relationship** link:
|
||||
|
||||
- Select the checkbox indicating whether or not you want delegated admin rights:
|
||||
|
||||
- NOTE: Depending on your partner, they might request Delegated Admin Permissions (DAP) when requesting this consent. You should ask them to use the newer DAP-free process (shown in this document) if possible. If not, you can easily remove their DAP status either from Microsoft Store for Business or the Office 365 admin portal: https://docs.microsoft.com/partner-center/customers_revoke_admin_privileges
|
||||
- Send the template above to the customer via email.
|
||||
2. Customer with global administrator privileges in Microsoft Store for Business (MSfB) clicks the link in the body of the email once they receive it from the CSP, which takes them directly to the following MSfB page:
|
||||
|
||||
|
||||
|
||||
NOTE: A user without global admin privileges who clicks the link will see a message similar to the following:
|
||||
|
||||
|
||||
|
||||
3. Customer selects the **Yes** checkbox, followed by the **Accept** button. Authorization happens instantaneously.
|
||||
4. The CSP will know that this consent/authorization request has been completed because the customer will show up in the CSP’s MPC account under their **customers** list, for example:
|
||||
|
||||
|
||||
|
||||
## OEM authorization
|
||||
|
||||
Each OEM has a unique link to provide to their respective customers, which the OEM can request from Microsoft via msoemops@microsoft.com.
|
||||
|
||||
1. OEM emails link to their customer.
|
||||
2. Customer with global administrator privileges in Microsoft Store for Business (MSfB) clicks the link once they receive it from the OEM, which takes them directly to the following MSfB page:
|
||||
|
||||
|
||||
|
||||
NOTE: A user without global admin privileges who clicks the link will see a message similar to the following:
|
||||
|
||||
|
||||
3. Customer selects the **Yes** checkbox, followed by the **Accept** button, and they’re done. Authorization happens instantaneously.
|
||||
|
||||
4. The OEM can use the Validate Device Submission Data API to verify the consent has completed. This API is discussed in the latest version of the API Whitepaper, p. 14ff [https://devicepartner.microsoft.com/assets/detail/windows-autopilot-integration-with-oem-api-design-whitepaper-docx](https://devicepartner.microsoft.com/assets/detail/windows-autopilot-integration-with-oem-api-design-whitepaper-docx). **Note**: this link is only accessible by Microsoft Device Partners. As discussed in this whitepaper, it’s a best practice recommendation for OEM partners to run the API check to confirm they’ve received customer consent before attempting to register devices, thus avoiding errors in the registration process.
|
||||
|
||||
## Summary
|
||||
|
||||
At this stage of the process, Microsoft is no longer involved; the consent exchange happens directly between the OEM and the customer. And, it all happens instantaneously - as quickly as buttons are clicked.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot Self-Deploying mode
|
||||
description: Windows Autopilot deployment
|
||||
description: Self-deploying mode allows a device to be deployed with little to no user interaction. This mode mode is designed to deploy Windows 10 as a kiosk, digital signage device, or a shared device.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting Windows Autopilot
|
||||
description: Windows Autopilot deployment
|
||||
description: Learn how to handle issues as they arise during the Windows Autopilot deployment process.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot User-Driven Mode
|
||||
description: Windows Autopilot deployment
|
||||
description: Windows Autopilot user-driven mode allows devices to be deployed to a ready-to-use state without requiring help from IT personnel.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Autopilot requirements
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
description: Inform yourself about software, networking, licensing, and configuration requirements for Windows Autopilot deployment.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot Reset
|
||||
description: Windows Autopilot deployment
|
||||
description: Windows Autopilot Reset takes the device back to a business-ready state, allowing the next user to sign in and get productive quickly and easily.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
@ -87,7 +87,7 @@ Performing a local Windows Autopilot Reset is a two-step process: trigger it and
|
||||
|
||||
1. From the Windows device lock screen, enter the keystroke: **CTRL +  + R**.
|
||||
|
||||
|
||||
|
||||
|
||||
This will open up a custom login screen for the local Autopilot Reset. The screen serves two purposes:
|
||||
1. Confirm/verify that the end user has the right to trigger Local Autopilot Reset
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot scenarios and capabilities
|
||||
description: Windows Autopilot deployment
|
||||
description: Follow along with several typical Windows Autopilot deployment scenarios, such as re-deploying a device in a business-ready state.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Autopilot what's new
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
description: Read news and resources about the latest updates and past versions of Windows Autopilot.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Overview of Windows Autopilot
|
||||
description: Windows Autopilot deployment
|
||||
description: Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.reviewer: mniehaus
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Validate and Deploy MFA for Windows Hello for Business with certificate trust
|
||||
description: How to Validate and Deploy Multifactor Authentication (MFA) Services for Windows Hello for Business
|
||||
description: How to Validate and Deploy Multifactor Authentication (MFA) Services for Windows Hello for Business with certificate trust
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works - Authentication
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Learn about the authentication flow for Windows Hello for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works - Provisioning
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Explore the provisioning flows for Windows Hello for Business, from within a variety of environments.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
@ -58,7 +58,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Hybrid Azure AD joined provisioning in a Key Trust deployment in a Managed environment
|
||||
|
||||
|
||||
|
||||
|
||||
| Phase | Description |
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works - Technical Deep Dive
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Deeply explore how Windows Hello for Business works, and how it can help your users authenticate to services.
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, hybrid, key-trust, works
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works - Technology and Terms
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Explore technology and terms associated with Windows Hello for Business. Learn how Windows Hello for Business works.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Learn how Windows Hello for Business works, and how it can help your users authenticate to services.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Hello for Business works (Windows 10)
|
||||
description: Explains registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
description: Learn about registration, authentication, key material, and infrastructure for Windows Hello for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user