We are an authorised reseller partner
Managing Director at a computer software company with 1-10 employees
A simple and perfect solution that has good integration with various platforms and 99.9% uptime
Pros and Cons
- "Its simplicity and its integration with various vendor-agnostic platforms are the most valuable features."
- "It can have more API integrations."
What is our primary use case?
What is most valuable?
Its simplicity and integration with various vendor-agnostic platforms are the most valuable features.
What needs improvement?
API Securities Solution
For how long have I used the solution?
I have been engaged with Okta for more than 2 years, have seen the latest version.
Buyer's Guide
Okta Platform
January 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
882,207 professionals have used our research since 2012.
What do I think about the stability of the solution?
It is highly stable. They claim 99.9% uptime. We never came accross downtime and performance issues
What do I think about the scalability of the solution?
Okta is not only a single sign-on platform but also Life cycle management, the core of the Identity Management platform. Okta access gateway can publish on-premise legacy applications to the cloud.
How are customer service and support?
They are very good. The Okta system engineers involved in presales engagement have sound knowledge on Okta platforms and IAM in general. What I have noticed personally is that Okta provides them with extensive training before assigning them to the Job. It helps them in understanding the technology well before starting with the job.
How was the initial setup?
Its initial setup is straight forward. Okta tenant creation can be done quickly. Adding users and applications to the okta platform has customer dependabilities. Integration and going live with O365 also takes a little bit more time than other apps because of internal rollout and user training. It is not an Okta problem but needs customer Microsoft teams active involvement
What about the implementation team?
Okta Service Partner
What other advice do I have?
I would recommend a phase-wise approach and not doing everything in one step. You can start with the basics of single sign-on and MFA and then proceed to life cycle management. I would also recommend starting with the lest critical applications and then add critical ones to the SSO platform. It is a journey, and we need to start small and slowly migrate it. Adaptive MFA provides proactive defence against login and credential abuse.
I would rate Okta Workforce Identity a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Chief Technology Officer at a tech services company with 1-10 employees
Easy to implement and manage, and the cost benefits are valuable
Pros and Cons
- "The most valuable features are ease of operation and visibility."
- "The integration with third-party tools needs to be improved."
What is our primary use case?
We are a solution provider and Okta is one of the products that we implement for our clients. I am a solution architect and help to design the system.
Most of our clients have a hybrid architecture where they want to use a single sign-on. They have some applications on-premises, whereas others are on the public cloud. This means that they have a two-tier or three-tier architecture.
How has it helped my organization?
Our clients are happy because prior to implementation, they had a very distributed architecture. Okta has allowed them to consolidate with respect to identity management, which increases their operational efficiency.
This product has the features that every customer is looking for.
What is most valuable?
The most valuable features are ease of operation and visibility.
This product is easy to deploy and easy to manage.
There are cost benefits to using this solution.
What needs improvement?
The integration with third-party tools needs to be improved. Mainly, the open-source APIs for Splunk would be helpful, as that is where they aggregate most of the data. If this process can be streamlined then it will definitely help.
For how long have I used the solution?
I have been working with Okta for the past three years.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
This solution is scalable. Our clients are large, Fortune 500 businesses.
How are customer service and technical support?
Okta has very good support and I would score them high, at nine out of ten. I am definitely happy with them.
Which solution did I use previously and why did I switch?
Prior to working with Okta, our clients had native solutions.
How was the initial setup?
The initial setup is straightforward.
We currently have one customer deployed on AWS and another on Azure.
What about the implementation team?
I am the solution architect and our in-house team does the implementation.
Which other solutions did I evaluate?
As part of the process, our clients did a couple of POCs. Symantec was one of them, Okta was another, and there was a third product that they evaluated. During this process, they had success criteria defined, and Okta did well with most of it.
The metrics included the operation and cost benefits, the business value, and the support.
What other advice do I have?
Every customer has a different need and a different requirement. For anybody who is considering this product, I think they should do a pilot POC to make sure that it works well in their environment.
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer. Integrator
Buyer's Guide
Okta Platform
January 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
882,207 professionals have used our research since 2012.
Information Technology Consultant at a tech services company with 1-10 employees
Provides the security that we were looking at and a number of options for multifactor authentication
Pros and Cons
- "The MFA part is the best. MFA provided most of the security that we were looking at with respect to the second level of authentication. Okta Workforce Identity provides a number of options with respect to multifactor authentication, such as the app, phone call, and text. These options provide different ways of logging in for users, and they were a lot more than what we needed. This is certainly a very good feature of Okta Workforce Identity."
- "They also have single sign-on (SSO). When we bought Okta Workforce Identity a year and a half ago, I was also looking at SSO, but not much documentation was available for SSO. The documentation for SSO should be a little more robust for somebody who is implementing it for the first time."
What is our primary use case?
We mostly use it for MFA for logging into our Windows RDS environment and a web-based application called Tableau. We are using the latest version.
What is most valuable?
The MFA part is the best. MFA provided most of the security that we were looking at with respect to the second level of authentication. Okta Workforce Identity provides a number of options with respect to multifactor authentication, such as the app, phone call, and text. These options provide different ways of logging in for users, and they were a lot more than what we needed. This is certainly a very good feature of Okta Workforce Identity.
What needs improvement?
They also have single sign-on (SSO). When we bought Okta Workforce Identity a year and a half ago, I was also looking at SSO, but not much documentation was available for SSO. The documentation for SSO should be a little more robust for somebody who is implementing it for the first time.
For how long have I used the solution?
I have been using Okta Workforce Identity for almost one and a half years.
What do I think about the stability of the solution?
It is stable. I never faced any issues with its stability.
What do I think about the scalability of the solution?
I have not scaled it much. The company for which we implemented this solution is into data mining or data analytics. They had multiple users. Most of the users were data scientists. I was the only one looking at it in terms of management.
How are customer service and technical support?
There were a couple of occasions where I needed some support while setting it up for our RDS environment. Their technical support was educated enough with respect to the product. They were able to help us out and resolve the issue pretty quickly. I would say they are good on the support part.
How was the initial setup?
Setting up the MFA for Windows RDS was very straightforward. Using it with Tableau was not very straightforward. It was a bit complex, but the documentation was handy enough to set it up.
What's my experience with pricing, setup cost, and licensing?
I believe it competes well. The pricing is pretty competitive. I know that Microsoft also provides something similar with its MFA and identity services.
What other advice do I have?
It has been sufficient for our needs. I haven't seen any issues, so I would say it is a good product. If there was anything, the users would have complained, but I haven't received any complaints with respect to Okta Workforce Identity from the users.
I would rate Okta Workforce Identity a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Managing Director at a tech services company with 1-10 employees
Good product with ease of deployment, ease of use, speed of delivery, and easy integration with other software
Pros and Cons
- "The ease of deployment, ease of use, and speed of delivery is what I like about Okta Workforce Identity. It is very easy to use. For a lot of software, you need to be trained extensively and have a very technical background. Okta Workforce Identity is quite simple. You can integrate any software into Okta. They've got a network of 7,000 applications that easily integrate into it."
- "It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free. Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it."
What is our primary use case?
It has got a big network of apps that easily integrate into it, making deployments a lot faster than traditional identity platforms. So, the use case will be companies that are looking to be on a cloud journey for cloud adoption strategies. It also suits companies that have on-premise applications and would like to make them web-based, essentially, access them on one portal. Thus, allowing companies to ensure that they can pretty easily manage access to these applications by their users.
What is most valuable?
The ease of deployment, ease of use, and speed of delivery is what I like about Okta Workforce Identity.
It is very easy to use. For a lot of software, you need to be trained extensively and have a very technical background. Okta Workforce Identity is quite simple.
You can integrate any software into Okta. They've got a network of 7,000 applications that easily integrate into it.
What needs improvement?
It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free.
Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it.
For how long have I used the solution?
I have been using this solution for the last two years.
What do I think about the stability of the solution?
They're really great stability-wise. The last year they've had like 99.9% uptime. They're really good for SLAs and things like that.
What do I think about the scalability of the solution?
Scalability is probably one of its best attributes.
How are customer service and technical support?
They're pretty good. I know they're a big organization, and they have a lot of clients. So, it's a place where they're always looking to improve, but from my side, it's been really good.
How was the initial setup?
It's pretty straightforward. If you need it, you get great support from Okta as well.
They provide a lot of datasheet information and step-by-step ways to deploy the solution. They're doing really well on this front.
What about the implementation team?
For deployment, right now, it's me and one more person. If we need any additional support, we get it locally in South Africa from a distributor who has a technical team skilled in Okta. Whenever I need more support, I go to them or directly to Okta, or the client can pay yearly fees for additional support if they need it.
What's my experience with pricing, setup cost, and licensing?
It could be a bit too pricey for small companies. Okta Workforce Identity can add a lot of benefits, but smaller companies may not have a lot of applications that need to be managed by Okta Workforce Identity. In larger organizations, there are more departments, applications, and users to manage. Okta Workforce Identity adds a bit more value to those bigger organizations.
In addition to standard licensing fees, there are also additional costs for things like additional support and so on.
What other advice do I have?
Okta Workforce Identity can be suitable for smaller companies, whereas Okta Workforce Identity is suitable for a bit bigger companies, but they serve different purposes.
Essentially, Okta Workforce Identity is for medium and large companies. I would say for companies with at least 50 users, but then these companies should really see the value in Okta Workforce Identity. I guess when you start talking about 200 employees upwards, that's where Okta Workforce Identity really starts creating a lot of value.
Okta has recently created a business value assessment. Those who are starting the process and looking into Okta must be open-minded to the value assessment with the Okta team or with the person at the company that is selling the solution to them. Just be patient, see the value, and not be so caught up in thinking that Microsoft is a great product. I think Okta is way better.
I would, a hundred percent, recommend Okta than Microsoft. Essentially, Microsoft wants you to stay within their stack, whereas Okta is neutral. You can integrate any software into Okta or any application, whereas Microsoft takes a bit longer, or they may not support the integration and so forth.
I would rate Okta Workforce Identity a nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Microsoft Azure Engineer at a computer software company with 201-500 employees
Straightforward to set up, good technical support, and the pass-through authentication is very useful
Pros and Cons
- "There is no password hash saved on the cloud, which is the part that I like the most."
- "I would like to see the provisioning simplified."
What is our primary use case?
We are using this solution for access management and user provisioning. We are also using it for user and group synchronization and as a password for authentication.
What is most valuable?
The pass-through authentication is very useful. You don't have to set up another ADFS. Instead, you can just authenticate your resources for services from the cloud to AD on-premises through the pass-through authentication. There is no password hash saved on the cloud, which is the part that I like the most.
The functioning of Azure AD Connect for both user and group synchronization is very smooth.
What needs improvement?
I would like to see the provisioning simplified. When it comes to certain tasks, such as where it is activated on-premises, Azure AD is simpler than Okta.
SSO functionality needs better client support.
For how long have I used the solution?
I have been working with Okta Customer Identity for two years.
What do I think about the stability of the solution?
We have had no issues with respect to stability.
What do I think about the scalability of the solution?
The scalability is good.
How are customer service and technical support?
I have been in touch with the technical support from Okta and they are very good. They answered my questions quickly and supported me very well.
How was the initial setup?
The initial setup is straightforward.
What about the implementation team?
Once we started, we received help from the Microsoft team and it was really good. We were able to complete the installation easily.
What other advice do I have?
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Manager- IT Operations at a tech company with 1,001-5,000 employees
Single portal to access and manage applications
What is our primary use case?
Intergated on-prem and cloud applications on multi-tier domains and user identity accessing applications hosted on cross domains. Full fleged automation using AD and Okta groups for app assignment.
Lifecycle Management of apps on our Okta tenant.
How has it helped my organization?
- Central administration of Apps
- Auto activation of user accounts/ Just-In Time Provisioning
- Global App availability
- Less or No Administration required
What is most valuable?
1. Active Directory Sync, as its useful for pre-assigning apps, can also be used for de-provisioning apps for exiting users
2. Shared apps with common password can now be managed centrally without revealing the credentials
3. User and Apps Management
4. Desktop Single Sign On
5. Auto-provisioning
6. Flexibility to integrate In-house applications
7. Password Self Service
8. Support non-domain users
9. Group based app assignment (okta, AD, pushgroup)
10. Adaptive MFA
11. Workflow for app requests
What needs improvement?
Command line access
Reporting
For how long have I used the solution?
Since 2015
What do I think about the stability of the solution?
It's very stable we have 99.999% uptime on the base
What do I think about the scalability of the solution?
Very high and secure, we have more than 170+ apps secured for sso
How are customer service and technical support?
Customer Service:
9 out of 10
Technical Support:
9 out of 10
Which solution did I use previously and why did I switch?
Yes, we had previously used a different solution which was replaced by Okta. Non-scalability was the major drawback of our previous solution.
How was the initial setup?
Initial setup is straightforward, simple and easy to manage
What about the implementation team?
Some apps needed assistance from Okta support team.
What's my experience with pricing, setup cost, and licensing?
Setup is simple if you are an AD admin, cost comparison is nominal compared secured access
What other advice do I have?
KB article from Okta is very detailed just spend some time on the okta
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Security Architect South Europe at a tech services company with 10,001+ employees
Good access management that includes passwordless biometric support
Pros and Cons
- "The most valuable feature of this solution for most customers is access management."
- "This solution would be improved by adding biometrics features."
What is our primary use case?
The primary use case of this solution is for access management, multi-integration, and passwordless access.
What is most valuable?
The most valuable feature of this solution for most customers is access management.
There are also some different views on Biometrics.
What needs improvement?
This solution would be improved by adding more biometrics features. One example is Cyberside Biometrics.
The technical support is good but needs to improve in their response time.
In the next release, I would like to see biometrics, multi-factor authentication, and to rely more on the mobile or something different on CyberSide.
For how long have I used the solution?
I have been using this solution for one year.
What do I think about the scalability of the solution?
Normally we deploy it on public Cloud, so it should be scalable.
I have been told that it's quite easy to integrate on Cloud. The scalability then depends on the third-party Cloud provider.
Our latest customers have over two hundred thousand users in a medium-sized company.
How are customer service and technical support?
The technical support is good but not very responsive regarding my needs in getting details. They are difficult to reach and to get them involved.
How was the initial setup?
I was not a part of the initial setup, but the feedback that I received was that the initial setup was quite straightforward.
What about the implementation team?
Normally we do the implementation ourselves. We are one of the largest integrators worldwide.
What other advice do I have?
My advice to others is to be aware of their current infrastructure.
The integration points have to be very clear to the customer to facilitate the main integration. Otherwise, it makes things very complex.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner.
Very good one-factor authentication, good integration capabilities, and very good stability
Pros and Cons
- "The most valuable aspects of the solution are the integration with external websites one-factor authentication."
- "The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based."
What is our primary use case?
We primarily use the solution to access cloud solutions and VDI.
What is most valuable?
The most valuable aspects of the solution are the integration with external websites one-factor authentication.
What needs improvement?
The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based.
For how long have I used the solution?
I've been familiar with the solution for two years.
What do I think about the stability of the solution?
The stability of the solution is fine.
How are customer service and technical support?
I've never contacted technical support. I've only ever used web pages to assist me with questions, and that has been enough.
Which solution did I use previously and why did I switch?
We previously used Workspace One Access Solutions from VMware. In fact, we're using it as well as Okta, so we never really switched.
How was the initial setup?
The initial setup is almost completely straightforward. The identity action is complex, so it makes it just a bit difficult.
What about the implementation team?
Customers should use an integrator to help assist in the initial setup.
What other advice do I have?
This solution is very good. Okta is, in my opinion, one of the leaders at the moment on the Polish market. However, there is some limited usability because of the requirements.
We use the cloud deployment model.
I'd rate the solution nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Okta Platform Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
Identity and Access Management as a Service (IDaaS) (IAMaaS) Single Sign-On (SSO) Authentication Systems Privileged Access Management (PAM) Access Management ZTNA as a Service Customer Identity and Access Management (CIAM) AI IT SupportPopular Comparisons
Microsoft Entra ID
Prisma Access by Palo Alto Networks
CyberArk Privileged Access Manager
SailPoint Identity Security Cloud
Omada Identity
Zscaler Zero Trust Exchange Platform
Cloudflare One
Workspace ONE UEM
Cato SASE Cloud Platform
Saviynt Identity Cloud
Check Point Harmony SASE (formerly Perimeter 81)
Fortinet FortiAuthenticator
Cisco Duo
Ping Identity Platform
Google Cloud Identity
Buyer's Guide
Download our free Okta Platform Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which IDaaS solution do you prefer and why?
- Looking for an Identity and Access Management product for an energy and utility organization
- Is SSO safe?
- Which is the best Privileged Account Management solution?
- What are your best practices for Identity and Access Management (IAM) in the Cloud?
- Why is identity and access management (IAM) so important in preventing data breaches?
- What access management tools would you recommend to help with GDPR compliance?
- How to convince a client that Identity and Access Management (IdAM) is essential for risk elimination?
- How is Zero Trust different from the Least Privileged model?
- What are the differences between LDAP and Active Directory?

















