Dec 03 2019 02:06 PM - edited Dec 05 2019 07:15 AM
Currently looking into migration options for an existing fleet of Windows 10 AD domain-joined PCs to Azure AD-joined in a target Azure AD tenant (no synchronization in place, don't want to put in place either due to 'cloud only' model)
The three migration options I see:
1) Manual - Manually unjoin AD domain, user joins azure ad domain, reboot and user logs-in, move legacy profile contents over to new azure ad profile (manual or third party)
2) AutoPilot User-Driven - Register devices in AutoPilot to target tenant, create deployment profile in target tenant, add the device to deployment group in target tenant and reboot PC, user logs in and goes through autopilot process
3) AutoPilot User-Driven with White Glove - Register devices in AutoPilot in target tenant, create deployment profile in target tenant, add the device to deployment group in target tenant and reboot PC, technician pre-provisions new profile then reseals, user logs in and goes through autopilot process
Can someone confirm that 2 and 3 are valid options, or if there are any methods I am missing? As in I can register a Windows 10 on-prem domain-joined PC to an Azure AD instance (no synchronization) and use autopilot to migrate the PC to being Azure AD joined.
Thank you
Dec 04 2019 02:08 AM
Dec 04 2019 10:17 AM - edited Dec 04 2019 10:18 AM
@ericjk4 I see what you are saying, but where does the migration of the PC to Azure-AD come into your plan.
Dec 05 2019 12:46 AM
Dec 05 2019 07:14 AM
@ericjk4 no on-premises infrastructure, everything will be consolidated to PaaS/SaaS
Dec 05 2019 08:07 AM