Change in naming convention of user’s Name parameter

Published Apr 13 2022 09:05 AM 40.4K Views

We want to inform you about a change that we are working on. This change will be rolled out in a phased manner. Update: based on feedback that has been provided, we have made the decision to delay this change. We will provide an updated timeline by end of April and deliver related communication in Message Center to allow customers to assess the impact of this change on their organization in advance of the change rolling out.

The Name parameter associated with a user within a tenant in Exchange Online should be unique. However, while we sync objects from Azure Active Directory to Exchange Online, the way Name parameter is being evaluated currently led to some conflicts. We realized that the current method is not the best method to compute this parameter. Hence, we want to move away from current method to a more robust way of generating the Name parameter which is through ExternalDirectoryObjectId (EDOID).

EDOID value is unique. We’ll use this GUID as Name instead of synchronizing the Name from on-premises or using the alias (if Name is not specified) to compute the Name parameter in Exchange Online. With this change the DistinguishedName (DN) value will also get impacted. To better understand how this will impact objects in a tenant where directory synchronization is enabled, consider the following example:

With this new change, when creating a new Office 365 (remote) mailbox from on-premises Exchange Admin Center, the Name field will no longer synchronize to Exchange Online.

NamePropChange.jpg

Before changes are implemented:
DisplayName: Jeff Smith
Name: Jeff Smith
Alias: jsmith
DistinguishedName: CN= Jeff Smith,OU=(tenant).onmicrosoft.com, OU=Microsoft Exchange Hosted Organizations, DC=NAMP283A001, DC=PROD,DC=OUTLOOK, DC=COM
ExternalDirectoryObjectId: 12313c53-fff7-46d4-8b83-71fb317d1853

After changes are implemented:

DisplayName: Jeff Smith
Name: 12313c53-fff7-46d4-8b83-71fb317d1853
Alias: jsmith
DistinguishedName: CN= 12313c53-fff7-46d4-8b83-71fb317d1853, OU=(tenant).onmicrosoft.com, OU=Microsoft Exchange Hosted Organizations, DC=NAMP283A001, DC=PROD, DC=OUTLOOK, DC=COM 

In this example, both the Name and DistinguishedName are updated with the EDOID value.

Note: This would also mean that any subsequent CN value change in Exchange on-premises will not be reflected in the object’s Name property in Exchange Online.

Will this change not allow modification of the Name property?
Customers can still use Exchange PowerShell cmdlets (New-MailUser, New-Mailbox, Set-User, Set-MailUser, Set-Mailbox with -Name parameter) to update the Name property in Exchange Online. Since the cmdlets ensure uniqueness, it would allow the operation to succeed only when the passed Name is unique in the tenant. 

How will the change impact new and existing users?
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). 

We recommend that Administrators evaluate any scripts or other automation that may rely on the Name property and update them accordingly.

Exchange Online Team

45 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-3302458%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3302458%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%20so%20many%20comments%20on%20here%2C%20especially%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203797%22%20target%3D%22_blank%22%3E%40Kevin%20Marquette%3C%2FA%3E.%26nbsp%3B%20It%20would%20cause%20much%20less%20of%20an%20issue%20if%20MS%20would%20just%20create%20a%20new%20attribute%20and%20go%20that%20route%20versus%20renaming%20an%20existing%20(and%20often%20used)%20attribute.%26nbsp%3B%20We%20have%20dozens%20of%20onboarding%2C%20offboarding%2C%20maintenance%2C%20etc.%20scripts%20out%20there%20that%20run%20on%20a%20schedule%2C%20now%20we%20have%20to%20go%20through%20each%20one%20to%20make%20sure%20that%20they%20all%20continue%20working%3F%26nbsp%3B%20And%20then%20combine%20that%20with%20the%20fact%20that%20this%20change%20will%20only%20impact%20some%20(new)%20objects%2C%20not%20existing%20ones!%26nbsp%3B%20Which%20sound%20to%20me%20like%20we'll%20have%20to%20also%20come%20up%20with%20some%20new%20try%2Fcatch%20stuff%20to%20test%20whether%20an%20object%20is%20using%20the%20old%20Name%20attribute%20or%20the%20new%26nbsp%3BEDOID%20attribute.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3302222%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3302222%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20Microsoft%20will%20reconsider%20this%2C%20as%20it%20seems%20poorly%20thought-out%20conceptually%2C%20and%20will%20only%20lead%20to%20massive%20confusion%20going%20forward.%26nbsp%3B%20Name%20should%20be%20some%20derivative%20of%20a%20human-friendly%20name%2C%20not%20an%20ugly%20number%20field.%26nbsp%3B%20Why%20not%20simply%20add%20(yet%20another)%20field%20to%20the%20EO%20record%20that%20we%20admins%20can%20gleefully%20ignore%20as%20it%20doesn't%20relate%20to%20our%20day-to-day%20work%2C%20instead%20of%20mucking%20about%20with%20a%20field%20that%20we%20may%20have%20built%20dependencies%20on%20in%20our%20scripting%3F%26nbsp%3B%20Yeah%2C%20great%2C%20I%20SOOOO%20look%20forward%20to%20trawling%20throught%20all%20my%20bits%20and%20bobs%20of%20scripts%20looking%20for%20spots%20where%20I've%20used%20Name%20and%20changing%20them%20to%20use%20something%20else.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3302051%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3302051%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EPlease%20reconsider%26nbsp%3Bthis%20change!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20want%20to%20change%20a%20common%20attribute%20like%20'Name'%20into%20a%20Guid%3F%20It%20makes%20no%20sense.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20you%20will%20create%20a%20mess%20because%20you%20write%3A%20%22Existing%20users%20won%E2%80%99t%20get%20impacted%20in%20any%20way%22.%26nbsp%3B%3CBR%20%2F%3ESo%20we%20will%20end%20up%20in%20a%20mess%20with%20existing%20account%20a%20decent%20name%20and%20new%20accounts%20with%20Guid%3F%3CBR%20%2F%3EWhy%20not%20use%20any%20of%20the%20your%20other%20unique%20fields%20of%20a%20mailbox%20you%20already%20have%3F%3CBR%20%2F%3ELike%3A%3CBR%20%2F%3EExchangeGuid%3CBR%20%2F%3ESamAccountName%3CBR%20%2F%3EExternalDirectoryObjectId%3CBR%20%2F%3ELegacyExchangeDN%3CBR%20%2F%3EExchangeObjectId%3CBR%20%2F%3EGuid%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYou'll%20harm%20no%20one%20that%20way!%3CBR%20%2F%3EAgain%3A%20Please%20reconsider%20this%20change!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301897%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301897%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20seems%20a%20very%20half%20assed%20way%20of%20handling%20a%20minor%20issue.%20Why%20on%20earth%20are%20you%20targetting%20an%20attribute%20that%20is%20commonly%20used%20and%20has%20been%20so%20for%20years.%3C%2FP%3E%3CP%3EWe%20sync%20around%2065k%20staff%20and%20350k%20students%20and%20make%20use%20of%20the%20name%20field%20and%20have%20done%20so%20for%20years%2C%20now%20you're%20saying%20we%20need%20to%20investigate%20and%20remediate%20your%20change%20in%20the%20space%20of%20a%20few%20weeks.%20This%20is%20ludicrous%20and%20puts%20a%20ridiculous%20amount%20of%20pressure%20on%20us.%3C%2FP%3E%3CP%3EA%20change%20this%20impactful%20should%20have%20a%20much%20longer%20lead%20time%20and%20advance%20notice.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301874%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301874%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E...instead%20of%20synchronizing%20the%20Name%20from%20on-premises...%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CBLOCKQUOTE%3E%3CP%3E...when%20creating%20a%20new%20Office%20365%20(remote)%20mailbox%20from%20on-premises...%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EIf%20I%20read%20between%20the%20lines%20here%2C%20especially%20the%20reference%20to%20%22%3CSPAN%3Esync%20objects%20from%20Azure%20Active%20Directory%20to%20Exchange%20Online%22%3C%2FSPAN%3E%2C%20I'm%20guessing%20that%20this%20change%20is%20happening%20at%20that%20point%3F%26nbsp%3B%20So%20for%20cloud-only%20customers%2C%20it%20will%20mean%20when%20new%20accounts%20are%20created%20with%20a%20mailbox%2C%20they%20will%20have%20in%20Exchange%20Online%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExternalDirectoryObjectId%20%3D%20AzureAD's%20ObjectID%3C%2FP%3E%3CP%3EName%20%3D%20EDOID%3C%2FP%3E%3CP%3EDistinguishedName's%20CN%20%3D%20EDOID%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20that%20afterwards%2C%20Name%20can%20be%20changed%2C%20but%20the%20CN%20component%20of%20the%20DN%20cannot%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOr%20is%20this%20being%20done%20in%20AzureADConnect%20somehow%2C%20and%20will%20have%20no%20impact%20on%20me%3F%26nbsp%3B%20You've%20tagged%20%22Hybrid%22%20specifically%2C%20and%20your%20examples%20are%20all%20hybrid%2C%20so%20maybe%20this%20means%20it%20won't%20affect%20me%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301745%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301745%22%20slang%3D%22en-US%22%3E%3CP%3EBecause%20they%20want%20to%20pivot%26nbsp%3B%20in%20their%20current%20journey%20to%20accommodate%20the%20latest%20asks%20from%20stakeholders%20so%20they%20can%20close%20the%20loop%22%20and%20synergize%20while%20leveraging%20blue%20sky%20opportunities%20being%20brought%20to%20the%20table%20by%20scalable%20vertical%20deep%20dives.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301704%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301704%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wouldn't%20call%20it%20%22AD%20Sync%22%20if%20it's%20going%20to%20write%20different%20values%20in%20the%20attributes%20in%20Azure.%20Come%20on%20Microsoft%2C%20this%20is%20ridiculous.%20This%20isn't%20going%20to%20fix%20much%2C%20but%20it%20is%20guaranteed%20to%20break%20a%20lot%20of%20things.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301687%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301687%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20change%20doesn't%20make%20sense.%20Why%20would%20the%20DN%20and%20Name%20suddenly%20be%20changed%20to%20a%20random%20ID%20when%20it's%20always%20been%20the%20Name%20in%20on-premises%20AD%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301637%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301637%22%20slang%3D%22en-US%22%3E%3CP%3EWow!%20Perfect%20example%20of%20MS%20teams%20working%20in%20a%20vacuum!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20no%20information%20provided%20on%20how%2C%20or%20if%2C%20this%20affects%20scripted%20processes%20that%20sync%20on-prem%20AD%20with%20Azure%20AD.%3C%2FP%3E%3CP%3EWe%20have%20custom%20automation%20that%20integrates%20with%20our%20ERP%20system%20and%20creates%20and%20updates%20on-prem%20AD%20accounts%20nightly%2C%20which%20then%20sync%20out%20to%20Azure%20AD.%20It's%20currently%20one-way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20the%20fact%20that%20we%20don't%20currently%20populate%20the%20corresponding%20AD%20property%20(ms-DS-ExternalDirectoryObjectID)%20create%20issues%20when%20we%20sync%20out%20to%20Azure%20AD%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20we%20now%20need%20to%20pick%20this%20up%20when%20Exchange%20accounts%20are%20created%20and%20synch%20EDOID%20back%20to%20on-prem%20accounts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301630%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301630%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20I'm%20seeing%20others%20say%20-%20I%20don't%20understand%20why%20the%20problem%20is%20being%20%22solved%22%20in%20this%20way%2C%20and%20it's%20not%20clear%20when%20the%20updated%20deadline%20is%20even%20though%20the%20article%20mentions%20one.%26nbsp%3B%3CBR%20%2F%3EIt%20seems%20that%20this%20change%20has%20the%20potential%20to%20disrupt%20some%20of%20the%20scripts%20that%20we%20use%2C%20and%20the%20from%20the%20article%20I%20do%20not%20understand%20what%20I%20need%20to%20do%20in%20order%20to%20get%20my%20scripts%20%22ready%22%20for%20this%20change.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anyone%20have%20information%20on%20the%20updated%20deadline%20for%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301501%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301501%22%20slang%3D%22en-US%22%3E%3CP%3ELeave%20it%20to%20MS%20to%20use%20a%20common%20AD%20field%20that%20effects%20everything%20we%20set%20up%20code%20based%20into%20an%20ambiguous%20mess.%20Doesn't%20it%20make%20sense%20to%20make%20the%20unique%20field%20something%20that%20isn't%20mandatory%20to%20set%20up%20in%20programmatically%20creating%20AD%20Accounts%20but%20can%20be%20a%20property%20of%20the%20main%20account%20(like%20suggested%20above%2C%20ID%20for%20instance).%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGiving%20us%20a%20month%20to%20prepare%20without%20some%20kind%20of%20testing%20to%20see%20how%20our%20environment%20will%20be%20effected%20seems%20like%20a%20recipe%20for%20disaster.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301461%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301461%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20would%20a%20NAME%20field%20need%20to%20be%20unique%3F%20Why%20was%20that%20logic%20built%20into%20Exchange%20Online%2C%20and%20why%20are%20you%20still%20enforcing%20it%3F%20The%20actual%20fix%20would%20be%20to%20not%20require%20NAME%20to%20be%20unique.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEven%20two%20or%20three%20months%20notice%20is%20not%20enough%20time%20to%20identify%20everywhere%20this%20change%20can%20break%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301442%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301442%22%20slang%3D%22en-US%22%3E%3CP%3EA%20change%20this%20significant%2C%20and%20unintuitive%2C%20warrants%20some%20explanation%20as%20to%20the%20reasoning%20behind%20it%20I%20think.%26nbsp%3B%20It%20stands%20to%20reason%20that%20if%20Azure%20AD%20Connect%20is%20synchronizing%20values%20from%20on-prem%20and%20they%20are%20unique%20there%2C%20then%20they%20would%20be%20unique%20in%20the%20cloud%20as%20well.%26nbsp%3B%20Are%20you%20just%20trying%20to%20cut%20down%20on%20compute%20time%20for%20replication%2C%20or%20is%20there%20some%20kind%20of%20failure%20occurring%20regularly%20because%20the%20directory%20object%20is%20being%20renamed%2Fmoved%20with%20a%20change%20in%20CN%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20really%20going%20to%20start%20seeing%20that%20GUID%20twice%20in%20the%20output%20of%20Get-Mailbox%2C%20which%20by%20default%20shows%20Name%20and%26nbsp%3B%3CSPAN%3EExternalDirectoryObjectId%3F%26nbsp%3B%20Could%20it%20have%20something%20else%20included%20instead%20(like%20DisplayName)%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EGiven%20that%20Name%2FCN%20is%20the%20output%20of%20some%20cmdlets%20(some%20already%20mentioned%20by%20others%2C%20and%20AcceptMessagesOnlyFrom%20comes%20to%20my%20mind%20from%20get-mailbox)%2C%20it%20makes%20it%20very%20difficult%20(or%20at%20least%20inefficient%2C%20increasing%20the%20number%20of%20calls%20to%20the%20cloud%20to%20resolve%20EDOID%20to%20Alias%2C%20etc.)%20to%20locate%20an%20on-prem%20user%20from%20EXO%20PowerShell%20output%20since%20EDOID%20isn't%20written%20locally.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHopefully%20the%20goofy%20mismatch%20between%20old%20and%20new%20accounts%20won't%20be%20visible%20to%20end-users%20(I%20don't%20believe%20it%20would%20be).%26nbsp%3B%20But%20once%20Name%20goes%20read-only%2C%20I%20hope%20there%20aren't%20any%20Exchange%20admins%20out%20there%20who%20are%20divorced%20from%20an%20abusive%20spouse%20and%20just%20can't%20get%20rid%20of%20that%20remaining%20reference%20on%20their%20own%20account.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301435%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301435%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20doesn't%20make%20any%20sense.%26nbsp%3B%20I've%20had%203%20or%204%20sync%20conflicts%20in%208%2B%20years%2C%20all%20easily%20fixed.%26nbsp%3B%20This%20'solution'%20will%20cost%20me%20at%20least%20a%20week%20of%20reviews.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301398%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301398%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20low-quality%20workaround%20for%20a%20problem%20caused%20by%20a%20previous%20low-quality%20workaround.%20Fix%20this%20the%20right%20way%2C%20don't%20arbitrarily%20repurpose%20data%20fields%20with%20existing%20meanings.%20This%20is%20like%20deciding%20to%20store%20email%20addresses%20in%20the%20middle%20name%20field.%20It's%20DUMB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301384%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301384%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20this%20cause%20problems%20for%20SAML%20applications%3F%20They%20pull%20in%20information%20from%20Azure%20AD%20and%20not%20Exchange%20Online.%20Can%20there%20be%20clarifications%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301369%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301369%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20this%20change%20affect%20the%20users%20that%20are%20created%20in%20On-Site%20Active%20Directory%20and%20synchronized%20with%20Azure%20Active%20Directory%20via%20the%20Azure%20Active%20Directory%20Connector%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301340%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301340%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20this%20affect%20Azure%20AD%20Connect%20or%20on%20prem%20Exchange%20only%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301327%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301327%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20as%20worthless%20as%20a%20NFT%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301322%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301322%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20%3CU%3Estrongly%3C%2FU%3E%20urge%20the%20Exchange%20Team%20to%20reconsider%20this%20change%20as%20other%20have%20suggested.%20I'm%20of%20the%20opinion%20this%20is%20going%20to%20create%20more%20problems%20than%20it%20solves.%20Surely%20there%20is%20a%20better%20way%20to%20address%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301277%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301277%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20real%20problem.%26nbsp%3B%20Per%20multiple%20vendor%20recommendations%20(including%20Microsoft)%2C%20we%20use%20Name%20field%20in%20External%20Applications%2FSAML.%26nbsp%3B%20Name%20field%20should%20contain%20name.%26nbsp%3B%20Recycling%20fields%20is%20flat%20file%20database%20era%20nonsense.%26nbsp%3B%20If%20a%20new%20field%20is%20needed%2C%20create%20one.%26nbsp%3B%20This%20is%20extensible%20architecture.%26nbsp%3B%20I%20suspect%20they%20wanted%20to%20change%20CN%20and%20a%20lot%20of%20internal%20coding%20linked%20CN%20and%20Name.%26nbsp%3B%20Instead%20of%20fixing%20the%20code%2C%20pass%20the%20problem%20off%20to%20the%20customer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhere%20do%20we%20vote%20to%20stop%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301142%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301142%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20if%20a%20colleague%20marries%20(or%20divorces%2C%20for%20example)%20and%20her%20last%20names%20changes%2C%20or%20on%20account%20creation%20there%20is%20a%20spelling%20error%20that%20needs%20to%20be%20corrected%2C%20we%20need%20to%20get%20our%20Frontoffice%20team%20to%20make%20a%20change%20in%20the%20appropriate%20fields%20in%20the%20on%20premises%20environment%20and%20that%20is%20not%20the%20end%20of%20it%2C%20we%20need%20to%20get%20our%20Backoffice%20team%20to%20make%20those%20same%20changes%20in%20the%20Exchange%20Online%20environment%20(as%20our%20Frontoffice%20team%20does%20not%20have%20those%20permissions).%20Or%20am%20I%20missing%20something%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3301055%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3301055%22%20slang%3D%22en-US%22%3E%3CP%3EMay%20I%20please%20endorse%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203797%22%20target%3D%22_blank%22%3E%40Kevin%20Marquette%3C%2FA%3E's%20comment%20-%20I%20feel%20very%20strongly%20that%20re-using%20an%20existing%20field%20that%20people%20are%20already%20using%2Frelying%20on%20is%20just%20crazy%20-%20create%20a%20new%20field%20to%20use%20for%20this!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EKevin%20Marquette%20MVP%3CBR%20%2F%3E%E2%80%8EApr%2030%202022%2002%3A02%20PM%3CBR%20%2F%3EWhy%20are%20you%20not%20just%20adding%20a%20%60EDOID%60%20or%20an%20%60ID%60%20property%3F%20By%20reusing%20the%20Name%20field%20in%20this%20way%2C%20it%20will%20be%20really%20hard%20to%20tell%20what%20code%20has%20been%20updated%20or%20not.%3C%2FP%3E%3CP%3EI%20would%20much%20prefer%20that%20the%20Name%20field%20become%20read-only%20and%20eventually%20removed%20than%20reuse%20it%20for%20the%20EDOID.%20This%20will%20give%20very%20clear%20errors%20when%20used%20incorrectly.%20There%20are%20going%20to%20be%20lots%20of%20random%20admin%20scripts%20that%20break%20because%20of%20this.%20Even%20if%20we%20update%20everything%2C%20there%20are%20years%20of%20online%20examples%20and%20documentation%20that%20will%20be%20out%20of%20date.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3300757%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300757%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20get%20a%20Principal%20Engineer%20review%20on%20this%20from%20someone%20outside%20the%20team%20implementing%20this%20approach.%20And%20take%20into%20consideration%20the%20long%20term%20confusion%20this%20will%20create%20for%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3300407%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300407%22%20slang%3D%22en-US%22%3E%3CP%3EA%20notification%20arrived%20at%20the%20message%20center%20on%204%2F30%2F22.%3CBR%20%2F%3EThe%20change%20deadline%20is%205%2F31%2F22.%3CBR%20%2F%3EThis%20article%20was%20updated%20on%204%2F28%2F22.%3CBR%20%2F%3EWhen%20is%20the%20updated%20deadline%3F%3CBR%20%2F%3EAfter%20all%2C%20the%20deadline%20for%20changes%20is%20short.%20Also%2C%20I%20don't%20think%20you%20should%20assign%20an%20EDOID%20to%20the%20Name%20property.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3300238%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300238%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203797%22%20target%3D%22_blank%22%3E%40Kevin%20Marquette%3C%2FA%3E%26nbsp%3BI%20can%20only%20like%20your%20comment%20once%20but%20I%20sincerely%20hope%20Microsoft%20considers%20your%20suggestion%20as%20a%20viable%20alternative.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3299558%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3299558%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20are%20you%20not%20just%20adding%20a%20%60%3CSPAN%3EEDOID%60%20or%20an%20%60ID%60%20property%3F%20By%20reusing%20the%20Name%20field%20in%20this%20way%2C%20it%20will%20be%20really%20hard%20to%20tell%20what%20code%20has%20been%20updated%20or%20not.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20much%20prefer%20that%20the%20Name%20field%20become%20read-only%20and%20eventually%26nbsp%3Bremoved%20than%20reuse%20it%20for%20the%20EDOID.%20This%20will%20give%20very%20clear%20errors%20when%20used%20incorrectly.%26nbsp%3BThere%20are%20going%20to%20be%20lots%20of%20random%20admin%20scripts%20that%20break%20because%20of%20this.%20Even%20if%20we%20update%20everything%2C%20there%20are%20years%20of%20online%20examples%20and%20documentation%20that%20will%20be%20out%20of%20date.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3292209%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3292209%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EWill%20you%20update%20Exchange%20commands%20to%20return%20useful%20data%20once%20Name%20becomes%20a%20non-readable%20string%20for%20end-user%20%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3EManager%3C%2FSTRONG%3E%20from%20Get-User%2C%20%3CSTRONG%3EGrantSendOnBehalfTo%3C%2FSTRONG%3E%20from%20Get-Mailbox%20and%20many%20others.%3C%2FP%3E%3CP%3EWe%20have%20many%20self-service%20tools%20exposed%20to%20users%20to%20do%20various%20reporting%20in%20Exchange%20Online%2C%20many%20of%20these%20tools%20take%20direct%20output%20from%20the%20Name%20attribute%20(so%20no%20other%20output%20is%20available)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3289711%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3289711%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20you%20rename%20the%20%22Name%22%20field%20as%20well%3F%20As%20having%20field%20%22Name%22%20but%20containing%20EDOID%20sounds%20not%20so%20logical.%3C%2FP%3E%3CP%3ENot%20sure%2C%20but%20could%20there%20be%20companies%20which%20are%20using%20Name%20field%20as%20an%20address%20policies%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWas%20this%20really%20%3CSTRONG%3Ethe%3C%2FSTRONG%3E%20only%20option%20to%20fix%20this%3F%20As%20after%20this%20there%20would%20be%20quite%20confuses%20mailboxes%20when%20old%20mailboxes%20have%20old%20name%20format%2C%20and%20then%20new%20mailboxes%20have%20something%20else.%20Or%20are%20you%20planning%20to%20rename%20old%20mailboxes%20as%20well%2C%20even%20those%20which%20are%20duplicates%3F%20What%20about%20other%20objects%2C%20will%20this%20impact%20to%20them%20as%20well%2C%20like%20MailUser%2C%20Contacts%20etc..%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3288260%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3288260%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181580%22%20target%3D%22_blank%22%3E%40Rob%20Roettger%3C%2FA%3E%26nbsp%3BYES!%20correct.%20I%20edited%20the%20comment.%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2F%40FE3C8A5543DEF164D4C09E9B7F45E1A4%2Fimages%2Femoticons%2Ffacepalm_40x40.gif%22%20alt%3D%22%3Afacepalm%3A%22%20title%3D%22%3Afacepalm%3A%22%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3288217%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3288217%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%22We%20recommend%20that%20Administrators%20evaluate%20any%20scripts%20or%20other%20automation%20that%20may%20rely%20on%20the%20Name%20property%20and%20update%20them%20accordingly.%22%3C%2FEM%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3EApril%202022%20-%20Don't%20you%20think%20its%20too%20short%20of%20a%20notice%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3EDoes%20it%20impact%20other%20objects%20like%20MailUsers%2C%20Distribution%20Groups%2C%20MailContacts%20%2C%20etc.%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3EAlmost%20all%20cmdlets%20have%20'Name'%20as%20the%20default%20output%2C%20and%20useful%20for%20a%20quick%20check%20without%20much%20of%20typing%20currently%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Get-Recipient%20%22A%20A%22%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Name%20RecipientType%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20----%20-------------%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20A%20A%20UserMailbox%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20get-mailbox%20%22A%20A%22%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Name%20Alias%20Database%20ProhibitSendQuota%20ExternalDirectoryObjectId%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20----%20-----%20--------%20-----------------%20-------------------------%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20A%20A%20A.A%20xxxPR01DG189-db020%201.979%20GB%20(2%2C125%2C4...%20xxxxx..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EMany%20outputs%20like%20SendOnBehalf%2C%20and%20Manager%20fields%2C%20doesn't%20even%20store%20full%20details%2C%20relies%20solely%20on%20this%3C%2FLI%3E%3CLI%3EExisting%20data%20vs.%20new%20data%20having%20mixed%20up%20values%20will%20cause%20lot%20of%20disruptions%3C%2FLI%3E%3CLI%3EAny%20options%20for%20opt%20out%2C%20for%20companies%20having%20a%20robust%20system%20and%20doesn't%20get%20into%20this%20sync%20error%20often%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3288181%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3288181%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1363772%22%20target%3D%22_blank%22%3E%40MSFrodo%3C%2FA%3E%26nbsp%3B%20-%20the%20DisplayName%20also%20won't%20be%20synchronized%20in%20a%20hybrid%20environment%3F%26nbsp%3B%20The%20article%20above%20only%20indicates%20that%20the%20Name%20field%20will%20not%20synchronize.%26nbsp%3BIsn't%20the%20Displayname%20a%20key%20property%20for%20the%20GAL%3F%20Can%20you%20please%20clarify%3F%20Thx!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3285417%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3285417%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20PowerShell%20scripts%20to%20create%20Shared%20and%20Room%20mailboxes.%3CBR%20%2F%3EThis%20command%20is%20executed%20on%20our%20Hybrid%20server%2C%20where%20the%20name%20(stripped%20from%20unwanted%20characters)%20is%20also%20used.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENew-RemoteMailbox%20-Shared%20-Name%20%24ResourceName%20-DisplayName%20%24DisplayName%20-SamAccountName%20%24SamAccountName%20-UserPrincipalName%20%24UserPrincipalName%20-PrimarySmtpAddress%20%24PrimarySmtpAddress%20-RemoteRoutingAddress%20%24RemoteRoutingAddress%20-Alias%20%24Alias%20-OnPremisesOrganizationalUnit%20%24ResourcesOU%20-ErrorAction%20SilentlyContinue)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20this%20be%20effected%3F%20Do%20we%20have%20to%20change%20our%20scripting%3F%3CBR%20%2F%3EThe%20name%20attribute%20is%20only%20used%20during%20creation%2C%20isn't%20used%20anywhere%20else.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3334702%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3334702%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3Ethe%20way%20Name%20parameter%20is%20being%20evaluated%20currently%20led%20to%20some%20conflicts.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExpect%20a%20landslide%20of%20support%20tickets%20coming%20your%20way%20Microsoft.%20You%20can't%20make%20a%20major%20change%20like%20this%20on%20such%20short%20notice%20without%20a%20better%20reason%20as%20to%20WHY%20it%20needs%20to%20be%20done.%20Years%20and%20years%20of%20work%20have%20been%20spent%20utilizing%20Name%20and%20you%20want%20to%20make%20us%20all%20jump%20through%20hoops%20to%20accommodate%20this%20for%20little%20to%20no%20explanation%20as%20to%20why%20it%20has%20to%20be%20done%20so%20quickly%20and%20why%20we%20must%20fix%20our%20own%20scripts%20when%20you%20were%20the%20ones%20that%20designed%20this%20parameter%20evaluation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3334686%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3334686%22%20slang%3D%22en-US%22%3E%3CP%3ELike%20many%20others%20here%20we%20have%20many%20scripts%20that%20uses%20the%20name%20attribute.%20Since%20we%20have%20the%20same%20value%20for%20Name%20and%20Alias%2C%20would%20this%20still%20work%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EName%20Before%20%3A%20D34882%3C%2FP%3E%3CP%3EAlias%20Before%3A%26nbsp%3BD34882%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EName%20After%3A%20Cryptic%20GUID%3C%2FP%3E%3CP%3EAlias%20Ater%3A%26nbsp%3BD34882%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewould%20this%20still%20work%3A%20%3CEM%3E%3CSTRONG%3EGet-mailbox%20D34882%3C%2FSTRONG%3E%3C%2FEM%3E%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3344506%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3344506%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20there%20been%20an%20updated%20announcement%20on%20this%20change%2C%20yet%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%3F%26nbsp%3B%20If%20so%2C%20can%20a%20link%20be%20posted%2C%20please%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3284733%22%20slang%3D%22en-US%22%3EChange%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3284733%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20inform%20you%20about%20a%20change%20that%20we%20are%20working%20on.%20This%20change%20will%20be%20rolled%20out%20in%20a%20phased%20manner.%20%3CEM%3E%3CSTRONG%3EUpdate%3A%3C%2FSTRONG%3E%3C%2FEM%3E%20based%20on%20feedback%20that%20has%20been%20provided%2C%20we%20have%20made%20the%20decision%20to%20delay%20this%20change.%20We%20will%20provide%20an%20updated%20timeline%20by%20end%20of%20April%20and%20deliver%20related%20communication%20in%20Message%20Center%20to%20allow%20customers%20to%20assess%20the%20impact%20of%20this%20change%20on%20their%20organization%20in%20advance%20of%20the%20change%20rolling%20out.%3C%2FP%3E%0A%3CP%3EThe%20Name%20parameter%20associated%20with%20a%20user%20within%20a%20tenant%20in%20Exchange%20Online%20should%20be%20unique.%20However%2C%20while%20we%20sync%20objects%20from%20Azure%20Active%20Directory%20to%20Exchange%20Online%2C%20the%20way%20Name%20parameter%20is%20being%20evaluated%20currently%20led%20to%20some%20conflicts.%20We%20realized%20that%20the%20current%20method%20is%20not%20the%20best%20method%20to%20compute%20this%20parameter.%20Hence%2C%20we%20want%20to%20move%20away%20from%20current%20method%20to%20a%20more%20robust%20way%20of%20generating%20the%20Name%20parameter%20which%20is%20through%26nbsp%3BExternalDirectoryObjectId%20(EDOID).%3C%2FP%3E%0A%3CP%3EEDOID%20value%20is%20unique.%20We%E2%80%99ll%20use%20this%20GUID%20as%20Name%20instead%20of%20synchronizing%20the%20Name%20from%20on-premises%20or%20using%20the%20alias%20(if%20Name%20is%20not%20specified)%20to%20compute%20the%20Name%20parameter%20in%20Exchange%20Online.%20With%20this%20change%20the%20DistinguishedName%20(DN)%20value%20will%20also%20get%20impacted.%26nbsp%3B%3CSPAN%3ETo%20better%20understand%20how%20this%20will%20impact%20objects%20in%20a%20tenant%20where%20directory%20synchronization%20is%20enabled%2C%20consider%20the%20following%20example%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWith%20this%20new%20change%2C%20when%20creating%20a%20new%20Office%20365%20(remote)%20mailbox%20from%20on-premises%20Exchange%20Admin%20Center%2C%20the%20Name%20field%20will%20no%20longer%20synchronize%20to%20Exchange%20Online.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NamePropChange.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F363876iE958A94A5990A2BF%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22NamePropChange.jpg%22%20alt%3D%22NamePropChange.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EBefore%20changes%20are%20implemented%3A%3C%2FFONT%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EDisplayName%3A%20%3C%2FEM%3EJeff%20Smith%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EName%3A%20%3C%2FEM%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23DF0000%22%3EJeff%20Smith%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EAlias%3A%3C%2FEM%3E%20jsmith%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EDistinguishedName%3A%20%3C%2FEM%3E%3C%2FSPAN%3E%3CSPAN%3ECN%3D%26nbsp%3B%3CSTRONG%3E%3CFONT%20color%3D%22%23DF0000%22%3EJeff%20Smith%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3E%2COU%3D(tenant).onmicrosoft.com%2C%20OU%3DMicrosoft%20Exchange%20Hosted%20Organizations%2C%20DC%3DNAMP283A001%2C%20DC%3DPROD%2CDC%3DOUTLOOK%2C%20DC%3DCOM%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EExternalDirectoryObjectId%3A%20%3C%2FEM%3E%3C%2FSPAN%3E%3CSPAN%3E12313c53-fff7-46d4-8b83-71fb317d1853%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EAfter%20changes%20are%20implemented%3A%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CEM%3EDisplayName%3A%20%3C%2FEM%3EJeff%20Smith%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EName%3A%20%3C%2FEM%3E%3C%2FSPAN%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23008000%22%3E12313c53-fff7-46d4-8b83-71fb317d1853%3C%2FFONT%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EAlias%3A%20%3C%2FEM%3Ejsmith%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%3CEM%3EDistinguishedName%3A%20%3C%2FEM%3E%3C%2FSPAN%3E%3CSPAN%3ECN%3D%20%3CSTRONG%3E%3CFONT%20color%3D%22%23008000%22%3E12313c53-fff7-46d4-8b83-71fb317d1853%3C%2FFONT%3E%3C%2FSTRONG%3E%2C%20OU%3D(tenant).onmicrosoft.com%2C%20OU%3DMicrosoft%20Exchange%20Hosted%20Organizations%2C%20DC%3DNAMP283A001%2C%20DC%3DPROD%2C%20DC%3DOUTLOOK%2C%20DC%3DCOM%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIn%20this%20example%2C%20both%20the%20Name%20and%20DistinguishedName%20are%20updated%20with%20the%20EDOID%20value.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22background%3A%20%23F0F0F0%3B%20padding%3A%20.5em%3B%20margin%3A%201em%200%201em%200%3B%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20This%20would%20also%20mean%20that%20any%20subsequent%20CN%20value%20change%20in%20Exchange%20on-premises%20will%20%3CEM%3Enot%3C%2FEM%3E%20be%20reflected%20in%20the%20object%E2%80%99s%20Name%20property%20in%20Exchange%20Online.%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSTRONG%3E%3CEM%3EWill%20this%20change%20not%20allow%20modification%20of%20the%20Name%20property%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3ECustomers%20can%20still%20use%20Exchange%20PowerShell%20cmdlets%20(New-MailUser%2C%20New-Mailbox%2C%20Set-User%2C%20Set-MailUser%2C%20Set-Mailbox%20with%20-Name%20parameter)%20to%20update%20the%20Name%20property%20in%20Exchange%20Online.%20Since%20the%20cmdlets%20ensure%20uniqueness%2C%20it%20would%20allow%20the%20operation%20to%20succeed%20only%20when%20the%20passed%20Name%20is%20unique%20in%20the%20tenant.%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EHow%20will%20the%20change%20impact%20new%20and%20existing%20users%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CSPAN%3EThe%20updated%20naming%20logic%20would%20take%20effect%20only%20during%20new%20user%20creation.%20Existing%20users%20won%E2%80%99t%20get%20impacted%20in%20any%20way.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%20note%20that%20since%20we%20will%20start%20using%20EDOID%20as%20Name%20in%20Exchange%20Online%2C%20we%20shall%20stop%20allowing%20changes%20in%20CN%20to%20reflect%20in%20Name%20property%20in%20Exchange%20Online%20for%20all%20users%20(both%20new%20and%20existing).%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWe%20recommend%20that%20Administrators%20evaluate%20any%20scripts%20or%20other%20automation%20that%20may%20rely%20on%20the%20Name%20property%20and%20update%20them%20accordingly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EExchange%20Online%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3284733%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20inform%20you%20about%20a%20change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%26nbsp%3Bthat%20we%20are%20working%20on.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3284733%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDirectory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20'n%20Tricks%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3345268%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3345268%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20over40%20underused%20extension%20attributes%20where%20this%20%22new%22%20ID%20can%20live.%26nbsp%3B%20To%20purposefully%20cause%20issue%20by%20using%20a%20common%20variable%20is%20like%20Russian%20Roulette%20-%20let's%20see%20how%20much%20destruction%20we%20can%20cause.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3345311%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3345311%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20MS%2C%20they%20should%20be%20able%20to%20just%20create%20a%20new%20attribute%2C%20right%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3285913%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3285913%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20script%20you%20provided%20should%20not%20conflict%20with%20this%20change.%20Anyways%20ADSync%20will%20not%20sync%20the%20%3CSTRIKE%3E-DisplayName%3C%2FSTRIKE%3E%26nbsp%3B-Name%20field%20from%20AD.%20It%20will%20use%20a%20GUID%20in%20Office%20365.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExchange%20Online%20uses%20%22DisplayName%22.%20Azure%20AD%20or%20active%20directory%20uses%20%22Name%22%20but%20this%20name%20is%20not%20populated%20on%20the%20GAL.%20I%20potentially%20forsee%20an%20issue%20when%20running%20scripts%20for%20specific%20object%20by%20-Name%20Attribute%20rather%20than%20UPN.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3346314%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3346314%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20create%20a%20mailbox%2C%20you%20must%20need%3A%20Alias%2C%20Email%20Address%2C%20Display%20Name.%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20create%20an%20object%3A%20(user)%20its%20required%20to%20have%20a%20username%20UPN%2C%20Name%2C%20%22First%20Name%22%2C%20%22Last%20Name.%22%3C%2FP%3E%0A%3CP%3ETo%20create%20an%20object%3A%20(invited%20user)%3A%20Its%20required%20to%20have%3A%20Name%2C%20Email%20Address%2C%20First%20Name%2C%20Last%20Name.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20would%20be%20nice%20to%20understand%20%22how%20not%20syncing%20the%20%22name%22%20attribute%20and%2For%20DN%22%20could%20affect%20the%20scripts.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3352297%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3352297%22%20slang%3D%22en-US%22%3E%3CP%3EYou%E2%80%99re%20only%20asking%20about%20new%20user%2Fobject%20creation%20and%20to%20me%2C%20it%20looks%20like%20this%20change%20impacts%20more%20than%20just%20the%20new%20user%2Fobject%20creation%20cmdlets.%20The%20most%20significant%20impact%20for%20us%20is%20with%20what%20I%20call%20maintenance%20scripts%2C%20not%20necessarily%20new%20object%20creation%20scripts.%20That%E2%80%99s%20minor%20for%20us%2C%20we%20only%20have%20a%20few%20scripts%20for%20onboarding%2C%20and%20we%20could%20probably%20update%2Ftest%20those%20in%20a%20couple%20of%20hours.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%E2%80%99re%20Exchange%20hybrid%20and%20AD%20hybrid%2C%20so%20we%20sync%20portions%20of%20our%20on-premises%20AD%20with%20Azure%20AD%20and%20keep%20an%20Exchange%20hybrid%20on-premises%20mostly%20for%20management%20and%20on-premises%20purposes%20(admin%20accounts%2C%20service%20accounts%2C%20SMTP%2C%20etc.)%2C%20basically%20items%20that%20we%20don%E2%80%99t%20sync%20with%20Azure%20AD%20for%20security%20reasons.%20We%20do%20have%20AD-only%20objects%2C%20AD-synced%20objects%2C%20and%20cloud-only%20objects%20in%20play.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20your%20question%20about%20new%20object%20onboarding%2C%20we%20still%20do%20it%20old-school%20and%20follow%20old-school%20best%20practices%20for%20our%20users%2C%20resources%2C%20and%20shared%20mailboxes.%20We%20disable%20AAD%20sync%20(so%20that%20a%20new%20mailbox%20doesn%E2%80%99t%20get%20created%20in%20EOL%20before%20one%20is%20created%20locally%20and%20the%20attributes%20synced%20to%20Azure)%2C%20then%20we%20create%20the%20new%20AD%20user%20with%20the%20needed%20attributes%2C%20assign%20a%20local%20mailbox%20and%20set%20some%20additional%20attributes%20locally%2C%20enable%20AAD%20sync%20then%20initiate%20a%20delta%20sync%20and%20then%20a%20New-MoveRequest%20to%20EOL%20(all%20scripted%20and%20initiated%2Ffed%20from%20input%20coming%20in%20from%20HR%2FRecruiting%20via%20API%E2%80%99s).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20where%20does%20an%20attribute%20like%20%3CSTRONG%3E%3CEM%3EName%3C%2FEM%3E%3C%2FSTRONG%3E%26nbsp%3Bcome%20in%20to%20play%20for%20us%20and%20where%20does%20this%20impact%20us%20the%20most%3F%20That%20thing%20called%20a%20pipeline%20and%20filtering.%20Numerous%20maintenance%20scripts%20that%20we%E2%80%99ve%20written%20over%20the%20years%20use%20the%20pipeline%20to%20filter%20objects%20based%20on%20the%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%3C%2FEM%3E%20attribute%20(we%20use%20that%20because%20we%20have%20naming%20standards%20at%20the%20Enterprise%20level%20so%20in%20many%20cases%2C%20we%20can%20leverage%20our%20Naming%20syntaxes%20for%20filtering).%20Many%20of%20our%20automated%20scripts%20are%201%2C000%E2%80%99s%20of%20lines%20of%20PS%20code%20so%20I%20can%E2%80%99t%20post%20most%20of%20the%20code%20here%20or%20it%20would%20take%20up%20a%20lot%20of%20space%2C%20but%20we%20use%20the%20attribute%26nbsp%3B%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%20%3C%2FEM%3Eall%20over%20the%20place.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20brief%20examples%2C%20first%20start%20with%20a%20query%20against%20on-premises%20AD%20to%20retrieve%20some%20AD%20info%20into%20an%20array%20(often%20%3CEM%3ESearchBase%3C%2FEM%3E%26nbsp%3Bis%20set%20to%20a%20specific%20OU%2C%20but%20this%20example%20is%20AD%20root%2C%20represented%20by%20a%20preset%20string%26nbsp%3B%3CEM%3E%24strADroot%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%24arrAllADobjects%20%3D%20%40(Get-ADObject%20-Filter%20*%20-SearchBase%20%24strADroot%20-Properties%20objectCategory%2C%20UserPrincipalName%2C%20accountExpires%2C%20mail%2C%20proxyAddresses)%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20some%20filtering%20and%20other%20stuff%2C%20run%20a%20%3CEM%3EFor-Each%3C%2FEM%3E%20loop%20against%20each%20object%20in%20the%20array%20to%20check%20the%20EOL%20mailbox%20for%20Legal%20Hold%2C%20forwarding%20and%20things%20like%20that%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E(Get-Mailbox%20%24_.Name)%20%7C%20%3F%20%7B(%24_.LitigationHoldEnabled%20-eq%20%24true)%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20this%20change%2C%20will%20the%20above%20still%20work%20for%20both%20the%20old%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%20%3C%2FEM%3Eattribute%20and%20the%20new%20%3CEM%3E%3CSTRONG%3EEDOID%3C%2FSTRONG%3E%26nbsp%3B%3C%2FEM%3Ewhen%20the%20array%20is%20created%20from%20objects%20queried%20from%20an%20on-premises%20AD%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20for%20example%2C%20if%20our%20company%20name%20was%20%22%3CEM%3EABC%3C%2FEM%3E%22%20and%20we%20prefaced%20all%20our%20shared%20mailboxes%20with%20the%20company%20name%20such%20as%20%22%3CEM%3EABC%20Human%20Resources%3C%2FEM%3E%22%2C%20it%20sounds%20like%20the%20following%20will%20no%20longer%20work%20for%20newly%20created%20shared%20mailboxes%20after%20your%20change%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3EGet-Mailbox%20-ResultSize%20Unlimited%20%7C%20%3F%20%7B%20%24_.Name%20-like%20%22ABC*%22%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20the%20above%20still%20work%20after%20your%20change%3F%26nbsp%3B%26nbsp%3BAlso%2C%20does%20this%20change%20impact%20other%20cmdlets%20like%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3EGet-MailboxPermission%20%24_.Name%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ETo%20me%20after%20reading%20the%20article%2C%20it%20appears%20that%20these%20things%20must%20all%20be%20updated%20in%20our%20scripts%20when%20MS%20makes%20this%20change%20and%20if%20it%20only%20impacts%20new%20objects%20and%20not%20existing%20objects%2C%20then%20we%20need%20to%20see%20how%20it%20works%20in%20action%20and%20be%20able%20to%20create%20pipeline%20filters%20based%20on%20both%20the%20(old)%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%20%3C%2FEM%3Eand%20(new)%20%3CEM%3E%3CSTRONG%3EEDOID%3C%2FSTRONG%3E%20%3C%2FEM%3Evalues%20(since%20this%20will%20only%20impact%20new%20objects%20and%20not%20existing%20ones).%20Otherwise%2C%20our%20PS%20filters%20won%E2%80%99t%20work%20properly%2C%20and%20we%E2%80%99ll%20have%20things%20like%20permissions%20being%20assigned%20to%20mailboxes%20that%20aren%E2%80%99t%20correct%2C%20etc.%20We%E2%80%99ll%20end%20up%20setting%20an%20attribute%20incorrectly%20based%20on%20bad%20pipeline%20filters%20and%20then%20the%20dynamic%20Azure%20AD%20groups%20won%E2%80%99t%20update%20their%20memberships%20properly%2C%20then%20licenses%20won%E2%80%99t%20be%20assigned%20correctly%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I%E2%80%99d%20have%20to%20find%20it%2C%20but%20yes%2C%20we%20also%20use%20DN%E2%80%99s%20in%20one%20or%20two%20places%20along%20with%20the%20AD%20attribute%20%3CEM%3ElegacyExchangeDN%3C%2FEM%3E%2C%20I%20just%20don%E2%80%99t%20remember%20which%20scripts%20use%20that%20ATM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20ensure%20that%20this%20change%20won%E2%80%99t%20impact%20the%20PS%20pipeline%20filtering%3F%20That%E2%80%99s%20the%20largest%20concern%20for%20us%20and%20probably%20impacts%20most%20Enterprise-level%20customers%20in%20some%20way%2C%20so%20if%20you%20can%20guarantee%20that%20pipelines%20will%20still%20work%20as-is%20after%20this%20change%2C%20then%20for%20me%2C%20I%E2%80%99m%20all%20in%20for%20this%20change%2C%20otherwise%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3Bwrote%3A%3CP%3E%3CSPAN%3E%3CSTRONG%3E%3CEM%3EWill%20this%20change%20not%20allow%20modification%20of%20the%20Name%20property%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3ECustomers%20can%20still%20use%20Exchange%20PowerShell%20cmdlets%20(New-MailUser%2C%20New-Mailbox%2C%20Set-User%2C%20Set-MailUser%2C%20Set-Mailbox%20with%20-Name%20parameter)%20to%20update%20the%20Name%20property%20in%20Exchange%20Online.%20Since%20the%20cmdlets%20ensure%20uniqueness%2C%20it%20would%20allow%20the%20operation%20to%20succeed%20only%20when%20the%20passed%20Name%20is%20unique%20in%20the%20tenant.%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EIf%20MS%20can%E2%80%99t%20guarantee%20that%20this%20change%20won%E2%80%99t%20impact%20us%2C%20I%E2%80%99m%20guessing%20the%20best%20and%20easiest%20approach%20for%20us%20(based%20on%20the%20above%20MS%20statement)%20would%20be%20just%20to%20write%20some%20more%20PS%20code%20to%20get%20all%20mailboxes%20with%20%3CEM%3E%3CSTRONG%3ENames%3C%2FSTRONG%3E%20%3C%2FEM%3Ethat%20are%20GUID%E2%80%99s%20using%20regex%20and%20then%20use%26nbsp%3B%3CEM%3ESet-Mailbox%3C%2FEM%3E%26nbsp%3Bto%20change%20the%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%20%3C%2FEM%3Eattribute%20in%20Azure%2FEOL%20back%20to%20what%20it%20is%20(or%20at%20least%20used%20to%20be)%20after%20MS%20assigns%20a%20GUID%20to%20the%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%20%3C%2FEM%3Eattribute.%20This%20whole%20thing%20may%20be%20an%20inconvenience%20to%20customers%20like%20us%20but%20at%20least%20doing%20that%20is%20easier%20to%20do%20in%20a%20few%20lines%20of%20PS%20code%20then%20to%20sift%20through%20dozens%20of%20scripts%20(many%20with%20100%E2%80%99s%20or%201%2C000%E2%80%99s%20of%20lines%20of%20PS%20code%20in%20them)%20and%20replace%20all%20of%20the%20code%20that%20filters%20on%20the%20%3CEM%3E%3CSTRONG%3EName%3C%2FSTRONG%3E%3C%2FEM%3E%20attribute.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3354895%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3354895%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20ridiculuous%2C%20we%20manage%20more%20than%20750%2B%20automation%20script%20using%20git%2C%20and%20how%20you%20telling%20us%20we%20have%20to%20review%20all%20of%20our%20automation%20script%3F%20And%20to%20make%20it%20worse%2C%20we%20have%20to%20finish%20review%20it%20in%20the%20matter%20of%20weeks%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3406907%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3406907%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20still%20going%20to%20happen%3F%20There%20have%20been%20no%20updates%20or%20replies%20back%20to%20anyone%20that%20I%20can%20see.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3407012%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3407012%22%20slang%3D%22en-US%22%3E%3CP%3EIts'%20postponed%20it%20looks%20the%20next%20update%20will%20be%20at%20the%20end%20of%20April.%3C%2FP%3E%0A%3CP%3EI%20suggest%20testing%20scripts%20to%20collect%20data%20from%20local%20AD%20using%20%22displayname%22%20or%20UPN%20variables%20to%20be%20use%20for%20scripts%20against%20Exchange%20Online%20or%20AzureAD%20for%20Identity.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3407055%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20in%20naming%20convention%20of%20user%E2%80%99s%20Name%20parameter%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3407055%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20in%20a%20month%20ago%3F%3F%20or%20April%202023%3F%3CBR%20%2F%3EWe%20need%20a%20little%20bit%20more%20transparency%20on%20this.%20-%20We%20have%20no%20idea%20whether%20we%20should%20start%20focusing%20our%20time%20on%20%22fixing%22%20our%20scripts%2C%20instead%20of%20working%20on%20already%20scheduled%20projects%2Ftasks.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎May 09 2022 08:14 AM
Updated by: