mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-17 07:47:22 +00:00
Merge pull request #9681 from paolomatarazzo/pm-20230312-freshness
[Security] freshness review
This commit is contained in:
Jeff Borsecnik
GitHub
commit
f4cd3a3885
@ -2,7 +2,7 @@
|
||||
title: Enterprise certificate pinning
|
||||
description: Enterprise certificate pinning is a Windows feature for remembering, or pinning, a root issuing certificate authority, or end-entity certificate to a domain name.
|
||||
ms.topic: concept-article
|
||||
ms.date: 05/24/2023
|
||||
ms.date: 03/12/2024
|
||||
---
|
||||
|
||||
# Enterprise certificate pinning overview
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Windows Hello for Business cloud-only deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in a cloud-only deployment scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.topic: how-to
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Cloud-only deployment guide
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Active Directory Federation Services in a hybrid certificate trust model
|
||||
description: Learn how to configure Active Directory Federation Services (AD FS) to support the Windows Hello for Business hybrid certificate trust model.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure and enroll in Windows Hello for Business in hybrid certificate trust model
|
||||
description: Learn how to configure devices and enroll them in Windows Hello for Business in a hybrid certificate trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure and validate the PKI in an hybrid certificate trust model
|
||||
description: Configure and validate the Public Key Infrastructure when deploying Windows Hello for Business in a hybrid certificate trust model.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business hybrid certificate trust deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in a hybrid certificate trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business cloud Kerberos trust deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in a cloud Kerberos trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure and enroll in Windows Hello for Business in a hybrid key trust model
|
||||
description: Learn how to configure devices and enroll them in Windows Hello for Business in a hybrid key trust scenario.
|
||||
ms.date: 12/29/2023
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business hybrid key trust deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in a hybrid key trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Plan a Windows Hello for Business Deployment
|
||||
description: Learn about the role of each component within Windows Hello for Business and how certain deployment decisions affect other aspects of your infrastructure.
|
||||
ms.date: 01/02/2024
|
||||
ms.topic: overview
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: concept-article
|
||||
---
|
||||
|
||||
# Plan a Windows Hello for Business deployment
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Active Directory Federation Services in an on-premises certificate trust model
|
||||
description: Learn how to configure Active Directory Federation Services (AD FS) to support the Windows Hello for Business on-premises certificate trust model.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
title: Configure Windows Hello for Business Policy settings in an on-premises certificate trust
|
||||
description: Configure Windows Hello for Business Policy settings for Windows Hello for Business in an on-premises certificate trust scenario
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business on-premises certificate trust deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in an on-premises, certificate trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Active Directory Federation Services in an on-premises key trust model
|
||||
description: Learn how to configure Active Directory Federation Services (AD FS) to support the Windows Hello for Business key trust model.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
title: Configure Windows Hello for Business Policy settings in an on-premises key trust
|
||||
description: Configure Windows Hello for Business Policy settings for Windows Hello for Business in an on-premises key trust scenario
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business on-premises key trust deployment guide
|
||||
description: Learn how to deploy Windows Hello for Business in an on-premises, key trust scenario.
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Prepare users to provision and use Windows Hello for Business
|
||||
description: Learn how to prepare users to enroll and to use Windows Hello for Business.
|
||||
ms.date: 01/02/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: end-user-help
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Hello for Business known deployment issues
|
||||
description: This article is a troubleshooting guide for known Windows Hello for Business deployment issues.
|
||||
ms.date: 06/02/2023
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: troubleshooting
|
||||
---
|
||||
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
title: Windows Hello errors during PIN creation
|
||||
description: When you set up Windows Hello, you may get an error during the Create a work PIN step.
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 01/26/2024
|
||||
ms.date: 03/12/2024
|
||||
---
|
||||
|
||||
# Windows Hello errors during PIN creation
|
||||
|
||||
When you set up Windows Hello in Windows client, you may get an error during the **Create a PIN** step. This topic lists some of the error codes with recommendations for mitigating the problem. If you get an error code that is not listed here, contact Microsoft Support.
|
||||
When you set up Windows Hello in Windows client, you may get an error during the **Create a PIN** step. This article lists some of the error codes with recommendations for mitigating the problem. If you get an error code that isn't listed here, contact Microsoft Support.
|
||||
|
||||
## Where is the error code?
|
||||
|
||||
@ -24,41 +24,41 @@ When a user encounters an error when creating the work PIN, advise the user to t
|
||||
3. Reboot the device and then try to create the PIN again.
|
||||
4. Unjoin the device from Microsoft Entra ID, rejoin, and then try to create the PIN again. To unjoin a device, go to **Settings > System > About > Disconnect from organization**.
|
||||
|
||||
If the error occurs again, check the error code against the following table to see if there is another mitigation for that error. When no mitigation is listed in the table, contact Microsoft Support for assistance.
|
||||
If the error occurs again, check the error code against the following table to see if there's another mitigation for that error. When no mitigation is listed in the table, contact Microsoft Support for assistance.
|
||||
|
||||
| Hex | Cause | Mitigation |
|
||||
| :--------- | :----------------------------------------------------------------- | :------------------------------------------ |
|
||||
| 0x80090005 | NTE_BAD_DATA | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| 0x8009000F | The container or key already exists. | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| 0x80090011 | The container or key was not found. | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| 0x80090029 | TPM is not set up. | Sign on with an administrator account. Select **Start**, type `tpm.msc`, and select **tpm.msc Microsoft Common Console Document**. In the **Actions** pane, select **Prepare the TPM**. |
|
||||
| 0x80090011 | The container or key wasn't found. | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| 0x80090029 | TPM isn't set up. | Sign on with an administrator account. Select **Start**, type `tpm.msc`, and select **tpm.msc Microsoft Common Console Document**. In the **Actions** pane, select **Prepare the TPM**. |
|
||||
| 0x8009002A | NTE_NO_MEMORY | Close programs which are taking up memory and try again. |
|
||||
| 0x80090031 | NTE_AUTHENTICATION_IGNORED | Reboot the device. If the error occurs again after rebooting, [reset the TPM](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd851452(v=ws.11)) or run [Clear-TPM](/powershell/module/trustedplatformmodule/clear-tpm). |
|
||||
| 0x80090035 | Policy requires TPM and the device does not have TPM. | Change the Windows Hello for Business policy to not require a TPM. |
|
||||
| 0x80090036 | User canceled an interactive dialog. | User will be asked to try again. |
|
||||
| 0x801C0003 | User is not authorized to enroll. | Check if the user has permission to perform the operation. |
|
||||
| 0x80090035 | Policy requires TPM and the device doesn't have TPM. | Change the Windows Hello for Business policy to not require a TPM. |
|
||||
| 0x80090036 | User canceled an interactive dialog. | User is asked to try again. |
|
||||
| 0x801C0003 | User isn't authorized to enroll. | Check if the user has permission to perform the operation. |
|
||||
| 0x801C000E | Registration quota reached. | Unjoin some other device that is currently joined using the same account or [increase the maximum number of devices per user](/azure/active-directory/devices/device-management-azure-portal). |
|
||||
| 0x801C000F | Operation successful, but the device requires a reboot. | Reboot the device. |
|
||||
| 0x801C0010 | The AIK certificate is not valid or trusted. | Sign out and then sign in again. |
|
||||
| 0x801C0010 | The AIK certificate isn't valid or trusted. | Sign out and then sign in again. |
|
||||
| 0x801C0011 | The attestation statement of the transport key is invalid. | Sign out and then sign in again. |
|
||||
| 0x801C0012 | Discovery request is not in a valid format. | Sign out and then sign in again. |
|
||||
| 0x801C0012 | Discovery request isn't in a valid format. | Sign out and then sign in again. |
|
||||
| 0x801C0015 | The device is required to be joined to an Active Directory domain. | Join the device to an Active Directory domain. |
|
||||
| 0x801C0016 | The federation provider configuration is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the file is not empty. |
|
||||
| 0x801C0017 | The federation provider domain is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the FPDOMAINNAME element is not empty. |
|
||||
| 0x801C0016 | The federation provider configuration is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the file isn't empty. |
|
||||
| 0x801C0017 | The federation provider domain is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the FPDOMAINNAME element isn't empty. |
|
||||
| 0x801C0018 | The federation provider client configuration URL is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the CLIENTCONFIG element contains a valid URL. |
|
||||
| 0x801C03E9 | Server response message is invalid | Sign out and then sign in again. |
|
||||
| 0x801C03EA | Server failed to authorize user or device. | Check if the token is valid and user has permission to register Windows Hello for Business keys. |
|
||||
| 0x801C03EB | Server response http status is not valid | Sign out and then sign in again. |
|
||||
| 0x801C03EB | Server response http status isn't valid | Sign out and then sign in again. |
|
||||
| 0x801C03EC | Unhandled exception from server. | sign out and then sign in again. |
|
||||
| 0x801C03ED | Multi-factor authentication is required for a 'ProvisionKey' operation, but was not performed. <br><br> -or- <br><br> Token was not found in the Authorization header. <br><br> -or- <br><br> Failed to read one or more objects. <br><br> -or- <br><br> The request sent to the server was invalid. <br><br> -or- <br><br> User does not have permissions to join to Microsoft Entra ID. | Sign out and then sign in again. If that doesn't resolve the issue, unjoin the device from Azure AD and rejoin. <br> Allow user(s) to join to Microsoft Entra ID under Microsoft Entra Device settings.
|
||||
| 0x801C03ED | Multifactor authentication is required for a 'ProvisionKey' operation, but wasn't performed. <br><br> -or- <br><br> Token wasn't found in the Authorization header. <br><br> -or- <br><br> Failed to read one or more objects. <br><br> -or- <br><br> The request sent to the server was invalid. <br><br> -or- <br><br> User doesn't have permissions to join to Microsoft Entra ID. | Sign out and then sign in again. If that doesn't resolve the issue, unjoin the device from Azure AD and rejoin. <br> Allow user(s) to join to Microsoft Entra ID under Microsoft Entra Device settings.
|
||||
| 0x801C03EE | Attestation failed. | Sign out and then sign in again. |
|
||||
| 0x801C03EF | The AIK certificate is no longer valid. | Sign out and then sign in again. |
|
||||
| 0x801C03F2 | Windows Hello key registration failed. | ERROR_BAD_DIRECTORY_REQUEST. Another object with the same value for property proxyAddresses already exists. To resolve the issue, refer to [Duplicate Attributes Prevent Dirsync](/office365/troubleshoot/administration/duplicate-attributes-prevent-dirsync). Also, if no sync conflict exists, please verify that the "Mail/Email address" in Microsoft Entra ID and the Primary SMTP address are the same in the proxy address.
|
||||
| 0x801C044D | Authorization token does not contain device ID. | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| 0x801C044D | Authorization token doesn't contain device ID. | Unjoin the device from Microsoft Entra ID and rejoin. |
|
||||
| | Unable to obtain user token. | Sign out and then sign in again. Check network and credentials. |
|
||||
| 0x801C044E | Failed to receive user credentials input. | Sign out and then sign in again. |
|
||||
| 0x801C0451 | User token switch account. | Delete the Web Account Manager token broker files located in `%LOCALAPPDATA%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\TokenBroker\Accounts\*.*\` and reboot.|
|
||||
| 0xC00000BB | Your PIN or this option is temporarily unavailable. | The destination domain controller doesn't support the login method. Most often the KDC service doesn't have the proper certificate to support the login. Another common cause can be the client cannot verify the KDC certificate CRL. Use a different login method.|
|
||||
| 0xC00000BB | Your PIN or this option is temporarily unavailable. | The destination domain controller doesn't support the sign in method. Most often the KDC service doesn't have the proper certificate to support the sign in. Another common cause can be the client can't verify the KDC certificate CRL. Use a different login method.|
|
||||
|
||||
## Errors with unknown mitigation
|
||||
|
||||
@ -73,18 +73,18 @@ For errors listed in this table, contact Microsoft Support for assistance.
|
||||
| 0x80090020 | NTE_FAIL |
|
||||
| 0x80090027 | Caller provided a wrong parameter. If third-party code receives this error, they must change their code. |
|
||||
| 0x8009002D | NTE_INTERNAL_ERROR |
|
||||
| 0x801C0001 | ADRS server response is not in a valid format. |
|
||||
| 0x801C0001 | ADRS server response isn't in a valid format. |
|
||||
| 0x801C0002 | Server failed to authenticate the user. |
|
||||
| 0x801C0006 | Unhandled exception from server. |
|
||||
| 0x801C000B | Redirection is needed and redirected location is not a well known server. |
|
||||
| 0x801C000B | Redirection is needed and redirected location isn't a well known server. |
|
||||
| 0x801C000C | Discovery failed. |
|
||||
| 0x801C0013 | Tenant ID is not found in the token. |
|
||||
| 0x801C0014 | User SID is not found in the token. |
|
||||
| 0x801C0013 | Tenant ID isn't found in the token. |
|
||||
| 0x801C0014 | User SID isn't found in the token. |
|
||||
| 0x801C0019 | The federation provider client configuration is empty |
|
||||
| 0x801C001A | The DRS endpoint in the federation provider client configuration is empty. |
|
||||
| 0x801C001B | The device certificate is not found. |
|
||||
| 0x801C03F0 | There is no key registered for the user. |
|
||||
| 0x801C03F1 | There is no UPN in the token. |
|
||||
| 0x801C044C | There is no core window for the current thread. |
|
||||
| 0x801C001B | The device certificate isn't found. |
|
||||
| 0x801C03F0 | There's no key registered for the user. |
|
||||
| 0x801C03F1 | There's no UPN in the token. |
|
||||
| 0x801C044C | There's no core window for the current thread. |
|
||||
| 0x801c004D | DSREG_NO_DEFAULT_ACCOUNT: NGC provisioning is unable to find the default WAM account to use to request Microsoft Entra token for provisioning. Unable to enroll a device to use a PIN for login. |
|
||||
| 0xCAA30193 | HTTP 403 Request Forbidden: it means request left the device, however either Server, proxy or firewall generated this response. |
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 01/03/2024
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows identity protection
|
||||
description: Learn more about identity protection technologies in Windows.
|
||||
ms.topic: overview
|
||||
ms.date: 07/27/2023
|
||||
ms.date: 03/12/2024
|
||||
---
|
||||
|
||||
# Windows identity protection
|
||||
|
||||
@ -3,7 +3,7 @@ title: Windows passwordless experience
|
||||
description: Learn how Windows passwordless experience enables your organization to move away from passwords.
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.date: 09/27/2023
|
||||
ms.date: 03/12/2024
|
||||
ms.topic: how-to
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Remote Credential Guard
|
||||
description: Learn how Remote Credential Guard helps to secure Remote Desktop credentials by never sending them to the target device.
|
||||
ms.topic: how-to
|
||||
ms.date: 12/08/2023
|
||||
ms.date: 03/12/2024
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Web sign-in for Windows
|
||||
description: Learn how Web sign-in in Windows works, key scenarios, and how to configure it.
|
||||
ms.date: 12/11/2023
|
||||
ms.date: 03/12/2023
|
||||
ms.topic: how-to
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -11,8 +11,8 @@ ms.collection:
|
||||
|
||||
# Web sign-in for Windows
|
||||
|
||||
Starting in Windows 11, version 22H2 with [KB5030310][KB-1], you can enable a web-based sign-in experience on Microsoft Entra joined devices, unlocking new sign-in options and capabilities.
|
||||
This feature is called *Web sign-in*.
|
||||
Starting in Windows 11, version 22H2 with [KB5030310][KB-1], you can enable a web-based sign-in experience on Microsoft Entra joined devices.
|
||||
This feature is called *Web sign-in*, and it unlocks new sign-in options and capabilities.
|
||||
|
||||
Web sign-in is a *credential provider*, and it was initially introduced in Windows 10 with support for Temporary Access Pass (TAP) only. With the release of Windows 11, the supported scenarios and capabilities of Web sign-in are expanded.\
|
||||
For example, you can sign in with the Microsoft Authenticator app or with a SAML-P federated identity.
|
||||
@ -21,11 +21,11 @@ This article describes how to configure Web sign-in and the supported key scenar
|
||||
|
||||
## System requirements
|
||||
|
||||
To use web sign-in, the clients must meet the following prerequisites:
|
||||
Here are the prerequisites for using Web sign-in:
|
||||
|
||||
- Windows 11, version 22H2 with [5030310][KB-1], or later
|
||||
- Must be [Microsoft Entra joined](/entra/identity/devices/concept-directory-join)
|
||||
- Must have Internet connectivity, as the authentication is done over the Internet
|
||||
- [Microsoft Entra joined](/entra/identity/devices/concept-directory-join)
|
||||
- Internet connectivity, as the authentication is done over the Internet
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Web sign-in is not supported for Microsoft Entra hybrid joined or domain joined devices.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user