Review Summary
See a synthesized overview of the key takeaways from verified reviews of Microsoft Entra ID.
See a synthesized overview of the key takeaways from verified reviews of Microsoft Entra ID.
Microsoft enables digital transformation for the era of an intelligent cloud and an intelligent edge. Its mission is to empower every person and every organization on the planet to achieve more. Microsoft is dedicated to advancing human and organizational achievement. Microsoft Security helps protect people and data against cyberthreats to give peace of mind.
Do You Manage Peer Insights at Microsoft?
Access Vendor Portal to update and manage your profile.
I like the clear documentation provided online, helpful advice about pre-requisites for setting anything up, and the default configurations. Plenty of information available via Microsoft community and partners when configuration issues or help to address specific use cases come up. Servicing - checking on accounts and logs, and Reporting using dashboards, and email notifications is generally full of useful information, and very easy to take action on if needed.
Multifactor Authentication Strengths with Conditional Access helps improve security for certain applications. The ease of SAML and OIDC implementation. Access controls with conditional access and entitlements help restrict and secure much of the service.
What I like most is how naturally it fits into the Microsoft ecosystem. Since we were already using M365, a lot of things worked out of the box, which reduced the initial setup effort. Features like Single-Sign-On and conditional access policies have been particularly useful. They allow us to control access based on user roles, devices, or locations without making the user experience overly complicated. It also simplified the onboarding and offboarding processes, which used to be so much more manual.
Session management is still not set right as default. Its too easy for attackers to steal authenticated tokens using Aitm methods, and replay session tokens and compromise accounts. The availability of entra id, and certain applications such as exchange, mean it is more exposed to brute force attempts and password sprays than local ad only accounts. Logs are very numerous for background actions when servicing an account - lead to a lot of logs. Sometimes its not clear from these logs who the subject and target account is. Logs from EntraId can be hard to parse and understand for analysts involved in incident detection and response. Especially SSPR actions produce a lot of individual logs, and the auditlogs table in Azure for a lot of Entra ID actions put a large amount of details within single column like additionalDetails, that then need to be parsed out to be useful for queries / auditing.
There is no way to delegate admin consent for users to specific groups, so we are forced to keep it as admin consent only. There are no customizable error or access denied pages; generic deny pages are confusing to users, so users are generally allowed into the application at the level providing the correct error. Group membership limitations should be flagged and exposed to users with large groups and what applications they will not be able to access. The users and application admins are unaware of this until after implementation and then a few users hit the error which is an empty claim. Nothing is exposed without a major effort to expose it is group memberships. This leads to this service not having a true Enterprise group management implementation. Sign-In log queries are slow and sometimes unresponsive.
One challenge is that some features and configurations are not always easy to understand at the beginning. Especially conditional access policies can become complex, and it takes some time to fully understand how the different rules interact. Also, certain advanced features are tied to specific licensing tiers, which can make planning a bit confusing if you don't fully understand the model upfront.