What is our primary use case?
To be able to use it, we do a lot of security permissioning within Microsoft Entra ID, although it is not our main identity provider. It makes sense to do it with Microsoft Entra ID because there is more granularity and there are more attributes that I can use.
We have a close to Zero Trust model as much as possible. We have biometrics set up absolutely everywhere, and we attach each user to a machine. Even if we work together, if I pick up your computer, I will not be able to log in on your machine to do any work. It is not fully Zero Trust in that sense, but it cuts down on the risk as much as possible.
How has it helped my organization?
The impact of Microsoft Entra ID is more on the user side. We are able to connect it to Intune, so users use their SSO credentials to get onto their user profile, and that exact same process works on macOS via MDM. We also have a next-gen VPN client, and because we also use Microsoft as our identity provider, they all use the same token. When I log into the computer, I have an active token, which automatically logs me into the VPN. That is a really nice and big benefit. The user never has to remember to connect to the VPN because it happens automatically in the background.
Microsoft Entra ID has influenced our setup through the ability to SSO the user login. It collects everything together and makes it a pretty package. For the end user, it is just easier. For me, it cuts down the attack surface to something significantly small.
What is most valuable?
I have realized benefits from Microsoft Entra ID. The other large option is moving to Google, and Google is unapologetic about not having certain things, and it is okay with that. Comparatively, with Microsoft Entra ID, the one big benefit is that there is usually a way to make it do what I need it to do. That is a benefit, but it is also not simple. I can't have it do what I want it to do without learning that only certain options are available via the graphical user interface, other options are only available via PowerShell scripts, and other options are only available by doing it via an enterprise app.
What needs improvement?
My biggest gripe with Microsoft Entra ID is that when I save something, it could take 30 seconds or it could take two days, and I don't really know where on that spectrum it is going to fall. It is not specific to a function, and it is not specific to a type of action. It falls into that error state. I don't even want to call it an error because no error comes up. It saves, but something happens where I have seen it take not two days, but a little over 24 hours.
I think that is the biggest issue for Microsoft Entra ID. After that, the reason why a product such as Okta is still more than viable, and is the leading provider, is that setting up SSO applications within Microsoft is not intuitive and not easy. There is also less of an inventory and library of applications.
For how long have I used the solution?
I have been using Microsoft Entra ID for two years.
What do I think about the stability of the solution?
We have had downtime and a crash with Microsoft Entra ID. Besides that one, and I think the Cloudflare outage or the AWS outage earlier this year also affected it, this last one was bad, but besides that, they were all nominal. On the reliability side, I have nothing bad to say.
What do I think about the scalability of the solution?
Microsoft Entra ID is the most scalable, which is, again, part of why it is the necessary evil.
Which solution did I use previously and why did I switch?
We use Okta alongside Microsoft Entra ID for the single pane of glass. From the GUI, I can do absolutely everything with Okta, and it is simple.
Prior to Microsoft Entra ID, we have always used Okta and Entra together.
How was the initial setup?
My experience deploying Microsoft Entra ID is that it was already deployed when I started.
If it is done at the beginning, it is extremely easy to deploy.
What was our ROI?
I have seen return on investment from Microsoft Entra ID in the best way possible, and I really don't mean this in a bad way. It is a necessary evil. In terms of options, you can host your own Exchange Server, but there are so many inefficiencies that come from that. There are so many more chances of things going down, although things did go down very recently. However, that is a much smaller gap than if a server were to crash and it is your only Exchange Server. That is one option. The other option is moving to Google, as I said. The migration is horrible. There is then a learning curve for users because it is extremely different. You also don't get the level of granularity with group types in Google that you do in Microsoft. In Microsoft, you have Distribution Lists, Security Groups, Microsoft 365 Groups, and many different types of groups that don't exist in Google. In Google, they are just groups. Shared Mailboxes don't exist in Google. I call it the necessary evil because it is genuinely the better product.
When I say Microsoft Entra ID, I am generalizing the entire Microsoft ecosystem as a whole, because for me it all ties together.
It is comparable to buying a Tesla for its smarts but not the car. You can’t do that. It is a necessary evil because Microsoft does a lot of things really, really well. However, with the things that it doesn't do well, it seems to be okay with just being okay.
What's my experience with pricing, setup cost, and licensing?
When it comes to the pricing, setup costs, and licensing of Microsoft Entra ID, you have Microsoft 365 E3, E5, and E7, and E1. You have Business Premium, which does 95% of what an E3 does, but not the whole thing. However, there are things in Business Premium that E3 doesn't have. E5 used to have everything, but now there is E7, and E7 doesn't have everything in it. You still have to have add-ons to be able to get the entire suite of features. On top of that, you have Microsoft 365 E1, E3, E5, and E7, and you have Office 365, which uses the same style of nomenclature, and they have astronomically different licensing.
Microsoft Entra ID’s licensing is totally new. It is completely different. It is not streamlined at all. You cannot call someone and get someone who actually cares on the phone.
That is terrible, but the partner programs are great because the partners do care about those things. However, now you have to work with a partner. So, am I getting the best price possible because I am working with a partner versus going direct? I cannot go direct. I don’t like it at all.
Which other solutions did I evaluate?
Before selecting Microsoft Entra ID and Okta, we did not evaluate other solutions. Those were the two.
What other advice do I have?
Since implementing Microsoft Entra ID, I would say this isn't relevant because we have external tools that do that for us.
Our approach to defending against token theft and nation-state attacks has not changed since implementing Microsoft Entra ID.
We don't require a passkey, so device-bound passkeys in Microsoft Authenticator have not affected our approach to phishing-resistant authentication.
On a scale of one to 10 overall, I would rate Microsoft Entra ID a seven.
My advice to someone evaluating Microsoft Entra ID is this: if you have nothing in place, use Google. If you don't have Microsoft in place, consider Google and Okta. If you already have Microsoft in place, it is not worth swapping it out because of the benefits that are already there. Again, the return on investment just isn’t there for swapping over if you have already dedicated time to Microsoft Entra ID.