Share via

Error:Migration Invalid Target Address Exception

Anonymous
2016-06-22T04:00:40+00:00

Staged Migration batch:

Target address no found...

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

9 answers

Sort by: Most helpful
  1. Anonymous
    2016-07-07T08:36:33+00:00

    Please send me an email with all information you need? I didnt find yout queries here in our community.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-07-07T07:51:58+00:00

    Hi Farooq,

    Let’s continue our troubleshooting. 

    Could you provide the information I asked on June 22 for further analysis? 

    Thanks,

    Young

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-07-06T17:58:45+00:00

    Yes,indeed.It is still an issue

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-25T09:38:02+00:00

    Hi Farooq,

    Do you need any further assistance?

    Thanks,

    Young

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-22T09:12:45+00:00

    Hi Farooq,

    May I collect some information to analyze the issue?

    1. What is your on-premise Exchange version?
    2. Could you provide the entire error message? To protect your privacy, I have sent a private message to request your tenant information. Please use this link to access the private message and reply to it: https://answers.microsoft.com/en-us/privatemessages/list
    3. How many mailboxes have this issue?
    4. Before staged migration, the on-premise mailbox is synced to Office 365 as a mail user. According to the error message, the possible cause is that the Office 365 mail user’s email addresses are not synced correctly. I’d like to check the recipient information via PowerShell commands:

    a. From on-premise Exchange Management Shell, run:

    Get-Mailbox UserName | fl

    b. From another PC, connect PowerShell to Exchange Online: https://technet.microsoft.com/library/jj984289(v=exchg.160).aspx. Then run:

    Get-User UserName| fl

    Get-Recipient UserName | fl

    Get-MailUser UserName | fl

    Note: replace UserName with this affected user.

    Please also provide the PowerShell outputs in private message. 

    1. Based on my experience, I suggest you try to permanently remove the affected Office 365 user, re-sync the user to Office 365. And then migrate the mailbox again. 

    Thanks,

    Young

    Was this answer helpful?

    0 comments No comments