Microsoft Entra ID Reviews

The most valuable features are

• authentication
• authorization
• two-factor authentication
• I have never had a failure.

It's multi-tenant, residing in multiple locations. Authentication happens quickly. Irrespective of whether I'm in Australia, the US, India, or Africa, I don't see any latency. Those are the good features that I rely on.

It also has a variable extension, which is an added value because in Active Directory, if you have to do a schema, you have to make changes on multiple Active Directory instances. But here, as the extension attribute can be done from the application level, it helps you provide the provisioning. 

Another good reason for using Azure AD is that it can connect with other SaaS services. It also has SSOs, which, along with the MFA, makes authentication much easier.

One area where it can improve is connectivity with other systems. Not all systems are connected and you have to do coding to establish a point of connectivity. It supports certain vendors and it supports certain protocols. It is limited in many other aspects at the attribute level.

Also, some of the provisioning filters are not capable enough. You cannot do a date filter on the provisioning.

Perhaps they could also have easy protocols to create the accounts. Instead of just a file upload, they should have an easy connector to do the provisioning part.

I work in a service-based company and I've been using Azure Active Directory for my customers for around 10 years now.

From 2020 to 2022, there have not been more than two or three outages, and none was more than three to four hours long. And those outages may not have occurred the whole time in the entire environment, they may only have been in certain places.

When there is an outage, the end-user experience is affected, but that happens in AWS and in Azure. It happens with any SaaS product. Overall, it has not affected the end-user experience, but when there is an outage in Azure, it will have an impact on our environment.

It's scalable, but if you need more than one region, you have to pay for it. You have to think about how you want the service to be available.

The technical support is good.

Positive

The initial setup is easy and straightforward. Setting up Azure AD doesn't require you to do anything. You buy the product from Microsoft and Microsoft sets it up for you. You just establish the connectivity to it. It does not take more than a week or two to complete the setup.

The number of employees you require for deployment and maintenance of the solution depends on how you have set up your provisioning platform. If it is automated, you can have one resource. If you're still in manual, then it depends on the volume of the workload.

Licenses are based on the usage. There is no cap. It's based on the number of users we provision.

A SaaS solution is the best product. You get it at a better price and you have many Windows-based services that are included for free.

I would definitely recommend using Azure AD. Many companies are moving from other vendors to Azure because every company uses Office 365 anyway for Word, Excel, and PowerPoint. As soon as you use that, by default, you get an Azure AD account. If you have an Azure AD account, you definitely have features to use. Why would you want to go for another product?

Overall, I haven't seen any major issues with the product.

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.

This solution is useful for user management because it is integrated with DNS.

The solution is deployed on cloud and on-premises. We're using the latest version.

We have about 200-250 users. All of our users have local and Active Directory. We don't have plans to increase usage.

It's user friendly.

The solution could be cheaper.

We have been using this solution for about five years.

It's stable.

The solution is scalable.

Technical support is good.

Installation is straightforward. It only took a couple of hours to set everything up.

We pay a yearly license. Licenses are very expensive.

I use Azure Active Directory for user credential login, control my users with end-user policies, and apply my conditions.

Active Directory helps me all the time. When users want to log in, it shows me this information with a time and date. It also shows me which computer they are going to use. I can track my users at any time.

I like that you can run it on-premises. I also like that I can use Azure at any time as the main one.

ESAE management, especially the admin tools, could be improved. It should be built in by the vendor, and I shouldn't have to add patches or updates to connect to my domain directly. It should be added by default. The price could be better.

I have been dealing with this product for almost 20 years.

Azure Active Directory is a stable product. 

Azure Active Directory is a scalable product.

Customer service and support are perfect, especially when I'm dealing with my local third-party Microsoft vendor, who always supports me at any time.

Azure Active Directory is expensive.

I would recommend this solution to potential users.

On a scale from one to ten, I would give Azure Active Directory a 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. 

The active directory on Microsoft Azure is similar to the corresponding system for an on-premise active directory.

I have no issues with Azure Active Directory.

Our users and clients are migrating from on-premises solutions to cloud-based solutions. As a result, they do not require on-premise service. 

What I like is that I can go anywhere, at any time, and to any client premise, and I can simply log in to the admin panel and can serve any of my clients.

Instead of using Team Viewer, you connect to their local service, which is centralized. I have got the Microsoft exchange, and have access to Microsoft Azure. I can check the workstations, and perhaps soon I will be using Microsoft Intune and the Microsoft Defender enterprise. Even if I am not on the premises, I will be able to check and secure my workstations.

I don't have any major problems. I don't use it in a way that requires a lot of resources.

The main issue is that because Active Directory is in the cloud, it will inevitably be dependent on internet connectivity.

It would be beneficial if Microsoft could make it lighter so that it requires fewer resources.

Better pricing will help us market it more than having it on-premises.

Azure Active Directory was implemented one year ago.

For the time being it has been stable. I have a small number of clients, and no hybrid system. We chose those clients with a maximum of twenty users. We don't want large clients so that we can implement one system in one location, and roll it out the same way to all of the clients.

In total, I have 10 clients, five of those are now users of Azure Active Directory.

By the end of the year, we hope to have all of our clients using Microsoft Azure.

New clients are immediately placed on Microsoft Azure.

The Microsoft team in Mauritius has been extremely helpful in implementing systems and resolving issues. We have small clients who have not been faced with many issues.

We deploy the M365 business premium services and a couple of months ago we started to implement 365 Defender. It is a cloud-based solution.

We're new to it. For the time being, we are only using the antivirus component. We haven't used Intune yet. We are not using the entire package. We are only now going to put such solutions into action.

Microsoft Azure was implemented a year ago, and is only used for the creation of users and emails, group emails, and shared boxes, but my clients are mostly lawyers. So, the primary uses are online email exchange and word processing.

We are trying to implement Microsoft Azure more and more.

Azure is the central point. Microsoft Azure is replacing my on-premises service.

The installation is rather straightforward.

We had some assistance from the local Microsoft team.

Licensing fees are paid on a monthly basis.

When I calculated the price, it appeared to be nearly the same as the on-premise server. 

Better pricing would attract customers to use the cloud.

We haven't had to deal with any major recovery issues.

We have had Excel and Word files that were simply recoverable. We backup the server, but nothing more serious than that.

We are Microsoft centric solution providers.

We have very small clients, companies with 20 to 30 users of Excel, Word, and the internet. We deploy Microsoft 365 platforms, not much in the way of large software applications.

I would recommend this solution to others, and I am already promoting it. 

I am suggesting that all of my clients migrate from on-premise active directory to a Microsoft view because, with the current COVID, many of our users work from home. I just wanted to point out that almost all of our users work from home. They are currently working on the roaster. Half of the company works from home, while the other half works on-site. Having active and SharePoint, is really assisting them in working from home.

I would rate Azure Active Directory a nine out of ten.

We use Office 365. We have different licenses because our users are using mail, mail strategies, Microsoft Teams, and the Office package. We use a lot of different services. We use Microsoft Intune, which is connected to Azure and other services like Conditional Access, which we also use. Microsoft Defender is another one, which is also connected to Azure.

The solution is deployed fully in the cloud through Microsoft Azure. We are using the latest version. The solution is on cloud, so we cannot control the version we're using. That is controlled by Microsoft.

We are satisfied with this solution because we use all of its features.

Reading documentation could be simplified. Technical support could also be faster.

We have used Azure Active Directory for several years.

We haven't had any problems with stability. Everything works fine.

We haven't had any issues with scalability.

We have approximately 500 users in our organization. We have plans to increase the number of people in our company and products because we're fully integrated with Microsoft and we will continue to use this solution and new ones.

We are an IT company, so the people who are using this solution are software developers.

I'm not satisfied with technical support. On a scale of 1 to 5, I would give it a 2.

Sometimes it is the first-line support, and it takes a lot of time to explain the problem. One problem can be discussed in one month. I even have some examples in the past where I created a request, my problem wasn't resolved, I found solution on the internet. It was faster than receiving a reply from Microsoft.

Previously, we used Active Directory on-premise. We also used different products from different vendors.

We switched to Microsoft because it is in the cloud and because of business continuity. For our company, it is better to use everything on the cloud than to keep it on-premise.

It's also better to go to the cloud because of security reasons.

On a scale of 1 to 5, I would rate the difficulty of setup as a 3. It's of medium difficulty.

With setup, sometimes there are difficulties with reading documentation because if you want to implement something, you have to go to Microsoft's instructions, and you will be redirected from one page to another. After reading about just one topic, you have to open 20 new tabs. Every time, you have to jump between instructions, from one instruction to another. I don't like this approach, personally. It should be done in one document, and the instructions could be a little bit simpler for the user.

We implemented Microsoft step-by-step, because first we only used the Office package. Then we started using the Intune solution. Later, we implemented Microsoft Defender, and continued working with Conditional Access. It is not like one setup, so it's a continuous process. It depends on organization scale and the needs from organization.

We deployed the solution ourselves.

The price is fine. It's a good value for the money compared with other solutions.

I cannot provide the exact numbers because we use a different type of licensing. For Azure, we have an Office 365 license. We also have a Microsoft Gold partnership and some products are included in one license.

I would rate this solution 8 out of 10.

The product is really good, but it's up to each company to decide.

The solution is primarily used for handling user permission and containing with the Online Exchange. It's for handling user passwords, user permissions, all of the privileges, and for using Azure Active Directory for the Online Exchange.

We're satisfied with the product in general.

The most valuable aspect of the solution is the connectivity with our on-premise Active Directory.

We've found the performance to be very good.

The stability is good.

The scalability of the product is decent.

The installation process is straightforward.

The synchronization with the local Active Directory and synchronization with all of the users on the local and cloud could be better. Every user on the cloud and the on-premise local users should have a connection, have the same privilege, the same features. We should be able to change passwords from the local and have it synchronized with the cloud users.

I've used the solution for four years. It's been a while. 

The stability is good. The solution offers good performance. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

We've found the scalability of the product to be very good. There aren't any issues with expanding as needed.

In my organization, we have about 25 users. I deployed it for another organization as my company is a service consultant. Therefore, I do this installation for other users and other companies. There are about 60 users in one and another has 100 users. Another company has only 20 users there. The amount of users each organization has varies. 

We do plan to grow our team and possibly use the solution more. 

I have contacted technical support from Microsoft many times, including when the mailing system is down or when I have a problem with Active Directory or Azure. I contact the help desk for Microsoft, and they reply to me in about one hour and help me to solve any issue. It takes about three or four hours and at that point usually, everything is resolved.

The initial setup was very straightforward and simple. It was not overly complex or difficult. We didn't have any problems with the process.

The deployment for the local setup takes some time. For the cloud, it's very straightforward, and it takes no time at all. It takes about two hours to totally install the hybrid, the connection, and go on with the application.

We have about five people who can handle deployment and maintenance duties. That includes me and five engineers.

I can handle the implementation myself. I do not need the help of an integrator or consultant.

We have many customers that purchase licensing agreements with Azure. Typically they are charged per user.

We're a partner.

I would recommend the solution to others. If they just read a bit about it and connect with Microsoft, they'll likely get some good advice as to how to use it. 

I'd rate it at a nine out of ten.