Try our new research platform with insights from 80,000+ expert users

Microsoft Purview Privileged Access Management vs Okta Workforce Identity comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Purview Privilege...
Ranking in Privileged Access Management (PAM)
15th
Average Rating
8.8
Reviews Sentiment
7.4
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Okta Workforce Identity
Ranking in Privileged Access Management (PAM)
7th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
67
Ranking in other categories
Single Sign-On (SSO) (2nd), Authentication Systems (6th), Identity and Access Management as a Service (IDaaS) (IAMaaS) (3rd), Access Management (4th), ZTNA as a Service (11th)
 

Mindshare comparison

As of July 2025, in the Privileged Access Management (PAM) category, the mindshare of Microsoft Purview Privileged Access Management is 2.0%, up from 1.5% compared to the previous year. The mindshare of Okta Workforce Identity is 2.7%, up from 2.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Privileged Access Management (PAM)
 

Featured Reviews

Mayeen Uddin - PeerSpot reviewer
Security features have increased satisfaction while implementation is seamless
I use Microsoft Purview Privileged Access Management primarily for Outlook, Microsoft Word, and Excel Microsoft Purview Privileged Access Management is easy to understand, particularly its menu. I am satisfied with its security features provided through Microsoft Security. However, my company…
Tor Nordhagen - PeerSpot reviewer
Extremely easy to work with, simple to set up, and reasonably priced
The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it. We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve. The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The integration with Azure Identity is a significant advantage, as it allows for seamless automation and power app integration."
"The integration with other Microsoft solutions is a standout feature of Microsoft Purview Privileged Access Management."
"Microsoft Purview Privileged Access Management is easy to understand, particularly its menu."
"Microsoft Purview Privileged Access Management is easy to understand, particularly its menu."
"The ability to provide just-in-time privileged access and set specific parameters for access duration is highly beneficial."
"The integration with Azure Identity is a significant advantage, as it allows for seamless automation and power app integration."
"The solution can scale very well."
"The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day."
"A solution that's easy to use, stable, and reliable."
"Other than Okta being an easy and awesome integration tool, one of the best features it has is the provisioning and deprovisioning, which makes management way easier. You don't need to be too technical to understand how it works."
"The tool provides a single place of contact for managing users. We only need to manage users in Okta Workforce Identity, eliminating the need to duplicate efforts across different systems. For example, if a user needs to be decommissioned, we don't have to go through all the systems and cloud services; we delete the user in one place. This process is automated with our HR system for both organizations, simplifying user lifecycle management."
"We find the solution to be stable."
"The most valuable feature of Okta is its security."
"I find the provisioning features and the integration with other applications useful."
 

Cons

"Microsoft Purview Privileged Access Management has made progress in providing insights into generative AI tools being used within organizations, but customers need to further track where sensitive information is being used within AI tooling."
"Sometimes, its functions, like XLOOKUP in Microsoft Excel, do not find situations properly, especially without the use of pivot tables."
"There's room for improvement in Microsoft's documentation, as it often lacks clarity."
"I do not see any financial benefit after implementing Microsoft Purview Privileged Access Management, however, this question would be better answered by my manager."
"Microsoft Purview Privileged Access Management could improve integration with multiple cloud environments."
"Microsoft Purview Privileged Access Management could improve integration with multiple cloud environments."
"We had some implementation issues."
"SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service."
"The lifecycle management part can be improved. It should also have identity governance and the ability to choose a specific factor authentication at the application level. Its licensing and pricing can also be improved."
"We faced some challenges during the Okta Identity Workforce deployment. Integrating with AWS and other cloud services posed some limitations with federated options. For instance, features like automatic user addition from AWS to the tool were missing, requiring manual intervention. The API is limited compared to the manual configuration possible through the UI."
"The integration with third-party tools needs to be improved."
"In some setup cases, there are issues with attributes not going in properly."
"You can't hide the device when you're checking logs."
"Okta Workforce Identity could improve provisioning it can be made simpler."
 

Pricing and Cost Advice

Information not available
"The pricing for Okta Workforce Identity could still be improved or made cheaper. It costs from 50 to 100 euros a year per user. Okta Workforce Identity has different packages you can choose from, and my previous company had all of them, particularly the full Okta suite."
"It has a yearly subscription. As compared to its competitors, it is quite expensive. It also has a complex licensing model."
"Workforce Identity is well-priced."
"The licensing model is fine for general service usage. However, the charges for API features and API tokens can be quite high."
"The price of Okta Workforce Identity is competitively priced. We pay annually for the use of the solution."
"The pricing is reasonable."
"This solution is costly. Pricing is decent if you have less users, but it significantly goes up the more users you have, with its cost not justified."
"License is around US$20,000 annually."
report
Use our free recommendation engine to learn which Privileged Access Management (PAM) solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
12%
Manufacturing Company
10%
Healthcare Company
9%
Computer Software Company
15%
Financial Services Firm
11%
Manufacturing Company
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Microsoft Purview Privileged Access Management?
The ability to provide just-in-time privileged access and set specific parameters for access duration is highly beneficial.
What needs improvement with Microsoft Purview Privileged Access Management?
Regarding improvements for Microsoft Purview Privileged Access Management, there are still some challenges. Purview contains numerous predefined sensitive information types, which sometimes makes i...
What is your primary use case for Microsoft Purview Privileged Access Management?
We are a company offering solutions to other customers, and Microsoft Purview Privileged Access Management provides great helping features and solutions. It is not the only thing needed to prevent ...
What do you like most about Okta Workforce Identity?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are ...
What is your experience regarding pricing and costs for Okta Workforce Identity?
Pricing for Okta is reasonably not that much, however, I don't have access to the commercial aspect.
What needs improvement with Okta Workforce Identity?
I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.
 

Also Known As

Microsoft Privileged Access Management (PAM)
No data available
 

Overview

 

Sample Customers

Information Not Available
FedEx, Zoom, Takeda, Lululemon Athletica, GrunHub, jetBlue, McKensson, Bain & Company, Engie, Peloton, Sonos, T-Mobile, Hewlett Packard, MGM Resorts, Ally Financial, Priceline, Albertsons, Itercom, Classy, FICO, Kensho, Live Nation, Drata, Rotary, and others.
Find out what your peers are saying about Microsoft Purview Privileged Access Management vs. Okta Workforce Identity and other solutions. Updated: June 2025.
860,592 professionals have used our research since 2012.