check before: 2022-09-01
Product:
Exchange
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Updated message
Links:
Details:
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.
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).
Change Category:
XXXXXXX ...
Scope:
XXXXXXX ...
Release Phase:
Created:
2022-04-30
updated:
2022-08-27
the free basic plan is required to see all details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
changes*
| Date | Property | old | new |
| 2022-09-15 | MC 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. ps://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name-parameter/ba-p/3284733/ | 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. https://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name-parameter/ba-p/3284733/ |
| 2022-08-27 | MC 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. https://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name-parameter/ba-p/3284733/ | 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. ps://techcommunity.microsoft.com/t5/exchange-team-blog/change-in-naming-convention-of-user-s-name-parameter/ba-p/3284733/ |
| 2022-06-29 | MC Last Updated | 06/01/2022 19:06:03 | 2022-06-28T20:19:32Z |
| 2022-06-29 | MC Messages | 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 late June (previously late May) and expect to complete late August (previously late July). [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). | 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.
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). |
| 2022-06-29 | MC Action Required By | 06/30/2022 09:00:00 | 2022-09-01T09:00:00Z |
| 2022-06-29 | MC End Time | 09/30/2022 09:00:00 | 2022-11-30T08:00:00Z |
| 2022-06-02 | MC MessageTagNames | Admin impact | Updated message, Admin impact |
| 2022-06-02 | MC Last Updated | 04/30/2022 02:36:12 | 2022-06-01T19:06:03Z |
| 2022-06-02 | MC Messages | 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 late May and expect to complete late July [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). | 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 late June (previously late May) and expect to complete late August (previously late July). [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). |
| 2022-06-02 | MC Action Required By | 05/31/2022 09:00:00 | 2022-06-30T09:00:00Z |
| 2022-06-02 | MC Title | Configuration Change in Name parameter for Exchange Online | (Updated) Configuration Change in Name parameter for Exchange Online |
| 2022-06-02 | MC End Time | 08/31/2022 09:00:00 | 2022-09-30T09:00:00Z |
*starting April 2022
Last updated 12 months ago
