Microsoft Entra ID Reviews

My main use cases for Microsoft Entra ID are identity and using Conditional Access to lock down security measures and ensure people are not engaging in risky activities when signing in from home.

I really love the Conditional Access feature of Microsoft Entra ID because it provides the security controls that we have sorely needed.

The impact of Microsoft Entra ID on my secure access to apps or resources in my environment has been significant. It has been helping us prevent phishing attempts, MFA phishing, password theft through SharePoint links, and similar threats.

Microsoft Entra ID's integration capabilities have had a significant influence on our Zero Trust model because we have been strengthening our security model over the last six months.

I have observed changes in the frequency and nature of identity-related security incidents. We have seen the reduction of risky behavior that is now being mitigated automatically rather than requiring our security team to investigate and determine if the user is legitimate. The system handles it automatically, and then we can investigate at our leisure instead of having to respond immediately.

I believe that Microsoft Entra ID can be improved by adding more granularity in options within Conditional Access specifically, because there are certain scenarios that we cannot address due to insufficient options to set up those rules.

Another area for improvement is IPv6 detection, which needs significant enhancement. I understand the technology is difficult because IPv6 contains billions of IPs, but the location detection for IPv6 is not effective.

I have been using Microsoft Entra ID for five years.

The stability and reliability of Microsoft Entra ID are quite good. There have been only one or two outages in the last two years, and I have not experienced any major issues.

Microsoft Entra ID scales very well to the growing needs of my company and is highly scalable.

Customer service and technical support for Microsoft Entra ID is about average and could definitely use some improvement.

I have not used another identity solution before choosing Microsoft Entra ID. This is the only one we have used, unless you consider Active Directory on its own as another product. Our entire infrastructure is Microsoft.

The experience with deployment of Microsoft Entra ID was straightforward and quite easy.

The biggest return on investment for me when using Microsoft Entra ID comes from its hybrid capability with on-premises Active Directory. Conditional Access, since we rolled it out, has significantly increased our return on investment as this was not something we had available before.

The pricing, setup cost, and licensing of Microsoft Entra ID is reasonable and probably one of the more competitively priced solutions available.

I did not consider other solutions before choosing Microsoft Entra ID.

Microsoft Entra ID has helped us prevent tokenized threats through Conditional Access policies. Since we obtained the P2 license to implement more advanced Conditional Access features, we have been able to prevent those threats much more frequently.

The impact of features from Microsoft Entra ID on defending against threats has been significant. Attacker-in-the-middle attacks have been the most significant help to us.

The reason is because of those phishing attempts. When you click a link, the person types in their username, provides their MFA, and the attacker replays that attack. However, because of Conditional Access, it is mitigated and they get denied access because of the attack.

Since implementing Microsoft Entra ID, my company's approach to defending against token theft and nation-state attacks has changed.

The implementation of device-bound passkeys in Microsoft Authenticator has not yet affected my company's approach to phishing-resistant authentication, but it is on our roadmap.

My advice for other companies that are considering Microsoft Entra ID is to get the higher tier, the P2, because it provides the security features that you really need at that level. I would rate my overall experience with Microsoft Entra ID as an eight out of ten.

Hybrid Cloud

Microsoft Azure

Our main use cases for Microsoft Entra ID are for governance while we're transitioning off of on-prem Active Directory.

I appreciate Microsoft Entra ID's ease of use for the identity governance aspect of it, and I also appreciate the app registrations and the enterprise applications.

The implementation of Microsoft Entra ID has definitely made it much easier to access apps or resources in my environment, eliminating the need to use VPN to get into things, providing conditional access, managing client secrets and tokens.

Microsoft Entra ID's integration capabilities have definitely made it easier for my zero-trust model; we can set up the secrets, we can set up the conditional access, and we have functionality for lockouts if we have any suspicious activity, such as logging in with a suspicious IP or from an unusual area.

Since implementing Microsoft Entra ID, I've observed real-time analytics, receiving alerts whenever there's suspicious behavior, being able to quickly review the logs, and identify issues with users or applications authenticating; it's been excellent.

The features of Microsoft Entra ID such as token replay detection, attack-in-the-middle detection, and verified threat actor IP protection have all had an impact on defending against these threats, with the last one being particularly significant.

With Microsoft Entra ID, the alerts and being able to have trusted domains and trusted areas, making sure we have ranges of IPs that have been identified as bad actors, have benefited my organization by making the entire process much more simplistic.

I don't know how Microsoft Entra ID can be improved; I think it works really well right now. I appreciate the breadcrumbs when I move through the different blades, and most of the functionality is fairly easy to figure out. My recommendation is to continue doing things that work, pay attention to customer feedback, and provide good ways for us to give feedback through user voice.

I have been using Microsoft Entra ID for the last six or seven years.

The only downtime I remember is the major one when AWS went down a month ago.

We have expanded usage of Microsoft Entra ID by approximately 15% since implementation, and that process has gone really well.

On a scale from one to ten, I would rate customer service and technical support a decent score, with no concerns.

Positive

Prior to adopting Microsoft Entra ID, we were using another solution to address similar needs; we had physical authentication keys, VPN access, and a secure client set up, so it was a combination of multiple different things.

The implementation of device-bound passkey in Microsoft Authenticator had significant resistance when we rolled it out, but now that people are used to it, it's made things much easier for our approach to phishing-resistant authentication.

I would describe my experience with deploying Microsoft Entra ID as intermediate.

I wouldn't say I'm a pro with Microsoft Entra ID; I don't think I could just run with it and conduct a full implementation on my own, but I don't think it would be a struggle to assist other people if I had a team to help me out.

What worked well with Microsoft Entra ID deployment was the training we provided, although change is hard for people and new technology; we have to get a grasp on it before we can expect anyone else in our organization to understand what's going on and why we're doing it.

My experience with the deployment of Microsoft Entra ID went well; I don't recall any major issues, and we stayed within our timeframe of when we wanted the project concluded.

I'm not certain about the return on investment with Microsoft Entra ID.

I'm not a procurement person, so I don't have to deal with any of that regarding pricing, setup costs, and licensing.

I honestly don't know what other solutions we considered before selecting Microsoft Entra ID.

I wasn't really a part of the evaluation process for Microsoft Entra ID; I gave my insights on having used it at previous companies, and they had already had it on the shortlist of things they wanted to move forward with, so I think it was an easy choice.

I think our organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID; we're much more diligent about expirations, who has access to it, conducting certificate renewals for shorter periods of time, and making sure that it has only the access it needs, so it's definitely caused us to be more holistic in our approach to it.

The factors that led me to consider a change included needing to modernize, keeping up with new technology, continuing trends in security, and making it easier to administrate.

My advice to other organizations considering Microsoft Entra ID is to carefully evaluate its capabilities and how it aligns with your needs. I gave this review a rating of ten.

Hybrid Cloud

Microsoft Azure

Our main use cases for Microsoft Entra ID include single sign-on into every application, even third-party.

The feature I like most about Microsoft Entra ID is the single source of truth for the data.

Microsoft Entra ID integration capabilities have influenced our zero-trust model heavily. We are also passwordless and we use PIM as well.

Since implementing Microsoft Entra ID, I don't think we have any identity-related security incidents because you have to have a fingerprint to even log in.

The implementation of Microsoft Entra ID has hardened our approach to defending against token theft and nation-state attacks. You have to be on a hybrid-joined device to access the system, so basically if you're not on a company device, it doesn't matter where you are in the world; you can't even get on anyhow.

Microsoft Entra ID protection has had the most impact on defending against threats such as token replay detection, attack on the middle detection, and verified threat actor IP. The features have had an impact on defending against all of the ones that I listed.

The verified threat actor IP and Microsoft Entra ID protection features have benefited our organization by helping secure our edge and preventing any type of data breaches.

Improvement for Microsoft Entra ID is a hard one; I don't necessarily have one.

I can't think of anything that immediately comes to mind.

I have been using Microsoft Entra ID for 25 years, even though Entra has only been around for a short time. It used to be called Active Directory.

I assess the stability and reliability of Microsoft Entra ID as being up 98% of the time.

I have experienced downtime. We've had instances of downtime.

Microsoft Entra ID scales well with the growing needs of the organization.

I can't expand anymore unless we hire more people; everyone in our company has an ID.

Since we have expanded, the process was easy.

On a scale from one being the worst and 10 being the best, I rate my customer service and technical support as an eight.

I rate it an eight because it depends on the engineer you get. Sometimes you don't get great engineers, but if you get the right engineer, it's good. Sometimes I'll just put in another ticket if I get the wrong engineer.

I evaluate my customer service and technical support as an eight for the same reason. Sometimes they have engineers that don't perform as well.

Positive

I would describe my experience deploying Microsoft Entra ID as definitely a challenge. We use SailPoint to manage it, and we actually have a third-party tool to help with it for the workflow of it.

What worked well with deploying Microsoft Entra ID is that it's already integrated into the Microsoft landscape. It just works with everything that's already Microsoft.

My experience with the deployment was good.

My experience with the deployment involves still using the on-prem integration. We push from on-prem to Entra, so we're not fully offloaded off the on-prem, but that's in case our network goes down and we can still work. The deployment was pretty seamless.

We use SailPoint to manage it, and we actually have a third-party tool to help with it for the workflow of it.

I have seen a return on investment with Microsoft Entra ID.

Before selecting Microsoft Entra ID, I don't think we considered any other solutions. We're a Microsoft shop, and we do everything Microsoft.

Since we don't have the premium licensing, just the regular E3 licensing, and we've been licensing it for where I'm at for over a decade for sure.

My advice to another organization considering Microsoft Entra ID is that it's a hard one to give. I think most people are already on Microsoft Entra ID, at least in the Fortune 500 companies. Literally everybody uses that, so I don't know anybody that would be doing a new deployment.

I rate this review a 9.

Hybrid Cloud

Microsoft Azure

Our primary use case for Microsoft Entra ID is mainly for single sign-on (SSO). We use it to log into other cloud-based applications. We have an internal sync from Active Directory to Microsoft Entra ID. Whenever an account is created in Active Directory, we immediately create an account in Microsoft Entra ID to automatically grant access to cloud-based applications. Some roles are assigned based on Microsoft Entra ID data.

Microsoft Entra ID's ability to extend and divide multiple applications based on requirements is valuable. It allows easy integration with One Identity and enables effective application management. The security configuration is straightforward and limits access to admin only, ensuring data integrity. Microsoft Entra ID enhances the Zero Trust model by providing simple integration and dedicated permissions for each application. Its features like token replay detection, attack-in-the-middle detection, and especially verify threat actor IP have been impactful in defending against threats.

I suggest improving the connector part. For technical users like me, it is manageable, but having comprehensive documentation for those who aren't familiar with the system would be beneficial. Additionally, synchronization issues occasionally occur, making it challenging to analyze logs and pinpoint the exact problem. Providing more detailed log information for synchronization failures would be helpful.

I have been working with Microsoft Entra ID for approximately six years.

I encountered no issues with the deployment of Microsoft Entra ID.

I find the stability of Microsoft Entra ID to be excellent. I would rate it a ten out of ten.

In terms of scalability, I would rate Microsoft Entra ID a nine out of ten.

I rate Azure Technical Support a nine out of ten. Whenever we require support, we receive it promptly.

Positive

I have primarily used Microsoft Entra ID. In various projects, we consistently used it and didn't switch to other solutions.

The initial setup of Microsoft Entra ID was simple.

We used an out-of-the-box connector available in One Identity management for connecting processes. It's easily available for configuration, and we customize it as per requirements.

The pricing for the setup and the cost overall is reasonable. I would rate the pricing nine out of ten, as per today's market.

Based on my experience, I would rate Microsoft Entra ID a ten out of ten. Setting up Microsoft Entra ID was simple. In terms of company size, I recommend it for enterprise-level companies. I find the overall pricing to be average but reasonable. As a real user of Microsoft Entra ID, I am not affiliated with the vendor or partners.

Hybrid Cloud

Other

We use Microsoft Entra ID for multi-factor authentication (MFA) and users logging in for any Microsoft applications, especially for Microsoft 365.

Microsoft Entra ID has helped make our company more secure. Conditional access policies have assisted our users in logging in from various locations, not just on-premises.

Microsoft Entra ID makes the apps or resources in our environment more secure, especially with conditional access policies.

We use the cloud sync, so we can sync up with our Active Directory user accounts with the on-premise AD. There is a single password for the user, so we can put all the policy requirements and password complexities around it. It helps when the user does not have all these separate passwords, and we can make passwords more complex for better security.

We have not used the device-bound passkeys, but the Microsoft Authenticator app has helped a lot in terms of proving that the users are who they say they are, helping with the MFA authentication. It is a pretty easy-to-use app, especially with the number verification. It provides an extra later when someone is not just accepting an MFA prompt on their phone in the middle of the night.

Microsoft Entra ID has helped us defend against token theft and nation-state attacks. We were at more risk without it. It has helped us to better secure our environment and our users.

When we implemented it many moons ago, it increased our incidents, but Microsoft has gotten a lot better and the incident count has dropped dramatically. When you put in your users' ability to log into the cloud, if anyone has an email address of a user, they can just go to Microsoft.com and try to log in. That increases incidents, but the MFA and contextual policies help reduce the incident count.

I find the conditional access policies to be the most valuable. They provide a lot of granularity in determining where the users can log in from, how they log in, and what they have access to.

Having a little bit more logging would be beneficial. Better user sign-in logging is needed. We work with Okta, and the two of them do not always work well together. We can have more insight into some of the user information and how it interacts.

I have been using Microsoft Entra ID for about six years.

Microsoft Entra ID is a stable solution. We rarely had significant problems or crashes. We have had very few issues over the years.

We have never had any issues with the scalability of Microsoft Entra ID.

I would rate their technical support a six out of ten. It requires starting at the bottom and working our way up, which is time-consuming. The tech support model or the person we are working with is not always knowledgeable to the level we need help. 

Before we call support, we would have already exhausted many possibilities. Having to start at the bottom and go through it all over again is frustrating because time is very critical. When working with support, it can be frustrating because we have to go over things that we have already tried to resolve.

The time they take to get back to us is also sometimes longer. They have their SLAs, but when you are back and forth with the rep, it sometimes takes a lot of time.

Neutral

We were a Novell shop before migrating to Microsoft. The decision to migrate happened many years ago before my time at the company.

We have a hybrid setup. We had a partner to help us. It was fairly easy. I have since done smaller implementations on my own, and it is fairly straightforward and easy.

Our partner had an implementation strategy for us. We worked with them to implement the solution.

Our implementation team was assisted by a partner named Araya. Working with them was a good experience. We were able to get everything migrated and launched in Microsoft Azure. Overall, it was a good experience, enabling us to launch in Microsoft Azure successfully.

I would rate Microsoft Entra ID a nine out of ten. You have to do a lot to get a ten.

Public Cloud

Microsoft Azure

Our primary use case is for identity platform and security platform, mainly for multi-factor authentication (MFA), to make all access to our enterprise applications unified for each user.

Our most valuable features are conditional access and Azure application proxy. The passkeys are a significant improvement, giving us the most phishing-resistant MFA.

Entra allows us to provide access to more users without a VPN, especially for our web-based platforms, which are published with the application proxy and MFA. Reducing VPN usage has been beneficial for us. The ability to offer employees access to any platform, including private PCs and tablets, has been a game-changer.

Private access and internet access should be available in a less expensive licensing model.

I was using Active Directory for more than 10 years before we switched to Entra ID.

We have experienced no problems with stability. We have had full uptime at all times.

Entra is a cloud solution, so scalability is not a problem for us.

The technical support has its downsides and upsides. While they are fast, it can take time to get the right person because there are many steps to reach the appropriate team member at Microsoft support, which can be somewhat annoying.

Neutral

We started with Office 365, so there was a clear statement that we would be using this solution.

The initial setup was prompted by the COVID pandemic and was executed as a big bang.

We only used Microsoft with direct workshops, and all the specialists had their work done well.

We are an enterprise customer with an enterprise agreement in place with many of our partner companies, so there are no special questions or issues about pricing, setup cost, or licensing.

I rate Entra ID 10 out of 10. We are fully satisfied. It's a seamless transition from Active Directory. There is no steep learning curve, and our knowledge from Active Directory allows for a fast ramp-up.

Public Cloud

Microsoft Azure

I use Entra to log into systems and applications, mainly within the office for work-related tasks and for other applications that accept Microsoft Authentication. I always use my work ID to log in when I can. Within the organization, everyone has an ID, so I'm engaged with the onboarding process, but I don't create the IDs.

I don't know what they had before Entra, but if we didn't have the solution, we wouldn't have a security model for Microsoft 365 products like Outlook, Excel, and all the other Office stuff. We wouldn't have a secondary way to identify people. Entra hooks into everything else that Microsoft does, making it much easier to manage security across systems and platforms.

Entra has made securing our apps and resources more straightforward. Microsoft has updated security methods to make its authentication more secure. The solution has facilitated our Zero Trust Model. You can't use the computers without authenticating. There is no public access, so unless you sneak up behind someone and take over their computer, you can't do anything without an ID.

I'm not on the security team, so I don't know the effect of Entra on the number of security incidents. Anecdotally, I know that some people at my organization don't like passwords, and they've had to get over that. Those people have likely seen a drastic decrease in identity theft incidents.

I love how it uniquely identifies a person universally. If you have the email address, it will be the same account across most platforms. If everything is set up correctly, it's easy to identify a person and get all kinds of information about them from Azure or whichever system. 

Microsoft support has some room for improvement. I avoid contacting them because it can be time-consuming. They don't necessarily find the solution, but you have to be on call for them to connect and do things on your system remotely. You have to schedule a time to meet with them, and it's somewhat inconvenient.

I've been using Entra ID for about 12 years.

Entra has never gone down as far as I know, so it's 100 percent stable.

It's stable for our organization of about three hundred people and can handle scalability.

I rate Microsoft support six out of 10. 

Neutral

The biggest return on investment on Entra is improved security, ensuring our organization is less of a target. It works how it's intended and does a good job.

It's the most basic Azure service available, and I understand it's cost-effective. You need a tenant to use Entra to authenticate.

I would rate Microsoft Entra ID a solid 10 out of 10.

On-premises

Microsoft Entra ID serves as the central repository for all of my service principals for the integration side of things, user management for different groups, and permissions, with a lot of role-based access control and service permissions mainly.

The features of Microsoft Entra ID that I appreciate the most include permission management.

Examples of how the features of Microsoft Entra ID have benefited the organization include permission management and general security, as we use Entra as our authentication and SSO tool, which has been performing well, and we have it synced up with our on-premises AD as well.

The implementation of Microsoft Entra ID has positively impacted my secure access to apps or resources in my environment because I appreciate that it has SSO, so you can use it for signing on to a whole bunch of different applications that are also running in your enterprise, and it is generally very good for governance of getting people access to whatever they need.

To improve Microsoft Entra ID, I think on the left navigation bar when you actually open Entra, there is a button that you need to click to make every option available for that tab open, so you always need to click that button, which is an arrow facing upward and an arrow facing downward.

I have been using Microsoft Entra ID for four years.

I assess the stability and reliability of Microsoft Entra ID as generally good, as I have not necessarily experienced downtimes, crashes, or performance issues, though there have been minor issues with the Azure portal itself.

Microsoft Entra ID scales well with the growing needs of the organization, as I have not had many issues with it at all.

I have expanded usage of Microsoft Entra ID. The process of expanding usage was fairly smooth, though I would not know the metrics behind it.

I would rate my customer service and technical support for Microsoft Entra ID around a solid seven, as I have never had to contact Microsoft support for Entra.

Positive

I would not know what other solutions I considered before selecting Microsoft Entra ID.

I have only used Microsoft Entra ID at my organization, and prior to adopting it, I did not use another solution to address similar needs.

I would not really know about my experience with deploying Microsoft Entra ID, including what worked well or what challenges I faced.

I am sure my company has seen a return on investment with Microsoft Entra ID, but I would not know.

I would not know about the pricing, setup cost, and licensing of Microsoft Entra ID.

I do not know if I am suited enough to answer in what ways Microsoft Entra ID's integration capabilities have influenced my zero-trust model.

I could not share any changes I have observed in the frequency and nature of identity-related security incidents in my organization off the top of my head.

I would not know if my organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID.

I would not say that the implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance, as I could not say since I do not have that information.

My advice to another organization considering Microsoft Entra ID is that it is a really good identity tool, though I am not so much ingrained on the infrastructure side of things, so I could not be the person to say this is what you should go for, but I appreciate using it as it is good for whatever I need to do, which is permission management and other tasks. I would rate this product an 8.5 out of 10.

Hybrid Cloud

Microsoft Azure