• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 22 subscribers
  • Views 2979 views
  • Users 0 members are here
Options
Related

Source and Target domains users are using the same O365 tenant can I migrate users from Source to Target using MMAD

JP_Migr8AD
over 4 years ago

Source and Target domains users are using the same O365 tenant can I migrate users from Source to Target using MMAD or do I need MM for O365?

The O365 subscription for the users in the source domain will be the same subscription as once they are in the Target domain. 

  • 0 over 4 years ago

    Yes MMAD is fine.

    My setup:

    Use a different forest

    Set up an external trust.

    Copy users over, keep same UPN.

    Shuffle users around between different OU's that sync to o365

    Move user to UnSync OU in source domain

    Run Delta Sync

    Confirm user is deleted 'get-msoluser -UserPrincipalName [test@source.com](mailto:test@source.com)'

    Restore as Cloud User 'Restore-MsolUser -UserPrincipalName [test@source.com](mailto:test@source.com) -AutoReconcileProxyConflicts '

    Set Immutable ID to $Null - Set-MSOLUser -UserPrincipalName "[test@source.com](mailto:test@source.com)" -ImmutableID "$null"

    Move user to Sync OU in new domain.

    Run Delta Sync

    Run full AADC import

    Ensure user now shows as Synced with Active Directory in Portal.

  • 0 over 4 years ago

    Yes, you can still use MMAD to migrate the users from source to the target.    MMAD can't sync the ImmutableID attribute, but it can sync the MS-DS-ConsistencyGUID attribute from the source to the target.   So, if you're using an older version of AADC that uses ImmutableID as the anchor you'll have to upgrade to the latest version and ensure that it's using the MS-DS-ConsistencyGUID as the new anchor.   

    Once MMAD migrates the user and it's in the scope of AADC, it should match the 2 objects.