SOLVED

Exchange Hybrid Mailbox Migration - RecipientNotFoundPermanentException

Copper Contributor

Exchange 2010 (14.3.468.0) is already setup as Exchange Hybrid with Office 365 and is working aswell. 

Unfortunately some mailbox migration fail.

RecipientNotFoundPermanentException:

Error: Cannot find a recipient that has mailbox GUID ‎'*************************‎'.

 

Log of failed migration:

 

'MigrationService (im Auftrag von "***")' created move request.
 'MigrationService (im Auftrag von "***")' allowed a large amount of data loss when moving the mailbox (*** bad items, *** large items).
 The Microsoft Exchange Mailbox Replication service '***.PROD.OUTLOOK.COM' (*** ServerCaps:***, ProxyCaps:***, MailboxCaps:, legacyCaps:***) is examining the request.
 Content from the Shard mailbox (Mailbox Guid: ***, Database: ***) will be merged into the target mailbox.
 Connected to target mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***.PROD.OUTLOOK.COM' Version *** (Build ***).
 Fatal error RecipientNotFoundPermanentException has occurred.

 

 

This also happens randomly to newly created mailboxes, that we try to test to migrate - some working, others not.

 

Log of successfully migrated mailbox.

 

'MigrationService (im Auftrag von "***")' created move request.
'MigrationService (im Auftrag von "***")' allowed a large amount of data loss when moving the mailbox (*** bad items, *** large items).
The Microsoft Exchange Mailbox Replication service '***.PROD.OUTLOOK.COM' (*** ServerCaps:***, ProxyCaps:***, MailboxCaps:, legacyCaps:***) is examining the request.
Content from the Shard mailbox (Mailbox Guid: ***, Database: ***) will be merged into the target mailbox.
Connected to target mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***' Version *** (Build ***).
Connected to source mailbox '***.onmicrosoft.com\*** (Primary)', database '***', Mailbox server '***' Version *** (Build ***), proxy server '***' *** ServerCaps:, ProxyCaps:, MailboxCaps:, legacyCaps:***.
Request processing started.

 

 

 

3 Replies

@Juakin 

 

Hi, is the test mailbox linked to the email address policy, and has the "user@domain.mail.onmicrosoft.com" attribute included as an email address?  The migration will certainly fail without this.

best response confirmed by Juakin (Copper Contributor)
Solution

Tried a lot of things to get this working.

 

In the end this worked out.

 

-Remove the Migration for the affected user.

-Remove the Mail user from the Organization\Retention Hold setup in Security and Compliance.

-Take backup of any OneDrive or any other data that exist for this user.

-Move the user into non Syncing OU in On Premise Exchange.

-Run the Delta Sync on the AAD connect Server Start-Adsyncsynccycle –PolicyType Delta

-Remove the MSOL user from the Recycle Bin: Remove-MsolUser -UserPrincipalName user@contoso.com -RemoveFromRecycleBin –Force

-Once done move the user back to syncing OU and run the Delta sync again on the AAD connect Server : Start-Adsyncsynccycle –PolicyType Delta

-Once the new mail user is synced to Office 365 begin the migration again for the affected user

@Juakin 

 

Thanks man. I had the same issue and your steps fixed it. Much appreciated. 

1 best response

Accepted Solutions
best response confirmed by Juakin (Copper Contributor)
Solution

Tried a lot of things to get this working.

 

In the end this worked out.

 

-Remove the Migration for the affected user.

-Remove the Mail user from the Organization\Retention Hold setup in Security and Compliance.

-Take backup of any OneDrive or any other data that exist for this user.

-Move the user into non Syncing OU in On Premise Exchange.

-Run the Delta Sync on the AAD connect Server Start-Adsyncsynccycle –PolicyType Delta

-Remove the MSOL user from the Recycle Bin: Remove-MsolUser -UserPrincipalName user@contoso.com -RemoveFromRecycleBin –Force

-Once done move the user back to syncing OU and run the Delta sync again on the AAD connect Server : Start-Adsyncsynccycle –PolicyType Delta

-Once the new mail user is synced to Office 365 begin the migration again for the affected user

View solution in original post