Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra ID Devices – Joining a Windows 10 Device as Microsoft Entra Hybrid Joined

Posted on December 26, 2019

Hello, everyone. In today’s article, we’ll explain step by step how to configure a federated environment with AD FS for joining devices from a local domain to Microsoft Entra ID.

As explained in the article Introduction to Device Management in Microsoft Entra ID, the hybrid scenario uses the best that on-premises AD and Microsoft Entra ID can offer in management tools and security solutions.

Configuring Automatic Registration in Microsoft Entra ID

Note: To follow the steps below, you need to have at least one AD FS server configured in the environment and Microsoft Entra Connect configured in federated mode with AD FS. If you don’t yet have a domain with AD FS, follow the steps in this link.

If you have a domain with AD FS installed and Microsoft Entra Connect configured in federated authentication mode, follow the steps below to set up the environment to configure hybrid device registration.

On the SYNC server, open Microsoft Entra Connect and click Configure.

Select the Configure device options menu.

Click Next.

Click Next.

Enter the credentials of a user with Global administrator privilege and the password.

Click Next.

Select the Configure Hybrid Azure AD join option.

Click Next.

Select the Windows 10 or later domain-joined devices option.

Note: If you have devices running a version earlier than Windows 10, select the Supported Windows downlevel domain-joined devices option.

Click Next.

Select the local domain you want to configure and enter credentials that have Enterprise Admin privilege.

Click OK and Next.

Enter the credential that has administrator privilege on the AD FS service.

Click Next.

Click Exit.

Click Configure.

Click Exit.

Note: After configuring hybrid device registration, there are some additional configurations to perform for a controlled rollout using GPO that we won’t cover in this article. For more information, access this link.

Enabling Device Authentication on AD FS

On the AD FS server, open the service manager and select Device Registration.

Click Enable device authentication.

Validating the SCP (Service Connection Point) Configuration

You can confirm whether the settings made by Microsoft Entra Connect in the previous steps are correct using ADSI Edit. Open the tool and navigate to CN=62a0ff2e-97b9-4513-943f-0d221bd30080,CN=Device Registration Configuration,CN=Services, [your domain], as shown below:

Right-click the 62a0ff2e-97b9-4513-943f-0d221bd30080 directory and you’ll be able to see the available SCP domain records.

Joining a Windows 10 Device to the Local AD (Microsoft Entra Hybrid Join)

Now let’s join a Windows 10 device to a local domain.

Select the Join this device to a local Active Directory domain option.

The alt attribute for this image is empty. The file name is image-95.png

Enter the information for the local domain you want to join the device to, and click Next.

The alt attribute for this image is empty. The file name is image-96.png

Enter credentials that have permission to join devices to the local domain, and click OK.

The alt attribute for this image is empty. The file name is image-97.png

You’ll receive a request to confirm the user who will use the device. You can choose whether that user will have administrator privileges on the device or not.

Click Next.

Let’s restart the device by clicking Restart now.

The alt attribute for this image is empty. The file name is image-99.png

Wait for the next Microsoft Entra Connect replication cycle, or run the command below in PowerShell to perform a delta replication:

Start-ADSyncSyncCycle -PolicyType Delta

In the Azure portal, access Azure AD and the Devices option.

By clicking the device we just joined to the local AD, we can verify that the Join type is Hybrid AD Joined.

You can also identify the device’s join status in Microsoft Entra ID by running the command below in the Windows prompt on the device:

dsregcmd /status

Summary

In today’s article, we showed how to configure a federated environment for the automatic join of a Windows 10 device using Microsoft Entra Connect and AD FS. We joined a Windows 10 device to the local domain and to Microsoft Entra ID.

I hope this content has contributed to enriching your knowledge of Azure.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, leave a comment.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Devices topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • 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 #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell 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}