Microsoft Entra ID (formerly Microsoft Azure Active Directory or Azure AD) is a cloud-based identity and access management (IAM) solution supporting restricted access to applications with Azure Multi-Factor Authentication (MFA) built-in, single sign-on (SSO), B2B collaboration controls, self-service password, and integration with Microsoft productivity and cloud storage (Office 365, OneDrive, etc) as well as 3rd party services.
$6
per user/per month
Omada Identity Suite
Score 9.0 out of 10
N/A
Omada Identity Suite is the eponymous flagship toolset for identity and access management (IAM) from the relatively established Danish software company for access governance and compliance on the enterprise level.
For one, a significant factor for us is that it is integrated with HelloID, which gives us, as the IT department, a lot of time back because we don’t need to create user accounts manually. It is great for the roles we have defined, as they can be used repeatedly. A great feature is that guest accounts can be created for external users; we only need to be in a closed area of your domain.
Omada is with very good and user-friendly interface. There are various access management best practices available and recommended to choose and configure easily. The system works smoothly and is very reliable. The Omada product team is frequently enhancing it and listens to customer feedback. There are out of the box integration capabilities with the most popular systems on the market
It addresses the issue of identity management very well with respect to putting in that multi authentication.
It can also support with respect to we can push these policies into another product that is not Microsoft, but it needs that SSO so we can have one account going into multi different accounts. I think that's the biggest pros and the easy use of Microsoft 365 also is one of those pros also in terms of administration.
Well, I'm an active ad admin, so there's a lot of features in active directory that Entra ID seems to be just adding now. We're kind of figuring out that the policies are different than Entra ID that they were in active directory and we're finding other products to do that, like Azure policy. Some things I'm used to seeing in identity products or like active directory aren't in Entra iID, but are doing good job of managing stuff that it does so far.
In Omada there is no convenient way to track or monitor the progress and status of authorization requests that are raised by other users or even for mine.
There is no way to extend the validity of multiple Contractor/External user accounts by line manager and have to extend them one by one.
Without custom development there is no way to create parallel access approval workflows.
Entra ID is a vital part of our Identity management/administration. With the integrations it has to other Microsoft products, setup and configuration is a breeze. Additionally, Microsoft has been around a long time and have the resources to ensure this product is stable and secure for many years to come. We know it will evolve with time to provide us what we need as technology changes.
Very easily usable. It could be easier to use. Implementation was kind of tricky. We do run a hybrid environment, so we're syncing a local active directory instance with Entra ID, so that could be a little tricky. But outside of that, if you're not running a hybrid deployment or a version of Entra ID usually, it's pretty straightforward.
Omada is with very good and user-friendly interface. There are various access management best practices available and recommended to choose and configure easily. The system works smoothly and is very reliable. The Omada product team is frequently enhancing it and listens to customer feedback. There are out of the box integration capabilities with the most popular systems on the market
Microsoft has offered Azure Active Directory as a solution for a couple of decades now, so they have seen and anticipated almost any issue that an organization may face and can therefore help. The cloud offering of Azure Active Directory offers some additional "self healing" or monitoring services that can minimize the need for a service call. However, as with most large companies supporting a fast growing market, there may be some gaps in service knowledge (and particularly processing) from the front line / tier one staff as they follow a corporate script at first contact.
Make sure you use a good partner. Our implementation was a bit longer and more problematic than we expected. Our partner got it done, but, in my opinion, some of their inexperience and staffing issues were evident.
Microsoft Entra ID is not as stand-alone product as competitors like Okta. It may lack some of the features that competing products have but on the other hand it integrates both technically and license wise with other Microsoft cloud services and is easy to deploy. It is also the easiest way to extend identity management to the cloud if you already have Microsoft Active Directory in use.
Omada is providing the desired functionalities that meet our needs as a standard features. The only custom development that we have identified that is going to be needed is related to a very specific process that would require development with any other solution that we might go for. The product appears to be highly configurable and is more than we expected from such product. Standard functionality to maintain Business roles from the user interface and also to do a mass changes to business roles via CSV uploads.Integration with SAP GRC for SOD compliance.
I don't know if I can really quantify that. It's one of those products that just exists and so there's not a whole lot of changes that we need to make with the product. And so I guess in terms of value, what we get is we don't have to worry about the identity management piece. We know that that's taken care of.
