Microsoft Entra ID Reviews

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.

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

We are using Microsoft Entra ID as a SAML provider for two products: Zscaler and Microsoft Sentinel, where we authorize users into the security SIEM platform.

I genuinely appreciate the attack surface reduction tool in Microsoft Entra ID, as well as the regional risk geofencing feature, which are excellent tools that I have used extensively.

I appreciate how you can authenticate into Microsoft Entra ID directly through its independent URL or also through the Azure portal.

Microsoft Entra ID being a single sign-on solution is beneficial because once you log into one platform, it allows you to access the other platforms seamlessly.

As an identity product, Microsoft Entra ID has a secure score rating system, which I find valuable.

I appreciate that Microsoft Entra ID underwent rebranding from Azure AD to Microsoft Entra ID, which was a positive change.

Microsoft Entra ID probably does not need any improvement at this time; it is the best solution available since there are two ways to access it, and I do not believe it requires any enhancements as it currently stands.

Regarding additional features, I would suggest more sandboxing capabilities, but I do not believe sandboxing is necessary within Microsoft Entra ID itself. Microsoft could potentially add a sandbox feature similar to CrowdStrike, the competitor, but it is not essential.

I have been in information security using Microsoft products for approximately fifteen years, with Microsoft Entra ID implementation starting in 2022.

I have experienced one hundred percent capability and full uptime with Microsoft Entra ID, so the stability and reliability are commendable.

I would rate customer service and technical support as ten out of ten. The support is excellent with local representatives available, and we have ISMs, CSMs, and TSMs with Microsoft who are very reachable and approachable.

Prior to adopting Microsoft Entra ID, I was not using another solution to address similar identity needs.

Deploying Microsoft Entra ID is straightforward. Once you gain access to admin.microsoft.com, this functionality is already built-in, so there are no deployment issues. I would rate the deployment process as ten out of ten since Microsoft products are very simple to deploy. It is entirely cloud-based, making it very easy and plug-and-play, functioning as a bolt-on solution with Microsoft Entra ID.

I believe the licensing for Microsoft Entra ID is excellent, as it includes everything with G5 or E5 plans, making the licensing structure a great option.

Okta would be a possible alternative, but I am a much bigger advocate for Microsoft Entra ID than Okta, despite them being competitors.

Microsoft Entra ID is easier to implement because it uses Google Authenticator through its own Microsoft authentication, whereas Okta requires a separate application, which can be inconvenient.

We have implemented a secure-based token system called SBC since adopting Microsoft Entra ID.

Token-based security has had a positive impact on defending against threats with Microsoft Entra ID. It functions as a tool similar to FIDO, serving as an MFA factor whether you have it or not.

While Microsoft Defender offers a very good attack simulation module, Microsoft Entra ID has built-in MFA, which eliminates much of the concern. I personally prefer using Google Authenticator on my phone for authentication, which creates a very secure environment.

When selecting an identity management solution, I would strongly recommend choosing Microsoft Entra ID over Okta. It is easier to implement because it is already integrated into the system, making Microsoft Entra ID very much universal with other security tools you will obtain, especially with Microsoft.

I would rate this solution an overall ten out of ten.

Public Cloud

Microsoft Azure

My main use cases for Microsoft Entra ID are primarily for Active Directory and tenant management, as well as software authentication.

The feature I appreciate most about Microsoft Entra ID is the ability to access it programmatically instead of having to use only the UI, and there are multiple different ways of accessing and managing it. Microsoft Entra ID has provided my company with a centralized place to establish a source of truth for the attributes of our personnel. Microsoft Entra ID benefits my organization by giving us the ability to bring in external sources by registering them within our tenant, and it also gives us much more security control, allowing us to collaborate and share data while remaining secure with only those accounts that we can manage.

One challenge we have faced with Microsoft Entra ID has been with the hybrid model, and we often have to keep some of the security groups on-premises with a mix of distribution. The variety of different group types has caused challenges in areas where we have Microsoft 365 groups, distribution groups, and security groups, and the different types do not always make programmatic management clear.

I have been using Microsoft Entra ID for approximately five years.

I would assess the stability and reliability of Microsoft Entra ID by saying that we have been very satisfied with its stability so far. We have not experienced any downtime or crashes other than those caused by Microsoft. The small outages we have seen have been primarily vendor issues or similar in nature.

I have seen a return on investment from Microsoft Entra ID. The major ease of use has certainly made it much easier, and that is worth the value that we are paying.

Regarding pricing and the setup cost for licensing Microsoft Entra ID, I do not get involved with the pricing, as it is simply a matter of recommending the technology that we use, and then the pricing gets handled by those that are adopting it.

I did not consider other solutions before I started using Microsoft Entra ID. Microsoft has been a good partner for us, and we continue to use their products.

Microsoft Entra ID's integration capabilities influence our Zero Trust model by allowing us to lock down access for certain things that are within our tenant and not worry about things that are not authorized to get in. Since implementing Microsoft Entra ID, I have not seen any changes in the nature of identity-related security incidents. We transitioned from on-premises to a hybrid model, and it made it easier for us to implement application security, especially when it is external-facing. Our organization's approach to defending against token theft and nation-state attacks has not changed since implementing Microsoft Entra ID. The implementation of device-bound passkeys in the authenticator has not affected our current approach to phishing-resistant authentication. I would rate this review as an 8.

Hybrid Cloud

Microsoft Azure

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

Seamless single sign-on into various destinations within the enterprise application space is a main use case for Microsoft Entra ID. ADP uses a variety of different applications throughout the organization, which serves as a common thread connecting those various applications.

The features of Microsoft Entra ID that eliminate the need to remember provisioning and passwords provide a seamless, frictionless experience. Not having to remember passwords benefits the company because employees can focus on their core work and their primary job responsibilities rather than the backend processes. For an organization with tens of thousands of employees, the implementation of Microsoft Entra ID makes security paramount, ensuring that the right people based on their roles and permissions have appropriate access to applications.

Security is paramount in this context.

I'm uncertain how Microsoft Entra ID's integration capabilities have influenced the Zero Trust model. I am not aware of any identity-related security incidents since becoming involved with Microsoft Entra ID, which is perhaps more of a testament to the security organization having things locked down so that any such incidents are completely transparent to people at my level.

Prior to it being called Entra, it was Microsoft Active Directory, which has been used for as long as I can remember. The earliest point was probably around 2010, when it became obvious what was being used.

I am not aware of any stability and reliability issues with Microsoft Entra ID. It is very rare that I sense any sort of hiccup, outage, or anything of that nature.

Microsoft Entra ID scales well with the growing needs of the company. ADP is a large organization with tens of thousands of employees, and I am not aware of any known scalability issues.

I have not directly experienced customer service and technical support from Microsoft at my level.

From an end-user experience perspective, the deployment experience of Microsoft Entra ID was very easy. The transition from the previous state to the current state was smooth, and users did not have to become experts. It was a very consumer-oriented experience in learning what to do and how to do it, and I found it to be quite easy.

The biggest return on investment from my perspective when using Microsoft Entra ID is a combination of security and risk avoidance with perceived or actual threats, which is paramount. Employee productivity is another front that directly impacts return on investment, and both security and productivity are essential—one cannot exist without the other.

ADP continuously conducts ethical hacking and penetration testing into the system to ensure that systems are protected. I am not aware that the approach to defending against token theft and nation-state attacks has necessarily changed over the past few years.

The features of Microsoft Entra ID such as token replay detection, attacker-in-the-middle detection, and verified threat actor IP do not appear to have had any effect that I am aware of.

Most of my experience with Microsoft Entra ID is within my work tenant at ADP. However, in my role, I also work with other enterprises in the ecosystem where I am required to use their tenant. Sometimes I sense complications when moving from one tenant to another, which is simply because different enterprises have different security guidelines. Microsoft Entra ID does not appear confused by this, but it seems like the experience is not quite seamless at times.

ADP has a multi-million dollar contract with Microsoft, and identity management is included in that agreement. While other solutions may have been considered, the tight relationship with Microsoft makes it difficult to imagine they would have selected anything other than a Microsoft solution.

When selecting a provider, consider your company culture, user base, and what is likely to work within your business. Examine your security requirements and goals, and ensure that whatever provider you select is consistent with those challenges and objectives. I would rate this review as an eight out of ten.

Public Cloud

Microsoft Azure

My main use cases for Microsoft Entra ID are authentication and single sign-on for multiple applications, both Microsoft and other systems.

Since implementing Microsoft Entra ID, we receive many more notifications for risky users, which is great because that was one of the areas where we really had blindness and could not see. Having that kick off automatically is excellent, and we are able to remediate those users right away.

Our organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID, as we had no idea there was such a thing.

The implementation of device-bound passkeys in Microsoft Authenticator has affected our organization's approach to phishing-resistant authentication, as the improvement where they forced us to move from just entering okay to actually entering a number has improved the platform quite a bit.

The features of Microsoft Entra ID that I like most include single sign-on for all of our applications.

The implementations of Microsoft Entra ID have controlled all of our access into a single platform, which has been great.

Microsoft Entra ID's integration capabilities have improved our Zero Trust model and have done an excellent job.

Microsoft Entra ID can be improved by probably including a better review of all of the accounts in Entra ID in the next release.

I have been using Microsoft Entra ID for seven years.

I assess the stability and reliability of Microsoft Entra ID as having experienced no downtime, crashes, or performance issues.

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

I have expanded usage quite a bit.

The process when expanding usage of Microsoft Entra ID was very easy and smooth.

I would rate my customer service and technical support as about a five right now, as we just got in contact with our Microsoft rep, so it is improving.

I would evaluate my customer service and technical support as probably a six or seven; it is pretty good.

Prior to adopting Microsoft Entra ID, I was not using another solution to address similar needs.

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

I did not really face any challenges during the implementation.

My experience with the deployment of Microsoft Entra ID was easy, and there is a lot of good documentation, so it was fairly easy for us to get implemented.

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

My experience with the pricing, setup costs, and licensing is that I take care of it, but I do not know the details.

Before selecting Microsoft Entra ID, we looked at Okta and also considered Cisco's solution.

What stood out in my evaluation process when comparing options for Microsoft Entra ID was that cost was probably one of the big ones, and integration into the rest of our platform was actually one of the big pluses for us.

My advice to another organization considering using Microsoft Entra ID is to go for it. I would rate this review a seven overall.

Hybrid Cloud

Amazon Web Services (AWS)

Everything for Office, for VPNs, AVD, or all VDIs are my main use cases for Microsoft Entra ID.

Conditional Access is one of the features of Microsoft Entra ID that I like the most. I think it's the one that we use the most.

The implementation of Microsoft Entra ID has made secure access to apps or resources in my environment more secure.

Microsoft Entra ID's integration capabilities have influenced my Zero Trust model significantly.

Microsoft Entra ID as a whole has created a lot of business for us. Since we're doing this every day, the impact is pretty huge.

I don't have any suggestions for improvement at this time.

My experience with the pricing, setup costs, and licensing of Microsoft Entra ID indicates that we need to make it simple. It's way too complicated. Customers are getting confused about what package and everything. It's confusing for them to actually know what features are actually included. Despite the documentation, it's too complex because there are too many add-ons and too many options. The number of options and packaging is too extensive.

I would assess the stability and reliability of Microsoft Entra ID as not really having experienced any downtime, crashes, or performance issues.

Microsoft Entra ID works perfectly and scales with the growing needs of my organization as it's the perfect source to use with perfect tools.

On a scale from one to ten, with one being the worst and ten being the best, I would rate my customer service and technical support as eight.

I give it an eight because sometimes the first support level is pretty basic and it's hard to get expertise right away on our problems. It's time-consuming for our customers. They have to wait for an answer when there's a problem in the back end. It takes longer to get support, so we actually have to subscribe to another service to get faster response from the support team.

Positive

The implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance since we're using it for all admin and users that have privileged roles inside the organization. We're using passkey throughout our organization and trying to implement it to our customers.

My experience with deploying Microsoft Entra ID has been that it's very simple to use. I think it makes sense how it's built.

The deployment process involves following the flow going from on-premises and then getting the users synchronized, using ID, and getting that going.

The usage of Microsoft Entra ID has expanded and is everywhere.

My advice to another organization that's considering Microsoft Entra ID is to go for it. I would rate this review overall as a nine out of ten.