Event banner
Event details
You can deploy an Entra hybrid joined device using Intune and Autopilot as documented here: Enrollment for Microsoft Entra hybrid joined devices - Windows Autopilot | Microsoft Learn
Once the device has been onboarded and joined to on-prem AD, deploying the ConfigMgr client would just be a matter of creating a Win32 app to run ccmsetup.exe with the appropriate command-line switches.
MicrosoftIdeally, you would use Autopilot for those devices that can be joined to Entra - NOT hybrid joined. Even though we allow hybrid joined via Autopilot, we recommend using Autopilot for the Entra joined devices.
Is there a reason that you want to reverse your process, and still have a hybrid joined device as the end result?
Our identity service is still hybrid (AD/Entra ID) and also some on-premises (legacy) applications require that workstations stay in a hybrid mode.
The aim (for the device management infra) is to move away from legacy processes (like an ConfigMgr OSD Task Sequence) and move on-premises workloads to cloud technology as much as possible.- Jason_Sandys
Hi VanakenJ​,
Please check out How SSO to on-premises resources works on Microsoft Entra joined devices - Microsoft Entra ID | Microsoft Learn. It is certainly possible that you an application that has some bespoke or non-standard dependency on on-prem AD, but these are relatively rare. As detailed in this article, standard Windows authentication works seamlessly and is not a limiting factor. Also, please check out the following for an wealth of information:
https://aka.ms/EntraJoin-WhichOption
Jason_Sandys​ Thanks for the info! The road to cloud-native is a challenge, but we'll get there someday.
