Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Início
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
Menu

Category: Windows Hello for Business

Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength

Posted on 21 de April de 2024

Explore the depths of Office 365 security in our latest blog post as we guide you through the implementation of a conditional access policy requiring Windows Hello for Business authentication. This step-by-step tutorial covers the integration process, authentication strength configuration, and offers insights into expected error messages. Discover how to investigate and resolve issues efficiently, ensuring a seamless transition to this advanced security measure and fortifying your Office 365 environment against unauthorized access. Elevate your digital workspace security and empower users with this comprehensive guide.

Troubleshooting Error Code ‘0x000005e’ in WHfB: PIN Authentication Woes

Posted on 11 de February de 2024

Encountering error code ‘0x000005e’ during PIN-based authentication in Windows Hello for Business (WHfB) can be a roadblock for users. In this blog post, we’ll delve into a specific scenario where users face this issue immediately after the enrollment process in a cloud Kerberos trust scenario.

WHfB: Fixing Windows Hello for Business error ‘LogoncertTemplateReady: NO (StateNoTemplate)’

Posted on 29 de December de 2023

Greetings, readers. In this article, we will delve into the process of investigating and resolving the message “LogoncertTemplateReady: NO (StateNoTemplate)” that may surface during Windows Hello for Business (WHfB) Hybrid Certificate trust deployments.

WHfB Cloud Kerberos Trust – Fixing config issue: ‘Cloud trust for on-premise auth policy is enabled: No’

Posted on 19 de June de 2023

Hello everyone. In this article, I will cover one common issue when moving from WHfB Certificate trust to WHfB Cloud Kerberos Trust.

WHfB Cloud Kerberos Trust – Windows Hello for Business provisioning will not be launched.

Posted on 22 de May de 2023

Hello everyone. For the ones implementing Azure AD Cloud Kerberos Trust and the WHfB popup doesn’t show up, please check this article. Today, I will share a few interesting logs to investigate WHfB Cloud Kerberos Trust enrollment issues. Normally they are related to missing requirements.

WHfB – Fixing error message 0xCAA20064 during windows hello for business certificate trust enrollment

Posted on 28 de July de 2022

Hi mates. Today I will cover error message 0xCAA20064 during Windows Hello sign-in certificate enrollment. 

WHfB – Suppressing Windows Hello for Business provisioning using Group Policy

Posted on 3 de July de 2022

Hi everyone. Today, we’re going to share a very useful Active directory group policy to help you deploy windows hello for business. 
Scenario: By default, once you enable Windows Hello for Business using GPO, once the users affected by the policy sign in, they receive the WHfB enrollment prompt. This rollout can confuse users if not properly communicated by the IT Admins. To help administrators avoid prompting users for WHfB enrollment immediately after sign-in, the option ‘Do not start Windows Hello provisioning after sign-in’ in the ‘Use Windows Hello for Business’ policy can be used.

WHfB – Fixing message ‘That option is temporarily unavailable. For now, please use a different method to sign in’

Posted on 15 de April de 2022

Hello everyone. Today we’re going to investigate message ‘That option is temporarily unavailable. For now, please use a different method to sign in’ when a user tries to use recent setup PIN on windows hello for business Hybrid deployments.

WHfB: Troubleshooting Windows Hello for Business provisioning AdfsRaIsReady:UNKNOWN

Posted on 15 de March de 2022

Hi everyone. Today, we’re going to explain how to investigate and fix the message ‘AdfsRaIsReady:UNKNOWN’ during Windows Hellos for Business Hybrid Certificate trust deployment.

WHfB – Fixing error message ‘Your credentials could not be verified’

Posted on 27 de February de 2022

Hi everyone. Today, we’re going to investigate the error message ‘Your credentials could not be verified’ when a user is trying to authenticate using a PIN to authenticate on a Hybrid WHfB deployment.

Recent Posts

  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know 17 de March de 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys 23 de September de 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength 21 de April de 2024
  • Troubleshooting Error Code ‘0x000005e’ in WHfB: PIN Authentication Woes 11 de February de 2024
  • WHfB: Fixing Windows Hello for Business error ‘LogoncertTemplateReady: NO (StateNoTemplate)’ 29 de December de 2023

Archives

  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #aadhybridjoin #adfs #adfsonsql #azuread #azureauth #azureCA #azuredevice #azurehybridjoin #azuremfa #azuresecurity #capolicy #cloudkerberostrust #conditionalaccess #conditionalaccesspolicy #deviceregistration #gmsaaccount #gopasswordless #hybridaadjoin #mfaserver #msadfs #msazure #msidentity #namedlocation #sslcertificatevalidation #tshootadfs #tshoothybridjoin #tshootwaptrust #waptrust #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #widdatabase adconnect authenticationcontext authenticationstrength az500 azuread azuremfa azurepim azuresecurity cloudsecurity microsoft365 msazure WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}