Updated June 28, 2022: Based on customer feedback, we have made the decision to provide additional time for organizations to prepare for the change. We have updated the rollout timeline below. Thank you for your feedback.
Updated June 1, 2022: Based on customer feedback, we have made the decision to provide additional time for organizations to prepare for the change. We have updated the rollout timeline below. Thank you for your feedback.
We’re making some changes to the way Name parameter is being set in Exchange Online. We will be making a change to utilize unique ExternalDirectoryObjectId (EDOID) in the place of Name parameter in Exchange Online only.
When this will happen
We will begin rolling this out in early September (previously late June) and expect to complete late October (previously late August).
How this impacts your organization
After this change administrators may no longer be able to see subsequent CN value change in Exchange on-premises to be reflected in the object’s Name property in Exchange Online.
The updated naming logic would take effect only during new user creation. Existing users won’t get impacted in any way.
Please note that since we will start using EDOID as Name in Exchange Online, we shall stop allowing changes in CN to reflect in Name property in Exchange Online for all users (both new and existing).
What you can do to prepare
We recommend that Administrators evaluate any scripts or other automation that may rely on the Name property and update them accordingly.
For additional details please refer Change in naming convention of user’s Name parameter.
Message ID: MC365786
Published: 30 April 2022
Updated: 28 June 2022
Action required by: 01 September 2022