Really quick video reviewing the Azure AD rename. Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature. Thanks for watching! 🤙
This is a necessary name change. People have good reason to think that implementing the authentication & authorization services provided by AAD require knowledge of “Microsoft Azure”, when in fact that’s not the case. Same goes for many other Microsoft 365 services. My former boss thought I was a nincompoop when I tried to explain that, from the perspective of a system administrator, “Azure” wasn’t a component of “Azure Information Protection”… and because the current naming is so misleading & terrible I couldn’t blame him.
@@NTFAQGuy I have created so much Visio files and internal docs for all my colleagues, I am sometimes something like an internal trainer for all IT related things. Last week I had a training session and showed Azure AD and Azure AD Connect. That week I have to train colleagues that all I mentioned before is now Entra. I am very exited about their reactions
It's about time, because Azure Active Directory mostly had nothing to do with Active Directory, operated completely differently, and subsequently confused an entire generation of admins.
Side note from the videos content. John I just wanted to take a moment to thank you. I’ve been on the journey to AZ305 for the past 3 months after obtaining AZ104, AZ700 and AZ500 just yesterday. I’ve used your Exam crams and Deep Dives on top MS Learn to get me to this point. Thank you so much for everything you provide the technical community. 💪
Just for clarity... Windows Azure Active Directory Sync aka DirSync should not be mistaken for Microsoft Azure AD Sync aka AADSync which were both replaced by Azure AD Connect aka AADConnect or by some people also called ADConnect which is currently called Microsoft Entra Connect which in future is likely to be replaced by Microsoft Entra Connect Cloud Sync which was previously called Azure AD Connect Cloud Sync. But if you want you can still use the Azure AD Connector for FIM/MIM which is now called Microsoft Entra Connector for FIM/MIM. For clarity reasons and to avoid discussions among colleagues it is allowed to use *Entrachangeable* names. 😜
It was well required as had two confusing terms (for non Azure ppl), Azure and AD where people often assume based on the terms used in name. As usual thanks John 👍
They are very different things. If you have services that need to JOIN a domain, use LDAP etc you still need domain controllers and Active Directory Domain Services. If you have a choice and can instead integrate with Microsoft Entra ID (fka AAD) including client OS which can Microsoft Entra Join then great. If deploying legacy services in Azure may be able to use the AADDS feature.
I would prefer it just be entra because we can awesome it is a Microsoft product as we are using Microsoft Azure. I agree the azure ad naming was very silly on Microsoft part.
powershell module for azuread has been deprecated for a while now. you should be using the management graph module instead. they won't rename the azuread since its deprecated.
I mean, I get what they’re trying to do but it’s annoying. They want all “identity” related tools under the same umbrella like they did with the defender branding. All data security related solutions are under “purview”. I wouldn’t care if the names weren’t so terrible. It’s like they have the same people responsible for the new threat group names also naming products. Unicorn Rain Directory
Before I look it up, I wonder if Azure Active Directory Domain Services will be renamed. Was it Azure ADDS or AAD DS?! This rename does feels different, though. AD, in my mind, instantly translates to identity store. It's going to take me quite a long time to translate that to Entra ID.
Thanks John, hopefully this might help renew an improved focus on Identity (from a security & protection perspective), simple yet effective post, think behind the scenes some ppl I know have been reviewing their current license position to see what tweaks or changes can better harden their IT org setup, so this might help promote better interest in what Entra can bring (ie. protection of identity which is often overlooked, some of the MSFT options if configured well, can actually help a great deal), thanks again.
So I am basically gonna do the certification of az-104 next week(was gonna do this week) but i can't find what will change. Do I need to restudy everything?
@@NTFAQGuy Thanks for the answer. There was some minor changes to each "module" in az104. I will keep studying the material I have + your awesome videos :)
You touched on this, but Azure AD has always been an integration shim, rather than being an Azure flavor of AD. Common point of confusion when discussing Azure migrations with leadership/decision makers, so the new naming will make the distinction clearer. Now we just need to convince Microsoft to remove the name "Azure" from "Azure DevOps" so that conversations are easier with leadership on adopting the DevOps platform even if they are not using Azure.
The rename of VSTS to "Azure" DevOps was almost certain a decision from the marketing department to promote the term Azure. Such a stupid name. "Yes, we have Microsoft Azure" "Oh really, so you build apps with PaaS components?" "? no Azure to build code" "oh.. that Azure. Azure DevOps"
Good stuff. It's not AD and it's not Azure (IaaS and PaaS for app hosting). Next let's rename Azure DevOps (also independent of Azure). Love the T (also had BDCs)!
They probably found some flows in they agreements, and they are losing a lot of money, so they desided to push a new name to be able to workaround some legal stuff
The renaming of Microsoft Azure AD to Microsoft Entra does not add any value to the service itself. The name change is simply a rebranding exercise, and it is not clear what Microsoft is trying to achieve with it.
They’re probably trying to differentiate AAD from ‘Azure’ from ‘Active Directory’. I had a former boss who thought that “Azure Active Directory” implied that there was an instance of Windows Server in Azure running a domain controller.
@@Teramos Microsoft have let other vendors like Zscaler and Netskope cover traffic steering and internet filtering from endpoints. Good to have more competition in this space.
Not true. The old name is _hideously_ misleading because Azure resources & on-premises Active Directory (or I guess just plain ‘Active Directory’ now) are unrelated. Titling Microsoft’s cloud-based directory service ‘Azure Active Directory’ was a likely a decision from before October 2008, when the Azure platform was first announced. The developers (or the marketing team) probably settled on the doubly-misleading label because 1) Microsoft’s new product releases needed the word ‘Azure’ for branding reasons, and 2) by inserting ‘Active Directory’ IT professionals could quickly grasp the nature of the service. There’s little doubt that Microsoft knew their titling wasn’t optimal, but the alternative meant positioning the product at risk for failure. I’m willing to wager that staff inside the company predicted this day 15+ years ago…
Really quick video reviewing the Azure AD rename. Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
👂 Translate the captions to your native language via the auto-translate feature in settings! ruclips.net/video/v5b53-PgEmI/видео.html for a demo of using this feature.
Thanks for watching!
🤙
Oh good, this will surely make all knowledge base articles easier to search through.
Microsoft and renaming Azure services. Name a more iconic duo. 😑
lol
This is a necessary name change. People have good reason to think that implementing the authentication & authorization services provided by AAD require knowledge of “Microsoft Azure”, when in fact that’s not the case. Same goes for many other Microsoft 365 services.
My former boss thought I was a nincompoop when I tried to explain that, from the perspective of a system administrator, “Azure” wasn’t a component of “Azure Information Protection”… and because the current naming is so misleading & terrible I couldn’t blame him.
Google and killing services
How about… Preview, but with only half the functionality ported and now it’s env:prod?
@@adamingle3896 this is over 9000% true :D
People will still refer to it as Azure AD for years to come
I'm pretty sure I'm going to slip up and say it a lot.
@@NTFAQGuy I have created so much Visio files and internal docs for all my colleagues, I am sometimes something like an internal trainer for all IT related things. Last week I had a training session and showed Azure AD and Azure AD Connect. That week I have to train colleagues that all I mentioned before is now Entra. I am very exited about their reactions
as we do with office 365
People still haven't moved off from Intune
I'll inform the guys who maintain our documentation tomorrow. cant wait haha 🤣
I’m looking forward to the same thing … not
It's about time, because Azure Active Directory mostly had nothing to do with Active Directory, operated completely differently, and subsequently confused an entire generation of admins.
I agree
It didn't really have anything to do with Azure either. It was originally created to support BPOS years before Azure was even a thing.
@@squirreldriver BPOS?
Side note from the videos content. John I just wanted to take a moment to thank you. I’ve been on the journey to AZ305 for the past 3 months after obtaining AZ104, AZ700 and AZ500 just yesterday. I’ve used your Exam crams and Deep Dives on top MS Learn to get me to this point. Thank you so much for everything you provide the technical community. 💪
That is very kind, thank you
Only at Microsoft would we require a guy as smart as John to explain our new branding of a product customers have been using forever 😂
ROFL
hahahaha, ridiculously true!!
You are the best! Thanks for sharing your knowledge!
Thx John CU Friday. Have a great day
I love your T-Shirt!
Just for clarity... Windows Azure Active Directory Sync aka DirSync should not be mistaken for Microsoft Azure AD Sync aka AADSync which were both replaced by Azure AD Connect aka AADConnect or by some people also called ADConnect which is currently called Microsoft Entra Connect which in future is likely to be replaced by Microsoft Entra Connect Cloud Sync which was previously called Azure AD Connect Cloud Sync. But if you want you can still use the Azure AD Connector for FIM/MIM which is now called Microsoft Entra Connector for FIM/MIM.
For clarity reasons and to avoid discussions among colleagues it is allowed to use *Entrachangeable* names. 😜
you have too much free time :D
Thanks for your good Videos! In my eyes you have the ability to simplify and explain complex constructs. This makes learning new topics much more fun
You're very welcome!
It was well required as had two confusing terms (for non Azure ppl), Azure and AD where people often assume based on the terms used in name.
As usual thanks John 👍
That shirt is the best!!!
Hehe thanks
Generally speaking, should new companies use domain controllers, or is it best practice to place directory services in the cloud?
They are very different things. If you have services that need to JOIN a domain, use LDAP etc you still need domain controllers and Active Directory Domain Services. If you have a choice and can instead integrate with Microsoft Entra ID (fka AAD) including client OS which can Microsoft Entra Join then great. If deploying legacy services in Azure may be able to use the AADDS feature.
I would prefer it just be entra because we can awesome it is a Microsoft product as we are using Microsoft Azure. I agree the azure ad naming was very silly on Microsoft part.
John that t-shirt is amazing!! Also great content thanks very much
hehe thanks. you can buy on my t-shirt store. all profit goes to cure childhood cancer. link in the video description.
Thank you for a quick update.
Not sure what's the benefit of changing the name of one of their key services other than just confusing people.
@NTFAQGuy come on. be honest. how long did you practice drawing the Entra logo?
let me just say I didn't get it right the first time I tried :D
I wish Microsoft would rename Hyper-V. Should be Hyper-G, the gangster hypervisor 😉
ROFL
what about Azure AD B2C /B2B - are they also renamed?
Microsoft Entra External ID. They were already called AAD External Identities for B2B
AD B2C is renamed Entra C3PO, and B2C is renamed R2D2. Probably.
What about the powerShell commands and modules? Will that be going through the name change too?
powershell module for azuread has been deprecated for a while now. you should be using the management graph module instead. they won't rename the azuread since its deprecated.
Maybe I missed it but what is Azure AD DS being renamed to? Entra ID Domain Services?
not discussed
Will this affect naming conventions for the certificates and exams such as AZ-900 or AZ-104?
Only azure ad is being renamed, not azure. So no
I am having the AZ-104 sertification on thursday, hope this dont flip me over lol
ROFL, they don't update the exams that fast :D
Microsoft, stop it please 🤣
ROFL
Renaming products and service offerings is keeping HUNDREDS of people employed!
I mean, I get what they’re trying to do but it’s annoying. They want all “identity” related tools under the same umbrella like they did with the defender branding. All data security related solutions are under “purview”.
I wouldn’t care if the names weren’t so terrible. It’s like they have the same people responsible for the new threat group names also naming products.
Unicorn Rain Directory
As always, great content John. Keep the good work!
Before I look it up, I wonder if Azure Active Directory Domain Services will be renamed. Was it Azure ADDS or AAD DS?!
This rename does feels different, though. AD, in my mind, instantly translates to identity store. It's going to take me quite a long time to translate that to Entra ID.
Probably they name it to "AADDSEntryID+365_23h2#P5Ultimate-EVD*KN"
It should be Entra Domain Services. Entra ID Domain Services wouldn't work because it's not directly a part of "Azure AD".
Thanks John, hopefully this might help renew an improved focus on Identity (from a security & protection perspective), simple yet effective post, think behind the scenes some ppl I know have been reviewing their current license position to see what tweaks or changes can better harden their IT org setup, so this might help promote better interest in what Entra can bring (ie. protection of identity which is often overlooked, some of the MSFT options if configured well, can actually help a great deal), thanks again.
Feels like it should have been “Microsoft Azure ID” instead of Entra
Well identity is more than just Azure. I like its beyond that.
Hi John, long time no speak...Are all the powershell commands getting rebranded (aliased) as well?
Should be using Microsoft graph cmdlets as the azuread module is deprecated anyway
The live session on Entra was pretty amazing. Sadly I got dragged back into work several times.. Great video, Cant wait for more!
So I am basically gonna do the certification of az-104 next week(was gonna do this week) but i can't find what will change. Do I need to restudy everything?
they don't change exams instantly and also this is just a name change of Azure AD.
@@NTFAQGuy Thanks for the answer. There was some minor changes to each "module" in az104. I will keep studying the material I have + your awesome videos :)
Great videos mate. Really appreciate them.
Much appreciated
Wow John, time to update half of your videos, titles and thumbnails 😅
Nope 🤣
Yeah... I project I will start calling AAD by this new name sometime in 3Q 2028
HAHAHAHAHAHA
and we would have three of them (BDC's)
Someone needs to give ms marketing a better job instead of remaining things for no reason
You touched on this, but Azure AD has always been an integration shim, rather than being an Azure flavor of AD. Common point of confusion when discussing Azure migrations with leadership/decision makers, so the new naming will make the distinction clearer. Now we just need to convince Microsoft to remove the name "Azure" from "Azure DevOps" so that conversations are easier with leadership on adopting the DevOps platform even if they are not using Azure.
The rename of VSTS to "Azure" DevOps was almost certain a decision from the marketing department to promote the term Azure. Such a stupid name.
"Yes, we have Microsoft Azure"
"Oh really, so you build apps with PaaS components?"
"? no Azure to build code"
"oh.. that Azure. Azure DevOps"
I like it. It's good that they're not afraid to change things.
Simple, suit, and short!
Good stuff. It's not AD and it's not Azure (IaaS and PaaS for app hosting). Next let's rename Azure DevOps (also independent of Azure). Love the T (also had BDCs)!
GitHub Legacy DevOps ;-)
They probably found some flows in they agreements, and they are losing a lot of money, so they desided to push a new name to be able to workaround some legal stuff
Don’t think it’s that
The renaming of Microsoft Azure AD to Microsoft Entra does not add any value to the service itself. The name change is simply a rebranding exercise, and it is not clear what Microsoft is trying to achieve with it.
They’re probably trying to differentiate AAD from ‘Azure’ from ‘Active Directory’. I had a former boss who thought that “Azure Active Directory” implied that there was an instance of Windows Server in Azure running a domain controller.
Mass confusion between (Windows Server) ADDS and Azure AD. Eg if your ADDS domain controllers are VMs hosted on Azure IaaS is that your Azure AD 🙃?
did you see global secure access? amazing feature
@@Teramos Microsoft have let other vendors like Zscaler and Netskope cover traffic steering and internet filtering from endpoints. Good to have more competition in this space.
This rename sounds good...
Dont see much value in that. Microsoft need to be careful not to go the Citrix route and confuse everyone to what product is what.
You can tell John is annoyed with this naming change. 😬
ROFL. Very little annoys me these days :)
Find: AAD Replace: EID
Tbh whoever thought up Entra should be fired what a horrible name.
Microsoft has to learn that simply renaming something is not going to make it any easier to understand, nor any easier to purchase.
Not true. The old name is _hideously_ misleading because Azure resources & on-premises Active Directory (or I guess just plain ‘Active Directory’ now) are unrelated.
Titling Microsoft’s cloud-based directory service ‘Azure Active Directory’ was a likely a decision from before October 2008, when the Azure platform was first announced.
The developers (or the marketing team) probably settled on the doubly-misleading label because 1) Microsoft’s new product releases needed the word ‘Azure’ for branding reasons, and 2) by inserting ‘Active Directory’ IT professionals could quickly grasp the nature of the service.
There’s little doubt that Microsoft knew their titling wasn’t optimal, but the alternative meant positioning the product at risk for failure. I’m willing to wager that staff inside the company predicted this day 15+ years ago…
Only just started getting used to AzureAD* cmdlets
use microsoft graph :-)
Microsoft killing off AzureAD commandlets anyway. RIP.
@@alexmags I know, I’m behind the times
@@NTFAQGuy sir you come here and make me 😂