Microsoft Entra ID Reviews

We are hybrid, so we mainly use Microsoft Entra ID for control of users that we've synced out to the cloud.

The features of Microsoft Entra ID that I like the most include the dynamic grouping, which is pretty cool.

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model positively since we can actually tie in single sign-on, which has been nice.

I can't think of any metrics or data points off the top of my head to demonstrate the impact of Microsoft Entra ID integrations, but it's helped simplify logins for the end users, which is good.

Our organization's approach to defending against token theft and phishing attacks has actually changed since implementing Microsoft Entra ID, as we are working on going passwordless using YubiKeys.

The passwordless feature of Microsoft Entra ID has been nice; it's super slick since users don't have to know their password anymore. We are still working on putting it in, but it has helped reduce help desk calls where users would ask about not knowing their password, which has been pretty nice.

The centralized management with the single sign-on feature of Microsoft Entra ID has been huge, and that aspect has been nice as a data point demonstrating the ROI.

The features of Microsoft Entra ID such as token replay detection, attack-in-the-middle detection, or verified threat actor ID protection haven't had a specific impact on defending against threats for us; however, we have worked with companies that have gotten hacked, and if they were on passwordless, that would have stopped that.

I can't think of any improvements for Microsoft Entra ID off the top of my head, but I would like to see more features brought from on-prem Exchange into the cloud, which would be huge, and also with Office, there are features that we just don't have anymore, raising the question of whether we will get these.

I've been using Microsoft Entra ID for about seven or eight years.

I would assess the stability and reliability of Microsoft Entra ID as fair; I've experienced downtime and crashes, especially when trying to use PowerShell, and there have been times where it has crashed as a whole due to something on their end, which sometimes gives us issues.

Microsoft Entra ID scales with my growing needs pretty well.

I have expanded usage of Microsoft Entra ID, and the process has been pretty smooth; we've expanded into using some of the cloud features when it comes to VMs and other resources. Though it's more in the testing phase compared to being in production, so far it's been pretty easy.

On a scale from one being the worst and ten being the best, I would rate my customer service and technical support from Microsoft a three.

I would give that rating of three because the last ticket that I had open with them was open for about seven months, and I messaged them multiple times; it got stuck in a queue waiting for somebody to pick it up. I couldn't open a different ticket because that one was already in, and then after about seven months, they sent me something that said they were sorry and that my ticket got put into the wrong queue, so they went ahead and closed it and asked me to submit a new ticket.

Prior to adopting Microsoft Entra ID, I was using another solution to address similar needs that included just on-prem AD and then ADFS for single sign-on.

I would describe my experience with deploying Microsoft Entra ID as pretty seamless for the most part; however, when it goes down, it is a bit of a pain, and we have noticed challenges with the documentation since they're constantly changing information, leading to dead links that don't go anywhere, making it hard to do something when the knowledge base isn't up to spec.

My overall experience with the deployment of Microsoft Entra ID has been pretty good.

An example of my deployment experience includes migrating all mailboxes from on-prem out to the cloud, which was pretty seamless, and the users and setting up the connect piece was honestly pretty easy for the most part.

I've seen a return on investment with Microsoft Entra ID.

Prior to selecting Microsoft Entra ID, I honestly considered staying on-prem; there wasn't really anything else, maybe Google.

What stood out in the evaluation process for Microsoft Entra ID, both positively and negatively, was that we already had on-prem, so it was a no-brainer to just keep going that way with them.

The implementation of device bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistant authentication positively, as it's going pretty well, but it has helped us find applications that don't support it, which means we have to either work with the vendor or find a solution for that.

Since implementing Microsoft Entra ID, I haven't observed any changes in the frequency of identity-related security incidents in the organization; one thing that confuses everybody is where they keep changing the name. If they would just stick to one thing, that would be nice, but it is what it is.

My advice to another organization considering Microsoft Entra ID is to make sure that you build it out properly, leverage dynamic grouping as much as you can, and use proper naming schemes so you know what your groups do. I would rate this product a six out of ten overall.

Hybrid Cloud

Microsoft Azure

My main use cases for Microsoft Entra ID are all access to anything and everything Microsoft.

What I like most about Microsoft Entra ID is how it's the continuation of what was started with Active Directory to the cloud.

The impact that Microsoft Entra ID has had on my secure access to apps or resources in my environment includes the integration with the Microsoft Authenticator and the multifactor authentication.

The features of Microsoft Entra ID benefit my organization by really having everything right there; it's cloud-based, and I don't have all that dependence on infrastructure. It's somebody else's problem, essentially.

Microsoft Entra ID could be improved with more out-of-the-box integrations with other parties.

I have been using Microsoft Entra ID for six years.

I assess the stability and reliability of Microsoft Entra ID as it has never let me down; it's always there.

I have not experienced any downtime, crashes, or performance issues with Microsoft Entra ID.

Microsoft Entra ID seems to scale with the growing needs of my organization, and I haven't found a limit; it seems to do everything we want it to do.

We really haven't expanded usage of Microsoft Entra ID beyond that initial deployment; it's really focused on the Microsoft products, and it seems to work fine.

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

My experience with pricing, setup cost, or licensing for Microsoft Entra ID was easy.

I would describe my experience with deploying Microsoft Entra ID as easy, very easy; I think the hardest part was really just getting everybody's cell phone numbers so they could enroll.

My experience with deployment of Microsoft Entra ID was pretty easy; I had a one-pager I gave out to the staff that walked them through the process of receiving a text, clicking it, and installing the app. I think we had to hand-hold only a very small number, maybe 10%.

I don't know if it's more return on investment with Microsoft Entra ID; it's more so that it was a necessity.

It was easy with Microsoft Entra ID because it was baked in already with our current license level, and I didn't feel that we had to add a lot in many cases to get what we wanted out of it.

In my evaluation process for Microsoft Entra ID, nothing really stood out to me, both positive and negative; I already knew of the technology, so when it came up, it was the perfect fit.

The advice I would give to other organizations considering Microsoft Entra ID is that it's solid, but the only criticism I would give out of everything I've said so far is to keep working on those integrations with third parties. I think that's key because not everybody is all Microsoft. I rate this product a 9 out of 10.

Since implementing Microsoft Entra ID, I can't say that we've really had any changes in the frequency and nature of identity-related security incidents in my organization.

My 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 passkey in Microsoft Authenticator has affected my organization's approach to phishing-resistant authentication, and I would say it's been very effective.

It's been effective with Microsoft Entra ID because I work for two organizations, and in the education sector, we've set it up in a way where if you're on campus, you don't have to do multifactor authentication. As soon as you walk off campus, though, we have conditional access set up where you've got to do your MFA through the Microsoft app, and it has really cut down on students getting into teachers' accounts and similar incidents.

Public Cloud

Microsoft Azure

My main use cases involve daily usage as a system technician, running InTune and Microsoft Entra ID, mainly for endpoint and user management. The main metric demonstrating the impact of the integrations is that we use Microsoft Entra ID for all of our devices. When assigning or removing users, if a user is terminated, or a device is lost or stolen, we use it to remove and manage all endpoints. User migration occurs when we have new hires or terminations, and most of that is what I actively use it for.

The user-friendliness of Microsoft Entra ID is what I appreciate the most. Everything is organized, simple, and straightforward. Even new technicians can come into it and know what they're looking for. The simplicity is a major factor.

Microsoft Entra ID has not had much direct impact on my secure access to apps or resources in my environment since we have been using it from day one, so it has not really changed much, but everything I need is accessible from there.

These features of Microsoft Entra ID have worked and benefited my organization. For my day-to-day role, endpoint management, user management, and policy management within our enrollments for our devices are directly involved between Entra and InTune. It is the main housing unit for everything that I do in my role.

Currently, I don't have any main suggestions for how Microsoft Entra ID can be improved; it has worked for what we needed it to. Since it is already quite simple, I would recommend keeping it as is.

In my current field, I have been working for about five years, and I have been using Microsoft Entra ID for at least four of those five years.

I assess the stability and reliability of Microsoft Entra ID overall as good. If anything does come up, Microsoft is great about notifying us; we get alerts if anything goes down, and we find out before it happens for the most part. We haven't had many issues; most of it is quite stable.

I definitely cannot say we have experienced no downtime, crashes, or performance issues. Recently, we had one issue that lasted for a few hours during the day. We went straight to Microsoft health and notified the issue, and then Microsoft came with a workaround for it quite quickly. Generally, if there are issues, there is a quick turnaround on either a repair or an alternative solution.

Microsoft Entra ID scales well with my organization's growing needs; we use it daily and don't plan on changing it.

I would say we have expanded usage of Microsoft Entra ID. My experience with the expansion has been smooth on my end. I'm not the engineer directing it, but everything has been smooth in my role.

I would rate customer service and technical support as a seven to eight on a scale from one to ten. I give it a seven to eight because most of my interaction is with the end user and managing their system, ensuring everything is up and running for them to do what they need to on their jobs daily. I would evaluate my experience with customer service and technical support as great; I have never had any complaints.

Positive

To my knowledge, Microsoft Entra ID is the only solution we have worked with; I'm not sure of any other alternatives we looked at. That is the only solution I have used to address similar needs prior to adopting Microsoft Entra ID.

My experience with deploying Microsoft Entra ID has been straightforward; everything works well.

Most of my experience with developing Microsoft Entra ID pertains to setting up new policies when we get new features and upgrades, and we are always looking at ways to improve. I do have an engineer who mainly handles that, but as a technician, I go in and maintain and manage it. I haven't seen any specific challenges on my end regarding the deployment.

My experience with the deployment of Microsoft Entra ID has been quite straightforward. Anytime we get new devices in, the new policies are managed through InTune right to the devices, and it all rolls right out. I haven't had any issues.

From what I understand, there has been a return on investment. They have at least spoken to it. I don't have specifics, but I know it's a positive notion.

Unfortunately, I don't have information on the pricing, setup cost, and licensing on my end.

Since implementing Microsoft Entra ID, the most change I have observed in the frequency of identity-related security incidents in my organization has been as policies get updated. A few more features show up in there that we can edit to strengthen the policies as a whole from a security outlook. Most of it is that as they change, we can go in and look again to see if there is any way we can strengthen our current policies. I couldn't think of any specific metrics or data points at the moment regarding the changes I have observed.

My organization's approach to defending against token theft or nation-state attacks hasn't changed much after implementing Microsoft Entra ID. The following features of Microsoft Entra ID—token replay detection, attacker-in-the-middle detection, Verified Threat Actor ID, and Microsoft Entra ID Protection—haven't had a lot of specific impact that I'm aware of for the most part. We could say that there are no specific data points or examples at the moment.

The implementation of device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing-resistant authentication by ensuring that we use MFA and the passwordless device token specifically. All access is limited, and we have them set up for specific policies based on certain groups for different access, and it's all managed through there for us.

I would advise another organization considering utilizing Microsoft Entra ID to give it a shot if they're not already. It has been great and smooth; we haven't had many issues, and if we do, they are fixed quite quickly. With the support of Microsoft on our side, it's worth trying out. I would rate this product an overall eight out of ten.

Other

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

My main use cases for Microsoft Entra ID are authentication and access management.

The features of Microsoft Entra ID that I like the most are Conditional Access.

The implementation of Microsoft Entra ID has a significant impact on my secure access to apps or resources in my environment because it ensures that for every SaaS app we have, we can log in with enterprise accounts instead of having to create different accounts. If we disable a user, they get automatically disabled as well in those SaaS apps. That's definitely a big win compared to Active Directory in the past.

I think Microsoft Entra ID can be improved, but that's a broad question, and I'm uncertain about specific areas.

I have been using Microsoft Entra ID for almost 10 years.

I would assess the stability and reliability of Microsoft Entra ID as working fine with good uptime. There was an issue a few years ago, but that's been resolved now.

I haven't experienced any downtime, crashes, or performance issues.

Microsoft Entra ID scales with my growing organizational needs and scales pretty well, supporting up to hundreds of thousands of users.

I haven't expanded usage beyond what we currently have, as we only have as many employees as we have.

When we have to expand usage, the process is smooth because we don't have to do anything; we just add users.

On a scale from one to ten, I would rate my customer service and technical support for Microsoft Entra ID as pretty good, with the support being amazing for identity.

Positive

Prior to adopting Microsoft Entra ID, I couldn't really use another solution to address similar needs because Office 365 can only work with Microsoft Entra ID; it's tied to it.

I would describe my experience with deploying Microsoft Entra ID as working pretty easily.

The deployment of Microsoft Entra ID was easy with just a quick setup, and for Conditional Access, it's well-documented.

I didn't face any challenges during the implementation.

I have seen a return on investment with Microsoft Entra ID, but we didn't have another solution, so when you have Office 365, that's the only thing you can use.

My experience with the pricing, setup cost, and licensing is that we have Microsoft Entra ID Plan 2 licenses, so for us, everything is included, and I don't really work with the other models.

I didn't consider any other solutions before selecting Microsoft Entra ID because it's the only option with Office 365, so you don't have another choice.

Since implementing Microsoft Entra ID, I observe changes in the frequency of identity-related security incidents in my organization, though I'm uncertain about the specific details.

Since implementing Microsoft Entra ID, I definitely see all of the identity risks that are detected for the users now. Before, we didn't have any view on that.

My organization's approach to defending against token theft and nation-state attacks has not changed specifically since implementing Microsoft Entra ID.

The features of Microsoft Entra ID have benefited my organization because we're just more secure. We have less identity theft and no identity compromises since we have MFA now, whereas before, we didn't have MFA.

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model significantly because we didn't have a zero-trust model before.

I don't share any metrics or data points that demonstrate the impact of integrations because before we had nothing.

The implementation of device-bound passkeys and Microsoft Authenticator has affected my organization's approach, and we use phone sign-in with Authenticator.

I would rate my overall experience with Microsoft Entra ID as a nine. The advice I would give to another organization that's considering Microsoft Entra ID is to pursue it because it's included in Office 365.

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

My use cases for Microsoft Entra ID mainly include single sign-on, PIM, and conditional access policies.

The integration of Microsoft Entra ID and its ease of use is helpful for my company. Being included with our Microsoft 365 licensing makes it a much more affordable solution than Okta, for example.

The implementation of Microsoft Entra ID has positively impacted secure access to apps or resources in my environment because it makes them more secure. There are many services that don't support MFA, but adding SSO through Microsoft Entra ID adds MFA and allows us to enforce all of our conditional access policies.

What I appreciate the most about Microsoft Entra ID is that it integrates seamlessly with all the Defender products and is easy to use.

Microsoft Entra ID's integration capabilities influence our Zero Trust model by allowing us to enforce our Zero Trust model. Conditional access policies allow us to leverage Microsoft Entra ID to verify that devices signing in to our cloud services are coming from registered devices, and that people are passing all the other requirements we have in order to complete sign-on or conditional access policies.

Since implementing Microsoft Entra ID, I've observed changes in the frequency and nature of identity-related security incidents. The organization already had it implemented when I arrived, and I've been working to enhance it. Better configuration of Microsoft Entra ID has allowed us to better protect our organization from threats. Having it alone isn't a solution, but ensuring proper configuration goes a long way in preventing future compromises.

My company's approach to defending against token theft and nation-state attacks has evolved since implementing Microsoft Entra ID. We haven't experienced any known compromises from nation-state attacks, and implementing newer features gives me more confidence in our protection.

Regarding device-bound passkeys in Microsoft Authenticator and our approach to phishing-resistant authentication, we are currently implementing Microsoft Entra ID certificate-based authentication. Adding a strong form of MFA is important as we found it to be the most cost-effective way. While other solutions might be equally or more secure, they are significantly more expensive.

Having worked as an IT consultant mainly with the Microsoft stack across various industries, I have experience with different identity management solutions. Microsoft Entra ID remains the best option. The major advantages when comparing it to Okta include integration with Defender products, Defender for Identities' integration with conditional access policies, and insider threat management integration for blocking sign-ins based on risk factors.

The enhancement of Microsoft Entra ID's implementation is relatively straightforward. My main concern is the occasional lack of documentation and the frequency of changes, which can make feature location challenging.

Microsoft Entra ID is already the best service I have ever used for identity, so identifying improvements is challenging. They have been making many changes rapidly. One area that can be improved is ensuring that detailed documentation is being produced in a timely fashion. There have been many instances where documentation either hasn't been updated to reflect recent changes or is either non-existent or not very accessible.

I have been using Microsoft Entra ID since before it was Entra, when it was still called Azure AD. It's likely been six or seven years. 

I would assess the stability and reliability of Microsoft Entra ID as generally stable. We haven't noticed many issues with it, with the exception of MFA. We have had some occasional hiccups with MFA service availability. The MFA component has been the only area where we have experienced issues with service consistency.

The scalability of Microsoft Entra ID is effective. I haven't observed many issues. Most aspects of it have not shown scalability problems. At our medium-sized organization of under 1,000 people, we haven't experienced the pain points that a large enterprise might have with Microsoft Entra ID. However, as we grow larger, some areas are becoming more challenging, such as PIM management. It becomes unwieldy with over 80 people in our IT division. Through discussions with other vendors, it appears there are several solutions that can help manage PIM at a larger scale. PIM and guest access-related areas are where Microsoft Entra ID could enhance its capabilities. While Microsoft has added many features in the past three or four years that enhance our security, they may not be as thoroughly developed for scalability.

The customer service and technical support of Microsoft Entra ID is good. While I have experienced some difficulties getting ahold of Microsoft support in other areas, support for Microsoft Entra ID hasn't been particularly challenging. We pay for premium support through our enterprise agreement, so we receive quality support.

There are a lot of solutions out there that are just as secure or maybe more secure, however, they are not as cost-effective.

The solution was already implemented when I got to the company. However, I have been working to further implement new features. I've made a lot of progress enhancing the implementation. It's easy to do so. It's not any harder than Okta, for example. The only real issue is when documentation is lacking. 

The biggest return on investment when using Microsoft Entra ID is securing access to our company's resources. I have been on a crusade trying to go through all the different divisions of the company and finding services that our security team doesn't have awareness of, ensuring that if they're single sign-on capable, they are integrated with Microsoft Entra ID so we can enforce MFA and conditional access policies.

Our experience with the pricing, setup costs, and licensing of Microsoft Entra ID involves leveraging Microsoft 365 E5 licensing, so it's included. Being included in Microsoft licensing makes it much more affordable.

We have been considering paying extra for some of the add-ons they recently released, though we haven't made that move yet. The licensing included with 365 is affordable. Management hasn't yet seen enough value in the add-on suite licensing or à la carte pricing to get any additional features. Once their identity-as-a-service solutions develop more, we might consider using it.

I used to be an IT consultant working with the Microsoft stack and I've worked with other identity solutions, like Okta. However, I still prefer Entra ID. The big value add is the integration with other Defender products. 

On a scale of one to ten, I rate Microsoft Entra ID an eight. I'd rate it higher if it had better documentation. 

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