Microsoft Entra ID Reviews

We primarily use the solution only for the employees. It offers a single sign-on to business applications. Internal modern applications also go through Azure Active Directory, however, we use Active Directory for the legacy ones. (Kerberos).

It takes a couple hours to add SSO to new business SaaS. The Azure AD Marketplace has all the applications we bought so far as built-in templates.

The single sign-on of the solution is the most valuable aspect.

The initial setup is straightforward.

The solution offers good bundles that include Office 365. 

The pricing is pretty decent.

The product is pretty user-friendly and offers good customization capabilities.

We find that most of the new features are in preview for too long. It gives you the announcement that there's a new feature and yet, most of the time, it takes more than one year to have it generally available. Often we have to go and sometimes just use a preview without support. 

We cannot run all the configurations from the APIs. I would like to have something that has code and to just be able to back up and apply my configuration. Right now, we are managing more Azure tenants. It's hard to keep all of those configurations at the same level, the same value.

We would like to have more granularity in the Azure conditional access in order to be able to manage more groups for applications. That way, when adding a new applications I don't have multiple conditional access to modify. 

One of the main requests from our security team is the MFA challenge. Azure, by default, is more user-friendly. We have a lot of debates with the security team here as the MFA doesn't pop up often enough for them. From an end-user perspective, it's a better user experience, as users generally prefer fewer pop-ups, however, security doesn't like it. It's hard for security to add. 

We don't have Azure Premium P2 yet, however, most of the advanced security features are in the P2, and it costs a lot more money.

I've been using the solution for four years at this point.

The solution is relatively stable. The only issue we have is that there's a lot of things on Azure that are synchronous. Sometimes it takes time for changes to apply, and it kind of depends on the time of the day. A lot of the time we're happy with it, however, sometimes it creates a bizarre issue that is difficult to troubleshoot.

The solution is quite stable. If an organization needs to expand it out, they can do so rather easily.

We have about 9,000 people in our organization using the solution.

While the technical support is good, you need premium support. The standard support is more for small enterprises. We have the premium support and with the premium support, it's much better. There's a direct line to the correct type of support. It's very good.

We previously used SiteMinder from Computer Associates. The main reason we migrated to Azure was for the integration with Office 365. It then became our primary authentication source for the employees.

The initial setup is not too complex. It's pretty straightforward.

We didn't need the assistance of an integrator, reseller or consultant for deployment. We were able to handle everything in-house.

The pricing is really great and Office 365 packages are good. We don't pay for it separately. It's included in our package and the APIs are really great. I'm not sure of the exact cost of Azure. It's a package deal.

We've looked into Okta for B2B and B2C clients, not necessarily for our internal employees.

We're just a customer.

We're using the latest version of the solution.

I would recommend the solution for employees. It's a really great tool. However, we tried it also for consumers, for clients for B2B and B2C. For me, it isn't really a great production product. We researched Okta for that.

Overall, I'd rate the solution nine out of ten.

We just use the solution for the authentication and the provision access control, among other tasks.

The access control aspect of the authentication is the solution's most valuable aspect.

The single sign-on is very convenient for us.

It would be ideal if the solution moved to a passwordless type of environment. It's the future of authentification. It's also more secure and convenient.

I've been using the solution for about a year.

The solution is quite stable. I haven't heard any bad things about it. It doesn't crash or freeze. I can't say that I've seen bugs or glitches. It seems to be very reliable so far.

I believe the solution is scalable, although I have not tried to scale it myself personally.

We have many people on the system, including doctors, nurses, practitioners, assistants, etc. It might be around 100 people, give or take.

I've never dealt with technical support for any reason. I wouldn't be able to evaluate their services or discuss their level of responsiveness.

I didn't handle any aspect of the implementation, as I'm not technical in any way. I wouldn't be able to specify if it was complex or straightforward or how the deployment went.

I don't have any insights into the licensing costs. I'm not a part of the accounting or payment process.

Our organizations has a few partnerships with Microsoft.

I don't know which version of the solution we're using. It's most likely the latest, due to the fact that it's a cloud deployment.

The only advice I have for other organizations considering the solution is this: just make sure that you have the right requirements. It's never a carbon copy. Every environment has different needs and requirements.

I'd rate the solution eight out of ten.

Most of my customers use Active Directory Premium for condition and access scenarios that they need to comply with my conditions to access my resources. They also build new environments, virtual machines, and some other products like SQL on the infrastructure as a service. There are some customers that use Microsoft Intune, which is mobile device management. Microsoft Intune is a cloud.

The most valuable feature is that it is very easy to implement, you don't need a lot of effort to set up the solution. This is the most advantageous point, that you can do anything on Azure without taking too much time.

Microsoft has a feedback page, in which if anyone has any suggestions or feedback, you can send them to them. They have all of the technical resources available on the internet, on their website. In case you need the support, you can easily open a ticket with them because you already have a subscription and you are eligible to open a ticket.

I've been working with Active Directory for twelve years. I have experience with Microsoft Active Directory Virtualization like Hyper-V systems in the family for Microsoft. So, this is a 12-year journey, it has been 12 years of experience with this product.

It's currently on-premise but because of COVID, a lot of our clients are moving to the cloud. 

I have contacted technical support many times for the cloud. They are good. But for on-prem, they have recently started becoming delayed. Maybe the technical resources are not very good. I know Microsoft, they are focusing on the cloud solutions more than the on-premise solutions. The support for on-premises has become not as at previous times. But for cloud solutions, they are good.

The initial setup complexity is based on the scenario. If it's infrastructure as a service where you are building VMs, it could take you one day to complete your setup for virtual machines. 

Whether or not I would recommend this solution, would depend on the users' needs. If their use cases fit what Microsoft provides, then I would recommend it. 

I would rate it an eight out of ten. The price plays a factor in the rating. Customers are not oriented with a cloud solution, they move forward very slowly towards the cloud, because maybe in my country big sectors, like the banking sectors, don't deal with the cloud. So customers see this and don't want to use the cloud either. They fear for their security and privacy. Although Microsoft assures that they protect their customer's data and privacy.

We are a software development company and solution provider, and this is one of the products that we implement for our clients.

This is an easy way to give users access to applications. I can share access with other organizations outside of our network.

This solution is easy to manage.

The ability to grant access to other organizations is helpful.

It integrates well with a large number of applications.

Microsoft needs to add a single setup, so whenever resources join the company or are leaving the company, all of the changes can be made with a single click.

I would like to see a secure, on-premises gateway that offers connectivity between the physical servers and the cloud. The capability already exists, but it is not secure enough when the setting is marked private.

I have been using Microsoft Azure Active Directory Premium for about a year.

In the time that I have been using Microsoft Azure, I haven't had any problem with stability.

This is the right platform if you are looking for scalability. We have more than 100,000 users.

We have not needed to use technical support. 

We have a couple of contacts in the Microsoft team, so we will reach out to them in case we have any questions.

I have recently been working with Okta, and I find that most organizations are moving toward it. With this in mind, I think that Microsoft has to take care, and consider why so many people are switching. The most important reason is the single setup. Once they set up Okta, it's easy for the organization.

I have been working in Microsoft Azure for a long time and I find the initial setup to be easy.

For maintenance, we have a team of 20 administrators and developers.

Licensing fees are paid on a monthly basis and the cost depends on the number of users. There are no charges in addition to this.

The suitability of this solution depends on the technology and the environment at the organization. Many companies are still transitioning to the cloud, leaving part or all of their data on-premises. Ultimately, it depends on the data that they have and their preference or requirements for keeping it on-premises. In some cases, people want to move only non-private data to the cloud. All of these things have to be considered before implementing Azure Active Directory.

I would rate this solution an eight out of ten.

We use Azure AD for sign-on security as well as for our customers' Microsoft 365 solutions. We help migrate our customers from the traditional Active Directory, and to use Exchange Online and Microsoft Teams. We use Azure AD to secure their login processes with multi-factor authentication. In some specific cases, where there are specific applications, databases, or Active Directory login information about users, we integrate Azure AD with those elements.

Multi-factor authentication really secures our environments and gives us the flexibility to use location-based policies. Azure AD also gives us a lot of flexibility in our scope of integration.

It's easy to configure Microsoft products with Azure AD. It is almost an instant integration. In hybrid installations it is a bit more complex to configure, but not that much. In short, it is good for most Microsoft customers and the products they use.

Some of the features related to authentication could be made clearer. In my last organization, I tried to integrate a third-party education solution with Azure AD, but it was a bit difficult to configure. I would like it to be easier to integrate third-party applications.

I have been using Azure AD for three or four years.

It's a stable product. I haven't encountered any problems or bugs.

The solution is very scalable.

In general, there is no problem in configuring Azure AD. It's not hard. But, as I said, configuring third-party, open-source applications with it is a little bit difficult.

We usually set aside one day to configure Azure AD for new organizations. In general, it takes one person to maintain it, perhaps two in some cases.

We have faced a few little problems in our customers' hybrid environments. Backing up the ADFS (Active Directory Federation Services) is very important, but some of our customers didn't do so and they lost their ADFS proxy servers. That is one of the important lessons I have learned. In those cases we had to reconfigure almost everything. It's simple to back up ADFS, so I would advise doing so.

But from the user's point of view, we've faced no problems. It works well.

We are using the solution primarily for demo purposes. We use active data cases from Microsoft. You can run different kinds of virtual machines and different kinds of services. We're currently using it in production.

It's very smooth and very easy to use. 

The performance is good. 

The product is stable.

It's quite scalable.

The initial setup is not complex.

We would like to see more system updates. They should happen more frequently.

I've used the solution for a while. 

The stability has been good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution can scale if you need it to.

About350 people use the solution in our organization.

Their support is not great when you are using cloud solutions, however, when you are using cloud solutions, it's very smooth and very effective. We haven't had any issues. 

I'm not sure if a different solution was used previously.

The installation was not complex. It was pretty simple and pretty straightforward.

The deployment is pretty fast. It takes ten minutes, at a maximum, to set up.

You only need one person for deployment and maintenance. 

I didn't need the help of any third-party integrator or consultant. I was able to handle it myself. 

The solution is pretty affordable. Sometimes you can get a Microsoft voucher to get some sort of discount.

I'd rate the solution a ten out of ten.

Anyone who moves to Azure must have Azure Active Directory.

Azure Active Directory is identity management.

It's something we have to deal with every day. It is present. If you're in a domain environment, you'll need it to log in. If you work in a Microsoft-centric environment, you can't avoid it.

It's in the background and anyone who is a member of a Windows domain must have it.

Many people believe that the Azure Active Directory is overly complicated and antiquated.

Active Directory Windows hasn't evolved that much in over 20 years. Azure Active Directory, has a few nuanced elements. It's fairly straightforward.

I have been dealing with Azure Active Directory for well over 25 years.

Azure Active Directory is very stable.

Azure Active Directory is quite scalable.

When you've been dealing with a piece of technology for 25 years, it's simple, but the public perceives it to be complicated and antiquated.

Active Directory is a Windows component that requires a per-user license. If you're on Azure, it can be free or it's incorporated,  at no extra cost, or it can become extremely complicated.

If there is a cost, it is not expensive, but you have to have it if you are running an Active Directory environment. It's a have to have, not a nice to have.

We are partners with Microsoft.

I would rate Azure Active Directory an eight out of ten.

We are using Azure Active Directory in our company at a group level.

Azure Active Directory has been very useful for our company, it is not difficult to use.

Azure Active Directory could improve the two-factor authentication.

I have been using Azure Active Directory for approximately four years.

The stability of Azure Active Directory is good.

Azure Active Directory is scalable.

We have approximately 1,000 users using this solution. Not everyone is using Azure Active Directory but the ones involved in the cloud are.

I have not used technical support.

The initial setup was very easy for Azure Active Directory.

My advice to others is if they're going to move to the Azure Cloud Platform, this could be a highly valuable add-on, in order to take care of authentication matters in general. It's a very useful tool and not difficult to use.

I rate Azure Active Directory an eight out of ten.