Update (4/12/23): This feature was enabled in our worldwide and 21Vianet clouds in November 2022. All tenants in these clouds will see the changes. Rollout to our GCCH and DoD clouds has been paused ...
Updated Apr 12, 2023
Version 11.0
Blog Post
"We recommend that Administrators evaluate any scripts or other automation that may rely on the Name property and update them accordingly."
- April 2022 - Don't you think its too short of a notice
- Does it impact other objects like MailUsers, Distribution Groups, MailContacts , etc.
- Almost all cmdlets have 'Name' as the default output, and useful for a quick check without much of typing currently
Get-Recipient "A A"
Name RecipientType
---- -------------
A A UserMailbox
get-mailbox "A A"
Name Alias Database ProhibitSendQuota ExternalDirectoryObjectId
---- ----- -------- ----------------- -------------------------
A A A.A xxxPR01DG189-db020 1.979 GB (2,125,4... xxxxx..
- Many outputs like SendOnBehalf, and Manager fields, doesn't even store full details, relies solely on this
- Existing data vs. new data having mixed up values will cause lot of disruptions
- Any options for opt out, for companies having a robust system and doesn't get into this sync error often