Microsoft Entra ID Reviews

We predominantly use Microsoft Entra ID for running our User Directory Service. It integrates with Intune, Exchange, and SharePoint.

Microsoft Entra ID acts as our core directory. It is essential for authentication, VPN authentication, and using onsite RADIUS. It supports our user scopes for various applications. Everything we do revolves around this directory and its authentication.

If I have one criticism, it's regarding processing times. Changes or even inbound email logging tend to take a minimum of fifteen to twenty minutes. There is a need for more real-time processing. Some user updates are instantaneous, while others can take two to three hours. A feature to force manual updates would be beneficial rather than waiting for scheduled updates.

I have been working with Microsoft Entra ID since 2009.

For stability, I wouldn't give it a ten because we have experienced some outages. I would probably rate it around a seven. Generally, it's stable, but when it goes down, the impact is substantial.

From my perspective, we haven't encountered any scaling limits. It meets our needs for user productivity.

I would rate Microsoft's technical support on the lower side. While some responses are quick and satisfactory, there have been occasions where issues took weeks or circles to resolve, sometimes closing and reopening without resolution. I would rate their support around a four.

Neutral

Through acquisitions, we used Google Workspace. We have spent a considerable amount of time with it.

The initial setup of Microsoft Entra ID is not straightforward without training. However, once you are familiar with it, the process is seamless.

We did not use an integrator or consultant for the first deployment. Initially, I did it all myself, although I have a few people working with me now.

Regarding pricing, for the services we receive, it seems within the market range and about average.

Through acquisitions, we have spent considerable time evaluating Google Workspace.

Overall, Microsoft Entra ID does what we need it to do. I would rate it around a seven on a scale of one to ten.

My job is to manage APIs on the enterprise end. We use Entra ID to limit contact with the end of the portal as much as possible. We have a lot of permissions that we don't want people to have, or we provide them with managed access. We also use Entra to manage application access. It tends to be blanket permissions, allowing an application total access.

Microsoft Entra ID drives our login and security perimeter, which is crucial for our organization. It has helped us implement multifactor authentication for most of our users despite the legacy systems in place. 

It is essential for supporting our aspiration towards a zero-trust model. It's driving our ambition to get serious about zero trust. We still have a lot of legacy systems that require support. 

Entra handles all the anti-phishing capabilities, and it's also helped us implement passwordless sign-in functionality. Now that we have MFA requirements and stuff like that, we're seeing identities flagged as risky because people are traveling. Sometimes people misuse credentials. It may not be malignant, but a group of people might share credentials. 

Delegated permissions and federated credentials are valuable features of Entra ID. We aim for a more secure environment by pushing for minimal use of static secrets. By utilizing delegated permissions, workflows can manage access, and federated credentials allow integration with platforms like GitHub and AWS. Entra ID drives our login and security perimeter, helping with multifactor authentication, despite the legacy systems.

Entra ID needs to improve its application credentials and use of ID permissions. There are challenges with the management layer. We want to create access down to the Graph level while invoking some management logic. That also means that if an application comes in, we cannot send that to the Graph because we would need an ID on behalf of the cloud hook. 

We have to switch contexts and do a lot of custom security checking. Does this application have permission to change these objects? If it does, then we can use our CNC powered by NMC. It botches our entire audit log so we can return to our service log and correct it rather than have it all in the old cloud. That's annoying. 

We also hit a problem with the federated credentials. Every hour, it exchanges a set of credentials from another IDP. For example, if I have a token from GitHub, I can exchange that for an application identity in NFT, which is awesome when you're doing GitHub workflows. However, because we have more than one tenant, we might need to access resources from one tenant to another. 

We do managed identities and federate to get a token and then assume an identity in the other tenant with that token. But for some reason, Microsoft has excluded all of their own IDP endpoints. Everything else is good to go, but if you come with a Microsoft token, you cannot use it. 

I have been using Microsoft Entra ID for the last two to three years.

I've had no issues with Entra ID. The portal could be slow now and then, but we don't have problems with the platform itself.

We have not observed any major scalability issues. However, when dealing with tens of thousands of objects, it requires proper management and best practices to retrieve only necessary data.

We rarely use customer service because we act as tech support. The few cases we have raised received decent support. 

Positive

We previously used Active Directory. While we haven't fully transitioned, we still source users from Active Directory but draw identities into Microsoft EntraID.

The decision to switch was made before I joined the team, so I'm not in a position to discuss ROI specifically. However, Microsoft EntraID is an integral part of our operations.

We face pricing challenges with newer licenses, as newer features often require them. This results in additional expenses for accessing new functionalities.

I rate Microsoft Entra ID seven out of 10. While it's an excellent standard for user sign-in, its open application model and security limitations lower my rating.

My main use case for Microsoft Entra ID is identity, and my organization performs many migrations, such as Office 365 migrations. This involves establishing an identity in the cloud, securing the identity with multi-factor authentication, and then onboarding it with SSO apps.

My favorite feature about Microsoft Entra ID is passwordless authentication because it makes the process easy.

The impact of Microsoft Entra ID on my company is significant because we are an MSP that resells IT services, and it serves as the foundation for all of our services, including single sign-on to all of our apps and to the customer's apps.

In the next generation of Microsoft Entra ID, I would appreciate improvements to consolidations for M&A activities. We perform many M&A migrations, and it would be beneficial to transfer identities from different tenants. While Microsoft has streamlined Exchange and SharePoint data, it would be helpful to have the ability to move identities between tenants if possible.

I have been using Microsoft Entra ID since it started, approximately eight years ago.

I have experienced some stability and reliability issues with Microsoft Entra ID, as there was recently a major outage that affected everyone. However, overall it has been quite solid.

I have used customer service for Microsoft Entra ID at some point. Although we have premier support and open cases, we are at the mercy of Microsoft. Customer service has been inconsistent for us, and we usually have to escalate issues. We typically resolve the problem before Microsoft can respond to us, so the service has not been very useful. We pay significant money for our support and do not receive a good return on investment.

Neutral

I have seen a return on investment from having Microsoft Entra ID.

My experience with the pricing, setup cost, and licensing of Microsoft Entra ID includes different tiers: Plan 1, Plan 2, and the Entra suite. I am quite familiar with these options.

I did not consider another product before selecting Microsoft Entra ID because it is the industry leader. We already use Microsoft products, so standardizing on Microsoft Entra ID was the logical choice.

Since implementing Microsoft Entra ID, I see more visibility in identity-related security incidents.

The integration capabilities of Microsoft Entra ID influence my Zero Trust model as it serves as the foundation for identity security.

I would rate this product 10 out of 10.

My main use cases for Microsoft Entra ID are to log in to Azure and also to log in our apps to Azure.

The feature of managing the users in Microsoft Entra ID is what I like the most.

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

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model by providing more granularity or control in the access that we are giving to users.

Microsoft Entra ID has benefited my organization through better management of the users and then more seamless connectivity.

I haven't thought of any specific improvements or additional features that should be included in the next release of Microsoft Entra ID.

I have been using Microsoft Entra ID for two years.

I am not sure how to assess the stability and reliability of Microsoft Entra ID as I haven't experienced any downtime, crashes, or performance issues.

Microsoft Entra ID scales well with my growing needs because the management of users is essential for our company as we are growing.

I don't really have any experience to rate customer service and technical support in Microsoft Entra ID.

I didn't have direct experience with the technical support of Microsoft Entra ID.

Positive

Prior to adopting Microsoft Entra ID, I think we didn't have Microsoft Entra ID and were mainly using password-based systems, for example.

I don't have direct experience with deploying Microsoft Entra ID.

I have seen a return on investment with Microsoft Entra ID.

I am not able to share any data points or examples of the return on investment.

I have no visibility on the pricing, setup cost, and licensing of Microsoft Entra ID.

I have no idea what other solutions were considered before selecting Microsoft Entra ID.

Since implementing Microsoft Entra ID, I have observed not much change in the frequency and nature of identity-related security incidents in the organization.

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

I haven't noticed any incidents at all related to token theft.

The implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance by adding more steps in the authentication, which has helped in improving the security of our applications.

I am not sure if we have expanded usage of Microsoft Entra ID.

I would rate Microsoft Entra ID an eight based on some experiences, such as asking for repetitive connectivity and on the confirmation or verification, but I think the rest are good.

The advice I would give to an organization considering Microsoft Entra ID is that it depends on the organization's need; if they are growing and they need more governance, then they should have Microsoft Entra ID. I would rate this product an eight out of ten overall.

I use Microsoft Entra ID to manage the identities of production and creating groups, as well as to enable multi-factor authentication for users. Other use cases include looking at devices that are linked to users.

Microsoft Entra ID is pretty user-friendly and intuitive. The graphics are particularly useful when it comes to the auditing part. I saw the benefits of Microsoft Entra ID immediately after I started using it.

I would appreciate it if they linked the Microsoft Entra ID platform with other 365 platforms, such as the governance of Power BI or the security for the App Center. That would be very useful since we have many platforms related to Microsoft 365. We need to have a link or different profiles for managing through Microsoft Entra ID, which is the main platform.

I have been using Microsoft Entra ID for four years.

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

I would rate the scalability for Microsoft Entra ID an eight out of ten.

I have contacted technical support for Microsoft Entra ID. The quality of support is regular. If you contact Microsoft support directly for Microsoft Entra ID, it's faster, but when you do it through a partner, it takes more time.

Neutral

I have not used any alternatives to Microsoft Entra ID in my career.

I wasn't in the company when Microsoft Entra ID was deployed. I started when it was already deployed. I know that the deployment of Microsoft Entra ID is pretty easy because we can do it with AD Connect.

It took me two weeks to learn how to use it. I would rate it a six out of ten in terms of the learning curve.

Its maintenance is taken care of by Microsoft. 

My advice for new users on how to start with Microsoft Entra ID is to take the Azure fundamentals certification AC-900, which gives you much insight, as well as the AC-500 for identity. 

I would rate Microsoft Entra ID as eight out of ten.

Our primary use case for the solution is building solutions using all Microsoft services, including migration projects, service provider roles, developer solutions, AI solutions, and ETL solutions for all those things, where we will use Microsoft services.

Recently, I did a migration project, which involved migrating from Microsoft Dynamics using ETL, for which I have used Microsoft Entra ID for app registration and API authentication. From Microsoft Dynamics 365, I want to connect to Microsoft services, and I perform the authentication and app registration and user login; I have used all these functions in Microsoft Entra ID.

The implementation of Microsoft Entra ID has impacted my secure access to apps or resources in my environment because it made it easier. For example, if I need to access a Key Vault and don't want to access it directly, I can use Microsoft Entra ID, and I can set all the policies there and use the Key Vault values.

These features are beneficial and valuable because they can be used to connect with third-party services and Microsoft services.

Since implementing Microsoft Entra ID, I've observed changes in the frequency and nature of identity-related security incidents. In app registration for a recent project, my Microsoft Dynamics 365 enterprise application is not visible. We need to add that app through client; we need to use AZ client, and there we need to add the ID, and it is not showing in the UI. This could be improved.

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

The Microsoft Entra integration capabilities have not influenced my zero trust model in any way.

I have been dealing with Microsoft Entra ID, which is not as an Azure product, since 2000. So, twenty-five years now. It is now known as Microsoft Entra ID.

Microsoft Entra ID is built on a robust database infrastructure for finding objects with specific capabilities, be they users, computers, members of a company, machines, or whatever else. It historically stems from the X.500 system, developed for efficiently finding specialists, as demonstrated with the Apollo project. This historical foundation underpins its effective directory services in the modern context.

Currently, Microsoft Entra ID is a pretty service. It could benefit from implementing a specific large language model instead of LDAP queries to find resources and implementation details in one comprehensive scoop. This could replace existing document references with AI-driven support for faster implementation.

I have been dealing with Microsoft Entra ID since 2000, which is now rebranded to Entra ID as a Software as a Service product of Active Directory.

The infrastructure of Microsoft Entra ID scales to register and manage various resources, including large-scale directory services for users, computers, machines, etc.

I find the support excellent. If I have an investigation and I am not progressing well, contacting support results in responses within one or two days, usually with competent people. Because it takes some time, I rate it a nine out of ten.

Positive

There are different licenses with various capabilities, as with any service Microsoft offers. Microsoft sets pricing based on customer demand, adjusting to find the optimal balance between sales volume and profit per unit, similar to how Costco manages product prices.

I rate Microsoft Entra ID ten out of ten. It can be improved with large language models for better usability, but currently, it is quite efficient. Microsoft CEO Satya Nadella suggested transitioning all Software as a Service systems to agent-based large language model solutions, which seems promising. I am willing to be a reference for Microsoft and I am open to receiving contact from people with questions about my review. The solution is rated ten out of ten.

As a bank in Turkey, we are prohibited from using cloud services for data storage. However, to utilize Microsoft Teams and implement a suitable Data Loss Prevention solution with Entra ID authentication, we adopted Microsoft Entra ID.

Microsoft Entra ID facilitated the implementation of Microsoft Teams as our collaborative platform. To prevent misuse of Teams features, particularly chat, we also integrated Symantec's data leakage prevention solution.

Microsoft Entra ID, integrated with Microsoft Teams, has enhanced the security of access to applications and resources within our environment.

People in the company are happy with Microsoft Teams, and we are quickly adopting it for collaboration. We are excited about the potential introduction of Copilot to Microsoft Teams, which is expected to be beneficial.

The most valuable aspect of Microsoft Entra ID is its ability to integrate with other cloud applications.

The quality of support has declined in recent years.

I have been using Microsoft Entra ID for two years.

Microsoft Entra ID has been stable since we started using it two years ago.

We experienced no scalability issues with Microsoft Entra ID. Our company's approximately 25,000 users were almost all synchronized to the cloud without performance problems.

Microsoft support has always been the best among all big companies. Although there is a general decrease in the quality of support across all companies, Microsoft Entra ID is still the best.

Positive

We previously used a local Microsoft Active Directory and integrated it with Entra ID. We also had other directory solutions like Oracle ID but chose not to switch because we depend on Microsoft solutions. Our desktops are Microsoft endpoints, and nearly half of our data center servers run Windows operating systems. We have existing long-term agreements with Microsoft, which led us to choose them for cloud adoption without considering other vendors.

We implemented Microsoft Entra ID in-house using resources and the help of Microsoft.

I would rate Microsoft Entra ID nine out of ten.