"Nothing is changing"
But, we will need to invest time to update documentation, presentations, training, end-user doc, design documentations, and so on...
And what about Azure AD Connect server? Will this also change to Microsoft Entra ID Connect server? And does this mean the installation path-names will change? And will the references to Azure AD in those tools change?
Because, this will mean even more changes in design and configuration documentation, and in scripts.
If path names changes, this also means updating WDAC rules and Applocker rules.
And what about reference URLs to documentation pages on Microsoft Doc? Those will also need to be updated in our own documentation.
Is Microsoft providing compensation and budget for all those changes?
In addition, I'm sure certification exams will not be updated at the same pace. So as an MCT, an additional frustration is that my training documentation needs to mention both names for a long time....
As a lot of people already mentioned the same, this name change does not bring any added value for the customers. Rebranding and renaming has always been something Microsoft is good at, but I think I share the feeling with all the others: If only they invested equally in improving the products...
For us customers the name isn't important, but the functionality is.
And to top it off, not everything will change at the same time. Some things will change end of July, other names will change in October, some names will never change (if Microsoft sticks to this). So this work will not be need once this year, but at least twice.
All this rebranding brings for us is:
- confusion
- tons of work checking documentation and training
- extra difficulties on certification exams
- frustration
- extra costs