Change in naming convention of user’s Name parameter

I feel like I am late to the party and while many have already echoed my sentiments, I feel it is necessary to formally air my displeasure with this change.  Like many have noted I can't make sense of why Microsoft repurposed a critical field (i.e; Name) and replaced what was useful information to something that is completely useless to us lowly human beings.  Also, while Microsoft is telling Admins to review their scripts to make changes to use another field (or to use pipe commands) when will Microsoft review "their" script modules to output a field (maybe DisplayName) to return more meaningful information that is understandable to a "real" person.  I get it, I can use piping but many of these modules (for at least 10 year) have always output the Name which was easy to relate information.  We now have 100's of scripts to review and am concerned if the addition of these extra piping activities will negatively impact processing time to obtain meaningful information.  For example, we have distribution groups that have 1000's of members and we have written scripts for our provisioning teams to that uses the Get-DistribtuionGroupMember command to list out all the members of a group.  Since new users now have this useless GUID in the name field we have to re-architect our scripts to put meaningful information that people can review.  Seems like if Microsoft "fixed" this on their end it would be eliminate a whole lot of changes that now need to be implemented by every O365 admin. 

Our tenant also changed on Nov 1,2022 and at this point I've not found every command that is part of the Microsoft module sets that are impacted by this change but as others have already noted above it seems that Microsoft has disregarded the concerns of many customers and forged ahead regardless of the impact to their customers which is very disappointing.

BTW, I did open a support ticket on and told my support engineer adding comments to these blogs is fruitless and a waste of time.  Based on the comments posted here it just confirms that perception as I've not seen any documentation or responses from Microsoft that address the issues that have been raised here.  Not sure if I feel any better but I guess I've put in my 2 cents regarding this change.