Microsoft Entra ID Review
Updated July 22, 2025

Microsoft Entra ID Review

Luca Piccirillo | TrustRadius Reviewer
Score 8 out of 10
Vetted Review

Overall Satisfaction with Microsoft Entra ID

Basically we integrated every device users in the directory and of course we exploit enterprise application wherever. We don't use user related accounts where they're not either. We only implement security application models and the same we do for our customer. Since we are a seller of this product, we instruct the customer how to do proper integration of the identities into directories. And our products are, some are based on ND as a component.

Pros

  • I really appreciate the hard integration with the Azure products, but also possibilities to integrate Feder identities from other parties and the management of external identities and manage identities and application identities. I can see something better at the moment.

Cons

  • The main problem I see is about, let's say documentation, but it's not a problem of documentation itself. It's a problem of the product makes so much things that for beginners it's hard to decide which is the right way to use the problem.
  • I think 20% of the customer basically accepted to OPT for our solution and our manager solution because they are already Microsoft customers, but they don't know how to use the licenses they acquired. So if they were not Microsoft customer, probably they couldn't afford our solution.
We only have identities on the cloud because we opted for a cloud only solution, which we think is the future and we actually actively work with our customer to migrate them to cloud only identity setups.
Yes
We actually connect to Android id many other party application both from the market let's say, because our customer also acquires other solution on the market and hopefully they support of any and other SSO compliant options of course, but we also integrate SSO capabilities with our own products, our own dashboard when we sell and it's part of our manager solution to get the customer application integrated into ID in order for them to use the solution for.
It's quite messy when you change names quite often and it's hard to explain the customers what are the right components over time because name changes are not by most of them and it's quite confusing for people when they need to learn how to manage.
We adopted both the endpoint security platforms and of course the cloud security platform. So when we sell Iku for our products, we also sell the licenses both for defender, for endpoint, and of course Microsoft 365 Premier. And we work for integrating the security model of the customer up on some of Microsoft products with our own partner. So the value of course it's in the integration that, so if you don't integrate them all, you're probably missing the most valuable model.

Do you think Microsoft Entra ID delivers good value for the price?

Yes

Are you happy with Microsoft Entra ID's feature set?

Yes

Did Microsoft Entra ID live up to sales and marketing promises?

Yes

Did implementation of Microsoft Entra ID go as expected?

Yes

Would you buy Microsoft Entra ID again?

Yes

I think it's well fitted also for small businesses, but in order to let them leverage it like they should, you need a partner of course. So it can scale very well from dimension, but you need a partner for the smallest. The biggest customers have no issues at all.

Microsoft Entra ID Feature Ratings

ID-Management Access Control
Not Rated
ID Management Single-Sign On (SSO)
Not Rated
Multi-Factor Authentication
Not Rated
Password Management
Not Rated
Account Provisioning and De-provisioning
Not Rated
ID Management Workflow Automation
Not Rated
ID Risk Management
Not Rated

Using Microsoft Entra ID

7 - Developers who need to setup new applications for Entra ID login into our products and other tasks related to Azure.
Customer Helpdesk who help our customers in everyday tasks about user administration, SSO setup for customer applications and side activities about adopting Security Defaults.
Security Analysts who work for our customers auditing incidents about stolen identities.
System Administrators who uses Entra ID functionality to protect our own environments with features like Conditional Access.

2 - Those people are engineers who knows how digital identity management works. Another part of the team is in charge of supporting Entra ID for our customers through our products. There is a gap between common knowledge about what Entra ID is and what Entra ID can actually do for companies. Our work is to to fill that gap for companies of any size bringing "hidden" functionalities up to their understandable knowledge.
  • Managing identities related to Azure
  • Managing multi-tenant login to our own SaaS app for customers
  • Used as a base identity platform for some of our security products
  • Protect internal identities by adopting passwordless methodology
  • We are now using logs from Entra ID as part of our feed to provide security insights about customer cybesecurity posture which also takes into account other proprietary on-premises components.
  • No idea, we are probably squeezing all the juice from this platform as we van without involving legacy or backward-looking connectors like AD Sync or ADFS.
  • We are already looking at Security Copilot as a tool to extract even more from Entra ID.
Quite impossible, even customers relying on other cloud platforms will always end up having Entra ID as main or federated identity management platform. Switching to another one would imply loosing some feature someone could be unaware of. People who knows what Entra ID does would hardly shift to another solution after an accurate comparison.

Comments

More Reviews of Microsoft Entra ID