Change in naming convention of user’s Name parameter

This change also affects the Room Finder in Outlook + OWA.

RoomList distribution groups created after the change will receive the bogus (guid) Name + DisplayName property and this is what's shown in the Outlook/OWA room finder.

This practically renders the otherwise awesome Room Finder feature useless.

It would seem that the Outlook/OWA team will need to implement the same change as the Exchange Admin Center team has made in most of the places where distribution groups are shown in EAC. Specifically, display the Azure AD DisplayName instead of the Exchange Online DisplayName:

EXO RoomLists:

PS C:\> Get-DistributionGroup -Anr RoomList

Name                                 DisplayName                          GroupType PrimarySmtpAddress
----                                 -----------                          --------- ------------------
cab67e5e-8c97-4260-9430-36673ae6c252 cab67e5e-8c97-4260-9430-36673ae6c252 Universal email address removed for privacy reasons
bd2d371f-0f94-4f46-b966-c0071d4b53ca bd2d371f-0f94-4f46-b966-c0071d4b53ca Universal email address removed for privacy reasons
77591a96-0505-4e4e-b129-fbc3bd661615 77591a96-0505-4e4e-b129-fbc3bd661615 Universal email address removed for privacy reasons
04691f74-9394-448b-9f09-d84e2a7003d2 04691f74-9394-448b-9f09-d84e2a7003d2 Universal email address removed for privacy reasons
92a5f75d-7092-4a3c-9f75-973fe508d276 92a5f75d-7092-4a3c-9f75-973fe508d276 Universal email address removed for privacy reasons
96c71512-f27b-4c9d-896b-c7a71361073b 96c71512-f27b-4c9d-896b-c7a71361073b Universal email address removed for privacy reasons
d89eac41-effb-404c-9eb1-a426969ddd49 d89eac41-effb-404c-9eb1-a426969ddd49 Universal email address removed for privacy reasons
c32cc25e-c698-4530-a91f-31ea1019486e c32cc25e-c698-4530-a91f-31ea1019486e Universal email address removed for privacy reasons

Azure AD Groups:

PS C:\> Get-MgGroup -Filter "startswith(displayName,'RoomList')"

Id                                   DisplayName
--                                   -----------
cab67e5e-8c97-4260-9430-36673ae6c252 RoomList-DE-Berlin Wilhelmstrasse
bd2d371f-0f94-4f46-b966-c0071d4b53ca RoomList-DK-Copenhagen Cylindervej
77591a96-0505-4e4e-b129-fbc3bd661615 RoomList-UK-London High St
04691f74-9394-448b-9f09-d84e2a7003d2 RoomList-US-Boston Bennington St
92a5f75d-7092-4a3c-9f75-973fe508d276 RoomList-US-Boston Causeway St
96c71512-f27b-4c9d-896b-c7a71361073b RoomList-US-Boston St James Ave
d89eac41-effb-404c-9eb1-a426969ddd49 RoomList-US-LosAngeles Pacific Blvd
c32cc25e-c698-4530-a91f-31ea1019486e RoomList-US-NewYork 6th Ave

This change is an outstanding showcase on the challenges of compartmentalized software development. Did the Exchange Online Core team involve the Exchange Admin Center team? The PowerShell team? The Outlook team? The REST API team? Or customers(?!?) before moving forward with this change?

It will probably be used as a how-not-to-do-it reference for years to come.