MicrosoftThank you Irina_Nechaeva for the thoughtful response. I wasn't aware that Microsoft customers were confused about what AD and AAD are/do, or how IAM strategy fits into security efforts. Customers directly involved IAM services tend to be pretty savvy and don't have a hard time getting their heads around these products, what they do, or how they relate to the original Entra suite. To the contrary, dealing with a name shift makes work for these customers, who already have plenty of work to do. What's more, underlying resource, CLI, and API names will likely carry the "aad" name for years to come, thus perpetuating a split-brained naming where we talk about "Entra" but manage/configure "aad" resources. This has been the case with Teams (OCS/Link/Skype names persist) and most Azure resources that got rebranded along the way . . . we end up with disconnections between what we call things and how we address then technically.
Thanks again for your attention to customer feedback.
