Microsoft Entra ID Reviews

I'm developing a SaaS application. I'm working with a company that develops a SaaS application where the first customers are Azure customers. Most of our customers are using Microsoft Entra ID as their single sign-on implementation. I saw not only my organization's Microsoft Entra ID configuration but also others. 

The smooth integration with Azure is a significant benefit of Microsoft Entra ID. We could see the benefits of Microsoft Entra ID immediately after starting to use it.

The UI of Microsoft Entra ID is very intuitive, and I appreciate the integration with Azure because it works seamlessly. This is the best aspect I appreciate about Microsoft Entra ID.

There is a feature that we have been waiting for regarding Bicep templates. The option to use Bicep templates to deploy Microsoft Entra ID objects from the Azure Portal is needed. The deadlines for this feature were set for March, and that has already passed without deployment. We commented that we are still waiting for that, and they commented that they would update us when it is finished, but we haven't received any update about it. This feature is very important.

I've used many variations of Microsoft Entra ID. It was Active Directory in on-premises situations, but for the last three years, I've been using Microsoft Entra ID, and in the last year, I've been using it heavily.

I have not experienced any instability such as lagging, crashing, or downtime with Microsoft Entra ID.

We have tested extensively concerning scalability, and Microsoft Entra ID is working well in all of our use cases.

I have contacted their technical support and customer support. Their response was very fast, taking less than a day, but the response was not clear because they didn't update the deadline and didn't provide much information. They just told us that it's still in internal testing, and they don't have a date when it will be announced, which is problematic.

I have used G Suite as an alternative to Microsoft Entra ID. Smooth integration with Azure is a significant benefit for Microsoft Entra ID. The integration with the Microsoft ecosystem is much better in Microsoft Entra ID. However, integrations with Chrome and other Google products are better in G Suite.

I was not the one who implemented it. My onboarding with Microsoft Entra ID was pretty easy to learn. It took me a few hours to learn how to use Microsoft Entra ID.

It doesn't require any maintenance on our end.

I would rate Microsoft Entra ID a ten out of ten.

Public Cloud

Microsoft Azure

I am currently using Microsoft Entra ID and have been working as a user and administrator for nearly two years. It serves as an ID management tool which used to be called Active Directory on on-prem servers. With the transition to the cloud, it became Microsoft Entra ID.

The features I find most useful in Microsoft Entra ID include sign-in logs, device management, and application registration. With the Entra ID dashboard, I can access logs easily without needing to remote into servers. This tool is excellent for integrating third-party applications through application registration, making it easy to configure for single sign-on seamlessly. It supports conditional access across various Microsoft applications, enhancing secure access.

There should be guidance on features, especially security features, in Entra ID and whether they are sufficient on their own. The solution could become expensive when paying extra for enhanced security features, so Microsoft needs to offer better clarity on this matter.

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

In terms of stability, I can say it is ninety-nine percent stable. The remaining one percent instability is mainly due to the hybrid setup.

I have no complaints regarding scalability for Microsoft Entra ID.

The customer service and support are excellent. I experienced a fast resolution within half an hour for an issue by the first line engineer on a Severity A case, which shows support is very good even with minimal licenses.

Neutral

I am not aware of the solutions used prior to Microsoft Entra ID, as I have been involved for the last two years only.

Since it is a SaaS model, everything is set up, and I just need to configure it according to my needs.

We did not require any integrator, reseller, or consultant for the deployment as we managed it internally, using Microsoft's extensive documentation for guidance.

Microsoft Entra ID is reportedly quite expensive for each user regarding security features. The renewal cost is particularly high according to the teams managing purchases.

I have only been involved with Microsoft Entra ID and am aware of another identity management solution called NetIQ, but Microsoft Entra ID is prioritized.

Users should prepare technically before using Microsoft Entra ID, especially in understanding ID management and security integration with applications. Microsoft Entra ID is regarded as the best ID management suite for integrating applications using SAML 2.0 for single sign-on. My total rating for Microsoft Entra ID is nine out of 10.

Hybrid Cloud

Other

I handle access management.

Microsoft Entra ID has positively impacted the secure access to apps and resources in our environment. It's just easy to integrate.

It makes management easier. We have visibility into password compromises and other things.

What I appreciate the most about Microsoft Entra ID is that it integrates seamlessly with other Microsoft products, which streamlines the process.

It integrates with applications, such as our Password Manager, and multi-factor authentication, and it integrates with Office 365 and third-party applications. That's very useful.

Microsoft Entra ID can be improved by having more resources for learning how to best use the tool and understanding best use case scenarios. The learning curve is challenging, so I would appreciate seeing a training portal that is easier to use. I would appreciate seeing more guides and training materials about Microsoft Entra ID.

I have been using it for six months.

The stability and reliability of Microsoft Entra ID are good. It is very reliable, and I have never experienced any problems.

Microsoft Entra ID is very scalable with third-party applications.

We have been using Entrust within our environment, and Microsoft Entra ID is in our larger environment. We use both solutions.

The biggest return on investment when using Microsoft Entra ID is the integration with third-party applications.

I would rate Microsoft Entra ID a nine out of ten.

Public Cloud

Microsoft Azure

We use Entra ID for single sign-on to all of our internal IT systems and public SaaS offerings within the company.

Entra ID streamlines permission management and authentication for most systems. It also unifies IDs, simplifies IT operations internally, and enhances security by enforcing a better security posture across the organization.

We like the ease of app registrations and single sign-on with Entra ID. It offers an easy way to add multi-factor authentication to nearly any application and system. 

We've used it within AKS clusters to do pod identities. That has greatly reduced the number of static credentials we have running around and drastically improved our security. Combining Entra ID with the amazing work of our AKS team has enabled us to shrink the blast radius of credentials given to applications instead of only at the node level. This has allowed us to scope down permissions to an application level instead of the Kubernetes cluster, making it more secure and much closer to a full zero-trust solution.

Entra has helped us fight token theft. We almost always use short-lived tokens, which help us address many of these challenges. They still exist for certain use cases, but they've been drastically reduced due to our ability to use short-lived tokens.

We have never had an identity-related attack because we're lucky. However, that's just a matter of time until we do in this industry. Not having them before does not mean that we're not better protected now

The automation aspects of Entra ID could be improved, particularly when automating through different providers and SDKs. It's somewhat clunky to automate ID management, but it's great once it's set up. I would also like to see better Terraform support. 

I have used Entra ID for the last three years.

The stability has been great. I haven't had any issues.

The scalability is great. I've hit no issues in terms of scalability.

I rate Microsoft support 10 out of 10. Microsoft customer service is the best in the industry. There are immediate answers to any issues that arise with great knowledge and a deep understanding of the product and business needs.

Positive

I've used multiple solutions in the past, including Google authentication and Okta. I switched mostly to consolidate and for a better feature set that integrated better with the rest of our Microsoft products.

The setup is one of the easiest I've seen in the industry. It's very easy to onboard.

We used ourselves since we're an integration company.

We have seen a return on investment. We already have Entra ID, and like many customers, we haven't used it to its fullest potential. We get a return from not needing to pay other vendors to do what we already had from Microsoft, which was better than the competition.

We evaluated Workspace ONE, Google, and Okta before switching.

I rate Microsoft Entra ID nine out of 10. Without good Terraform support, it will stay below a 10, but everything else is so great.

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

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

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

At first, we used Entra for Single Sign-On (SSO) purposes, but there are multiple use cases. It is the backbone of managing identities and access to Microsoft 365, for which we have licenses. We were also using it for SSO authentication for third-party applications.

We do not use Microsoft Authenticator. We use ADFS, which is federated with Entra, and we are integrated into that, so we do not use Microsoft Authenticator except for admin accounts.

Entra has had a positive impact by enabling us to synchronize the IDs from on-prem to Entra ID and grant access to applications based on those users and their groups. 

The identity and access management piece is probably the most valuable to us. Since its implementation, synchronizing the identities from on-premise to Entra ID has had a positive impact. This allows us to grant access to applications based on those users and the groups they belong to. 

The conditional access policies are helpful. They let you control access based on what devices they connect from. The conditional access policies prevent people from accessing our environment from outside our domain or non-company computers. We've relied on the verified threat actor feature to identify whether it's a real user or a bad actor based on the source.

The area that needs improvement is integrating IDs between multiple environments and forests. In our case, it's hard to get the identities from multiple forests into one location. This is probably our biggest challenge.

I've used Entra for about eight years since we opened our commercial cloud.

I haven't had any issues with the virtual machine, so it is stable.

It's been great. We have the upgrade support package, but actually, most of the built-in support is the best.

Neutral

We previously used ADFS and switched mainly because of our licensing model and to gain access to Microsoft 365. So it just became an extension of it.

Ultimately, it's the base setup for everything. It's Microsoft 365, so it's a required piece. It's hard to quantify our ROI because it's just something we need. 

I rate Entra ID seven out of 10 because it's hard to have a single tie to integrate all identities within our core curriculum due to multiple forests.

Public Cloud