Missing x500 or LegacyExchangeDN from source mailbox

Question

Missing x500 or LegacyExchangeDN from source mailbox

Arve 76

Hi,

I get the following error when running a migration batch with one user.
One or more X500 proxy addresses or legacyExchangeDN of source mailbox are missing on target MEU as X500 proxy address.

The source does not contain any x500 addresses.
The other emailaddresses are the same on both source mailbox and target mailuser.

Must I create a X500 address on both source and tenant?
Or is there something else that might be the problem of this?

Joyce Shen - MSFT 16,416 Reputation points Microsoft Vendor

2022-04-12T06:33:40.42+00:00

Hi @Arve ,

For the email address type, we could check the introduction below:

And according to my research, the SPO address has something to do with the switch to using EWS for sending any SharePoint related notifications. And they are automatically added to any licensed mailbox, so no shared or room mailboxes should have them. It also seems that those addresses are not added immediately upon user creation, and might appear only after the user has explicitly shared a document.

And the address can be edited, removed or added just like a regular SMTP address, however for objects synced from the on-prem AD this will not be possible (although they do get the address as well!)
So you could make a backup before editing them.

Here is a related arcticle you could take a reference: New type of addresses in Office 365 (SPO)
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

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.

Joyce Shen - MSFT 16,416 Reputation points Microsoft Vendor

2022-04-12T06:33:40.42+00:00

Hi @Arve ,

For the email address type, we could check the introduction below:

And according to my research, the SPO address has something to do with the switch to using EWS for sending any SharePoint related notifications. And they are automatically added to any licensed mailbox, so no shared or room mailboxes should have them. It also seems that those addresses are not added immediately upon user creation, and might appear only after the user has explicitly shared a document.

And the address can be edited, removed or added just like a regular SMTP address, however for objects synced from the on-prem AD this will not be possible (although they do get the address as well!)
So you could make a backup before editing them.

Here is a related arcticle you could take a reference: New type of addresses in Office 365 (SPO)
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

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 1

Andy David - MVP 120.5K MVP

See:
https://techcommunity.microsoft.com/t5/microsoft-365-blog/cross-tenant-mailbox-migration-in-now-in-public-preview/ba-p/1692465

Arve 76 Reputation points

2022-04-11T12:27:12.673+00:00

The only difference I find is that on the target the type is written in lowercase letters, spo, sip, smtp etc.
But on the source it's all uppercase. SPO, SIP, SMTP.

I will change them to be uppercase if it is possible on the target as well, and see if that may help.
Arve 76 Reputation points

2022-04-11T12:41:35.2+00:00

The difference was only that reply addresses is uppercase, and the rest are lowercase.

The target now has two SPO addresses. Should I keep the one that is identical with the source SPO and delete the other one? Or is it ok to keep both?

Missing x500 or LegacyExchangeDN from source mailbox

0 additional answers

Activity