We performed a comparison between Microsoft Azure API Management and WSO2 API Manager based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: Many users are heavily invested in Microsoft Azure products, making Microsoft Azure API Management more widely used and trusted. Additionally, WSO2 API lacks some new features and updated functionalities that other API solutions commonly provide. In terms of pricing, however, users are happier with WSO2.
"The Azure Active Directory Synchronization is quite good."
"Ease of integration into the entire Microsoft environment."
"We use this solution for API rate limiting and for its security features against DDoS."
"It's easy to use compared to other products. It's easy to set up."
"It's a very robust tool. So you see that there is a developer portal which can be used by developer or the vendors as well. And other external partners to create keys and manage their own APIs. The other thing is that they have a lot of policies there are too many options within API. So I do the difficult to tell one, but probably I would say, like, proxy sorry. The policies is one of the thing wherein you can just configure the policies and modify the behavior of the APIs."
"The UI management is very easy to use."
"It's easier to use and has more features than Google."
"Initial setup was quite easy."
"It's very scalable, which is one of the best features."
"The most interesting feature is its Mac-based function."
"Its open-source features are very good, especially for your production work."
"The main feature — the publication of the API, the management section — is great in general."
"API management lifecycle is the most valuable."
"WSO2 API Manager is easy to use."
"The user interface is easy to navigate, and the documentation is extensive. It's open-source, so everything is available, and we can create what we need. That's not necessarily a feature, but it's an advantage."
"WSO2 API Manager has a user-friendly model."
"There is room for improvement in the user interface and workflow for hosting APIs, especially third-party APIs."
"Azure API Management could be improved with better integration with all of Microsoft's tools."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
"Microsoft Azure API Management needs to improve stability."
"Support for GraphQL could be better."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection."
"It would be better if it were easier to transition to Azure from JIRA. For example, different nomenclature must be performed when you shift to Azure from JIRA. JIRA's storage, tasks, and ethics are treated differently from Azure. Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. If someone has to get into the nomenclature, then there can be different tasks from clients, and here, they may be treated as functions. JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between ethics and a function and a story are different, and people may have to learn to adapt to the new nomenclature."
"I would improve the product documentation. There are some gaps, and it can be difficult to find the proper documentation for the product if you need to solve something."
"The technical support must be improved."
"The price and the complexities attached to the solution are two areas of concern where improvements are required."
"The interface needs to be modernized and made more user friendly so the product continues to have a growing community of users."
"Integration is an area that needs to be improved."
"I would like it to be a more stable solution. Maybe in the last version that is approved. For me it would be good if they had a community established version."
"Providing easy configuration for email and SMS notifications, layout and customization of admin and developer landing pages."
"From a product perspective, the first thing is that although the documentation provided by WSO2 is good, it could be much better. We're in the middle of a complex migration, moving away from VMs to Kubernetes with the latest version of WSO2 and good documentation is essential to us right now."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while WSO2 API Manager is ranked 7th in API Management with 33 reviews. Microsoft Azure API Management is rated 7.8, while WSO2 API Manager is rated 8.0. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of WSO2 API Manager writes "Reliable with good capabilities and good support". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM DataPower Gateway, whereas WSO2 API Manager is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, Apache APISIX and 3scale API Management. See our Microsoft Azure API Management vs. WSO2 API Manager report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
