Intune & Device Migration - Domain Joined Hybrid scenario

Hi,

Based on my understanding,

• Remove device, autopilot hash from source tenant
• Remove device (leave) from azure ad
• Disjoin from on prem AD
• Join the device to the new tenant

if autopilot is required on target tenant, reset is required https://techcommunity.microsoft.com/blog/intunecustomersuccess/support-tip-how-to-transfer-windows-autopilot-devices-between-tenants/3920555

Please note that other factors to be considered like count of users, devices, location, authentication token cleanup, certificates, local admin account, enrollment GPO, etc.

Tenant migration is not a supported scenario for Intune. The supported and recommended way is re-enrollment that may have require reset\wipe.

You can also explore migration tools to migrate devices along with user profiles. Also, start with test migration to capture the environment specific dependencies, experiences.

If the above suggestion helps, please click on 'Accept answer' and 'upvote' it.

@Michael Ohff Thanks for posting in our Q&A.

For this issue, there is no method to do device migration without removing devices. The devices will need to be removing from the old tenant and then re-enrolled into the new tenant. You can export some policies and profiles from the old tenant and import them into the new tenant

Hope it will clarify something.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

@Michael Ohff I reviewed this thread and add more information. As I said, you can remove devices from old tenant.

I noticed your tenant3 is cloud only, so we can enable automatic enrollment in tenant3 and enroll these devices to tenant3 via Settings > Accounts > Add a work or school account > connect > Join this device to Azure AD.

Hope it will help.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Hello Michael, as someone who has done copious tenant to tenant migrations over the last 15years, I know how stressful this is.

For the workstations, yes, the official Microsoft response, is to wipe and reset, aka fresh start. And like Ashok says, there are alternatives like disjoin the device and re-joining to the new tenant one by one.

However, we've had customers where it is 9k to 15k machines which all have to happen in a single weekend, there is no number of help desk or admin resources that can handle with that without some serious downtime for the users and the organisation. Not to mention the length of time it takes to fresh start and to get all the apps re-installed.

As you have pointed out the vanity domain can only exist in one tenant so you have to move it big bang, and focus on all the identity during that weekend.

You can of course send out a new device to all 15k users in readiness but that isnt workable either.

Therefore to successfully migrate copious machines, like we did in the customers with 9k or 15k machines, is to use a tool like powersyncpro migration agent which will orchestrate all the devices in a single go, repermission the workstation, keep all the user profiles, and the user is back up and running on average within 7minutes.