Microsoft Entra ID Reviews

My main use cases for Microsoft Entra ID are managing all users and everything related to user management.

The feature I like the most about Microsoft Entra ID is the ease of use on the platform.

The benefits that these features of Microsoft Entra ID have brought to my organization are that it is easy to use, pretty secure, and customizable.

The impact of implementing Microsoft Entra ID on my secure access to apps or resources in my environment is that it is pretty secure.

Microsoft Entra ID's integration capabilities have influenced my Zero Trust model through conditional policies.

I think Microsoft Entra ID could be improved by assigning permissions to nested groups in the next release.

I have been using Microsoft Entra ID for four years.

I would assess the stability and reliability of Microsoft Entra ID as pretty reliable.

I have not experienced any downtime or performance issues.

Microsoft Entra ID scales pretty well with the growing needs of my organization.

I have expanded usage of Microsoft Entra ID.

On a scale from one being the worst and ten being the best, I would rate my customer service and technical support as a nine.

I give it a nine because sometimes it is pretty slow.

I would evaluate my customer service and technical support as a nine.

Positive

Prior to adopting Microsoft Entra ID, I was not using another solution to address similar needs.

I would describe my experience with deploying Microsoft Entra ID as excellent.

It works well, and I did not face any challenges.

My experience with the deployment of Microsoft Entra ID is that it is pretty easy; it was very smooth.

The process was very smooth, with just opening a support case and having it resolved.

I have definitely seen a return on investment with Microsoft Entra ID.

My experience with the pricing, setup costs, and licensing of Microsoft Entra ID is that it is decent.

Before selecting Microsoft Entra ID, we only considered Microsoft because we are a Microsoft shop.

My organization's approach to defending against token theft and nation-state attacks has not changed since implementing Microsoft Entra ID; fortunately, we have not experienced any attacks yet.

Since implementing Microsoft Entra ID, I have not observed any changes in the frequency or the nature of the identity-related security incidents in my organization.

The implementation of device-bound passkeys in Microsoft Authenticator has positively affected my organization's security posture as compliance and MFA requirements are being met by the Authenticator app.

Microsoft Entra ID makes work easier; compared to competitors, it is easier to use, easier to navigate, and more customizable, which makes it a better choice.

My advice to another organization considering using Microsoft Entra ID is that it is very reliable and easy to use; you can manage all your security and infrastructure-related user management, lock everything up with Zero Trust policies and conditional access, and it integrates well with everything, whether you are on AWS or Azure. I would rate this solution a ten out of ten.

We implement standardized conditional access policies for our customers using Microsoft Entra ID, mainly for security, governance, and conditional access. We also sync on-premises Active Directory accounts to Microsoft Entra ID to manage groups and Azure resources like Azure Virtual Desktop.

We started our journey with Entra from a security standpoint, using features like PIM and Microsoft Defender for Cloud. It has improved our security posture, especially in healthcare, where security is paramount. We have to ensure that our data is secure for HIPAA compliance. 

It improves our user account management and initial access. We can see a lot of stuff using Microsoft Lighthouse because we're an MSP, so we use Lighthouse to gain visibility into the tenants and accounts. We can dive into the financial side and get reports. It's highly granular and easier from an organizing standpoint.

We use the Microsoft security stack, including Defender, Purview, etc., so we get a security score and recommendations on ways to fill in the gaps. We get some ideas on how to tweak the Entra tenant or the environment better. But we're following Microsoft's guidelines with reporting or recommendations.

We implemented FIDO 2.08 for phishing resistance, so we use security keys like the UBP. We're passwordless now. It depends on our customers' licensing, such as whether they have an E1 or E3 or whichever Microsoft 365 license they have. We're moving them to a passwordless architecture or, at minimum, improving phishing resistance with an MFA authenticator. 

We primarily use Entra to monitor risky users or detect questionable sign-ons. We get alerts if a user logs in outside a trusted location or from a different IP address we don't recognize. We have recommendations or conditional access policies to detect or block risky sign-ons. 

We had more risky log-ins detected than normal, so we updated our conditional access policies to say that if we see more risky log-ins in the next 24 hours, we'll lock it down in the next 12 hours to fine-tune the conditional access policies and that kind of stuff. We're trying to standardize or make everything the same, depending on pricing or cost. We're trying to move everybody to the standard baseline for just what we try to deploy for the next of this year. 

It's had a tremendous impact on our security. We can set granular permissions and different levels of access for various teams. We can govern the Entra side of the house or the Azure public cloud side and other teams like marketing, HR, finance, or any of those groups as needed. 

Entra helps us advance our zero-trust strategy. We have to follow CIS standards and HIPAA because we're in healthcare and PCI DSS. We're implementing Microsoft's best practices for their security framework. It makes a big difference when we're deploying new infrastructure for new clients and everything.

Microsoft Entra ID provides granular role assignments for Azure permissions or Azure AD roles. Using a privileged identity manager allows us to give specific access to certain groups of employees for a limited time. Entra's ability to integrate Azure Virtual Machines and security benefits has been exceptional, especially for managing infrastructure and applications.

I'm satisfied with the features provided by Microsoft. They are continually improving their offerings, and I don't have any downsides or issues with Microsoft Entra ID. We're integrating a lot of Azure virtual machines and utilizing the Azure side. We love Microsoft licensing, all that stuff. And Yeah. It's just, you know, just using the CSP portal as well has just been a game changer for us too. 

We have been using Microsoft Entra ID for about three years as a Microsoft CSP partner.

The stability of Microsoft Entra ID is very great. It's a high availability solution, and we haven't had any major issues. Even in cases of global outages, Microsoft provides transparency through their health portal.

The scalability of Microsoft Entra ID is excellent. We have no problems scaling virtual machines, and we can tailor solutions based on customer needs and budget, ensuring proper SLA and redundancy.

Whenever we have needed Microsoft support, they have provided fast response times and have been very helpful. Although we've occasionally needed to be transferred between departments, overall, their support service is reliable.

Positive

Before Microsoft, we used various on-premises solutions with Active Directory domains. The shift to Microsoft Entra ID was driven mainly by the convenience and cost benefits of consolidating under a single vendor, a single pane and glass setup.

The initial setup was done through Ingram Micro, and it was smooth. They helped set up our accounts and provided the necessary training for managing CSP.

The implementation was done with the help of Ingram Micro, a third-party vendor. They provided excellent guidance throughout the CSP integration process and conducted seminars for further training.

Our ROI has been strong since becoming a CSP partner. We've seen tremendous growth and attracted many new customers using Microsoft products. We leverage existing licensing, like Windows Server or SQL, and hybrid benefits, and our sales and marketing teams benefit from co-selling and partnership advantages.

Our sales and marketing teams handle licensing, co-selling, and marketplace activities, which makes it easier to centralize and manage our Azure or multi-cloud costs effectively.

Before implementing Microsoft Entra ID, our sales team evaluated other vendors offering similar solutions. However, the benefits of Microsoft licensing and CSP partnership made it an obvious choice.

I rate Microsoft Entra ID a nine out of 10.

My main use case for Microsoft Entra ID is full identity management and system security.

The features I appreciate most about Microsoft Entra ID are Conditional Access.

The control that Microsoft Entra ID provides is significant, as when we tie it in with Intune, we can then set policies where only enrolled devices can access it. So even if users have the correct credentials and they get compromised, they must be on a device that's enrolled and known to Microsoft Entra ID and Intune. This aspect, from a security standpoint, makes our lives considerably easier.

Thanks to the implementation of Microsoft Entra ID, our security team can operate with confidence. The main benefit is that we can go to clients and say that no matter if their credentials get leaked, while we still want to change them, they still cannot access work data because the device they use must be enrolled within Intune. This compliance piece and the Conditional Access piece make life much easier, and also the geo-fencing as well. So if we know that a client only works in the UK, we then do not allow connections from outside of the UK.

The integration of Microsoft Entra ID has influenced our Zero Trust model significantly, as we use SonicWall Cloud Secure Edge, which has a direct integration with Microsoft Entra ID. Rather than having to set up individual users within the SonicWall platform, we tie it straight into Microsoft Entra ID. You can use security groups, so only those within the security group can use Cloud Secure Edge, and then you can dictate what systems within the Zero Trust architecture they can access. The integrations are fantastic and make life considerably easier.

Our organization's approach to defending against token theft and nation-state attacks has changed since implementing Microsoft Entra ID, as we have employed a full SOC solution. We have a direct SOC team that monitors identities and management and does the full ITDR piece with us. That integration with Microsoft is fantastic because of the amount of data we get from it, allowing us to ensure policies are correct and people are not doing what they should not be doing while using the systems as required.

An example of this is that we can set policies tied in with geolocation using Microsoft Entra ID. If we have clients traveling abroad for work, we can set policies within both Microsoft Entra ID and the Huntress SOC solution that allow those specific users to access work while they are over there, but only for that time period. Rather than opening the whole company up, we specify which users are going, so we just set it up for those five or six users. Then, we can also set it on a time-date delay, so one day after they return, we can shut it all down, and the security stance steps up again, which keeps everyone satisfied.

I think sometimes Microsoft Entra ID provides a bit too much information from the start. For example, when I first sign into the portal, it can be overwhelming, particularly when the SOC calls me saying there is something going on and I need to look at the tenant. At three in the morning, I find myself staring at a display full of information. Overall, can it really be improved? Perhaps a little bit, but the main issue is just the sheer amount of information in there.

I have been using Microsoft Entra ID for six years, or when it was Azure AD as well.

Since the implementation of Microsoft Entra ID, I have not really used anything else, as we have been a Microsoft house.

I definitely see a return on our investment from Microsoft Entra ID; being able to use single sign-on both on-premises and in the cloud is massive in terms of time and energy.

I have not really considered any other solutions from other companies since all our clients have always used Microsoft Office, so using Microsoft Entra ID along with that whole single sign-on feature with the on-premises solution and Entra Connect was just an already made decision for us. Why make life difficult for ourselves and switch?

Once I get my head around Microsoft Entra ID, I would give it a nine on a scale from one to ten, with one being the worst and ten being the best. I would rate this review a nine overall.

We predominantly use Microsoft Entra ID for running our User Directory Service. It integrates with Intune, Exchange, and SharePoint.

Microsoft Entra ID acts as our core directory. It is essential for authentication, VPN authentication, and using onsite RADIUS. It supports our user scopes for various applications. Everything we do revolves around this directory and its authentication.

If I have one criticism, it's regarding processing times. Changes or even inbound email logging tend to take a minimum of fifteen to twenty minutes. There is a need for more real-time processing. Some user updates are instantaneous, while others can take two to three hours. A feature to force manual updates would be beneficial rather than waiting for scheduled updates.

I have been working with Microsoft Entra ID since 2009.

For stability, I wouldn't give it a ten because we have experienced some outages. I would probably rate it around a seven. Generally, it's stable, but when it goes down, the impact is substantial.

From my perspective, we haven't encountered any scaling limits. It meets our needs for user productivity.

I would rate Microsoft's technical support on the lower side. While some responses are quick and satisfactory, there have been occasions where issues took weeks or circles to resolve, sometimes closing and reopening without resolution. I would rate their support around a four.

Neutral

Through acquisitions, we used Google Workspace. We have spent a considerable amount of time with it.

The initial setup of Microsoft Entra ID is not straightforward without training. However, once you are familiar with it, the process is seamless.

We did not use an integrator or consultant for the first deployment. Initially, I did it all myself, although I have a few people working with me now.

Regarding pricing, for the services we receive, it seems within the market range and about average.

Through acquisitions, we have spent considerable time evaluating Google Workspace.

Overall, Microsoft Entra ID does what we need it to do. I would rate it around a seven on a scale of one to ten.

We use Microsoft Entra ID for risk management of our users and compliance policies. We focus on automating processes, managing user identities, and placing them in appropriate groups with specific access roles. 

We do a lot of risk management for our users. We have a lot of compliance policies and custom assignments. We try to automate as much as possible. There are a lot of policies that take our users, identify where they should be, what back roles they should have, and put them where they need to be.

The management and risk assessments have become much easier. We can identify and address potential security threats quickly, especially given our mobile college student population. We have a lot of college students who are very mobile. It works with our CyFlare and security suite. This integration lets us know right away when we have somebody trying to impersonate. We get the notification right away. We can assess our risk factors and automatically put that user in a high-risk area. We can then initiate a contact to know what is going on. Are they in Mexico and Davenport, Iowa at the same time or did they put a VPN in?

We have a much better level of comfort. Everybody does not have admin rights. We need such a level of control considering the number of users that are out there. We had to get that in a bundle, and they have done a good job with that.

Microsoft Entra ID has allowed us to move forward with the zero-trust model. Unless you have control over your users and your authentication mechanisms, you have no control. It is our main portal coming into our security suite. They would not get to the security suite till they got through Microsoft Entra ID.

We have just stepped into the passkey. We like its simplicity. Our users are much happier that they are not thumbprinting, fingerprinting, and typing code numbers in. We are still a little leery, just because it could be a stolen device or stolen pass. Once they have that device in their hand, they are already halfway there. Between Entra ID, our policies and risk assessments, and the passkey system, we are on our way.

Implementing Microsoft Entra ID has not changed our organization's approach to defending against token theft and nation-state attacks a whole lot. Our security team has things locked down, and we have our network segmented, so you cannot jump. We do penetration testing almost daily. We have Entra ID and Defender. We monitor all that through API connections. We monitor any phishing and risk factors for our users and any anomalies in baselines.

So far, we find it working very well in terms of the detections, the risks, the events, and the logs that it sends us. Intercepting these attacks in the middle, seeing that the keys have been hit, and going into a more managed identity has helped. It gives us a feeling of security.

There has not been any reduction in the incidents. We have the same number of incidents, maybe an increase. However, we are catching them, and we know where they are coming from, so we can be more proactive instead of reactive.

Identity management with policies stands out as the most valuable feature. It offers a hands-off experience, providing full control over user access. The granular control, such as preventing logins from specific locations, enhances security significantly.

They are already improving it on a daily basis. They are all the time taking things away and adding things. I went through Update Manager which has all the automated, hot patching. With all the different things that Microsoft has been doing and adding, they are on the right path. It is moving so fast that keeping the knowledge on the IT side, for the people who have to use it, is going to be a bit difficult. 

Microsoft's biggest challenge is the documentation. The challenge lies in keeping documentation up-to-date due to rapid changes. Troubleshooting requires workarounds and research. I try to convert everything to graphs. There are a lot of commands that they say work in graphs but are not there yet. They are not functioning as expected. So, we have to try a workaround. It takes a little bit more research.

I have been using it for about four years.

It is becoming increasingly stable as time progresses.

Its scalability is impressive, aided by Microsoft's efforts to expand its data centers. It is growing so fast. It is growing faster that they could build the buildings and stuff them full of computers.

Our experience with Microsoft support has been good, despite occasional challenges caused by unexpected deprecations.

Positive

Prior to Entra ID, there were different systems such as Intune and Azure portal. Entra ID was integrated as part of the natural progression.

We are in the process of moving completely to the cloud. We are satisfied with the cloud and going all in. The process has been up and down because things are changing so fast. That is just the nature of IT. I have been in this for 30 to 40 years.

I implemented the system myself, gaining information from Microsoft documentation. At the school, I handled implementation without a reseller.

I have been at this job only a year. I was in the public school district. In the public school district, we had it for three years, and the return on investment was not requiring as many people to monitor and track intrusions. It reduced the need for hands-on monitoring and intrusion tracking, minimizing personnel requirements. We were not watching firewall logs and traffic the way we used to all day long. There has been about a 20% decrease in people required.

I just now started looking at it. Our CIO and CFO have brought us into the fold to show us what we are spending. From a pricing standpoint, with all the services that we get, we are okay. I do not see a problem with the pricing structure. We are getting our money's worth.

Microsoft Entra ID deserves a ten out of ten rating.

My job is to manage APIs on the enterprise end. We use Entra ID to limit contact with the end of the portal as much as possible. We have a lot of permissions that we don't want people to have, or we provide them with managed access. We also use Entra to manage application access. It tends to be blanket permissions, allowing an application total access.

Microsoft Entra ID drives our login and security perimeter, which is crucial for our organization. It has helped us implement multifactor authentication for most of our users despite the legacy systems in place. 

It is essential for supporting our aspiration towards a zero-trust model. It's driving our ambition to get serious about zero trust. We still have a lot of legacy systems that require support. 

Entra handles all the anti-phishing capabilities, and it's also helped us implement passwordless sign-in functionality. Now that we have MFA requirements and stuff like that, we're seeing identities flagged as risky because people are traveling. Sometimes people misuse credentials. It may not be malignant, but a group of people might share credentials. 

Delegated permissions and federated credentials are valuable features of Entra ID. We aim for a more secure environment by pushing for minimal use of static secrets. By utilizing delegated permissions, workflows can manage access, and federated credentials allow integration with platforms like GitHub and AWS. Entra ID drives our login and security perimeter, helping with multifactor authentication, despite the legacy systems.

Entra ID needs to improve its application credentials and use of ID permissions. There are challenges with the management layer. We want to create access down to the Graph level while invoking some management logic. That also means that if an application comes in, we cannot send that to the Graph because we would need an ID on behalf of the cloud hook. 

We have to switch contexts and do a lot of custom security checking. Does this application have permission to change these objects? If it does, then we can use our CNC powered by NMC. It botches our entire audit log so we can return to our service log and correct it rather than have it all in the old cloud. That's annoying. 

We also hit a problem with the federated credentials. Every hour, it exchanges a set of credentials from another IDP. For example, if I have a token from GitHub, I can exchange that for an application identity in NFT, which is awesome when you're doing GitHub workflows. However, because we have more than one tenant, we might need to access resources from one tenant to another. 

We do managed identities and federate to get a token and then assume an identity in the other tenant with that token. But for some reason, Microsoft has excluded all of their own IDP endpoints. Everything else is good to go, but if you come with a Microsoft token, you cannot use it. 

I have been using Microsoft Entra ID for the last two to three years.

I've had no issues with Entra ID. The portal could be slow now and then, but we don't have problems with the platform itself.

We have not observed any major scalability issues. However, when dealing with tens of thousands of objects, it requires proper management and best practices to retrieve only necessary data.

We rarely use customer service because we act as tech support. The few cases we have raised received decent support. 

Positive

We previously used Active Directory. While we haven't fully transitioned, we still source users from Active Directory but draw identities into Microsoft EntraID.

The decision to switch was made before I joined the team, so I'm not in a position to discuss ROI specifically. However, Microsoft EntraID is an integral part of our operations.

We face pricing challenges with newer licenses, as newer features often require them. This results in additional expenses for accessing new functionalities.

I rate Microsoft Entra ID seven out of 10. While it's an excellent standard for user sign-in, its open application model and security limitations lower my rating.

My main use case for Microsoft Entra ID is identity, and my organization performs many migrations, such as Office 365 migrations. This involves establishing an identity in the cloud, securing the identity with multi-factor authentication, and then onboarding it with SSO apps.

My favorite feature about Microsoft Entra ID is passwordless authentication because it makes the process easy.

The impact of Microsoft Entra ID on my company is significant because we are an MSP that resells IT services, and it serves as the foundation for all of our services, including single sign-on to all of our apps and to the customer's apps.

In the next generation of Microsoft Entra ID, I would appreciate improvements to consolidations for M&A activities. We perform many M&A migrations, and it would be beneficial to transfer identities from different tenants. While Microsoft has streamlined Exchange and SharePoint data, it would be helpful to have the ability to move identities between tenants if possible.

I have been using Microsoft Entra ID since it started, approximately eight years ago.

I have experienced some stability and reliability issues with Microsoft Entra ID, as there was recently a major outage that affected everyone. However, overall it has been quite solid.

I have used customer service for Microsoft Entra ID at some point. Although we have premier support and open cases, we are at the mercy of Microsoft. Customer service has been inconsistent for us, and we usually have to escalate issues. We typically resolve the problem before Microsoft can respond to us, so the service has not been very useful. We pay significant money for our support and do not receive a good return on investment.

Neutral

I have seen a return on investment from having Microsoft Entra ID.

My experience with the pricing, setup cost, and licensing of Microsoft Entra ID includes different tiers: Plan 1, Plan 2, and the Entra suite. I am quite familiar with these options.

I did not consider another product before selecting Microsoft Entra ID because it is the industry leader. We already use Microsoft products, so standardizing on Microsoft Entra ID was the logical choice.

Since implementing Microsoft Entra ID, I see more visibility in identity-related security incidents.

The integration capabilities of Microsoft Entra ID influence my Zero Trust model as it serves as the foundation for identity security.

I would rate this product 10 out of 10.

My main use cases for Microsoft Entra ID are to log in to Azure and also to log in our apps to Azure.

The feature of managing the users in Microsoft Entra ID is what I like the most.

The implementation of Microsoft Entra ID has made my secure access to apps or resources in my environment more seamless.

The integration capabilities of Microsoft Entra ID have influenced my zero-trust model by providing more granularity or control in the access that we are giving to users.

Microsoft Entra ID has benefited my organization through better management of the users and then more seamless connectivity.

I haven't thought of any specific improvements or additional features that should be included in the next release of Microsoft Entra ID.

I have been using Microsoft Entra ID for two years.

I am not sure how to assess the stability and reliability of Microsoft Entra ID as I haven't experienced any downtime, crashes, or performance issues.

Microsoft Entra ID scales well with my growing needs because the management of users is essential for our company as we are growing.

I don't really have any experience to rate customer service and technical support in Microsoft Entra ID.

I didn't have direct experience with the technical support of Microsoft Entra ID.

Positive

Prior to adopting Microsoft Entra ID, I think we didn't have Microsoft Entra ID and were mainly using password-based systems, for example.

I don't have direct experience with deploying Microsoft Entra ID.

I have seen a return on investment with Microsoft Entra ID.

I am not able to share any data points or examples of the return on investment.

I have no visibility on the pricing, setup cost, and licensing of Microsoft Entra ID.

I have no idea what other solutions were considered before selecting Microsoft Entra ID.

Since implementing Microsoft Entra ID, I have observed not much change in the frequency and nature of identity-related security incidents in the organization.

My organization's approach to defending against token theft from nation-state attacks has changed since implementing Microsoft Entra ID.

I haven't noticed any incidents at all related to token theft.

The implementation of the device-bound passkeys in Microsoft Authenticator has affected my organization's approach to phishing resistance by adding more steps in the authentication, which has helped in improving the security of our applications.

I am not sure if we have expanded usage of Microsoft Entra ID.

I would rate Microsoft Entra ID an eight based on some experiences, such as asking for repetitive connectivity and on the confirmation or verification, but I think the rest are good.

The advice I would give to an organization considering Microsoft Entra ID is that it depends on the organization's need; if they are growing and they need more governance, then they should have Microsoft Entra ID. I would rate this product an eight out of ten overall.