Microsoft Entra ID Reviews

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

Entra ID covers our entire user identity stack, including authentication. Interactive capabilities are particularly useful.

Microsoft Entra ID has helped the company with user identities, user device management, and endpoint management. We use it with other Microsoft products like Defender for Endpoint and Sentinel to improve our security. 

Active Directory has conditional access, so you only log in from a company device. You also have multi-factor authentication and other systems generate tokens. It's well protected.

The integration with all Microsoft services and external applications is crucial. Microsoft Entra ID has helped the company with user identities, user device management, and endpoint management. Integration capabilities are significant.

There should be a clearer separation between objects held in Entra and Azure, so we don't need to approach the Entra ID team to create rules, policies, and app registrations. It would help if we could make independent IDs on the Azure side to go through that team to create a role, change permissions, or create something for a specific task.

I've used Entra for the last couple of years but have worked with Microsoft solutions for 30 years. Entra ID is the successor to Azure Active Directory

Microsoft Entra ID is a stable platform. There was a big incident with Azure Active Directory a few years ago, but since then, Microsoft has worked to distribute the risk properly.

There is no issue with scalability.

I rate Microsoft support eight out of 10. They respond quickly, but the solutions aren't always satisfactory. Microsoft cannot test some things internally when you face a problem. 

Positive

Before Entra ID, I used the on-prem Active Directory for around 30 years. The foundation of Entra and Azure Active Directory comes from Active Directory.

Initially, we could complete the setup by following the guides, but now the setup is more complicated. 

We try to handle implementation in-house, supported by an external company that acts as an outsourced part of the team.

I am aware of the tier we use and know the pricing per user or account, but I am not in procurement.

I rate Entra ID nine out of 10. 

Public Cloud

Microsoft Azure

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 to secure Boulevard by Density.

Entra's multifactor authentication has kept our organization secure. We've decreased the number of password resets and extended the length of passwords, which has kept users happy and improved security.

Entra's conditional access policies allow us to fine-tune how we allow people into the environments and secure them. Microsoft Entra ID has also massively improved secure access to apps or resources compared to our previous setup. We've rolled out Microsoft Authenticator. That went pretty well, pretty smooth. The users seem to enjoy ID. And, yeah, we're starting on passwordless soon.

There are no specific areas where improvement is needed at the moment. Everything has been good so far.

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

There have been a couple of outages so that I would rate the stability around a seven out of 10.

I rate Microsoft support nine out of 10. Customer service and technical support have been pretty good.

Positive

We did not use any different solutions before implementing Microsoft Entra ID.

The initial setup and experience with deploying Microsoft Azure ID was straightforward.

We used an integrated reseller or consultant for the deployment.

We have seen a return on investment because Entra is included in licenses we already own. Deploying it was a no-brainer. 

The solution was included in the licenses we already had, so it presented a no-brainer setup cost.

I rate Entra ID nine out of 10. 

Hybrid Cloud

Microsoft Azure

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

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