Jump to content

Recommended Posts

Posted (edited)

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name

 

To unify the Microsoft Entra product family, reflect the progression to modern multicloud identity security, and simplify secure access experiences for all, we're renaming Azure Active Directory (Azure AD) to Microsoft Entra ID.

 

Another name change...

 

Azure AD no more!

 

Absolutely the long overdue, and critical necessary change that Azure users have been waiting for I'm sure. :o

Edited by Cat_Jam148
  • Thanks 4
Posted
To unify the Microsoft Entra product family, reflect the progression to modern multicloud identity security, and simplify secure access experiences for all, we're renaming Azure Active Directory (Azure AD) to Microsoft Entra ID...a little bit at a time so that our confusing documentation will refer to the same thing by two different, interchangeable names for a long time to come.

FTFY!!

Posted (edited)
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name

 

 

 

Another name change...

 

Azure AD no more!

 

Absolutely the long overdue, and critical necessary change that Azure users have been waiting for I'm sure. :o

 

As I've said elsewhere, this is necessary. Active Directory is a legacy product. While it’s going to be around for a long while yet, it’s effectively deprecated. So there's no need or benefit to associate EntraID with Active Directory. And you don’t need to have all your services in Azure to run idp in AAD/Entra ID, so 'Azure' is unnecessary here.

 

I've been in plenty of meetings when senior IT staff have been confused as to the difference between "AD" and "AAD", and these are not stupid people by a long chalk.

 

This is an intentional attempt to break any link, any idea that AAD is just ’AD in the cloud’. It’s not. It has always been a different product and riding on the coattails of AD via name association no longer. This is part of the journey to on-prem AD being something MS did in the past, not something they have to support in the future.

Edited by Roberto
Posted
As I've said elsewhere, this is necessary. Active Directory is a legacy product. While it’s going to be around for a long while yet, it’s effectively deprecated. So there's no need or benefit to associate EntraID with Active Directory. And you don’t need to have all your services in Azure to run idp in AAD/Entra ID, so 'Azure' is unnecessary here.

 

IMO it shouldn't have been called Azure AD in the first instance. It's a whole different beast compared to legacy AD

 

A name like Azure ID would've made more sense.

Posted

Azure ID's? I'm sure having an acronym of AID's wouldn't be a problem :)

 

I get that now it's different from Active Directory and should not be named similarly to avoid confusion, but I think that changing the name now after years is going to cause more confusion. Especially since Microsoft have a habit of changing the names of services and products seemingly to cause such confusion!

  • Thanks 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...