Share via

New Migration Errors: ProvisioningFailedException UserPrincipalName being used already

Anonymous
2016-01-10T01:15:39+00:00

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

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

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

12 answers

Sort by: Most helpful
  1. Anonymous
    2016-01-14T00:35:40+00:00

    Hi Greg,

    We have received the requested information via Private Message. We have engaged the relevant team to continue to assist you on this.

    You will be contacted via email for further troubleshooting. 

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-12T21:13:38+00:00

    Hi Greg,

    Given the situation, I will escalate the case to our relevant team for further troubleshooting. I have sent a private message to you to request tenant information. After getting that, the case will be escalated, and you will be contacted via email.

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-12T03:31:02+00:00

    Hi Johnny

    Sorry, exactly the same result, ran the cutover batch and the user that I deleted above is coming up with the same error -

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

    Can you please take a look in the back end.

    thanks, Greg

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-01-12T03:00:50+00:00

    Thanks Johnny

    1 - I have done this, only one occurence of the name

    2 - I have removed this user and removed it from the recycle bin and I have just started a new batch and will provide the output once it goes through

    3 - Sorry, It is not practical to import/export pst files as we have 870 users.

    4 - Yes our plan is not to use local mailboxes, the reason we need an incremental sync to still occur is we started using the mailboxes in office 365 and noticed the mail in some subfolders did not sync so we want to run the incremental sync again.

    Thanks, I will respond again once the batch produces some results.

    Greg

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-01-12T01:51:03+00:00

    Hi Greg,

    After doing more research, could you check the following points?

    1.  Regarding the error” Error: ProvisioningFailedException: The value "*** Email address is removed for privacy ***" of property "UserPrincipalName" is used by another recipient object. Please specify a unique value.”, could you run Get-MsolUser -UserPrincipalName *** Email address is removed for privacy *** using Azure PowerShell to check if there are more than one outputs?
    2.  Could you remove one of the impacted mailboxes in cloud, and hard delete the user? After doing that, please run a new cutover batch to see if the user mailbox can be migrated to Office 365 without any issue. If the issue persists, it could be related to back end. We will take further action.
    3.  Could you accept the situation that users export/import pst for impacted mailboxes? 
    4. The purpose of cutover will migrate all local mailboxes to cloud. As long term, it is not suggested you keep local mailboxes. 

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments