IMAP Migration MigrationRecipientNotFoundException

Question

I already posted my problem in another thread but since I got no reply I'm starting a new one here.

Recently I had a situation where I had to remove some users from the Office365 and then later add them back in (so their mailboxes would be recreated) but after doing that when I run our migration batch I'm getting the "MigrationRecipientNotFoundException" error. The only difference between our earlier attempts and now is that I upgraded from DirSync to the new AD Connect tool so I'm assuming that might be the source of the problem (since the users that were created with the old DirSync tool are not getting this error).

I also had some issues with the user mailbox recreation but that has been resolved in this thread : https://community.office365.com/en-us/f/156/t/440238 

The steps I used so far for the migration are as following:

1. Migrated users from our local AD to Office365 through Dirsync
2. Ran the IMAP migration batch successfully (our email is hosted on a outside provider)
3. Upgraded from DirSync to AD Connect
4. Removed some users from the sync and then later added them back
5. Those specific users then had problems provisioning mailboxes since the AD Connect tool synced them with an old mailbox GUID (something that was disabled in DirSync but the AD Connect tool apparently re-enabled after upgrade)
6. Removed the users again, removed the GUID from the sync process and synced the users back (after which they were successfully provisioned a mailbox)
7. After running the IMAP migration batch (the same one from step 2) I am now getting the "MigrationRecipientNotFoundException" error for the newly created mailboxes

The mailboxes most certainly exist since I see them in the "Mailboxes" window in Office365 Admin ECP and I can also log into them through outlook.office365.com. When I run the "get-mailbox" command in Powershell I also get confirmation that those mailboxes exist.

Answer 1

Hi Igor,

Thanks for your feedback. We have confirmed with our related team that although in your situation, it is IMAP migration, the migration is also relevant to Exchange Online server. And our engineers are still deploying the fix.You can find the detailed information about this via the following thread.

https://community.office365.com/en-us/f/156/t/444366

However, as the workaround in the above thread is for Hybrid move based on mailbox guid, it cannot be applied to your situation because they are very different migration methods. Given this situation, another workaround what we can think of is to use PST file to migrate the affected mailbox occured in the error message above.

Many thanks,

Ran

Answer 2

Here is the exact message I get (I've edited my email in the error message):

Status: Failed

Skipped item details

Data migrated:

Migration rate:

Error: MigrationRecipientNotFoundException: A recipient wasn‎'t found for "myusername@mydomain" on the target. Create a recipient of the appropriate type for this migration on the target and try again.

The powershell command "Get-Mailbox -SoftDeletedMailbox" does not return the mailboxes I'm trying to import

Answer 3

Hi Igor,

Thanks for the elaboration. Regarding the error “MigrationRecipientNotFoundException”, can you share the screenshot so that we can know if it is same as the one we talked about the in thread below?

https://community.office365.com/en-us/f/156/t/444366

Meanwhile, please first run Get-Mailbox -SoftDeletedMailbox to list the deleted mailbox users and check if the mailboxes you deleted previously are listed here. Then run Remove-Mailbox -PermanentlyDelete to completely remove them. After, run a new IMAP migration batch to see if this can be resolved.

Best regards,

Ran

Answer 4

Maybe I didn't explain my situation well so I'll try to elaborate:

We have a local domain from which we synced our users to Office365 (through DirSync ) and assigned those users licences. We also have a ADFS setup running so the user authentication is going through our domain controller (which means that creating users on the Office365 side is just not an option).

Our email is hosted by a outside provider so I need to import the mailboxes from there to Office365 using the IMAP migration batch (I know there is also the PST import option but that brings its own complications).

In our first testing phase using DirSync the entire process went smoothly (both the user sync and the IMAP migration) but now that I've upgraded from DirSync to AD Connect I'm getting errors.

If I'm understanding your explanation correctly, the AD connect tool has some new exchange properties in the sync process and so it's no longer enough to remove only "msExchMailboxGuid" ?

Answer 5

Hi Igor,

Thanks so much for the detailed description. We don’t have related Official articles which support the scenario that in IMAP migration, creating Office 365 users via sync tool from AD. MS suggests creating users from Office 365 directly and assigning licenses. Meanwhile, since you previous had on-premises Exchange sever, the synced users are attached many Exchange related attributes not only the msExchMailboxGuid. This may cause failure of the IMAP migration. So, given this situation, we recommend you create users from Office 365 rather than syncing them from AD. If you have got a large number of users, you can use the article to add bulk users in the same time.

https://support.office.com/en-gb/article/Add-several-users-at-the-same-time-to-Office-365-Admin-Help-1f5767ed-e717-4f24-969c-6ea9d412ca88?CorrelationId=4d8a037b-2dcd-4fa2-b0bb-3b19c6f8fb8a&ui=en-US&rs=en-GB&ad=GB

After you move the MX to Office 365 and finish the IMAP migration batch, if you still want to keep DirSync which allow you to manage users from AD, you can delete IMAP mailboxes and server in AD and then perform the Soft match via the KB article below to match the Office 365 users and on-premises users.

https://support.microsoft.com/en-sg/kb/2641663

Best regards,

Ran