MicrosoftI get the impression from your responses that this decision has been made after carefully consulting so-called decision makers and end users.
"Decision makers" and marketing people may have the perception that Azure AD is too complicated. AAD is complicated.
AD - OnPrem or Azure is NOT SIMPLE, it cannot be made simple by branding it in a simplistic way.
Microsoft could better invest in simplifying and modernizing the product (say stop using DOS-era environment variables to configure powershell)
We NEED all this stuff, often because Microsoft has spent more energy on marketing and renaming than on actually consolidating and modernising the products, but we have to keep them running as well as implementing new functionality, staying secure and compliant.
The tech community does not need this new name. We are the real users.
As when Microsoft started with Office365 and tried to make a "simple" UI, you will find that the idea of "simplifying" Azure AD will just end up in a morass of multiple names for nearly identical functions and menu systems linking to the same underlying functionality.
We are not just managing identities but compliance and security and data and email and Teams. We are managing configurations of users, groups, devices, Microsoft and third party software, customizations and all. Marketing cannot make it simple by creating a new name and putting links to a few key functions in a nice new menu.
It's not just internal documentation but say third party compliance and security audits which always begin with some nice phrase like "leveraging the power of Azure AD (AAD)". "Contoso's Identity and Access Management strategy is based entirely on the Microsoft Azure AD toolset".
Internally we would have to identify all the procedures that use all the urls like aad.portal.azure.com (MicrosoftEntraID.portal.azure.com?) as well as I suppose all the Powershell scripts (are you really going to change New-AzureADServicePrincipal to New-MicrosoftEntraIDServicePrincipal?
Just from a counting the keystroked productivity measure, 15 keystrokes for New-MicrosoftEn instead of 6 keystrokes for New-Az is a severe hit for anyone who uses powershell regularly.
Think of the scripts, reports, training courses, books, YouTube videos, and the confusion for Bard and ChatGPT.
Have you really talked to all the partners and developers? Have you even asked the PowerShell (pwsh) team?
I could go on, but I also have work to do.
