Domain Join to Cloud Only (AADJ) Migration without Wipe and Load!!

Doesn't Profile Wizard Simplify this?

This is really promising however reading the instructions im slightly lost regarding on where the files are required to go for this to work?

Thanks for the video. But what configuration must take place on Azure to facilitate this?

This looks incredible! One question though.. Onedrive was setup pre migration, but what happened after migration? I assume the intune policy for Onedrive (if created/assigned) would kick in, but I didn't see anything about this in your video..

Sidenote, I've had issues with signing in silently with OneDrive on AAD joined VMs despite setting up the policy in Intune. Compliant devices are excluded from requiring MFA with Conditional Access but the Onedrive app remains untouched (logged out). If anyone has got an idea what might be wrong, I'd appreciate some guideance 😊 I was thinking that maybe the device being a VM may be the reason behind this behaviour since interactive/remote logon is used via the Hyper-V manager. Haven't had the time to test with AAD joined physical hardware yet, so I don't know if the outcome will be different. (Edit: physical hardware gave the same result, so I'm still head scratching 😉)

Thanks for great content Dean!

Seems a good option, I have done this in the past using the USMT but need to have twice the local profile size in free disk space or a very fast network location.

I'm trying to test this, but his guide on setting up the directory was a little vauge. Can you explain how you set up your folder structure? I got confused because he says Download the PowerShell App Deploy Toolkit and place the contents in the “Toolkit” folder, but there is no toolkit folder in the AADMigration folder, does he mean for us to copy the appdeploy toolkit folder to the AADM folder? And when he says to place the OnedriveLib and bulk token to the files directory, is he meaning AADM\FILES or AADM\Toolkit\files as there is a files folder within the toolkit folder.

Hi, thanks for this info. However, i've just done my first migration. Never even heard of "Wipe and load".
This is what i did to my hybrid joined w10 devices:
1. unjoin device from domain (ensure local admin account access)
2. reboot into local admin account
3. rename computer and reboot back into admin account
4. Join AAD using intune licenced admin account
5 sign out and back in as AAD user (so that they are not granted admin access).
This process takes about 15 mins per device. The main caveat i've found is that if the domain-joined account has a profile that takes up a lot of hard disk space, then you will essentially double that when joined AAD as above (OneDrive for business is in operation here).

Does your method convert or remove the domain only profile?

How would you recommend the final step: turn of sync and turning users into Cloud only ?

We use ForensiT ProfWiz for these migrations. Can recommend it!

Haha, I also look forward to Andrew's Friday Newsletter!!

But I didn't notice this! looks like magic. moving from AD joined to Azure AD joined device is a real bore! will certainly be checking this out.

I actually do want to do a wipe and load. Can you make a video about deploying modern computers with MDT? Where MDT installs vanilla Windows 11 and Autopilot takes over?

Hi, Thanks for some great content. Is this a better method for migrating from local AD to Azure AD, than using Forensit User Profile Wizard Release 24 ? I have been using Forensit for years, with very few problems.

For domain join only (not hybrid) who will the primary user be onthe device?

I have seen many of nice hacks using power shell script, but these cant be used in Production but good to know 😊

I am not going to tell you how to do dat either 😂😂😂😂😂

My company is looking to migrate fully from in on prem to cloud! This video is so helpful, appreciate it!