Microsoft Entra ID Reviews

We use Microsoft Authenticator as well as Microsoft SMS Authenticator. Normally, we enable MFA for all users who have email access and application access. Users can choose which authenticator they want to use. Based on their convenience, they enable Microsoft Authenticator or Microsoft SMS Authenticator. Almost 80% to 90% of users use Microsoft SMS Authenticator. Users who travel a lot choose Microsoft Authenticator. 

We are using the latest version. It is updated by default, and we don't have to update the application. It is also automatically updated on mobile.

It has been stable, and we haven't had any issues since we started to use it. 

Microsoft Authenticator is as easy as Google Authenticator, but it is not open to all types of applications. Google Authenticator is integrated with other third-party platforms and applications, whereas Microsoft Authenticator is not. It should have more integration with third-party platforms and applications.

I have been using this solution for the last two years.

It is stable.

We didn't have any issues or concerns. Therefore, we have never raised a ticket for Microsoft Authenticator.

The initial setup is very easy. You have to enable MFA on the portal for a user, and you have to put the user's phone number. The user can then log in with Azure ID. The user is redirected to the second level of code authenticator and receives an SMS on the mobile. The user needs to enter the OTP.

It comes free with the Microsoft account. We have a yearly agreement, and all products are covered under it.

We will keep using Microsoft Authenticator as a secondary solution. We prefer Microsoft SMS Authenticator over Microsoft Authenticator. 

I would recommend this solution to others. I would rate Microsoft Authenticator a nine out of ten.

I use the product for user policy and group management. 

The tool's most valuable feature is auto logs. It helps with user activity and monitoring. It also assists us with GLBA policies and procedures. Microsoft Entra ID gives a 360 view of what the user has access to, what applications are available to them, when they are logging in and out, etc. It makes knowing what is happening to our tenants incredibly powerful. 

I want to be able to identify the audiences effectively and manage them. 

I rate the product's stability a ten out of ten. 

I rate Microsoft Entra ID's scalability a ten out of ten. 

The tool's support is very responsive. 

Positive

We have seen ROI with the tool's use. 

Microsoft Entra ID's pricing is reasonable. 

Microsoft Entra ID is very transparent and easy to access. It is easy to understand, but you shouldn't get lost in the updates. 

The product has helped our IT administrators save time. We will be onboarding the HR team soon. 

My company is loyal to Microsoft products because of its consistency and flexibility. 

I rate the product a ten out of ten. 

I set up Azure Active Directory for many customers of the company I work for. I'm an implementer. It is the basis of identity and access for all the tenants we are using for our customers.

Microsoft Entra helps our clients save a lot of time, especially with the many automation processes that we can leverage to facilitate our work. The amount of time saved depends on the customer's needs. In general, on average I would estimate it saves them 40 percent in terms of time. But in some cases, it could be up to 70 percent.

It also helps them save money because they can work with fewer employees, or they don't have to hire more employees to do tasks that can be automated.

Another benefit is that it provides satisfaction at the administration level. On the user level, the ease of use makes it easy to understand without any limitations.

And it provides quite a good level of security for all users.

All the features of the solution are helpful. Among them, one of the most important is the Conditional Access. It helps affect a Zero Trust strategy positively.

Also, I use Entra Permission Management to distribute the roles among all users according to management requests. Microsoft provides reports for visibility and all kinds of controls where you can see the users and their access. Permission Management helps reduce the risk surface when it comes to identity permissions. It supports adaptive controls and that helps me in defining the right controls for users.

I would like them to improve the dashboard by presenting the raw data in a more visual way for the logs and events. That would help us understand the reports better.

I have been using Azure Active Directory for about three years.

It's stable. I haven't experienced any downtime or breakdowns with the product.

It's scalable.

I'm satisfied with their support. 

Neutral

It's easy to set up. 

The amount of time needed to set up Azure Active Directory depends on each customer's use case. It will take at least three to four hours for a small organization, and in that scenario you wouldn't need more than one person to set it up. For larger organizations, it may take a week and we would need two to three persons.

Our customers are looking for advanced features and processes for it to be cost-effective for their organizations. They see it as an overpriced product. They are enjoying using Azure Active Directory, but they are looking for better prices.

Just follow the book.

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.

Containerization is mainly what I've been dealing with lately. I've been trying to provide solutions with Active Directory and cloud resolutions so that Edge services can communicate properly to the main data centers.

We use Active Directory for global authentication.

The advantage of Azure Active Directory is that it's a cloud environment, so just about anybody can get to it. As long as you can get to the cloud, you can get to the internet. You can authenticate offshore resources to client services, which is what my present company does. That kind of authentication is much more advantageous as an Active Directory solution.

If you want to replicate a website at the frontend in Azure, it's very easy to do it globally.

As soon as you authenticate to the web storage, where you hit the frontend, then you can redirect to whatever resources locally that are duplicated.

It doesn't function the same way as Active Directory inside of a physical infrastructure. Even VMware Active Directory doesn't function the same way in the cloud. Cloud is all flat. That's one of the disadvantages. You can authenticate through Active Directory through Federated Services, but it's mainly like an IIS web frontend and bulk storage.

It's all record based.

I've dealt with Azure Active Directory for about three years.

It is a cloud solution.

Stability-wise, it is much more secure and stable than AWS. Oddly enough, a lot of people think that AWS has many more regions and sites. It's actually not true. Azure has far more. There's a good reason why the government jumped right on Azure and uses it for their internal resources.

It is very scalable.

Microsoft technical support is very responsive. If you buy the enterprise package, then when you call them, they will jump right in and help you out.

When one of our clients had a ransomware outbreak, Microsoft helped them solve quite a lot and helped them get up and running.

The initial setup is very straightforward. Microsoft is very good about helping you get things set up, and they're very responsive.

We evaluated AWS AD. AWS support will provide bits and pieces, but Microsoft will jump in and help out. Of course, you have to pay the price for the corporate support, but who wouldn't want that, especially when your whole environment is a Microsoft environment.

It works really well, and I would rate it at nine on a scale from one to ten. You need good training, and Microsoft will provide that for free as part of their package.

We primarily use this solution for tracking authentication.

The quantum we are using is probably the authentication The security-based factor of authentication.

The most valuable feature is the factor identification. I find that it is natural integration, and it is just a natural step. I do not need to do anything else.

I think there is room for improvement with actually discussing, and advertising Microsoft as a an authenticator. Many people just get confused and use Google. It's weird because it's exactly the same way that it works. But it's there, it's definite region to start the people is more used to use their the Google authenticator instead of the Microsoft authentication. I think if Microsoft would make more of an effort to penetrate the market, that would be key.

In addition, it would be nice to have a biometric authentication like voice ID, or any of your medical ID. This would be a nice additional feature for Azure to have.

We experienced the aset surge that happened a month or so ago. There was a storm that broke one of the data centers in south-central. The functionality of active directive for Microsoft support was in shortage.  It took a day to return back to functional use.

The solution is scalable for our needs.

I have not needed to request technical support. All of the Microsoft guides are really good and are very helpful.

I know more about Microsoft than any other technology, that's why I didn't look for any other competitors.

It was a very straightforward initial setup. To be honest, we are a pretty small company so for us it's one portal and everything is there. It's not that complicated.

I like it, I love it and it works fine.

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.