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
Netwrix Threat Prevention
Score 8.2 out of 10
N/A
Netwrix Threat Prevention, formerly StealthINTERCEPT, is a real-time monitoring and blocking solution that helps organizations proactively stop identity-based and file system threats before they cause damage.
N/A
Okta
Score 8.9 out of 10
N/A
Okta is an enterprise grade identity management service, built in the cloud. IT can manage access across any application, person or device. Whether the people are employees, partners or customers or whether the applications are in the cloud, on premises or on a mobile device, Okta helps IT become more secure and maintain compliance. The Okta service provides directory services, single sign-on, authentication, provisioning, workflow, and built in reporting. ment systems.
$2
Per User Per Month
Pricing
Microsoft Entra ID
Netwrix Threat Prevention
Okta
Editions & Modules
Premium P1
$6.00
per user/per month
Premium P2
$9.00
per user/per month
No answers on this topic
Single Sign on
$2.00
Per User Per Month
Multi Factor Authentication
$3.00
Per User Per Month
Single Sign on Adaptive
$5.00
Per User Per Month
Multi Factor Authentication Adaptive
$6.00
Per User Per Month
Offerings
Pricing Offerings
Microsoft Entra ID
Netwrix Threat Prevention
Okta
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
Yes
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Browse products and price points that make the most sense for your organization on the Okta website.
We looked at Okta. There was another Sammo product. Okta was one of the big-name ones and I forget the other smaller one off end. It's a little less robust, but that's not necessarily a bad thing because it just needs to work and it does that.
Previously we had worked with Okta, which was kind of using our replacement for active directory server, and I know that has integrations, but we ended up just going with Entra ID just for the ease of access and without having to stack on an additional third party application …
We're a Microsoft Native shop, so we're looking at Okta's identity tool, SailPoint and a few other competitors of Venture id. And we decided to go with this one because we're already using Active Directory, so just using the native Microsoft Suites kind of just they integrate …
We use DUO as another IDP solution and we also evaluated Okta as a solution. We didn't have a choice to be honest, because Microsoft products, you can't get away with it, but it's built in and a bunch of other providers have it as authentication, so it's great.
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 …
Microsoft Entra ID offers the same or very similar services to the other products but in a package that is familiar and recognizable to everyone. It enjoys better community support and world-class security and reliability.
Because we use a lot of other Microsoft products, so my inclination is more towards Entra ID because it's a Microsoft system. And we'll find support for Microsoft more than any other software. So that's why I lean more towards Microsoft.
Our company ecosystem is microsoft based and using Microsoft Entra ID is very easy, The integration is much easier for microsoft environment as compared to other.
Selecting Microsoft Entra ID is a good choice over Okta if you already utilize parts of the Microsoft Suite. It is a solid competitor and if your business is already paying for Microsoft products, why not use it? Okta is a great competitor, but simply already using Microsoft …
Okta may be somewhat more advanced in terms of function, but the cost to do so, and the added complexity in choosing that path make it an easy decision for us to stay with Microsoft. Other than Okta, Microsoft functionality is very strong against all other contenders.
Microsoft seems to be the better service for cloud identity syncing and is still a leader in this realm. Their service is reliable, and we use it with all of our clients. Compared to Okta, the cost is more affordable and they include a lot of services in the Microsoft licensing …
I was not part of the research or decision-making (evaluation) of Okta vs Entra ID. In fact, we are currently utilizing both products at this time, so I'm not quite sure you really need to select one over the other. Having so many companies and differences between them, …
Okta has no chance to compete with Microsoft Entra ID's features. Also the usability of microsoft products and user management is easier when you have one product that does almost everything.
We previously looked at Azure AD (now known as Microsoft Entra ID) for our IDP (Identity Provider). Okta has an interface that seems easier to navigate and configure than that of Entra ID. Additionally, the wide range of vendors/software that Okta supports made it an easy …
We have used Azure Entra ID which sometimes lacks compatibility with new SAAS apps and also not so easy to manage user access provisioning and deprovisioning like Okta. Also I believe managing sign-on policies are easy in Okta as comparison to Azure AD.
Okta provides a better user experience and a portal to make things simple not only for the admins but also the customers. Compared to Entra and Duo Okta is light years ahead in innovation and user experience.
At the time when we moved from ADFS to Okta, Okta was the superior product for are use case. There was no ADFS/SAML connection available for for Citrix Cloud. Now, Entra ID has progressed and is supported by almost every application, we might be moving back to Entra ID.
I had the opportunity to use Citrix but it was an "heavy" tool. I prefer Okta here. Regarding MS Active Directory I think is a good too with good features and not hard to use.
With respective to user interface and license cost, we thought The Okta Identity Cloud was better than other tools for use. Their customization of license was another reason for us to go with The Okta Identity Cloud over other tools.
Okta was the most expensive choise between than, but still our best bet. This was caused because they were able to integrate with 90% of our software without any headache and 10% with some studies - this work would be higher and requires more working hours from our engineers if …
While I wasn't involved in the official purchasing process of Okta, I would imagine that the scalability that Okta provides and usability would be a big differentiator in whether you were to utilize Okta over Azure AD for SSO purposes across a your user base.
Azure AD had better developer library support and documentation, but we weren't with Okta because it had more flexibility in how user tokens for OIDC could be generated. At the time, a few years ago (2017), Azure only allowed so many AD groups into the token but Okta didn't …
Okta is the best out of its competitors due to its ease of use, out of the box functionality, and opportunities for customization. It is a good company to work with and strives to be there for its customers. Administration is a breeze and the documentation is quite extensive.
Our main points of consideration in choosing an identity provider were simplicity of integration into our existing enterprise application suite and cost. Okta Identity Cloud proved to be on par with other contenders in the field in terms of integration capability, and was more …
Okta is more flexible, easier to use, and continuously gets better. The organization listens well to its users, and enhances the product frequently with what the users are looking for.
Siteminder---It is an on-premise application which is difficult to integrate with cloud-based applications. As Okta is a cloud application we can integrate both on-premise and cloud applications. Ping--It doesn't provide the applications templates which [are] provided by Okta. …
This is subjective to your own experience, but I do find Okta is far simpler to setup, connect with apps and use. Okta is the front runner in gartner for a reason, Microsoft is improving but [is] still complicated. When choosing apps for your business, consider the ease of use …
Okta has the best dashboard for navigation and is very end-user friendly. Easy to navigate and configure applications and SSO and a very effective way of managing end-user issues. SSO-wise it is the best product in terms of end-user experience; [it's a] seamless process for the …
It is especially good for organizations that are otherwise in the Microsoft ecosystem (Microsoft 365 applications). Microsoft Entra ID is really well supported sign-in method in various SaaS-applications and they often have step-by-step guides how to deploy the SSO with Microsoft Entra ID. It's less suitable for organizations that might use other productivity tools than M365 or do not have Windows-based computers.
If you have an environment where there is heavy changes being made to your AD, then this is a great tool to have. Now, if your environment is being managed by one person and has very little change activity, then I would stick with searching the windows log files.
It has extensive compatibility and rich feature set of integrating with a wide array of core systems and SaaS platforms. Daily I utilize Okta's user-friendly central hub to simplify access the numerous applications we utilize within my company (Google Workspace, Slack, Zoom, Salesforce, Microsoft Office 365, among many others.)
Single Sign-on helps ease the user experience, allowing users to avoid typing multiple passwords.
The identity and management are straightforward to use and easy to connect to other applications, as well as third-party applications.
The support of remote work. Nowadays, many people work from home and need to access their accounts. Microsoft Enterprise ID gives secure access to the company data.
Probably the most primary thing is just the interface itself. It's frequently changing and so oftentimes we kind of have to go back and redocument our processes for our IT staff because the steps that they would take to perform a task one month. Now it's a totally different staff, new dashboard, even a new name for the product or the feature. So it would be nice if that stuff was a little bit more consistent.
I'm not sure it's really a room for improvement thing, but due to the granularity offered by Okta, sometimes it can be challenging to find exactly what you're looking for.
There was an instance in which we had issues getting SAML configured for an application. I feel this challenge was mostly user error (on our part) because we didn't realize the SAML instructions were SPECIFIC to each app integration and changed (codes) each time. We attempted to mirror the settings/configurations of an existing app (same app, but different domain). I think having a note somewhere that indicated that the instructions were unique to each integration would have saved us a bit of time. Again, I'm not sure this is really an issue with Okta though, more of a user learning curve thing.
Sometimes searching for things is a challenge (without the "Rockstar" add-in). For example, if you have a user group called "Okta_users_everyone", searching for "everyone" will not find it. You have to search for the beginning of the object name (not just any part of it). The ability to search partial or wildcard would greatly enhance search functionality.
MSFT Entra ID has been essential for managing our geographically dispersed team. We're confident that it will scale with us as grow, and we'll be able to take advantage of additional security and ID management features as they become necessary. Being able to centrally manage our user access from anywhere with a small support team is such a relief.
Okta has a passion to provide secure and scalable identity solution. Their passion has come across as advocacy in a way that has deepened my knowledge of the field of authentication. I took identity for granted before but after seeing features such as external authentication I know that Okta can enable my business to reach new heights
I mean it's pretty good. It is click, click. I mean, oftentimes I can go to the expert or layer two support to get help. Suddenly I go to them. So it has to be pretty useful to be honest. I do a lot of, and there's a lot of, you could do research quickly online to find out how to do certain things. I think that's the only thing we can improve to in terms of kind of a best practice path is setting up it. But because I'm it profess of tons of years in co-management services, I can figure it out. But for others they may not be able to figure it out. You still need an IT person of course to translate all of that. But to me pretty straightforward. I come from the days of directory from 2008, 2000, Microsoft server 2000.
The Okta Identity Cloud advertises 4 9's of reliability and I would go as far to say that it may even do better than that. As a true Global organization that operates in just about every region of the world, we have yet to have an issue with The Okta Identity Cloud that has impacted our business operations.
From my perspective, for the things that my group uses it for, Okta is very fast. It is as least as fast as the local password database methods that it replaces on our campus enterprise services. I do not believe that it slows anything down at all. In fact, not having to think too much about the login, because they all look the same, probably speeds things up somewhat.
I have not needed to engage support for anything at this time. I have been able to find the answers either online or in a knowledgebase. I tried to skip the question but it would not let me, so I rated a 9 based on other interactions with Microsoft support I have had
They are very knowledgeable and willing to assist with any issue that may occur. We have not had to call support very often because they make sure there is a subject matter expert in place before concluding the implementation.
We've had a few support cases over the years and every case has been handled by the Okta support team beautifully. We received clear answers to questions we had regarding setup and even were provided simple to follow guides on how to setup their product to use with custom applications.
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.
We've used other Microsoft products and we've also used some standalone products, like each application you can have its own identity, so we've looked at some of those too, but we try to use the Entra ID as much as possible because it offers a wider range of reliability.
Varonis did a good job compared to the same things that StealthIntercept does. When it comes to configuring the reports within StealthIntercept, the configuration portion is easier. However, the web console in Varonis looked better and is a bit easier to navigate.
With respective to user interface and license cost, we thought The Okta Identity Cloud was better than other tools for use. Their customization of license was another reason for us to go with The Okta Identity Cloud over other tools.
Being a cloud native application, The Okta Identity Cloud is extremely scalable and easy to setup. By integrating into existing directories and applications via standard techniques and protocols, it is very easy to both initially setup and add additional users as required. Once all the necessary integrations are setup, it's a simple rinse and repeat process to onboard additional users (which can be automated with imports as well)
Microsoft Professional Services' technical knowledge is appreciable as consultants design the solution as per customer requirements. Mapping of features per user specifications and assisting Customer IT engineers to implement so they can manage and administer the services.
I think it's had positive. It's enabled us to make authentication easier and more streamlined across the organization from frontline workers to back office workers.
It's allowed us to really adopt authentication policies and methods that suit that user and their work environment.