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

Microsoft Entra ID Governance vs Okta Workforce Identity comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 2, 2024

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 Entra ID Governance
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
15th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
9
Ranking in other categories
No ranking in other categories
Okta Workforce Identity
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
65
Ranking in other categories
Single Sign-On (SSO) (3rd), Authentication Systems (5th), Privileged Access Management (PAM) (6th), Access Management (2nd), ZTNA as a Service (10th)
 

Mindshare comparison

As of May 2025, in the Identity and Access Management as a Service (IDaaS) (IAMaaS) category, the mindshare of Microsoft Entra ID Governance is 1.5%, up from 0.2% compared to the previous year. The mindshare of Okta Workforce Identity is 13.1%, down from 13.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Identity and Access Management as a Service (IDaaS) (IAMaaS)
 

Featured Reviews

William Kox - PeerSpot reviewer
Great policies and timelines for streamlined compliance
There are some areas where improvements are necessary. Even though we have almost the full package, there are some bugs. I cannot directly perform some tasks from the portal. First, I have to go to the policy, change it, and then return to the package to add it. I cannot do it directly from the package. Workarounds are needed, so that can be improved. At the moment, that is the only issue we are facing that needs enhancement.
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 most valuable feature of Microsoft Entra ID Governance for identity management is multi-factor authentication."
"The solution gives me the capability to automatically move guest accounts from the tenant without any manual intervention."
"It is compliant with our RVRT and CSV guidelines."
"The most valuable feature of Microsoft Entra ID Governance is access reviews."
"The solution is fully scalable, supporting everything from small companies to large enterprises."
"The product's most valuable features are the robust audit trail capabilities."
"The platform's most valuable feature is the single sign-on service."
"The most valuable features are multifactor authentication and account creation for the Exchange environment in Office 365."
"It made things a lot easier, especially with passwords."
"The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day."
"It's reliable and it does what it is advertised to do."
"This solution has a lot of capabilities and features."
"The feature that is most valuable to me is the automated user provisioning that we set up using Okta as a major part of that process."
"One of the features that I have found to be very valuable is its interoperability and compatibility with all types of resources, whether it's networking, infrastructure, or applications. That is, it is compatible as well as interoperable, as far as the federated authentication is concerned."
"The solution's technical support is good."
"The solution can scale very well."
 

Cons

"Even though we have almost the full package, there are some bugs."
"Microsoft Entra ID Governance is relatively new, and some features require more development. For example, when creating user access review campaigns, we can't specify the time to send emails to reviewers—only the date."
"Microsoft Entra ID Governance should improve its capability to manage identities and access from a single console."
"There are some areas where improvements are necessary. Even though we have almost the full package, there are some bugs."
"Microsoft has done a commendable job with RPAX. However, Microsoft should prioritize enhancing its ABAC (Attribute-Based Access Control) capabilities. Currently, Microsoft's ABAC offering falls behind AWS in comparison."
"The platform's configuration process needs improvement."
"Bridging between on-premises and cloud services has the potential for improvement. For instance, it would be beneficial to be able to synchronize traditional directory schemas with Azure. I need to maintain an on-premises Active Directory server for certain required services."
"One area for improvement in Microsoft Entra ID Governance could be providing more granular control over security policies."
"We had some implementation issues."
"Okta should have at least a local peering partner for countries that align with or comply with GDPR, so there are no compliance or audit questions."
"The solution should have greater on-premises availability, not just cloud and more package customization in its processing."
"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."
"SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service."
"It only facilitates provisioning and not de-provisioning."
"There are some issues with the interface that can be improved."
"The initial setup can be complex at first."
 

Pricing and Cost Advice

"While other products give the pricing for their application, Microsoft Entra ID Governance has a per-user-based license model."
"The solution's pricing is not low but reasonable."
"There are no additional costs besides the standard licensing fees."
"In the education sector where I work, the annual cost for my Google and Microsoft environments is approximately $35,000. This covers the needs of 3,400 students and 800 faculty and staff members."
"License is around US$20,000 annually."
"The solution's pricing model could be better for SMBs."
"It is costly for large companies."
"The product's price is high. For each feature, a certain payment is required."
"The solution’s pricing needs to be reasonable. You are dealing with a lot of components and the pricing is component-based."
"Though I don't know about the licensing model of the product, I wouldn't be surprised if Okta offers a per user license subscription model."
"The price of Okta Workforce Identity is competitively priced. We pay annually for the use of the solution."
"Okta has fairly competitive pricing."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Manufacturing Company
9%
Financial Services Firm
8%
Government
8%
Computer Software Company
16%
Financial Services Firm
11%
Manufacturing Company
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Microsoft Entra ID Governance?
The most valuable feature of Microsoft Entra ID Governance is access reviews.
What needs improvement with Microsoft Entra ID Governance?
There are some areas where improvements are necessary. Even though we have almost the full package, there are some bugs. I cannot directly perform some tasks from the portal. First, I have to go to...
What is your primary use case for Microsoft Entra ID Governance?
We use it throughout the company. My colleagues and I are utilizing it, and we are creating access packages and so forth. We are using it for the entire company to manage access.
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?
Okta should have at least a local presense for countries that align with or comply with GDPR or data sovereignty, so there are no compliance or audit questions. There are integration issues with Of...
 

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 Entra ID Governance vs. Okta Workforce Identity and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.