Microsoft Entra ID Reviews

My organization's approach to defending against token theft and nation-state attacks since implementing Microsoft Entra ID does erase a few of the common attack vectors that are worth solving. Prior to adopting Microsoft Entra ID, I was using another solution to address similar needs.

The features of Microsoft Entra ID that I like the most are its ease of use.

The impact that the implementation of Microsoft Entra ID has had on my secure access to apps or resources in my environment is negative, because it opens up more security awareness and public awareness of who is in the ecosystem. Then you have other attackers looking at, 'Hey, there's Microsoft Entra ID out there. Let's go figure out...' So, it's not exactly a good thing.

Microsoft Entra ID's integration capabilities have not influenced my zero-trust model.

Microsoft Entra ID can be improved by open-sourcing it. You already have Windows Subsystem for Linux, which is open-source Linux in Microsoft. One major shift for Microsoft would be using the common community to help make it better and more secure. We would not have to do things with it if you open-sourced it.

The implementation of device-bound passkeys and Microsoft Authenticator has affected my organization's approach by suggesting to get rid of passkeys. You want non-attribution. You want to still have a password. You do not want a central authority that requires fingerprints, facial recognition, or passwords. That is changing our world. I do have passkeys, but I try to not use them. When they are forced on you, we see the same thing being forced on you, verifying your age. Why is your age related to having an account on your library?

I have been using Microsoft Entra ID for six months.

I assess the stability and reliability of Microsoft Entra ID as having nothing worth a report. It is a good piece of software.

The factors that led me to consider a change to Microsoft Entra ID were that I wanted a better, holistic solution available. Years ago here, I bought someone lunch just to talk with them, and they said, 'Hey, so if we made a silver bullet solution, how would we eat?' Point made. So, I was exploring other things I could use that I could virtualize or not. I am all Linux. I can virtualize anything. I was exploring other opportunities to see if they could help me out instead of causing another headache.

I would describe my experience with deploying Microsoft Entra ID as a command line for me. It is a script. It does its job.

Before selecting Microsoft Entra ID, I considered a few open-source ones that can do what I need. There are not too many, but this is worth looking at.

What stood out to me in the evaluation process between those solutions and Microsoft Entra ID is that my whole ecosystem is primarily Linux. Microsoft Entra ID does not orchestrate or interface well with that type of environment. If you have a smaller or larger enterprise that is all one homogeneous Microsoft environment, it probably fits. However, I run entirely Linux, so it does not work for my situation.

My advice to other organizations considering Microsoft Entra ID is to buy time until some open-source style technology is available and do more exploration. I would rate this review a seven out of ten overall.

On-premises

We are a Microsoft partner, and all our internal computing is on Microsoft 365, managed by Microsoft ID and Intune. Entra ID serves as our directory containing all our users and guest users, and it's managed by Intune.

It simplifies the management of identities in our hybrid environment, covering on-prem and Azure. It streamlines integration with other Microsoft technologies like Authenticator, SSO, and MFA. Entra ID is crucial to our zero-trust model based on Microsoft security.

Entra ID's anti-phishing measures have improved our phishing response. We had phishing tests a month ago, and some employees still fell for it but the number has dropped. I think we've prevented some security incidents using Entra ID with other apps.

Entra ID is our directory that registers all users, guest users, and even labs. It's integrated with Microsoft technologies like Authenticator, SSO, and MFA, streamlining operations and creating a seamless environment.

Entra ID has limited integration with non-Microsoft solutions like iOS or Ubuntu. If it worked across different software and all kinds of devices could be managed under it, that would be great.

We have been using Microsoft Entra ID for quite some time, as it replaced Active Directory when we moved from an on-prem solution.

The platform is stable. We haven't encountered any problems.

It is deployed across all of our employees within the company and group of companies. If we had to deploy it further, it would be straightforward as we frequently deploy it for customers.

I rate Microsoft support four out of 10. Tier 1 and Tier 2 support could be better. It's not timely or professional. They often provide solutions we've already tried. 

Neutral

We previously used Active Directory, which Microsoft Entra ID replaced when we transitioned from on-prem.

Our in-house team handled the implementation.

Compared to other Microsoft products, the cost is not too expensive. There's a free tier available, though it doesn't include all features. Overall, it's well-priced.

We did not evaluate another solution before implementing Entra ID.

I rate Entra ID nine out of 10. 

Hybrid Cloud

We use Microsoft Entra ID for authentication purposes and are planning to implement additional modules like Mobile Device Management. Our current use is mainly for integrating third-party applications for distributed applications to centralize authentication.

The major feature we utilize is the ability to perform third-party validations. This functionality allows our distributed applications to be integrated with a single authentication system using Microsoft Entra ID. Previously, each application had standalone authentications, but with Microsoft Entra ID, we have consolidated them. After implementing Microsoft Entra ID, secure access to apps has become seamless.

There are a couple of main concerns. Microsoft plans to move away from SMS authentication for Multi-Factor Authentication and only implement application-based authenticator, which will be challenging for retail outlets reliant on Microsoft Active Directory. Additionally, the pricing for Microsoft services is rising. Furthermore, there is a tool to measure resource usage in Power BI, but it is not functioning properly, making it difficult to understand resource consumption.

We have been using Microsoft Entra ID for three and a half years. Initially, it was Azure Active Directory before transitioning to Microsoft Entra ID, and we've mostly used it over the last three years.

The solution is stable without any latency issues. However, in the last two quarters, we experienced three Power BI outages.

There are no current issues with scalability.

Support could be better at times. There was an incident where I couldn’t get help with deleting an unused subscription and another where Power BI support took weeks without providing a solution. Overall, the support incidents mentioned involved delays and inefficiencies.

Neutral

We have been with Microsoft from the start and have not explored other solutions.

The initial setup for Microsoft Entra ID was straightforward.

The setup was done in-house. I personally handled it without needing a full team.

We did not perform a detailed ROI analysis, but using Microsoft Entra ID has saved about fifteen percent of resources since one person used to manage login details, a task now simplified by the integration.

Microsoft's pricing is increasing significantly. The Office suite has undergone multiple licensing changes, driving up costs, and this also applies to Microsoft Entra ID.

We have been with Microsoft since the beginning and did not evaluate alternative solutions.

One additional feedback is that Microsoft plans to discontinue SMS functionality for Multi-Factor Authentication, which poses a challenge for retailers without mobile application authentication. This requires having an authenticator for Windows, so retail operations dependent on Microsoft Entra will not encounter authentication issues. Furthermore, the overall rating I would give this solution is seven due to issues with support. The MFA upcoming changes must be addressed before they cause further complications.

Hybrid Cloud

Microsoft Azure

We are using Microsoft Entra ID for single sign-on with our hybrid domain environment and for identity management with multi-factor authentication using Microsoft Authenticator. We plan to migrate our whole user base over to Microsoft Authenticator with MFA capabilities, possibly with certificate-based authentication.

We're still testing Entra and having implemented it on the application side. We'll soon start using application proxies to get into our line-of-sight businesses on-prem. 

We follow a least privileged access model, and Entra ID has helped us to avoid overextending access from the administrative side. And we plan also to implement it with devices. Our administrators are more careful when auditing access and ensuring everyone has access. 

We haven't implemented permission identity management, but we plan to use it. Entitlement management and dynamic grouping of Microsoft 365 groups are features I enjoy. From an administrative perspective, we can now manage users from a single pane of glass, which enhances efficiency. MFA will improve the user experience and increase organizational efficiency.

The implementation of other third-party MFA such as Okta or Duo could be improved, even though Duo is integratable. The response from actual support tickets is a bit laggy, and I would like them to be more responsive.

We have been using Microsoft Entra ID for about two years.

Entra's stability is great and consistently meets our expectations.

The scalability is excellent. We can scale Entra up and down as needed efficiently.

Our consultants are excellent and provide consistent help, but there is room for improvement in the responsiveness of actual support tickets.

Positive

We previously used on-prem Active Directory as our solution.

The initial setup was straightforward.

We did it all in house without any additional team.

We go through a reseller, CDW, who walked us step-by-step through the process. The pricing, setup cost, and licensing have been fairly straightforward.

Hybrid Cloud

I work on it to investigate it. I work at a cybersecurity company, so I focus on how the product behaves, particularly how Microsoft Entra ID behaves with group permissions and such.

We work with Microsoft because we're also a security company, so we scan Microsoft Entra ID and then monitor what happens regarding defending against token theft and nation-state attacks.

We are partners with Microsoft. We don't sell Microsoft products; we sell our own product, but we integrate it with Microsoft.

It's simple to create groups or accounts and to add users. There are several options for dynamic groups.

Microsoft Entra ID influences our zero trust model because we need to make sure that we give the right user permissions.

To improve Microsoft Entra ID, it should be made simpler because there is a lot of stuff to do in the platform, which could be reduced to fewer buttons.

I have been using Microsoft Entra ID for two years.

Microsoft Entra ID is pretty stable.

I don't know about scalability, but I assume it is suitable because it is used for huge organizations.

Customer service and technical support for Microsoft Entra ID are very good because I open many tickets with the support and get straight answers. If I don't get an answer, they update me all the time that they will provide an answer, and they work on that.

Positive

Microsoft Entra ID is pretty easy to deploy. The speed of deploying Microsoft Entra ID depends on the organization and its structure, but building new users is very simple.

There is a return on investment when using this platform, though I am uncertain about the specifics.

I haven't observed any problems or changes in the frequency and nature of identity-related security incidents after using Microsoft Entra ID in my company.

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

We are using Microsoft Entra ID for multiple purposes, such as managing all authentications and changing passwords online. Previously, we relied on an on-premise network, which required us to be on-site to change passwords. With Microsoft Entra ID, we can synchronize it from anywhere on the network. We have an Azure AD Premium license and utilize features like conditional access policies to control identities. We use it primarily for managing identities inside the organization.

The best feature of Microsoft Entra ID is that it provides more granular control over user identities. The conditional access policy feature is particularly valuable, and it's something we use frequently. Microsoft Entra ID helps us manage identities according to security standards, and it allows us to implement least privilege access effectively. The logging and monitoring capabilities give us insights into activities, offering a single pane of visibility to detect anomalies, ensuring enhanced security.

In terms of improvement, we face issues with latency and responsiveness. Changes take some time to reflect across all users, sometimes up to twenty-four hours, which can be challenging when we need to implement drastic changes. Additionally, Microsoft's documentation can be insufficient. Some technical configuration details are missing, requiring us to consult external sources like forums or communities. They need to improve their documentation to ensure all necessary technical information is covered.

We have been using Microsoft Entra ID for six to seven years. Before that, we had an on-premises Active Directory environment, and then we transitioned to a hybrid setup with Azure connect. This has been our setup for around six to seven years.

Microsoft Entra ID is stable. It functions as it is designed, but improvements regarding the responsiveness of the solution are needed. Sometimes, rolling back changes takes longer than expected, affecting our operations.

Microsoft Entra ID is scalable. It integrates well with third-party tools.

I have experienced mixed results with technical support. Sometimes the support is excellent and technical issues are resolved quickly. However, there are times when complex tickets are assigned to non-technical personnel, which prolongs resolution times. After a delay, we might find out that an issue is out of scope for a particular agent, causing further delays.

We previously used on-premises Active Directory and switched to Microsoft Entra ID to reduce infrastructure. We have a hybrid environment now but maintain some local infrastructure for testing purposes.

The initial setup of Microsoft Entra ID is not straightforward; it sits between easy and tough. Implementing features requires vigilance and certainty before making changes due to its complexity. Microsoft's documentation misses some technical details, creating a need to refer to external resources for certain configurations.

Our deployment was done in-house. We did not use an integrator, reseller, or managed service provider.

Microsoft Entra ID provides visibility for security, such as tracking identity movements. By not relying on an on-premises solution, our infrastructure management is simplified, which aids in disaster recovery planning. We also integrate security features like risky users policies that enhance our security architecture. This contributes to a good ROI.

I rate Microsoft Entra ID at eight to 8.5 out of 10 overall. The solution is mature, with a big community and a strong reputation in the market. It's recommended due to its features and community support, though implementation challenges and documentation issues require attention. Community support and Microsoft's reputation are valuable, but the latency and documentation need improvement.

Hybrid Cloud

Microsoft Azure

Entra ID serves as our primary identity security tool. 

Entra ID enables us to implement security easily and effectively. It has built-in integration with all the Microsoft tools, like SharePoint, Outlook, Teams, etc., the condition access we discussed earlier. It's our primary identity security tool. We can't live without Entra ID. 

Using Entra ID has improved our security. Our security score is close to 80 percent, which is a critical metric because that includes everything under the hood. We have continuously improved in the last two or three years. We have implemented many improvements since the pandemic, so the number of incidents has decreased a bit, and automation has been throttled up.

Conditional access and Privileged Identity Management (PIM) are the most valuable features from a security perspective. 

Rule management and permissions need improvements. I have had discussions with product managers about these challenges and sent emails regarding them. Additionally, improvements are needed in the Identity Governance and Administration (IGA) side of things.

I have been working with Entra ID for around six years.

I rate Entra ID 10 out of 10 for stability. I have not encountered any issues.

I rate Entra ID's scalability 10 out of 10. It's great.

Customer service has been very good. I have raised sophisticated queries and received responses within a day.

Positive

I have never used a different solution and have always worked with Entra ID.

I have not personally deployed Microsoft Entra ID. However, I have integrated the solution, and we have worked with integrators to set it up.

The biggest return on investment is the seamless integration with all Microsoft apps and services. If you choose something new and integrate it, it can take a lot of time.

I rate Entra ID eight out of 10. 

Hybrid Cloud

Other

We've been using Entra ID in a hybrid scenario. We have an on-premise Active Directory that replicates to the cloud.

Scalability has been the biggest benefit. Moving more to a cloud footprint and leveraging Azure resources provides increased scalability and security. Entra helps us drill down into who can access our secure apps using resource groups, etc. We haven't had a security incident in the past two years, so we've been secure since going hybrid with Entra.  

The most valuable feature is the ability to establish resource groups and set permissions through RBAC across these groups.

The device-bound passkeys have helped us implement phishing-resistant authentication. We moved everybody to the authenticator app through Microsoft Entra and integrated that with our Azure applications.

We're more secure than we've been in the past. Our security score was poor when we implemented Entra ID. It was about 30 percent. We increased it significantly using recommendations from Microsoft about the authenticator app and other identity measures.

The transition from on-prem Active Directory to the Azure Cloud was difficult because there aren't group policy objectives. This is handled differently in the Azure cloud environment.

I've been using Entra ID for a little over two years.

We haven't had any issues since moving to the platform. It has been one hundred percent reliable without outages.

The scalability is perfect, allowing us to easily move more functions to the cloud.

I've never had to reach out to Microsoft support, which I consider a positive aspect. From what I've heard from colleagues, they'd rate Microsoft's technical support around an eight.

Positive

We previously used strictly on-premise Active Directory.

It was rough because we didn't have much experience in cloud space. It was pretty seamless after a couple of days of researching and powering through it.

We used Insight for the implementation. Their cloud engineers were amazing and helped us through many challenges.

The biggest return on investment is peace of mind, knowing I won't receive phone calls in the night.

The licensing model was straightforward initially. However, it has become more complex. It's not bad. The price has gone up a bit, but it's still affordable. 

We evaluated Amazon Web Services but chose Entra due to seamless integration, primarily because we are a Microsoft shop.

I'd rate Microsoft Entra ID as a 10 out of 10.

Hybrid Cloud

Microsoft Azure