Microsoft Entra ID Reviews

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.

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.

Neutral

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.

We have been using Microsoft Enterprise for ten years, and we actually started beginning to really use it about two years ago. Earlier, we had an access manager on the premises, but everything is moving to the cloud. So we are moving our access management and identity management solutions to the cloud as well.

The whole access management solution is valuable. In 2015, we were selecting a new access management solution, and because it was already integrated, we started using it. 

Integration with Defender allows us to get alerts and respond to them by blocking users. Microsoft Entra ID has streamlined and centralized our device management and threat response processes.

We are looking for more customization with BRAIN and everything else, and while they are following up on that, we want some more of it.

We have experienced some downtime because of the use of the data centers.

In Microsoft technical support or Microsoft Denmark, we have an account manager and strategist, whom we contact along with the suppliers who have their own technicians. The experience has been positive.

Positive

Earlier, we had an access manager on the premises before moving to Microsoft Enterprise for cloud-based solutions. In 2015, we selected a different access management solution initially.

Would you rate the overall solution on a scale of 1 to 10? Yeah, excellent. From one to ten, would you mind the call? I think, yeah, excellent.

Microsoft Entra ID serves as an identity protector and service privilege manager.

It has enabled my organization to build a secure environment for user login and asset access. We can enable secure user logins and access to assets.

When we implement app access with Microsoft Entra ID, it gives us confidence that we have secure authentication for our applications.

With privilege identity management, we can grant or escalate rights to a role for a short duration of time and not forever. It is a great feature. It is useful to validate the escalation of privileges. 

Federation on access service principle and the ability to be passwordless in certain use cases are valuable. Federated identity management is a great feature for the zero-trust model. 

Microsoft Entra ID could benefit from more fine-tuned rights. It is necessary to prevent granting an application or user broad access rights. A more precise approach would allow for specific rights, limited to certain contexts within the organization.

I have been using Microsoft Entra ID for three years.

Microsoft Entra ID efficiently responds to numerous requests, and we have not faced significant connectivity issues, making it reliable.

Their customer support is good.

Positive

I have not used any other solution. I was previously using Azure AD. About two years ago, it was renamed to Microsoft Entra ID.

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

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.