Event banner
Event details
As a company we are planning to evolve from Hybrid to Cloud-first. At the moment we have a PC provisioning process in ConfigMgr Task Sequence and co-management configured; so first on-prem config, second cloud config.
What do we need to 'reverse' our PC provisioning process to put the cloud first (EntraID/Intune) and then connect to on-prem (AD/ConfigMgr) ?
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.
- Joe_Lurie
Microsoft
Ideally, 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.
