Microsoft is causing a stir among some tech pros after confirming it plans to rename Azure AD to Entra.

The Entra name was introduced in May last year as the overarching brand for the Identity and Access suite. It included two Entra family products – Permissions Management and Verified ID, and Azure AD, though Azure AD is much older, has been in use for around a decade, and has 720,000 biz customers.

In the past year or so since, Microsoft added ID Governance, Workload ID, Internet Access, and Private Access to the Entra suite.

[1]

In a [2]blog post , Irina Nechaeva, Microsoft general manager of product marketing for Identity & Access, said the change is supposed to "make it easier for you to use and navigate the unified and expanded Microsoft Entra portfolio."

[3]

[4]

"I want to assure you that your work protecting your organization, customers, partners, and the investments you've made in deploying Azure AD will continue uninterrupted. All configurations and integrations will continue to work as they do today, without any action needed from you. You'll see the new name start appearing in Microsoft product experiences in August 2023."

She added that there are zero changes to Azure AD capabilities, APIs, login URLs, PowerShell cmdlets, Microsoft authentication library, developer experiences or tooling. Licensing plans and pricing will also remain unaffected.

[5]

"Once the new name rolls out, all Azure AD features will also move under the new name," the blog said.

Service plan display names will change on October 1: Azure AD Free is to become Microsoft Entra ID Free, Azure AD Premium P1 or P2 will move to Microsoft Entra ID P1 or P2, and Azure AD External Identities will switch to Microsoft Entra External ID.

Feature naming will also be overhauled. Azure AD Conditional Access, for example, will become Microsoft Entra Conditional Access, Azure AD MFA will change to Microsoft Entra MFA, and Azure AD single sign-on will move to Microsoft Entra single sign-on.

[6]

A separate but related blog from Microsoft states: "We'd like your help spreading the word about the name change and implementing it in your own experiences. If you're a content creator, author of internal documentation for IT or identity security admins, developer of Azure AD-enabled apps, independent software vendor, or Microsoft partner, we hope you use the naming guidance outlined in the following section (Azure AD name changes and exceptions) to make the name change in your content and product experiences by the end of 2023."

A source close to Microsoft's developer community told us they suspected a "monetization aspect" is related to the name change as Azure AD was initially free until premium versions were introduced, though all four tiers of the service plans remain and Microsoft insists prices will not be altered.

Azure AD is well known and often crops up in terminology such as Azure AD Join for configuring a PC to a specific Azure AD directory.

"Renaming it requires editing millions of documents and educating users/customers on what it means," added our dev source. "Nobody can see any advantage in the new name, which is more obscure."

Nechaeva signs off by saying the community's insights and feedback "guided the evolution of identify security."

[7]Miscreants exploit five Microsoft bugs as Windows giant addresses 130 flaws

[8]Microsoft decides it will be the one to choose which secure login method you use

[9]Microsoft disarms push notification bombers with number matching in Authenticator

[10]Microsoft pushes users to the Edge in Outlook, Teams

The response from the community is largely negative, judging by the comments below the blog. One that was more positive in tone came from techie dieknet who reckons past name changes by Microsoft didn't make sense but this does. "Azure Active Directory sounds way too similar to Active Directory, even though it's a completely different product."

Others weren't in favor. "Not a fan," said Steve Kurtz. "This change is both unnecessary and wasteful of customers time. MS should spend more time improving products and less time renaming them. How much will this rebranding cost MS, and who pays for that?" He adds: "Marketing-driven changes only create confusion and busywork within customer environments, making MS products less appealing to those who support them."

Another, ranual, said: "This is clearly another bonehead move by Microsoft for marketing purposes. There's no technical reason to make this change."

"Was Azure AD a perfect branding? No, not even close. I could have done better. But how long has AAD been around for now? 10 years? I think at this point people who are in-the-know understand what it means," said JamesEpp, who concedes the rebrand may grow on them over time.

Brucey_ said: "Technical teams around the world will be split as they will continue to call a spade a spade making communication with teams that use a newer word to describe that same spade twice as hard… Vendors will scramble to update documentation and images in their materials to get in front of customers only for their customers to turn around and ask 'But do you support Azure?'"

And Jim_ Woodward pointed out: "This is one of the worst ideas Microsoft has had, this branding is unnecessary and confusing, just create a new product and leave the existing one alone, the amount of internal documentation that will need updating is immense, hundreds of hours of KB updates."

Nechaeva jumped into the comments section to say the name change decision "wasn't taken lightly."

"Yet, we believe this change will create a path to deliver a simpler way to protect every identity and secure every access point as we'll continue to expand Microsoft Entra portfolio. Ultimately, all Microsoft customers would need to remember is that anything they need for securing access is Microsoft Entra."

So basically, the name change plan goes ahead. Maybe the community needs to turn up the volume. ®

Get our [11]Tech Resources



[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZK8ihxiFlqWPaxGQEJwgJQAAAwk&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[2] https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/azure-ad-is-becoming-microsoft-entra-id/bc-p/3871391/highlight/true#M5105

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZK8ihxiFlqWPaxGQEJwgJQAAAwk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZK8ihxiFlqWPaxGQEJwgJQAAAwk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZK8ihxiFlqWPaxGQEJwgJQAAAwk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZK8ihxiFlqWPaxGQEJwgJQAAAwk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2023/07/11/microsoft_patch_tuesday/

[8] https://www.theregister.com/2023/05/18/microsoft_azure_system_authentication/

[9] https://www.theregister.com/2023/05/09/microsoft_authenticator_number_matching/

[10] https://www.theregister.com/2023/05/02/microsoft_edge_outlook/

[11] https://whitepapers.theregister.com/