MicrosoftIrina_NechaevaI can only speak for myself, but I think you need to take a step back here and look at the underlying common theme of the complaints. Going through internal and customer documentation and updating text, screenshots, powerpoints, etc., is a pain and I'm glad you want to "listen" and "assist" in this effort. But the problem is we shouldn't have to do this at all. I have met exactly zero people in all my technical pre-sales calls and project scoping who were confused by "Azure AD." I have met zero people who thought or cared that it shared a name with the server Active Directory. It's just completely unnecessary. Even the five minutes I'm spending typing this reply is five minutes I should not have to spend in my busy day at all. This whole thing is just entirely made up by marketing for no apparent reason whatsoever. I am going to guess that after all is said and done, this isn't going to increase adoption of Microsoft identity products. In fact, it may decrease it because "Azure AD" is already well-known. You see it everywhere as an integration option into cloud products. People who don't follow tech news will just think "Entra" is a new product and will wonder if they have to pay more or be worried "Azure AD" doesn't exist. There is just no logical reason at all for this.
You could have saved a lot of trouble by just announcing "Azure AD is now a part of the Microsoft Entra family of products" and then left it at that. Everything else is completely unnecessary and only going to create extra unnecessary work for your partners for absolutely no benefit for either Microsoft or those partners.
