How to join Autopilot devices to Hybrid AD

Jonathan LefebvreIntune3 Comments

In our previous post, we covered how to set up computers using Windows Autopilot. While the main scenario is to join computers to Azure AD, leaving the on-prem domain aside is for sure not realist in many cases. Microsoft has added the ability to join the On-prem domain as part of the Autopilot setup. This feature is still currently in Preview, but worth testing and checking it out.

In this post, we will detail the requirements and how to configure Azure and on-prem AD to allow Hybrid AD joined computers.

This post is part of a series on Windows Autopilot that will be published in the following weeks. In the next posts, we will cover the following subjects :

Intune Autopilot Hybrid AD joined Requirements

  • Hybrid AD join requirements are completed
  • Windows 10 1809 or higher
  • Internet Access
  • On-prem(domain connected) network access.
    • VPN connection is not supported
  • Intune automatic enrollment enabled
    • See our previous post about Autopilot for this requirement
  • A server running Windows Server 2016

High-level steps

  • Delegate AD rights to the server that will have the Intune connector installed on
  • Install and configure the Intune connector
  • Modification to the Autopilot Deployment Profile
  • Create Domain join configuration profile

Delegate Active Directory rights

Before we move on to set up the AD delegation, the server that will be used to host the Intune Connector needs to be chosen. This server requires to run Windows Server 2016.

Because will be delegating rights on an OU, we created a new one. This is not mandatory to have a dedicated OU.

Intune Autopilot Hybrid AD joined
  • Right-click on the OU and select Delegate control
Intune Autopilot Hybrid AD joined
  • On the Users or group, find and add the computer account for the server.
Intune Autopilot Hybrid AD joined
  • Select Create a custom task to delegate
Intune Autopilot Hybrid AD joined
  • Select Only the following objects in the folder and check Computer Object and also check Create selected object in this folder and Delete selected object in this folder
Intune Autopilot Hybrid AD joined
  • Check General, Property-Specific, Creation/deletion and Full Control
Intune Autopilot Hybrid AD joined
  • Delegation is completed!

Install and configure the Intune Connector

The server that will have the Intune connector must be running Windows Server 2016, have internet access and can talk to the Active Directory

  • Connect on the server to host the Intune Connector
  • Browse to Azure Portal/Intune/Device Enrollment/Windows Enrollment/Intune Connect for Active directory(Preview)
Intune Autopilot Hybrid AD joined
  • Click on Add and select Download the on-premise Intune Connector for AD
Intune Autopilot Hybrid AD joined
  • Run the ODJConnectorBootstapper.exe, check the I agree… and click Install
    • The install path can be changed under options if needed
Intune Autopilot Hybrid AD joined
  • Click on Configure Now
Intune Autopilot Hybrid AD joined
  • Click on Sign in and provide credentials of a Global administrator or Intune Service Administrator
Intune Autopilot Hybrid AD joined
Important Info

The note at the bottom is really important :

The Intune connector for Active Directory automatically downloads and installs updates. The user that signs in must have an Intune license installed

  • Intune Connector for AD successfully enrolled!
Intune Autopilot Hybrid AD joined
  • Looking back in Azure Portal/Intune/Device Enrollment/Windows Enrollment/Intune Connect for Active directory(Preview), the server name now shows up.
Intune Autopilot Hybrid AD joined

Configure Autopilot profile for Intune Hybrid AD joined

If you currently have an Autopilot profile to Azure AD join, it will not be possible to modify it. So we’ll create a new one.

  • Go to Intune/Device enrollment – Windows Enrollment/Windows Autopilot deployment profile and Create a new profile
Intune Autopilot Hybrid AD joined
Important Info

Note that the computer name will not be configured in the Autopilot deployment profile. This will be done in a Device configuration profile for Domain join.

This actually limits the use of variables like %SERIAL%, meaning that it is not currently supported to use the serial number as a computer name with Hybrid Domain join.

  • Make sure you assign this deployment profile to your All autopilot group

Create Domain Join configuration profile

Once the Autopilot configuration is completed, we need to create a Device configuration profile with the domain specific informations.

  • Browse to Intune/Device Configuration – Profiles and create a new profile. Select Windows 10 or later and Domain Join (Preview)
Intune Autopilot Hybrid AD joined
  • On the right side, provide the computer name prefix, domain name, and OU to add to a computer to, in DN Format.
Intune Autopilot Hybrid AD joined
  • Make sure you assign this Device configuration profile to your All autopilot group. Also, make sure that only one profile is available to your device.

Testing the Intune Hybrid AD joined

As mentioned earlier, the computer must be connected to the on-prem network and can access the domain before we initiate a reset.

After completing the OOBE section, we can see under Intune/Devices that this specific device as the Device Configuration – Domain join with a state of Succeeded!

Intune Autopilot Hybrid AD joined

Under Azure AD/Devices our new computer is now Hybrid Azure AD joined instead of simply Azure AD joined!

Intune Autopilot Hybrid AD joined

Because SCCM is also on our domain, it automatically push out the SCCM agent. This means that the Co-Management must be up and running in order to fully complete the process from Intune, for example, to push default applications.

Intune Autopilot Hybrid AD joined

Bottom line notes

Here’s a few observations while testing the Hybrid AD join.

Double computer with the same name

While we haven’t found a clear statement on this, it seems normal that 2 computers with the same name are store in Azure AD.

Intune Autopilot Hybrid AD joined

BitLocker recovery keys

In our previous post, we stated that the recovery keys are stored under the Intune device/ Monitor/Recovery Keys.

Intune Autopilot Hybrid AD joined

When doing the Hybrid AD join, this isn’t the case. The BitLocker recovery key will be stored on the on-prem AD object. Is this a feature? a bug? We don’t know…

Intune Autopilot Hybrid AD joined

For more details about Hybrid AD with Autopilot, see Microsoft docs

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading...

Share this Post

3 Comments on “How to join Autopilot devices to Hybrid AD”

  1. Hi guys,

    Is it normal to have duplicate devices within Azure AD? One ‘Azure AD Registered’ and another ‘Hybrid Azure AD Joined’ after this?

    1. Hi Alex,

      as stated in the bottom line notes, it seems normal to have 2 entries per devices. But I haven’t found any official statement on this.
      Jonathan

Leave a Reply

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