I work in a hybrid 365 environment with a forest containing six subdomains, each representing a different company. We have a situation where one user is transitioning from one company to another within this setup. I'm trying to gauge how challenging it is to transfer just one user from one domain to another. The last time I handled this was years ago when we were using on-prem Exchange, and it was straightforward with the ADMT tool. However, I've been checking out the current ADMT release notes on Microsoft's website, and they seem to suggest it's not well-supported anymore, mentioning bugs and that users should proceed at their own risk. Has anyone gone through a similar experience recently?
1 Answer
ADMT is pretty much considered outdated now. For migrating within a hybrid 365 setup, the best approach is to convert the user to cloud-only by disabling dirsync, then move them to the target tenant and resync from the new domain. It can be a bit tricky, especially with mailbox migration and app-specific authentication. I’d rate the PITA level around 6 out of 10.
Could you clarify what you mean by moving to the target tenant and then resyncing? I plan to disable dirsync for the user by moving their AD account to a non-synced OU. Also, would it just be easier to create a new account in the target domain and sync their existing cloud account rather than messing around with AD accounts?