Our primary use case for Microsoft Entra ID is as our identity provider (IdP), which is our identity platform. We synchronize our on-premises environment to the cloud and make use of cloud apps through it.
Microsoft Entra ID offers advanced identity management capabilities, ensuring security and efficiency with features like single sign-on and multifactor authentication.


| Author info | Rating | Review Summary |
|---|---|---|
| Director, Network & Cloud Infrastructure at a legal firm with 501-1,000 employees | 5.0 | As our identity provider, Microsoft Entra ID enables secure app access and zero trust. While Conditional Access is critical and improved security detection, I dislike short logging periods, costly P2 features, and the ridiculous Security Copilot charges, despite improving support. |
Our primary use case for Microsoft Entra ID is as our identity provider (IdP), which is our identity platform. We synchronize our on-premises environment to the cloud and make use of cloud apps through it.
The benefit we have realized since using Microsoft Entra ID is that everything is moving toward single sign-on, SAML integration, and OIDC. All the vendors are moving to the cloud, so logging in and signing in is key. Identity is the new security boundary, and that is where we make use of the biggest company out there for this product.
The implementation of Microsoft Entra ID has enabled secure access to our apps and resources. It is the foundation and the cornerstone. You can't do it without it.
Microsoft Entra ID's integration capabilities have influenced our zero trust model. For zero trust, I can require phishing-resistant and stronger biometric authorization into apps, and that is helping to defeat many of the bad guys who are trying to get in, such as the nation-states, et cetera.
Since implementing Microsoft Entra ID, I have seen changes in the frequency and nature of identity-related security incidents. They have gone up tremendously, but the reason they are going up tremendously is that the detection capabilities are so much better than what I had on-premises. Things are more available, and it's not just within the secure container of a VPN with all my apps behind a wall. Being able to see those attacks and have Microsoft run interference for all of those types of attacks shows you how many there are. It also gives us more detail as to who is coming after us.
Our company's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID. That is why we have gone a little bit beyond the standard MFA requirements and the registration campaigns for different levels of MFA. For us, it's all phishing-resistant.
The implementation of device-bound passkeys in Microsoft Authenticator has affected our approach to phishing-resistant authentication. It is the reason we rolled it out. It is the main reason we want that level of authentication, which is to block the theft of credentials, password harvesting attacks, and everything similar.
The feature of Microsoft Entra ID that I value the most is Conditional Access. Conditional Access keeps all the bad guys out and gives me the tools that I need to help protect my users. It is foundational to our security. It has defeated a bunch of the bad guys, and we have seen them try. With Conditional Access policies and the granularity that I keep giving them, it is only getting better as time goes by. We really appreciate that.
We use features such as token replay detection, attacker-in-the-middle detection, and verified threat actor IP in Microsoft Entra ID Protection. For Entra ID Protection and Defender for Identity, those are in place, and we have the default set. We have done some customizations, but that tends to fall underneath another team. I interact with that team, but I am not running the day-to-day.
In my opinion, Microsoft Entra ID could be better in a few ways. The default logging period for Log Analytics and other features is just 30 days, which is not sufficient.
Microsoft Entra ID P2 should be bringing more features than it does, and many of the features that it has should be rolled down to P1 and other tiers. People shouldn't have to pay for advanced security. I don't agree with that, so I would like for them to do that.
The next issue is the charges for the Microsoft Security Copilot. Those charges are ridiculous. As soon as you turn it on, anything that is being used in Defender or any visit to the page incurs a charge. That seems to be completely a money grab for no good reason, and we don't need that. We just want to run the Conditional Access agent and the other security features as we need them, and not as Microsoft decides to charge for them.
I have been using Microsoft Entra ID for seven years.
The stability and reliability of Microsoft Entra ID has been better. There have been a couple of issues recently, within the past year or two, such as when East US went down and that impacted us, along with other incidents. They could improve on the reliability.
We have expanded our usage of Microsoft Entra ID since the initial implementation. You have to. You don't have a choice once you start moving into the world of SAML.
I would evaluate Microsoft support as follows. It depends. The AI support has been okay since they started to roll that out. They made a shift within the last few years to their tech talent, and their tech talent was pretty poor for a while.
Microsoft support keeps asking for the same data set over and over and over again, and I find myself saying, "I've already given you this." It is frustrating when the case gets requeued and requeued and requeued. It could be better.
On a scale of one to 10, I would place Microsoft support at a six. They have gotten better. It was a four, but they have improved, and unfortunately, I think AI has helped quite a bit.
Before adopting Microsoft Entra ID, we were not using another solution to address similar needs. We didn't have Okta or anything else similar. We just had Active Directory.
I was involved in deploying Microsoft Entra ID, and I did it myself. It was easy. We needed a consultant to help us through it, but once you understand it and what you are doing, it's not hard.
We have seen a return on our investment from Microsoft Entra ID, but I can't quantify it.
Google Workspace is the other solution we considered before selecting Microsoft Entra ID.
In our evaluation process comparing these solutions, what stood out was that Microsoft Entra ID got rolled into our enterprise agreement, which made going to it that much easier.
| Product | Mindshare (%) |
|---|---|
| Microsoft Entra ID | 8.4% |
| Okta Platform | 10.9% |
| Auth0 Platform | 6.5% |
| Other | 74.2% |
| Company Size | Count |
|---|---|
| Small Business | 88 |
| Midsize Enterprise | 43 |
| Large Enterprise | 155 |
| Company Size | Count |
|---|---|
| Small Business | 1535 |
| Midsize Enterprise | 506 |
| Large Enterprise | 1502 |
Designed for hybrid environments, Microsoft Entra ID provides seamless synchronization between on-premises Active Directory and Azure Active Directory, enhancing security with multifactor authentication and conditional access. By integrating with a broad spectrum of cloud services, it supports user authentication and mobile device management, facilitating streamlined application registration and secure API access.
What are the most notable features of Microsoft Entra ID?In finance and healthcare, Microsoft Entra ID plays a crucial role in managing access to sensitive information while maintaining compliance with industry regulations. Retail and manufacturing sectors leverage its capabilities for secure supply chain operations and partner collaboration.
Microsoft Entra ID was previously known as Azure AD, Azure Active Directory, Azure Active Directory, Microsoft Authenticator.
Microsoft Entre ID is trusted by companies of all sizes and industries including Walmart, Zscaler, Uniper, Amtrak, monday.com, and more.