Does changing the email field on the on-prem field cause Legacy DN Value?

Question

Does changing the email field on the on-prem field cause Legacy DN Value?

muhi-entra 0

Hello, We have a hybrid environment with on-premises AD syncing to their Azure AD We converted an on-prem user profile to External ID in Azure AD. As a result, sending party is receiving an NDR whenever they try to send an e-mail to this converted user. We later found out that the legacy DN value somehow changed during the conversion process, hence the reason the sending party receives a bounce back when they select the converted user from their outlook cached profile. Part of the procedure when we converted the user to External ID, we turned of Sync, changed the email field to match the external email address and then turned on Sync.

My question is: Does updating he email field cause the legacy DN value to change?
Does toggling the Sync option cause the legacy DN value to change?

Akhilesh Vallamkonda 15,320 Reputation points Microsoft External Staff Moderator

2024-02-02T02:25:05.4033333+00:00

@muhi-entra
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Akhilesh Vallamkonda 15,320 Reputation points Microsoft External Staff Moderator

2024-02-05T01:44:07.3166667+00:00

@muhi-entra
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jarvis Sun-MSFT 10,231 Reputation points Microsoft External Staff

2024-02-08T05:28:39.1466667+00:00

Just checking if there's any progress or updates? --please don't forget to upvote and Accept as answer if the reply is helpful--

2 answers

Your answer

Akhilesh Vallamkonda 15,320 Reputation points Microsoft External Staff Moderator

2024-02-02T02:25:05.4033333+00:00

@muhi-entra
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Akhilesh Vallamkonda 15,320 Reputation points Microsoft External Staff Moderator

2024-02-05T01:44:07.3166667+00:00

@muhi-entra
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jarvis Sun-MSFT 10,231 Reputation points Microsoft External Staff

2024-02-08T05:28:39.1466667+00:00

Just checking if there's any progress or updates? --please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 1

Hi @muhi-entra

Thank you for post!

The email field is a different attribute that can be modified without affecting the legacy DN value, so updating the email field does not cause the legacy DN value to change.

The Sync option allows the on-premises Active Directory objects to match the Entra ID Directory Objects Sync option and the legacy DN value are independent of each other and do not affect each other so toggling the Sync option does not effect the legacy DN value to change.

The other side receiving an NDR when sending an email to user could you please share the NDR message for the error code and the reason for the failure. Also let us know is the legacy DN value is change manually?

Answer 2

Andy David - MVP 157.8K MVP Volunteer Moderator

Throughout the years whenever you "convert" a mail-enabled object, it creates a new legacyExchangeDN for that object.

muhi-entra 0 Reputation points

2024-02-21T15:35:05.12+00:00

Hi Andy,

Thank you for your reply. I am sorry for not responding sooner. We have a bunch of mail enabled users in AD, we converted many so far and the only pattern here is that the NDR error is only happening with users where we had to manually change the e-mail field to reflect the external email address and then convert them to external. Other users that aren't experiencing this issue already had their external email address stamped to the email field, so we just simply converted them to external without updating the email field. Thanks,
Muhilan

Share via

Does changing the email field on the on-prem field cause Legacy DN Value?

2 answers

Your answer