JumpCloud® delivers a unified open directory platform used to securely manage identities, devices, and access across an organization. With JumpCloud, IT teams and MSPs enable users to work securely from anywhere and manage their Windows, Apple, Linux, and Android devices from a single platform.
$11
per month per user
Microsoft Entra ID
Score 8.9 out of 10
N/A
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
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.
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 …
We integrate with all the other identity providers. For me, as a consultant and engineer, it's very important to embrace the modern features and functionalities being made available in 2026, especially when it comes to platform SSO. And I've been working with Microsoft on that …
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 …
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 is far superior in terms of integrations, user interface, automation, and connectivity. Additionally, Okta offers better support and availability, and a more robust solution across every capacity Entra competes in. Okta simply works, whereas Microsoft Entra has a large …
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 …
JumpCloud is least suited in situations where you have few devices, but lots of users. JumpCloud heavily focuses on the "One-User-One-Device" type of use, and does lack some of the features things like Active Directory is better suited for when having multiple users accessing one machine. Their Powershell APIs are fantastic and getting only more powerful. Lots of features are hidden behind these APIs, so admins not as familiar with Powershell would have more issues leveraging these tools. BYOD deployments are amazing, especially for macOS devices that are using Apple Business Manager and can leverage Zero Touch deployments. It is especially good at handling mixed systems, whereas other options, such as Jamf, are really suiting only for macOS, or Intune is more suited for Windows; JumpCloud managed to handle both systems well.
That one is tough. It's just easy to integrate the sign-on portion with other products from other companies. Like BluePoint or Podint. It's very easy to integrate the user information with others. Using Android ID to register an application with other companies' applications.
Should be well-suited for a SaaS business organisation as they have a lot of internal applications and need a role-based authentication system between the various teams, improving security and audit log system to account for any breaches. It integrates well with internal applications such as Salesforce and Oracle. Best when need of SSO.
User Management - The ability to control our users and set password/polices is made easy in the JC console
Device Management - Using JC each user is assigned to their own device with only the rights to do their job - When elevated rights are required, this is done simply via the JC console for the period of time required
SSO - Using JC's SAML SSO integrations we are building out our SSO offering and this is making for a much simpler daily user experience
The first thing is that it's a really good platform to make a whole inventory of your hardware and software that you already have in the organization. It's very simple. It's very easy to look at what you have in the whole organization. And after that, start applying, for instance, some policies, some solutions in terms of zero trust access using MFA as a second form of authentication. So, these are the ways we use the MTIV platform.
SSO via OpenID - Opening up their SSO from just SAML to including OpenID (OAuth) would allow us to make more use of the service and to also incorporate it into some internal testing suites
Time Limited User Elevation - The ability to time limit a users elevation of privileges would be a great addition
Extending device management to include LPA - Least Privilege Access is becoming a bigger ask from our external auditors - Being able to do this via JC would be amazing
There is one thing that we lost since we migrated from Active Directory and it is the user expiration date. If I have an external that I know will work for six months, I have to manually check or put some kind of reminder. I cannot set an expiration date in Microsoft Entra ID. I still don't know why.
I do have to reset my password quite frequently. However, I don't think there is really a way to improve this, as it's a good security measure.
It makes me re-sign in a couple of times a day, sometimes if I haven't used my laptop for a couple of hours, and sometimes just randomly throughout the day.
It doesn't remember my devices, either my laptop or phone. so it always calls that out.
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
It's simple. I like how JumpCloud keeps things simple. Similar to Apple's ecosystem, they give you what you want with some extra features and bells and whistles but it doesn't take a large instruction manual to use it. They have the support system and KB articles to back up their product and learn about a feature and how to implement it
It's not complex. It works as configured, right? There's a lot of granular rules, and it'll get very specific if you need it to. But for many of our security capabilities, especially for mid-market enterprises, I think you can get all the capabilities you typically need with OnStar.
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 rarely contacted support. When I have, the responses were within expected time frames, and easy to access. Community support is incredible, both from the JumpCloud representatives, and the user base community at large. The support pages on the website also are typically very well written and strike a nice balance between having the technical information needed, and also being easy to understand for the small business types that might not have as much of a technical background as an IT Admin.
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
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.
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.
Okta is far superior in terms of integrations, user interface, automation, and connectivity. Additionally, Okta offers better support and availability, and a more robust solution across every capacity Entra competes in. Okta simply works, whereas Microsoft Entra has a large overhead that is difficult to use when configuring things.
Some features would make more sense for us to be bundled by machine, instead of the user. We have fewer machines, and multiple users log into one machine, so doing something like paying per user for services like Patch Management are difficult to warrant the cost. I also feel a more complete package that includes common addon features; Patch Management and Password Manager, would be an improvement. It would also be nice if we could change packages, addons, and other billing services via self-service instead of reaching out to our account manager.
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.
Definitely, I can consider this one a positive because, as I mentioned earlier, it's a tool that can help our internal ID team track end users' activities in their sign-in logs and a lot of other things, which is really good and helpful for us.
Increased user productivity - not fighting with IT all the time!
Though there could be a bit more on the 'lost/broken phone' front, the self-service eliminates time that would typically be spent waiting for IT support/admins.
An Okta account under a certain domain allows proper access from the get-go, and under certain apps (such as our HRIS), adding members is easy.
Improved security - deactivating Okta removes all account access across multiple platforms instantly for leavers.