Thanks for the feedback on this. There are several ways to do Azure AD join (OOBE, bulk enrollment and Autopilot) which provide a richer experience to join devices to Azure AD. We’re continuously working to enhance those, so currently this is unplanned for the near future. Please continue to vote to help us prioritize
An error occurred while saving the commentLevi Stevens commented
Ravi - This is a cop-out by Microsoft. We don't need a "richer experience", we need a hands free way to migrate systems to AAD join without having to wipe out the user state on the device as both Bulk Enrollment and Windows Autopilot require OOBE. I have clients that simply want to disjoin from AD and then AAD join. They do not want to have to effectively do a wipe and reload to migrate. They will get cleaner systems with a break/fix reinstall or part of their hardware refresh cycle. This is a particular pain point for the SMB sector who may not have the same resources as a large enterprise to pull off a W&R of all their devices to migrate.
We are aware of the requirement to be able to convert a synced user to cloud only and are designing that feature, but we have no timelines to share right now.
We reverted the change that would block the “hack” to delete and restore a user to change a user to “Cloud Only”.
31 votesLevi Stevens shared this idea ·