Microsoft Entra ID Reviews

We need it for running MSA protection for most of the users. We need Azure AD Connect because they are highly on primary setup, so they need to sync on primary with Azure AD.

From the beginning when I joined the company, they were already using Azure AD Premium. The most wanted features would be the synchronization between the Windows AD, Azure AD, because there are so many capabilities that just because we can't sync their own from Azure AD.

The most beneficial feature would be the effectiveness of having a hybrid set-up. When we need to create an account, we create it in Auto Activator 3. Even though the users are created and managed in Windows really, we can use all the benefits of the cloud, as well.

Right now I can't point out a particular feature, but sometimes when we work, it evolves.  There are so many features that are out recently, so it'd be hard to set up MSA for obvious remote users, so users who are using Azure are hard to use it remotely. So, while we're setting that up, we have face of issues which show the limitations of Azure.

Initially, we wanted to exclude specific users from MSA. So, we had a condition policy, which forces MSA for all the users. So we wanted to exclude users who are using an NPS extension.  So it was not listed, as a NPS extension was not listed outside an application, in actual, so, we go back and were not able to exclude users using NPS extension from MSA. So that was one limitation that we found and we had to work around that.

We noticed recent additions on display that have been in recent updates. On the board, there are some features that still need help. 

The stability is pretty good. Earlier, there were freezes here and there. But, we overcame it. What w have now is stable, but they are trying to include more features.

We have almost 500 users. So, it is pretty easy. They are including more features, which enhances onboarding and decommissioning users. From an actual perspective, it's pretty easy to scale.

Tech support has its up and downs. So, sometimes it will take one week, and other times two weeks to resolve a case. Sometimes they have to respond fast, and they do so. It is not consistent.

It's really affordable. It does not feel as if it is too costly. It's okay to spend this money for this product or feature. Yeah, I think it's affordable.

If you have connections with a PSP partner, it will be easy, I guess. If you're buying an Azure AD Premium independently, you won't have a helping hand from them. You'll have support  but, not much other than that. With a PSP partner, you will feel like that you can implement or you can quadrate.

Once Azure is developed, and fully established, it will be a perfect product. It is still in the development stage at present. 

I primarily use this solution for hybrid deployment, security, securing resources and for integration purposes. In terms of security, we have been using the B2B/B2C hybrid integration with the certificate authentication.

From a practice point of view, of storing secrets internally on Azure AD, we use the certificate when we can.

I would advise to allow an ex-client user to change their password. At present, you can only change your password externally if your password is still valid. If your password is expired, you cannot actually do it through Azure AD.

Most of the time, this product is doing purpose-built solutions. Some people on my team like the multi-step authentication. Others like the fact that it secures their resources externally.

We found the ADFS being a redundant part of the solution. But, it was removed. The licensing is a bit confusing if you are not going into the premium model.

Three to five years.

It is pretty good in terms of stability. I have not had any issues. It has not crashed.

In terms of scalability, we have not had any formal issues or outages from the solution. We are currently using it for 100 users. But, our clients are also using it, and I think we have at least several thousand clients using it.

The initial setup was straightforward. It has been improving a lot in the past couple of years. Yes, it is a lot easier now than when I first started working with this solution. 

I would estimate that the initial setup would probably take a team a week to set up.

When implementing for one client, where they had ADFS turned on, we could not ID enough ADFS and when there was no internet connection. This was a Catch-22 for us, and very frustrating. I would advise new users to use Azure over the ADFS.

I use Authenticator across my company for controlling access to our platforms and data.

The most valuable feature is the prompt for a number so that you're sure what you're seeing is what you're agreeing to.

It would be an improvement if Authenticator made it easier to recover the app if you reboot your cellphone and lose access.

Authenticator is stable.

The initial setup is straightforward.

Don't delay implementing this solution, it's the best thing you can do for your identity protection. I would rate Authenticator as nine out of ten.

My main use is for directory services, including identity access, management policies, access control, authentication features, and endpoint management.

The licensing model makes it difficult to understand the real cost of the solution, especially because it changes all the time.  

I have fifteen years of experience with Active Directory.

The stability has improved from a couple of years ago. From time to time, there are service interruptions, but they're not a problem.

This solution is easily scalable.

The technical support can be confusing - if you're looking for something very specific, it can be hard to get the right answer or a solution. Google Workspace's support is stronger - it's fast and easy, and they go the extra mile without asking.

Active Directory is straightforward to set up.

Azure is the leading market solution because of its history, features, and maturity. I'd rate this solution seven out of ten.

My primary use case is to access our company resources. I'm a solution architect and we are customers of Authenticator.

I use this solution on a daily basis and it's a very functional app. that adds an extra layer when it comes to securing the data owned by my company. It's quite easy to deploy. 

I'd like to see integration between applications and phones included in the solution. It would also be helpful to have support for the kind of integration you see between Facebook and Google, support with protocols from one application on the internet or SaaS to another one. I've seen several kinds of applications in the area of risky behavior that are a little better in other solutions.

I've been using this solution for a year. 

The solution always works, it's stable. 

The solution is scalable, we have around 40,000 users in our company. 

I have previously used other products but Authenticator is included in the Microsoft license suite package so the decision to go with it was commercial. 

The solution is connected with Intune in the cloud so implementation is very easy and took me less than five minutes. Everything is updated via Microsoft cloud delivery.

I rate this solution eight out of 10. 

I am using this product for user authentication.

I think the documentation and configuration are both areas that need improvement. 

The product changes and gets updated, but the documentation doesn't keep pace.

The initial setup could be simplified.

I would like to see a better UI tool.

The company has been using this solution for approximately four years.

We are using the latest version.

It's a stable solution. We have not experienced any issues.

Microsoft Azure Active Directory Premium is a scalable solution. It scales very well.

We all use this solution daily. We are a team of five the company.

The most valuable feature is the ease of scalability.

The initial setup is fairly complex.

We are a smaller company and it only took us two days to deploy.

We did not use an integrator, we used in-house knowledge.

If you are familiar with Microsoft, this is the product to use.

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

• Office 365 authentication
• SSO for ServiceNow
• SSO for other cloud applications.

Improved user experience with SSO logins.

Keeping the same credentials as Active Directory.

Role-based access controls.

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.