How To: Plan your hybrid Azure Active Directory join implementation
In a similar way to a user, a device is another core identity you want to protect and use it to protect your resources at any time and from any location. You can accomplish this goal by bringing and managing device identities in Azure AD using one of the following methods:
- Azure AD join
- Hybrid Azure AD join
- Azure AD registration
By bringing your devices to Azure AD, you maximize your users' productivity through single sign-on (SSO) across your cloud and on-premises resources. At the same time, you can secure access to your cloud and on-premises resources with Conditional Access.
If you have an on-premises Active Directory (AD) environment and you want to join your AD domain-joined computers to Azure AD, you can accomplish this by doing hybrid Azure AD join. This article provides you with the related steps to implement a hybrid Azure AD join in your environment.
This article assumes that you are familiar with the Introduction to device identity management in Azure Active Directory.
The minimum required domain controller version for Windows 10 hybrid Azure AD join is Windows Server 2008 R2.
Plan your implementation
To plan your hybrid Azure AD implementation, you should familiarize yourself with:
|Review supported devices|
|Review things you should know|
|Review controlled validation of hybrid Azure AD join|
|Select your scenario based on your identity infrastructure|
|Review on-premises AD UPN support for hybrid Azure AD join|
Review supported devices
Hybrid Azure AD join supports a broad range of Windows devices. Because the configuration for devices running older versions of Windows requires additional or different steps, the supported devices are grouped into two categories:
Windows current devices
- Windows 10
- Windows Server 2016
- Windows Server 2019
For devices running the Windows desktop operating system, supported version are listed in this article Windows 10 release information. As a best practice, Microsoft recommends you upgrade to the latest version of Windows 10.
Windows down-level devices
- Windows 8.1
- Windows 7. For support information on Windows 7, see Support for Windows 7 is ending.
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2. For support information on Windows Server 2008 and 2008 R2, see Prepare for Windows Server 2008 end of support.
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
Hybrid Azure AD join is currently not supported if your environment consists of a single AD forest synchronizing identity data to more than one Azure AD tenant.
If your environment uses virtual desktop infrastructure (VDI), see Device identity and desktop virtualization.
Hybrid Azure AD 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 Hybrid Azure AD join. Microsoft does not provide any tools for disabling FIPS mode for TPMs as it is dependent on the TPM manufacturer. Please contact your hardware OEM for support. Starting from WIndows 10 1903 release, TPMs 1.2 are not used for hybrid Azure AD join and devices with those TPMs will be considered as if they don't have a TPM.
Hybrid Azure AD join is not supported for Windows Server running the Domain Controller (DC) role.
Hybrid Azure AD join is not supported on Windows down-level devices when using credential roaming or user profile roaming or mandatory profile.
If you are relying on the System Preparation Tool (Sysprep) and if you are using a pre-Windows 10 1809 image for installation, make sure that image is not from a device that is already registered with Azure AD as Hybrid Azure AD join.
If you are relying on a Virtual Machine (VM) snapshot to create additional VMs, make sure that snapshot is not from a VM that is already registered with Azure AD as Hybrid Azure AD join.
If your Windows 10 domain joined devices are Azure AD registered to your tenant, it could lead to a dual state of Hybrid Azure AD joined and Azure AD registered device. We recommend upgrading to Windows 10 1803 (with KB4489894 applied) or above to automatically address this scenario. In pre-1803 releases, you will need to remove the Azure AD registered state manually before enabling Hybrid Azure AD join. In 1803 and above releases, the following changes have been made to avoid this dual state:
- Any existing Azure AD registered state would be automatically removed after the device is Hybrid Azure AD joined.
- You can prevent your domain joined device from being Azure AD registered by adding this registry key - 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 re-setup Windows Hello for Business after the dual state clean up.This issue has been addressed with KB4512509
The Azure AD registered device will not be automatically removed if it is managed by Intune.
Review controlled validation of hybrid Azure AD join
When all of the pre-requisites are in place, Windows devices will automatically register as devices in your Azure AD tenant. The state of these device identities in Azure AD is referred as hybrid Azure AD join. More information about the concepts covered in this article can be found in the article Introduction to device identity management in Azure Active Directory.
Organizations may want to do a controlled validation of hybrid Azure AD join before enabling it across their entire organization all at once. Review the article controlled validation of hybrid Azure AD join to understand how to accomplish it.
Select your scenario based on your identity infrastructure
Hybrid Azure AD 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.
These scenarios don't require you to configure a federation server for authentication.
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 hybrid Azure AD join for Windows down-level devices.
- WS-Trust protocol: This protocol is required to authenticate Windows current hybrid Azure AD joined devices with Azure AD.
When you're using AD FS, you need to enable the following WS-Trust endpoints:
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.
Azure AD does not support smartcards or certificates in managed domains.
Beginning with version 1.1.819.0, Azure AD Connect provides you with a wizard to configure hybrid Azure AD join. The wizard enables you to significantly simplify the configuration process. If installing the required version of Azure AD Connect is not an option for you, see how to manually configure device registration.
Based on the scenario that matches your identity infrastructure, see:
- Configure hybrid Azure Active Directory join for federated environment
- Configure hybrid Azure Active Directory join for managed environment
Review on-premises AD UPN support for Hybrid Azure AD join
Sometimes, your on-premises AD UPNs could be different from your Azure AD UPNs. In such cases, Windows 10 Hybrid Azure AD join provides limited support for on-premises AD UPNs based on the authentication method, domain type and Windows 10 version. There are two types of on-premises AD UPNs that can exist in your environment:
- Routable UPN: A routable UPN has a valid verified domain, that is registered with a domain registrar. For example, if contoso.com is the primary domain in Azure AD, contoso.org is the primary domain in on-premises AD owned by Contoso and verified in Azure AD
- Non-routable UPN: A non-routable UPN does not have a verified domain. It is applicable only within your organization's private network. For example, if contoso.com is the primary domain in Azure AD, contoso.local is the primary domain in on-premises AD but is not a verifiable domain in the internet and only used within Contoso's network.
The table below provides details on support for these on-premises AD UPNs in Windows 10 Hybrid Azure AD 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, Azure AD SSPR on Windows lockscreen is not supported|