MicrosoftIrina_Nechaeva , as the name of Azure AD Connect will change to Microsoft Entra ID Connect, what will happen with the installation paths?
Now it is installed to: 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync'
This path is referenced in scripts to for example import the psd modules....
Will this also update?
And what about the product versioning? Will the MS Entra ID Connect sync agent be launched as new product, starting from v1.0 or will only the name change?
OpenXDR, I totally agree a rebranding should not be stopped based on some feelings, cultural insensitivities, or minor inconveniences, but as the comments indicated this will not be minor. This will bring a lot of work redirecting documentation on many levels of the organization: design doc, architectural diagrams, end-user support doc, training, instructional videos, presentations, support personal doc, references to license packs in contracts, standards, benchmarks, scripts, and so on.
Another consequence is that all Azure AD related CIS benchmarks will need to be reviewed and updated.
And, as said, not everything will change at the same date or even month. This means we will need to keep the double naming for a long time, and redo all the work again when eventually all has changed.
And, maybe by that time a new rebrand has been announced.... 
As you say, a hidden cost
I guess this rebranding will go forward as planned, but I really do hope Microsoft thinks twice for the next one and listens to their customers before stating "No action is needed from you".
(This is by the way not the first time this feedback has been given to Microsoft)
