Okta Platform Reviews

My use case for Okta Platform is that we mostly use it for SSO for the applications we have integrated with Okta. We primarily use SSO for user authentication, and user management is not particularly involved, but we are importing users from Active Directory to Okta.

I assess the role of Universal Directory as a single source of truth for our user identities by stating that there is an application called Workday, and from Workday to SailPoint, Okta Platform will be the target system for SailPoint. When a user joins the organization, aggregation runs from HRMS to SailPoint, which is responsible for creating the birthright application, with AD being one of those. Once the user is created in AD, import jobs will run based on the mapping we did with AD and Okta Platform, and the user will be created in Okta Platform.

The best features of Okta Platform include the import feature, which allows for new employees joining the organization to have their AD account created, and when this import runs from AD to Okta Platform, this employee will be created in Okta Platform. This feature represents automation between Okta Platform and AD.

Apart from these features, I appreciate that there are password policies and authentication policies or network zones we can configure in Okta Platform. If we want to restrict the users from logging in from specific network zones or blacklisted ones, we can configure those.

The context-aware policies of adaptive MFA influence my authentication process because we can enable more MFA based on client requirements. Okta Platform is one of the MFA tools available, alongside others such as RSA, and based on the requirements, we can enable those and apply the policy accordingly.

The positive impact I have seen from using Okta Platform is that it makes it easier for new joiners to get birthright access and have users added based on department or employee type. We implement rules and policies, such as when a user joins the sales department; we can configure the group rule, and the user will automatically be tagged to that specific group. This represents an automated process with Okta Platform, rather than doing it manually.

The automated lifecycle management helps with the efficiency of onboarding and offboarding by ensuring that once a user joins the organization, they come into HRMS. From there, it goes to AD, and the target will be Okta Platform. Birthright access and applications are provisioned based on conditions. For offboarding, if an event is triggered, such as leaver or termination, values will be populated in AD, and once the import runs, Okta Platform will terminate the user, disabling access and removing whatever accesses the user had.

In Okta Platform, I do not see much room for improvement because currently, they are managing automations and the new workflow, which helps with automation. Previously, this was not available in Okta Platform, but it was introduced recently.

The automation aspect can be improved.

I have been using Okta Platform for three and a half years.

The stability of Okta Platform, I would say, is an eight because it is growing day by day. Previously, it had static features without automation, but currently, it is moving towards automation and introduced workflows.

I would consider the scalability of Okta Platform to be a six.

The scalability rating of six is due to factors that come with the tenant and the specific elements around that, which I am not entirely sure about.

My relationship with the vendor is as a customer and partner. When we have issues with Okta Platform, we reach out to their support team, and they take care of the issues we encounter.

We do not go through AWS, GCP, or Azure for Okta Platform; instead, we usually access the Okta Platform support portal to raise our concerns, and the team reaches out to us to resolve those issues, sometimes scheduling meetings as needed.

Before using Okta Platform, I did not really use any other software, but I did consider Entra ID, which is most probably similar to Okta Platform. However, Okta Platform has a user-friendly interface and is easy to use.

The integration aspects include that the capabilities come with modern protocols, making it easier for integration with various protocols and target systems.

Integration capabilities of Okta Platform enable faster deployment, as they support modern protocols such as IDP and SSO.

I have not used Okta Platform AI, but I need to check on its automated threat response features.

Regarding pricing for Okta Platform, I am not aware of how much it costs because I used to work as a consultant for them, and the licensing details are taken care of by the sales team or others.

The solution requires little maintenance, and I would say it is easier to maintain compared to other IM platforms such as SailPoint, which had huge coding and infrastructure costs.

My advice to others looking to implement Okta Platform is to definitely go for the software instead of Entra ID, as it offers a much easier and user-friendly UI.

I use Okta Platform for single sign-on and managing the authentication process. I have used all of the geofencing features for security purposes. In the current field of cybersecurity, I have been working for seven years specifically.

My favorite aspect of Okta Platform is that it is really user-friendly. The admin configuration UI is user-friendly when you view it.

I have worked on Okta Platform's IGA features, and they were not great or up to the mark. While they were trying to get new features, it was not working as expected at that time when it was in beta. There are some features, especially on the customization side, that cannot be customized, and there are a few things that would be nice to customize as well.

I would like Okta Platform to protect non-human identities in the environment, such as service accounts.

In terms of industry or regulatory requirements, it depends on the person implementing Okta Platform. All necessary protocols need to be followed, but I don't think Okta Platform has set any templates to ensure these protocols are being followed. It would be a nice-to-have feature where they could set some templates and provide guidance on what can be implemented.

I have been working with Okta Platform for five to six years overall.

Okta Platform is stable with very few instability issues.

Okta Platform is 100% scalable.

I have had to contact technical support for Okta Platform many times.

The speed and quality of their answers depend on the nature of the issue. Sometimes it was an easy fix, and sometimes I had to do a lot of back and forth. Speed is good initially, but depending on the problem nature, it becomes a little stagnant. However, I have no complaints as I think they have been super helpful. Even if they are not able to help, it goes to another team member, but they generally try to help.

I would give the support for Okta Platform a score of seven out of ten.

I have used alternatives to Okta Platform.

I was definitely there for the initial deployment of Okta Platform, and I would rate it as medium.

A team is required for Okta Platform. I don't believe we should be dependent on one person, and there should be people from many different teams involved. Even if there is not a lot of work, in all of my projects, Okta Platform has indicated that we need people. In one or two instances, Okta Platform professionals were not there to help, but I highly recommend someone from Okta to be there to guide us through the whole process.

Okta Platform requires maintenance on my end as a customer. It is 100% the customer's responsibility to maintain all features. Even if someone is going out of the company, there needs to be deactivation, so everything needs to be maintained by customers of Okta Platform. With respect to features and patches, sometimes they release a few patches that we will have to update ourselves, but in other cases, they try to do some silent pushes. However, it totally depends on how Okta Platform chooses to do it.

Overall, regarding the pricing of Okta Platform, I think it is a little expensive.

The biggest differences that come to mind are that, positively, Okta Platform is more user-friendly, but negatively, Okta Platform is way more expensive than a few other products in the market.

I have used Ontra, Ontra ID, PingID, SiteMinder, SailPoint, and Saviant, which are not exactly competitors to Okta Platform but somewhat similar.

How long it took to finish projects with Okta Platform from start to finish depends on multiple factors. I have done many projects with Okta Platform, starting from overnight to even a week, so it depends on the customer as well, on what is being implemented, and what the go-live date is for the particular time. The deployment depends on a client-to-client basis. My overall review rating for Okta Platform is eight out of ten.

I have been using Okta Workforce Identity for single sign-on purposes to identify and authenticate my identity and access resources at AWS. Whenever I want to connect to Amazon Web Services, I provide a particular CLI Okta command, which opens a window where I am redirected to Okta Workforce Identity's single sign-on page. I authenticate myself through mobile, and once that authentication is completed, I am able to access a particular account according to the role that I have configured in the CLI command.

The best features that Okta Workforce Identity offers are single sign-on, multi-factor authentication, and privileged access management. It has reduced the time required for authentication and provided a secured way of accessing the Amazon web console.

The user interface could be enhanced to allow direct number selection for multi-factor authentication instead of typing out information.

I have been using Okta Workforce Identity for two years.

I used Ping, but I find Okta to be more reliable with a great user interface.

Time saved is a great example of return on investment. It has saved approximately 50 to 80 percent of our time.

The pricing and licensing setup is typical, and since it follows a per-user, per-month subscription model, it is helpful.

One of my team members lost his phone and was unable to do a direct Okta Workforce Identity login. At that time, email multi-factor authentication was useful and helped him to get logged into Okta Workforce Identity and authenticate himself. I do not see any areas for improvement as Okta Workforce Identity is at its best level currently. Okta Workforce Identity is reliable, and its user experience and user interface are great. I would recommend Okta Workforce Identity to others. My overall experience using Okta Workforce Identity has been excellent. I have given this review a rating of ten out of ten.

Most of what I appreciate about Okta Platform are the no-code features that I have found excellent, as you have a very low requirement to code. Even if a new teammate comes in and tries to get familiar with it, after some basic training, they will be able to perform some minimal tasks that are repeated processes for us. It is quite easy to learn from my perspective if you have basic IAM knowledge. If you understand the concept, a new person can come in and get up to speed very quickly. You don't have to do very extensive training as you might have to do for some other tools to handle advanced tasks. With five to six months of experience, we can put a person on policy creations.

For me, learning to use Okta Platform was quite easy because I have been in this space for around seven-plus years. I had previous knowledge of ForgeRock and SailPoint, so it was easy for me to transition to Okta Platform because I had knowledge of the concepts.

The major problem we face with Okta Platform is pricing because most of our clientele move away from Okta Platform because of the pricing. If someone is looking for on-premises solutions, they usually don't choose Okta Platform.

They predominantly try to go for Ping rather than Okta Platform because Ping provides a very wide variety of concepts and tools and details their tool on a very specific level, particularly their on-premises tools. Anyone who invests has to pay a higher price, and if with the same kind of structure they can get some other enterprise-grade tool that caters to all those things, they will definitely choose Ping rather than Okta Platform.

I have approximately three to four years of experience working with Okta Platform, from the time I started working and even before that.

The only issue I faced was once at the start. I have worked with around 50,000 users. Right now, the recent client has more than that, but on average, around 50,000 in a typical scenario. I have never seen drops in Okta Platform systems.

I have contacted technical support or customer support multiple times, but not through standard channels. We are a technical partner with Okta Platform, so we have a channel open all the time. I have been in contact with them for different types of RFPs, and even right now, I am still in communication with Okta Platform support.

I think the quality and speed of support for Okta Platform are among the best. The way they respond and the quickness in terms of when you raise an issue through technical channels such as creating a support ticket, they respond back within the SLA they have provided, which might depend on the kind of service the client has signed an MOU for. It can either be 24 hours or 48 hours based on severity. They do respond within that time, whichever they have agreed on.

I give them a score of eight because I have seen them respond in detail, and you usually don't have to follow up on that. Sometimes, with those kinds of detailed scenarios, there might be misinterpretation at the level where you misunderstand something in the question, and that follow-up can be tricky.

For me, the initial deployment of Okta Platform was already completed for most of the clients because you get built-in support from Okta Platform, so that is majorly the case. For the current client, the tool itself is not decided, so I have not worked on an Okta Platform deployment.

I am majorly on the development and implementation side. For Okta Platform, I have not seen much maintenance happening. There was only once I faced an issue, and that was at the start of my career, but I have never faced that kind of issue in Okta Platform since.

Pricing-wise, Okta Platform is higher compared to the other tools, and my current client actually moved away from Okta Platform because of that reason alone.

Right now, we don't have a tool selected on our client's side, and we are mostly targeting Ping because that caters to all their requirements, and the costing is lower than Okta Platform.

I think the score I give to Okta Platform overall will completely depend on the use cases each client has because it might vary. From my personal opinion, I would rate it around eight because I think there are many things Okta Platform has that are best in terms of IAM solutions. However, there are still many things that other platforms are doing that are missing in Okta Platform. From my perspective, Okta Platform is currently trying to move towards IGA as well, but there are still some areas for improvement. 

Okta Platform is essentially the gateway for everything we do. We have the Okta app on our phones and computers, and it is the only way we can access any of our interfaces on a day-to-day basis, including work messaging on Slack or any of our apps. We go through Okta FastPass to gain access. Every 60 days, I have to reset that on my phone by logging out of everything, doing Face ID, and verifying my credentials before I can log back in and keep everything secure. Additionally, we have to update our password every 180 days or so. I basically start my day every morning with Okta identification or verification.

Okta Platform helps to secure access to cloud infrastructure, APIs, containerized workloads, and AI generative AI services. It pairs well with some of the AI tools we use. I even have a verification method for ChatGPT and Glean, which is another AI interface. Okta Platform essentially applies to anything I use on a day-to-day basis. I do not get any pop-ups throughout my day, which indicates that it is securing the interface or network I am using or even just the application.

Okta Platform protects our benefits and payments app through Workday, so it definitely protects my benefits, my pay information, and any type of personally identifiable information such as first name, last name, and Social Security number.

Ease of use is what I value most about Okta Platform. It is not difficult to learn or navigate. Once you have a username and password, you can have your computer memorize it. On my phone, I use Face ID so that I am not having to type in my password every single time, but it does make things very secure. If I ever were to leave my laptop anywhere by accident and not be able to recover it that same day, I would be able to trust that it would block anybody from getting access to anything because that is something you have to log into every day. Ease of use and the ability to trust the product are what I value most.

Okta Platform does not recognize when I have already verified myself once on my HubSpot login across multiple tabs. I have to verify myself for every single tab. If there were a way to recognize that I already verified myself on that URL or domain and just give me access to the rest of the tabs instead of having to click one by one, that would be an improvement.

Okta Platform does not recognize when I have already verified myself once on my HubSpot login across multiple tabs. I have to verify myself for every single tab. If there were a way to recognize that I already verified myself on that URL or domain and just give me access to the rest of the tabs instead of having to click one by one, that would be an improvement.

I have been using Okta Platform for at least five years.

Okta Platform does not lag. The only thing that might happen every once in a while is that I will click Okta FastPass, it will spin, I will click submit, and then nothing will happen. I just have to refresh my tab and then do it again. However, that happens pretty infrequently.

Okta Platform definitely supports our whole company, which is not small at all. It is good to know that it can support both smaller and larger teams.

I have not had to contact Okta's technical support or customer support, which is probably a good thing.

Negative

I have used Cloudflare in the past. I know it is not really a direct competitor, but that is maybe the only thing else that I would mention.

I did not do the initial deployment, but when I was first brought on, I had to go through the whole setup of everything to tie to my email address and all my information to be a verified user on the account for Okta Platform through HubSpot. It was pretty easy. I had to set it up on my phone, download the app, and scan the QR code. It was pretty simple on both my laptop as well as my phone.

Okta Platform does not protect non-human identities in my environments.

My customers approach me to integrate with Okta Platform. I have configured multiple AWS accounts to Okta Platform.

My usual use case for Okta Platform is to onboard AWS accounts into Okta Platform and add the users AD groups into Okta Platform and add those AD groups to integrate with the AWS account, which is my job.

I find the most useful feature of Okta Platform is that it allows the preconfiguration of multiple applications, eliminating the need for customized application onboarding, which is very helpful for me to configure multiple applications such as AWS, Azure, Zoom, Salesforce, and more than 1000 applications in Okta Platform dashboard.

Okta Platform has had a lot of positive impacts on my organization. For example, it is very difficult to disable user access in multiple places, but once we implement Okta Platform, we just need to disable it at the AD level, and the rest gets taken care of by Okta Platform.

A couple of things need to be improved at Okta Platform level. In AWS, we are using tag-based policies to enforce the RABC, but when trying to configure tags in Okta Platform level, we are not able to configure them.

At Okta Platform level, we have not yet configured the machine-to-machine configuration. It is very difficult for me to create the API accounts to enforce. For example, when we generate temporary credentials in AWS, it is challenging to use Okta Platform level because there are no features to create CLI-based temporary credentials.

I would like to improve the tagging on Okta Platform. For every identity, we need to create a tag. Instead of hard coding in AWS, we use tag-based authentication, allowing access based on tags associated with resources.

From my perspective, everything is good on Okta Platform except for the tags that need to be improved.

I have been using Okta Platform for three years.

The stability of Okta Platform is good. We have not faced any major issues or outages in the last couple of months.

Because we are using the cloud for Okta Platform, it is automatically scalable. There is no need to inquire about scalability since it scales as required.

I do not often communicate with the technical support of Okta Platform.

I have never communicated with the technical support of Okta Platform.

Before Okta Platform, we used Entra ID or Azure AD for similar use cases.

The decision to stop using Azure AD and start with Entra ID is not my call, as management decides. From my perspective, technically, Okta Platform is very user-friendly for application onboarding, whereas Entra ID is a bit more challenging for onboarding applications.

I went straight with Okta Platform and did not consider anything else.

I did not evaluate other options besides Okta Platform.

I am not sure about the GenAI aspect, but Okta Platform is very helpful for integrating the identity center and allows us to create multiple individual accounts using the IAM or at the organization level using the identity center.

I am in the healthcare industry, but I am not sure how Okta Platform helps address specific industry or regulatory requirements.

I do not know about the regulatory environments of the healthcare industry regarding Okta Platform because I am not managing health standards or other governance standards.

I have not noticed any measurable security or operational improvements in my cloud-based workloads since implementing Okta Platform, but I find it very helpful to utilize MFA or UBIKeys or other security keys to enforce the login mechanism.

I do not know the pricing details of Okta Platform because I am not the appropriate person to discuss pricing matters. The purchasing department will take care of those.

We are providing identity access management to the customers with Okta Customer Identity, and then application integration, user onboarding, and related functions.

I'm a senior consultant using Okta Customer Identity.

We are the implementers of Okta Customer Identity as users.

The most valuable feature of Okta Customer Identity is the application interface with SSO. Integration with SSO helps us make use of the credentials. Once we log in, we get the opportunity to explore many applications within the organization with the same login, with no need to log in again.

Adaptive authentication in Okta Customer Identity is a flexible feature that is very secure and user-friendly. The authentication is more complex for man-in-the-middle attacks while remaining useful for end users.

Okta Customer Identity's API gives a clear view of how user onboarding takes place, so we can easily configure with Postman. We can onboard and off-board users, which is very flexible through the APIs.

Regarding multi-factor authentication, it helps reduce unauthorized access in our organization. We are using passwordless authentication with Okta FastPass on mobile devices. Users can get authenticated with two-factor authentication, first entering the password, then directly using the second factor authentication with Okta FastPass.

It is complex when adding it for the first time to users of Okta Customer Identity. For end-users and new users, it can be complex to use.

Okta Customer Identity analytics and reporting tools do not help much to improve customer engagement strategies.

Training should be provided to novice users. There are multiple online learning resources in the Okta documentation part, which users can access free of charge.

I have been working with Okta Customer Identity for six years.

There are no doubts regarding the stability of Okta Customer Identity. It is scalable and we can directly make use of this tool.

The solution is scalable.

The setup for Okta Customer Identity is straightforward.

The price of Okta Customer Identity is acceptable.

For those planning to use Okta Customer Identity, MSA and SSO are among the best features that can be recommended for users. We also have direct integration with Active Directory. There are many features that will be helpful for organizations to easily integrate applications and manage user onboarding and off-boarding.

The solution is deployed on the cloud and I did not purchase it through AWS Marketplace. I usually buy for the entire organization.

I rate Okta Customer Identity 10 out of 10.

I usually used Okta Platform for managing user identities and ensuring secure access to our applications.

Okta Platform helped me secure access to cloud infrastructure, APIs, containerized workloads, and AI/GenAI services in my architecture, enhancing our security posture significantly.

Okta Platform protected non-human identities in my environment, such as service accounts and machine-to-machine access.

The features or capabilities of Okta Platform that I have found the most valuable include its single sign-on and multi-factor authentication.

The positive impact and benefits I have seen from using Okta Platform involve enhanced security and streamlined user access.

Specific industry and regulatory requirements that Okta Platform helped me address in my cloud environment were critical for compliance.

Since implementing Okta Platform, I have noticed measurable security and operational improvements in my cloud-based workloads.

Okta Platform could be improved or enhanced by adding more integration options for third-party applications.

I have been working with Okta Platform for a considerable time now, which has provided me with great insights into its functionalities.

Okta Platform's stability and reliability are impressive, which is crucial for our operations.

My experience with the technical support of Okta Platform and their customer service was positive, as they were responsive to my inquiries.

I would rate the technical support from one to ten as an eight, appreciating their effectiveness though there is always room for improvement.

I changed the previous solution and decided to switch from Adaxes to something else because we needed more robust features, and with large companies offering solutions such as Okta Platform, it became inevitable.

I participated in the initial setup of Okta Platform, which allowed me to understand its configuration better.

I found everything straightforward during the initial setup; however, I did encounter some challenges with integration.

I have experienced a notable ROI from Okta Platform, which has justified our investment in it.

I last engaged with Okta Platform around this time of the year.

I was a customer of Okta Platform and found the solution to meet our requirements effectively.

The last time I used Okta Platform was relatively recently, and it still remains quite effective for our needs.

I did not participate in the decision-making process for Okta Platform purchasing, as that was handled by our procurement team.

I would rate this review an eight out of ten.

The main differences between Okta Platform and Cisco for the IAM solution are that Okta Platform does not have an exclusive product that is tagged federal, and it depends on the person who is deciding it. The way I made Okta Platform comparable with Duo Federal is by attaching it to CAC, which is used by the military.

In my opinion, Okta Platform's best features include federation, which is very important, especially when you work with different systems. SAML plays an important role, and then there is the OAuth feature of Okta Platform and the OpenID. Those three—SAML, OAuth, and OpenID—are crucial. The scope, which is essentially the permission that you give to a token, and then the token that is being used by the application or by your user to authenticate themselves, is also important.

Automated lifecycle management positively impacts onboarding and offboarding processes for Okta Platform in terms of efficiency. When you integrate with Workday, ServiceNow, ITSM, and HR, those integrations make the onboarding process quite smooth. Whether the application involves a new employee, a joiner, or a leaver, those integrations handle all of those scenarios.

Some areas for improvement with Okta Platform, especially concerning AI and the federal aspect, are acknowledged as areas that Okta Platform needs to work on to offer features comparable to those provided by Duo.

In terms of Okta Platform's stability or scalability, I would grade its stability at around seven. Okta Platform is quite stable compared with Oracle. It is scalable compared with Oracle as well, but that is where the effort will come in. When you are doing basic things, it is straightforward, but if you are going to be doing workflows, other things, or recon and trust, then there is effort involved, and that is where it gets convoluted.

On a scale of one to ten, I would rate Okta Platform's support or customer service as around seven. With Duo, I was not directly involved because there is a group that handles it. I am a contractor, so my account does not have the privilege to open a ticket. I document it and pass it to a group, which is most likely the help desk. They are the ones who create the ticket and interface with Duo. If there is a need for collaboration, that is where I come in, and they introduce me to Duo, saying that they want me to collaborate on this particular design.

Positive

My experience with deploying Okta Platform shows that it is not that difficult to deploy, but the integration is challenging. The integration, the tweaking, the configuration, and the tailoring require significant effort.

Compared to Cisco, deploying Okta Platform is a little bit harder. Cisco Duo is quite straightforward.

Regarding costs, I think Okta Platform is more expensive compared to Cisco, but it is less expensive when compared with Oracle.

The reason we recently switched to Okta Platform was a decision made while I was not on the project, as I was with the Air Force at the time. The decision was made by a different branch, I think with the Marines, who were using it and then said that Oracle is obsolete. It was presented as a short message: 'We are using Okta Platform and it works well.' They then asked me to investigate and see how we could use Okta Platform integrated with Oracle.

The improvements I already mentioned are based on the fact that IAMs are evolving, and integration with other components is important. My experience with Okta Platform's integrated PAM capabilities involves many steps. There are many steps, and you have to do this, but as long as the document is fine at the start, it is a trial and error process. If it works or not, then you are going to repeat the whole thing and try a different scenario. The project management does not always see the effort behind all of this tweaking Okta Platform to do what they want it to do and meet their business requirements. I would rate this review a seven overall.

My job title at FNTS is Senior Security Analyst.

I have been using Okta Platform for three years.

My main use case for Okta Platform is multifactor authentication.

For multifactor authentication in my organization, to log into specific sites, we need Okta Platform as a multifactor authentication to get in.

The process has made logging in easier and more secure for me and my team.

The best features Okta Platform offers are easy SSO, strong security, and improved productivity.

Out of easy SSO, strong security, and improved productivity, the single sign-on has had the biggest impact for my team because it protects effectively and signs on without problems.

Okta Platform has positively impacted my organization with easy single sign-on, as we need single sign-on multifactor authentication for various things and Okta Platform is very secure.

I have definitely noticed specific outcomes such as fewer help desk tickets, as it is very straightforward, streamlined, and easy to use.

I think the setup in the beginning can be a bit of a learning curve.

I have been working in my current field for seven years.

Okta Platform is stable.

Okta Platform's scalability is good.

The customer support is good.

I would rate the customer support on a scale of 1 to 10 as a nine.

Positive

We previously used Duo and switched because we thought Okta Platform had better features.

I think the setup cost was pretty good, but the pricing is moderate.

I am not sure about Okta Integration Network's capability to enable faster deployments, as I have not used it in that capacity and I have not deployed it.

I would assess the role of Universal Directory as a single source of truth for user identities in my organization as it works effectively.

I cannot describe the impact of automated lifecycle management on onboarding and offboarding processes in terms of efficiency.

I have not had any experience with Okta Platform's integrated Privileged Access Management, PAM capabilities, so I cannot compare them to using separate tools.

I have seen a return on investment, as there have been fewer employees needed for multifactor technical responses, and the number of people to assist with tickets has gone down since Okta Platform is a really easy system to use.

I think the setup cost was pretty good, but the pricing is moderate.

Before choosing Okta Platform, we evaluated other options, including Microsoft.

I would advise others looking into using Okta Platform to look very carefully at the pricing and move forward.

My company does not have a business relationship with this vendor other than being a customer.

I find this interview satisfactory and do not think anything needs to change for the future.

I would rate this review an overall eight out of ten.