Impact of ADMT 3.2

Tao Cuong 41 Reputation points
2020-11-12T07:25:45.457+00:00

Hi everyone, i have some important questions for my customer case. Here is it
In AD i have 1 forest/ 3 child domain. User is in 3 child domain. We use hybrid AD with password hash sync. AD connect is synchronization user in 3 child domain depent OU. Hybrid Exchange but all user have all mailbox in Exchange online. We plan to move all user in 3 child domain to root domain use ADMT 3.2

  • Question 1. I think when i migrate user from child to root. I know when migrate user between domain, there are many attribute is exclude by ADMT 3.2. But i think if i can migrate two important attribute is UPN and SourchAnchor. There is no impact to AD connect, to Azure AD, and to Office 365. Am I right? Can anyone have experience about this? Are there more important attribute?
  • Question 2. One more two important attribute is Mail and ProxyAddresses can be migrate when migrate user. But attribute legacyExchangeDN is exclude by ADMT 3.2. So if legacyExchangeDN is lost, user cannot receive mail, so user AD connect don't see that attribute to synchronization, user in Exchange online cannot receive mail. If i export before migrate and import legacyExchangeDN after migrate. It's OK, but cannot do that with thousand users. My question is are there any attribute have to migrate for NO IMPACT to Hybrid Exchange. And anyone have solution for migrate attribute legacyexchangedn?
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,136 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
22,112 questions
0 comments
Accepted answer
  1. KyleXu-MSFT 26,271 Reputation points
    2020-11-13T02:31:29.867+00:00

    @Tao Cuong
    From Exchange side, here are some of suggestions for you:

    For your first question:

    Based on my searching, from this article, we can know that AAD connect connect users with userPrincipalName, proxyAddresses, and sourceAnchor/immutableID, so make sure those attributes are migrated correctly.

    For you second question:

    There exist many script which could batch export and import X500 email address, such as script in the end of this blog.
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    For more detail information, you could confirm with AD and AAD teams, they may could provide a more detailed information to you.

    I would suggest you test with one temp account then apply on all users.

    If the response is helpful, please click "Accept Answer" and upvote it.
    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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.