Plan your Microsoft Entra hybrid join implementation

If you have an on-premises Active Directory Domain Services (AD DS) environment and you want to join your AD DS domain-joined computers to Microsoft Entra ID, you can accomplish this task by doing Microsoft Entra hybrid join.


SSO access to on-premises resources is also available to devices that are Microsoft Entra joined. For more information, see How SSO to on-premises resources works on Microsoft Entra joined devices.


This article assumes that you're familiar with the Introduction to device identity management in Microsoft Entra ID.


The minimum required domain controller version for Windows 10 or newer Microsoft Entra hybrid join is Windows Server 2008 R2.

Microsoft Entra hybrid joined devices require network line of sight to your domain controllers periodically. Without this connection, devices become unusable.

Scenarios that break without line of sight to your domain controllers include:

  • Device password change
  • User password change (Cached credentials)
  • TPM reset

Plan your implementation

To plan your hybrid Microsoft Entra implementation, you should familiarize yourself with:

  • Review supported devices
  • Review things you should know
  • Review targeted deployment of Microsoft Entra hybrid join
  • Select your scenario based on your identity infrastructure
  • Review on-premises AD UPN support for Microsoft Entra hybrid join

Review supported devices

Microsoft Entra hybrid join supports a broad range of Windows devices. Because the configuration for devices running older versions of Windows requires other steps, the supported devices are grouped into two categories:

Windows current devices

  • Windows 11
  • Windows 10
  • Windows Server 2016
    • Note: Azure National cloud customers require version 1803
  • Windows Server 2019

For devices running the Windows desktop operating system, supported versions are listed in this article Windows 10 release information. As a best practice, Microsoft recommends you upgrade to the latest version of Windows.

Windows down-level devices

  • Windows Server 2012 R2
  • Windows Server 2012

As a first planning step, you should review your environment and determine whether you need to support Windows down-level devices.

Review things you should know

Unsupported scenarios

  • Microsoft Entra hybrid join isn't supported for Windows Server running the Domain Controller (DC) role.
  • Microsoft Entra hybrid join isn't supported on Windows down-level devices when using credential roaming or user profile roaming or mandatory profile.
  • Server Core OS doesn't support any type of device registration.
  • User State Migration Tool (USMT) doesn't work with device registration.

OS imaging considerations

  • If you're relying on the System Preparation Tool (Sysprep) and if you're using a pre-Windows 10 1809 image for installation, make sure that image isn't from a device that is already registered with Microsoft Entra ID as Microsoft Entra hybrid joined.

  • If you're relying on a Virtual Machine (VM) snapshot to create more VMs, make sure that snapshot isn't from a VM that is already registered with Microsoft Entra ID as Microsoft Entra hybrid joined.

  • If you're using Unified Write Filter and similar technologies that clear changes to the disk at reboot, they must be applied after the device is Microsoft Entra hybrid joined. Enabling such technologies before completion of Microsoft Entra hybrid join will result in the device getting unjoined on every reboot.

Handling devices with Microsoft Entra registered state

If your Windows 10 or newer domain joined devices are Microsoft Entra registered to your tenant, it could lead to a dual state of Microsoft Entra hybrid joined and Microsoft Entra registered device. We recommend upgrading to Windows 10 1803 (with KB4489894 applied) or newer to automatically address this scenario. In pre-1803 releases, you'll need to remove the Microsoft Entra registered state manually before enabling Microsoft Entra hybrid join. In 1803 and above releases, the following changes have been made to avoid this dual state:

  • Any existing Microsoft Entra registered state for a user would be automatically removed after the device is Microsoft Entra hybrid joined and the same user logs in. For example, if User A had a Microsoft Entra registered state on the device, the dual state for User A is cleaned up only when User A logs in to the device. If there are multiple users on the same device, the dual state is cleaned up individually when those users log in. After an admin removes the Microsoft Entra registered state, Windows 10 will unenroll the device from Intune or other MDM, if the enrollment happened as part of the Microsoft Entra registration via auto-enrollment.
  • Microsoft Entra registered state on any local accounts on the device isn’t impacted by this change. Only applicable to domain accounts. Microsoft Entra registered state on local accounts isn't removed automatically even after user logon, since the user isn't a domain user.
  • You can prevent your domain joined device from being Microsoft Entra registered by adding the following registry value to HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001.
  • In Windows 10 1803, if you have Windows Hello for Business configured, the user needs to reconfigure Windows Hello for Business after the dual state cleanup. This issue has been addressed with KB4512509.


Even though Windows 10 and Windows 11 automatically remove the Microsoft Entra registered state locally, the device object in Microsoft Entra ID is not immediately deleted if it is managed by Intune. You can validate the removal of Microsoft Entra registered state by running dsregcmd /status and consider the device not to be Microsoft Entra registered based on that.

Microsoft Entra hybrid join for single forest, multiple Microsoft Entra tenants

To register devices as Microsoft Entra hybrid join to respective tenants, organizations need to ensure that the Service Connection Points (SCP) configuration is done on the devices and not in AD. More details on how to accomplish this task can be found in the article Microsoft Entra hybrid join targeted deployment. It's important for organizations to understand that certain Microsoft Entra capabilities won't work in a single forest, multiple Microsoft Entra tenants configurations.

Other considerations

  • If your environment uses virtual desktop infrastructure (VDI), see Device identity and desktop virtualization.

  • Microsoft Entra hybrid join is supported for FIPS-compliant TPM 2.0 and not supported for TPM 1.2. If your devices have FIPS-compliant TPM 1.2, you must disable them before proceeding with Microsoft Entra hybrid join. Microsoft doesn't provide any tools for disabling FIPS mode for TPMs as it is dependent on the TPM manufacturer. Contact your hardware OEM for support.

  • Starting from Windows 10 1903 release, TPMs 1.2 aren't used with Microsoft Entra hybrid join and devices with those TPMs will be considered as if they don't have a TPM.

  • UPN changes are only supported starting Windows 10 2004 update. For devices before the Windows 10 2004 update, users could have SSO and Conditional Access issues on their devices. To resolve this issue, you need to unjoin the device from Microsoft Entra ID (run "dsregcmd /leave" with elevated privileges) and rejoin (happens automatically). However, users signing in with Windows Hello for Business don't face this issue.

Review targeted Microsoft Entra hybrid join

Organizations may want to do a targeted rollout of Microsoft Entra hybrid join before enabling it for their entire organization. Review the article Microsoft Entra hybrid join targeted deployment to understand how to accomplish it.


Organizations should include a sample of users from varying roles and profiles in their pilot group. A targeted rollout will help identify any issues your plan may not have addressed before you enable for the entire organization.

Select your scenario based on your identity infrastructure

Microsoft Entra hybrid join works with both, managed and federated environments depending on whether the UPN is routable or non-routable. See bottom of the page for table on supported scenarios.

Managed environment

A managed environment can be deployed either through Password Hash Sync (PHS) or Pass Through Authentication (PTA) with Seamless Single Sign On.

These scenarios don't require you to configure a federation server for authentication.


Cloud authentication using Staged rollout is only supported starting at the Windows 10 1903 update.

Federated environment

A federated environment should have an identity provider that supports the following requirements. If you have a federated environment using Active Directory Federation Services (AD FS), then the below requirements are already supported.

  • WIAORMULTIAUTHN claim: This claim is required to do Microsoft Entra hybrid join for Windows down-level devices.
  • WS-Trust protocol: This protocol is required to authenticate Windows current Microsoft Entra hybrid joined devices with Microsoft Entra ID. When you're using AD FS, you need to enable the following WS-Trust endpoints: /adfs/services/trust/2005/windowstransport /adfs/services/trust/13/windowstransport /adfs/services/trust/2005/usernamemixed /adfs/services/trust/13/usernamemixed /adfs/services/trust/2005/certificatemixed /adfs/services/trust/13/certificatemixed


Both adfs/services/trust/2005/windowstransport or adfs/services/trust/13/windowstransport should be enabled as intranet facing endpoints only and must NOT be exposed as extranet facing endpoints through the Web Application Proxy. To learn more on how to disable WS-Trust Windows endpoints, see Disable WS-Trust Windows endpoints on the proxy. You can see what endpoints are enabled through the AD FS management console under Service > Endpoints.

Beginning with version 1.1.819.0, Microsoft Entra Connect provides you with a wizard to configure Microsoft Entra hybrid join. The wizard enables you to significantly simplify the configuration process. If installing the required version of Microsoft Entra Connect isn't an option for you, see how to manually configure device registration. If is registered as a confirmed custom domain, users can get a PRT even if their syncronized on-premises AD DS UPN suffix is in a subdomain like

Review on-premises AD users UPN support for Microsoft Entra hybrid join

Sometimes, on-premises AD users UPNs are different from your Microsoft Entra UPNs. In these cases, Windows 10 or newer Microsoft Entra hybrid join provides limited support for on-premises AD UPNs based on the authentication method, domain type, and Windows version. There are two types of on-premises AD UPNs that can exist in your environment:

  • Routable users UPN: A routable UPN has a valid verified domain that is registered with a domain registrar. For example, if is the primary domain in Microsoft Entra ID, is the primary domain in on-premises AD owned by Contoso and verified in Microsoft Entra ID.
  • Non-routable users UPN: A non-routable UPN doesn't have a verified domain and is applicable only within your organization's private network. For example, if is the primary domain in Microsoft Entra ID and contoso.local is the primary domain in on-premises AD but isn't a verifiable domain in the internet and only used within Contoso's network.


The information in this section applies only to an on-premises users UPN. It isn't applicable to an on-premises computer domain suffix (example: computer1.contoso.local).

The following table provides details on support for these on-premises AD UPNs in Windows 10 Microsoft Entra hybrid join

Type of on-premises AD UPN Domain type Windows 10 version Description
Routable Federated From 1703 release Generally available
Non-routable Federated From 1803 release Generally available
Routable Managed From 1803 release Generally available, Microsoft Entra SSPR on Windows lock screen isn't supported in environments where the on-premises UPN is different from the Microsoft Entra UPN. The on-premises UPN must be synced to the onPremisesUserPrincipalName attribute in Microsoft Entra ID
Non-routable Managed Not supported

Next steps