Office 365 Mail Migration: Exchange 2016 -> Office 365

Question

Office 365 Mail Migration: Exchange 2016 -> Office 365

BMallon 21

Overview:
I am currently trying to migrate a customer from Exchange 2016 to Office 365, in the past we have used BitTitan but this time I have chosen to use the Office365 Migration Wizard.
The company owns 2 domains and using the same alias for some accounts, for example ******@domain1.com.au and ******@domain2.com.au.

Error:
Am receiving the following conflict errors for accounts with same Alias

Error: MigrationProvisioningPermanentException: The name "accounts" is already being used. Please try another name. --> The name "accounts" is already being used. Please try another name.

BMallon 21 Reputation points

2021-11-29T06:22:54.257+00:00
If I run Get-Recipient | where {$_.EmailAddresses -match "accounts@"} | fL Name, RecipientType,emailaddresses on the Exchange server I can see the two mailboxes listed separately

Name : Mailbox Name RecipientType : UserMailbox EmailAddresses : {SMTP:******@domain1.com.au} Name : Mailbox Name RecipientType : UserMailbox EmailAddresses : {SMTP:******@domain2.com.au}

BMallon 21

I am no longer receiving the "is already being used error". Thank you all for your help, in the end I manually created the existing mailbox and restarted the migration. I am now receiving the following error, I suspect it is referencing an invalid object somewhere in Exchange, does anyone know how I can check and remove.

Error: MigrationProvisioningPermanentException: Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object. --> Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object.

BMallon 21

Conclusion:
Error 1:

Error: MigrationProvisioningPermanentException: The name "accounts" is already being used. Please try another name. --> The name "accounts" is already being used. Please try another name.

Solution:
Manually create ******@domain2.com.au and restart migration. (This is a bug in 365, these accounts should not have ever conflicted as different SMTP, Username and LegacyExchangeDN)

Error 2:

Error: MigrationProvisioningPermanentException: Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object. --> Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object.

Solution:
Conflicting Administrator account preventing migration of account, Administrator account was provided with delegated access to ******@domain2.com.au and since Admin@ hadn't migrated it was "invalid" in Office365. Rename conflicting Admin account, complete Admin migration, restart migration for ******@domain2.com.au

Accepted answer

2 additional answers

Your answer

BMallon 21 Reputation points

2021-11-29T06:22:54.257+00:00

If I run Get-Recipient | where {$_.EmailAddresses -match "accounts@"} | fL Name, RecipientType,emailaddresses on the Exchange server I can see the two mailboxes listed separately

Name : Mailbox Name RecipientType : UserMailbox EmailAddresses : {SMTP:******@domain1.com.au} Name : Mailbox Name RecipientType : UserMailbox EmailAddresses : {SMTP:******@domain2.com.au}
BMallon 21 Reputation points

2021-12-01T03:53:12.627+00:00

I am no longer receiving the "is already being used error". Thank you all for your help, in the end I manually created the existing mailbox and restarted the migration. I am now receiving the following error, I suspect it is referencing an invalid object somewhere in Exchange, does anyone know how I can check and remove.

Error: MigrationProvisioningPermanentException: Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object. --> Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object.
BMallon 21 Reputation points

2021-12-01T05:28:04.23+00:00

Conclusion:
Error 1:

Error: MigrationProvisioningPermanentException: The name "accounts" is already being used. Please try another name. --> The name "accounts" is already being used. Please try another name.

Solution:
Manually create ******@domain2.com.au and restart migration. (This is a bug in 365, these accounts should not have ever conflicted as different SMTP, Username and LegacyExchangeDN)

Error 2:

Error: MigrationProvisioningPermanentException: Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object. --> Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object.

Solution:
Conflicting Administrator account preventing migration of account, Administrator account was provided with delegated access to ******@domain2.com.au and since Admin@ hadn't migrated it was "invalid" in Office365. Rename conflicting Admin account, complete Admin migration, restart migration for ******@domain2.com.au

Answer 1

Amit Singh 5,306

The error message most likely refers to the name of an existing mailbox. This name is not visible through the web UI.

Connect to Exchange Online PowerShell or, if you're using MFA, Connect to Exchange Online PowerShell using multi-factor authentication.
List all existing mailboxes:
Get-Mailbox
If you have a lot of mailboxes and want just to see the problematic one:
Get-Mailbox | Where {$._Name -Match "some.one"}
This should show you the existing mailbox with the conflicting name. Rename it using Set-Mailbox:
Set-Mailbox some.one -Name SomeOne
Start your existing cutover migration batch again to re-try migrating the failed mailboxes.

You can test it at a later stage from your Office 365 portal or use tools like https://testconnectivity.microsoft.com.

Helpful links - Migrating Mailboxes from MS Exchange 2010 to Office 365.

Please mark as "Accept the answer" if the above steps helps you. Your suggestion will help others also !

BMallon 21

I am no longer receiving the "is already being used error". Thank you for your help, in the end I manually created the existing mailbox and restarted the migration. I am now receiving the following error, I suspect it is referencing an invalid object somewhere in Exchange, does anyone know how I can check and remove.

Error: MigrationProvisioningPermanentException: Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object. --> Failed to update one of the recipient properties. --> Couldn‎'t find object "/o=First Organization/ou=Exchange Administrative Group ‎(FYDIBOHF23SPDLT)‎/cn=Recipients/cn=Admin670". Please make sure that it was spelled correctly or specify a different object.

Answer 2

Hi @BMallon

I test your scenario in my environment and found the reason.

Firstly we can know that, a mailbox created in o365, the following email addresses are provided:
The user is provided with a primary SMTP address that's user@Company portal .com.
The user is provided with an alternate email address that's user@Company portal .onmicrosoft.com.

So when the first 'accounts' is migrated to o365, o365 will create the above two addresses for this user with no issue.

Then another 'accounts' from the second domain is migrated to o365, will still have the same address 'user@Company portal .onmicrosoft.com.' which is used already. That's why we will get the error" The name "accounts" is already being used. Please try another name.

However, if we manually create the user in o365 and select the second domain for this user, this account can be created successfully. That's because if we check the secondary email address for this user, we may find: the system will randomly add numbers after the name, it will be look like user1234@Company portal .onmicrosoft.com.

This change operated by system will not happen during the migration.

So the solution to such issue:

Change name, email address for one of the 'duplicate name' account. And note that this operation will lead to the mails sent to the old email address not received
Like you shared above, create the user with different domain in o365 manually.

And a related official document for your reference as well: "A user with this name already exists. Use a different name." error in the Office 365 portal

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Joyce Shen - MSFT 16,701

Hi @BMallon

Like the error states, you could not have same name accounts even they are not in same domain if you want to migrate them to o365

So we will need to rename one of these two accounts in, make sure 'accounts' not contained in Emailaddresses for that account as well.

We could make changes using EAC, and user logon name in ADUC

After changing this, the account will not show in result, then you could perform the migration again.

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

BMallon 21 Reputation points

2021-12-01T03:46:40.873+00:00

Hi Joyceshen,

This was my first thought, however in Office365 I have manually created the ******@domain2.com.au and didn't receive any errors, this makes me think there shouldn't be a conflict with the ******@domain1.com.au when migrating.

If I edit the users mailbox name they will no longer receive emails from customers who have saved their email address? Or can I keep the alias but just update the username?

Share via

Office 365 Mail Migration: Exchange 2016 -> Office 365

2 additional answers

Your answer