Microsoft Entra ID Reviews

Our primary use case for Microsoft Entra ID is mainly for single sign-on (SSO). We use it to log into other cloud-based applications. We have an internal sync from Active Directory to Microsoft Entra ID. Whenever an account is created in Active Directory, we immediately create an account in Microsoft Entra ID to automatically grant access to cloud-based applications. Some roles are assigned based on Microsoft Entra ID data.

Microsoft Entra ID's ability to extend and divide multiple applications based on requirements is valuable. It allows easy integration with One Identity and enables effective application management. The security configuration is straightforward and limits access to admin only, ensuring data integrity. Microsoft Entra ID enhances the Zero Trust model by providing simple integration and dedicated permissions for each application. Its features like token replay detection, attack-in-the-middle detection, and especially verify threat actor IP have been impactful in defending against threats.

I suggest improving the connector part. For technical users like me, it is manageable, but having comprehensive documentation for those who aren't familiar with the system would be beneficial. Additionally, synchronization issues occasionally occur, making it challenging to analyze logs and pinpoint the exact problem. Providing more detailed log information for synchronization failures would be helpful.

I have been working with Microsoft Entra ID for approximately six years.

I encountered no issues with the deployment of Microsoft Entra ID.

I find the stability of Microsoft Entra ID to be excellent. I would rate it a ten out of ten.

In terms of scalability, I would rate Microsoft Entra ID a nine out of ten.

I rate Azure Technical Support a nine out of ten. Whenever we require support, we receive it promptly.

Positive

I have primarily used Microsoft Entra ID. In various projects, we consistently used it and didn't switch to other solutions.

The initial setup of Microsoft Entra ID was simple.

We used an out-of-the-box connector available in One Identity management for connecting processes. It's easily available for configuration, and we customize it as per requirements.

The pricing for the setup and the cost overall is reasonable. I would rate the pricing nine out of ten, as per today's market.

Based on my experience, I would rate Microsoft Entra ID a ten out of ten. Setting up Microsoft Entra ID was simple. In terms of company size, I recommend it for enterprise-level companies. I find the overall pricing to be average but reasonable. As a real user of Microsoft Entra ID, I am not affiliated with the vendor or partners.

Hybrid Cloud

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

Microsoft Entra ID serves as the central repository for all of my service principals for the integration side of things, user management for different groups, and permissions, with a lot of role-based access control and service permissions mainly.

The features of Microsoft Entra ID that I appreciate the most include permission management.

Examples of how the features of Microsoft Entra ID have benefited the organization include permission management and general security, as we use Entra as our authentication and SSO tool, which has been performing well, and we have it synced up with our on-premises AD as well.

The implementation of Microsoft Entra ID has positively impacted my secure access to apps or resources in my environment because I appreciate that it has SSO, so you can use it for signing on to a whole bunch of different applications that are also running in your enterprise, and it is generally very good for governance of getting people access to whatever they need.

To improve Microsoft Entra ID, I think on the left navigation bar when you actually open Entra, there is a button that you need to click to make every option available for that tab open, so you always need to click that button, which is an arrow facing upward and an arrow facing downward.

I have been using Microsoft Entra ID for four years.

I assess the stability and reliability of Microsoft Entra ID as generally good, as I have not necessarily experienced downtimes, crashes, or performance issues, though there have been minor issues with the Azure portal itself.

Microsoft Entra ID scales well with the growing needs of the organization, as I have not had many issues with it at all.

I have expanded usage of Microsoft Entra ID. The process of expanding usage was fairly smooth, though I would not know the metrics behind it.

I would rate my customer service and technical support for Microsoft Entra ID around a solid seven, as I have never had to contact Microsoft support for Entra.

Positive

I would not know what other solutions I considered before selecting Microsoft Entra ID.

I have only used Microsoft Entra ID at my organization, and prior to adopting it, I did not use another solution to address similar needs.

I would not really know about my experience with deploying Microsoft Entra ID, including what worked well or what challenges I faced.

I am sure my company has seen a return on investment with Microsoft Entra ID, but I would not know.

I would not know about the pricing, setup cost, and licensing of Microsoft Entra ID.

I do not know if I am suited enough to answer in what ways Microsoft Entra ID's integration capabilities have influenced my zero-trust model.

I could not share any changes I have observed in the frequency and nature of identity-related security incidents in my organization off the top of my head.

I would not know if my organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID.

I would not say that the implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance, as I could not say since I do not have that information.

My advice to another organization considering Microsoft Entra ID is that it is a really good identity tool, though I am not so much ingrained on the infrastructure side of things, so I could not be the person to say this is what you should go for, but I appreciate using it as it is good for whatever I need to do, which is permission management and other tasks. I would rate this product an 8.5 out of 10.

Hybrid Cloud

Microsoft Azure

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

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

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

Security is paramount in this context.

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

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

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

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

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

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

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

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

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

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

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

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

Public Cloud

Microsoft Azure

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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 use a hybrid environment with Active Directory and Microsoft Entra ID along with SCCM. Our hybrid setup with Entra and Azure allows us to use role-based groups for access while keeping our AD environment intact. We sign our automation based on Active Directory and use write-back for populating new groups. We are able to use the enhanced security from Microsoft Entra ID while maintaining our existing environment. Our company has been slow to modernize in the cloud environment and we are on the tail end of the actual conversion. We conduct a lot of pen testing with our existing accounts because we still use Active Directory. We haven't had a lot of incidents with identity management. We are just getting into issuing out cloud PCs, having done that in the last year. Some of the more advanced features on Microsoft Entra ID have not been implemented yet.

The write-back caching of Microsoft Entra ID allows us to keep our existing Active Directory environment while also using Azure services. The write-back caching helped tremendously because we didn't have to do a full conversion from one to the other. We could keep our existing environment and still use the zero-trust platform to build it out.

The return on investment from having an Azure tenant comes from being able to use Microsoft Entra ID with our deployment of cloud PCs and having them auto-join the tenant. We are able to build this into our deployments with SCCM and use the hybrid environment to leverage Microsoft Entra ID for deployment. This has made deployments a lot easier, especially with moving to cloud PCs. We still use physical devices, but moving to a virtual environment is a much better solution overall once we get it fully implemented and move everything over to cloud. We are able to release our lease on physical machines and use virtual machines instead.

We have just recently started implementing write-back caching. We were able to go from AD to cloud, but we were not going from cloud back down to AD. When we created new accounts, they were created in AD and then moved up to cloud, but we are not yet creating accounts in cloud and having them populate down to AD. As far as what can be improved, we haven't gotten that deep into it to know what we are missing or what we could improve on.

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

We have very good uptime, and the only time we have suffered any issues is when Microsoft experiences issues.

Information security would be more knowledgeable about pen testing and security configurations for preventing threats, as that is outside my area of expertise. I would not be knowledgeable on those details. I am rating this review an eight out of ten.

Hybrid Cloud

Microsoft Azure