New Migration Errors: ProvisioningFailedException UserPrincipalName being used already

Question

Hi

We recently migrated mailboxes to office 365 with a few errors which caused the migration to keep stopping and needing to click resume. We thought all boxes had been migratedfrom what we could see so deleted the batch. We have found some mailboxes are missing email in some subfolders so we are trying to run the cutover migration again to enable a resync of missing mail. All accounts are the same and no new ones have been created (as we are a school and on holidays for a few more weeks).

With the new cutover migration we are getting the following error on most accounts: 

Error: ProvisioningFailedException: The value "*** Email address is removed for privacy ***" of property "UserPrincipalName" is used by another recipient object. Please specify a unique value. 

It has this error but recognises previous syncs as it has a last sync date for each email address and a number listed in synced items so knows the right account.

Can someone please take a look for me or is there a sync team that can look in to the data for us please.

Many thanks

Greg

Answer 1

I have started the migration again and getting the same errors, 580 or so of them provisioning failed errors which seems to happen during the incremental sync, do you have any more suggestions or can it be esculated?

Thanks, Greg

Answer 2

Thanks, I have checked and no users in deleted users. It seems to be that when I created the migration batch again, It is only partially recognising the existing users. It knows they already exist as each has a number of synced items, it just wont do the incremental sync for them and causes an error.

Any other ideas of how to tidy it up before trying a new migration batch, I dont want to remove users as we have already migrated around 400GB of user data and the new office 365 emails are being used.

thanks, Greg

Answer 3

Hi Greg,

Thanks for the information provided in PM.

The issue is most likely to be related to the incremental synchronizations. Could you check if there are any deleted users in Office 365 portal? If yes, please hard delete them via the following steps before you run cutover batch:

1.  Connect to Azure AD

msdn.microsoft.com/.../jj151815.aspx   

2.  Please perform the following cmdlets to hard delete the user.

1). Remove-MsolUser -UserPrincipalName *** Email address is removed for privacy ***

2). Remove-MsolUser -UserPrincipalName *** Email address is removed for privacy *** -RemoveFromRecyclebin

If there are no deleted users in Office 365 portal, I would like to confirm if you have made any changes for local AD objects or Cloud mailboxes during cutover migration.

Thanks,

Johnny Zhang

Answer 4

Thanks Johnny, I have sent you a private message with the output of those commands as requested, I appreciate your help.

Answer 5

Hi Greg,

To check the issue, please view the details in the right part of the migration batch page, and select one of the impacted user mailboxes. Then you can use Exchange Online PowerShell to run the following cmdlet.

Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FL 

Get-MigrationStatistics | fl

Get-MigrationBatch -Identity "the batch name"

I have sent a private message to you to request them.

Please click on the link below to access to your Private Message.

">community.office365.com/.../conversations 

Regards,

Johnny Zhang