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

Microsoft Azure API Management vs Perforce Acana comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 21, 2025

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 Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
83
Ranking in other categories
No ranking in other categories
Perforce Acana
Ranking in API Management
33rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the API Management category, the mindshare of Microsoft Azure API Management is 14.7%, down from 19.3% compared to the previous year. The mindshare of Perforce Acana is 0.9%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
Microsoft Azure API Management14.7%
Perforce Acana0.9%
Other84.4%
API Management
 

Featured Reviews

RJ
Database Manager at a manufacturing company with 10,001+ employees
Facilitating seamless integration and robust security support
The integration process is very easy, which is crucial for our organization. Another valuable aspect is the support from Microsoft. Whenever support is required, it is readily available. Additionally, I appreciate the technical expertise Microsoft brings to the table. The security features are highly satisfactory, with various options providing flexibility to implement security measures based on specific compliance requirements.
Saurav Krishna - PeerSpot reviewer
Data Engineering and AI Intern at .3Lines Venture Capital
Authentication mechanism is easy to implement but improvement is needed in documentation
For API security purposes, we use the tool to host all our APIs. This allows us to take advantage of the security features provided by the platform. With the solution, we can implement rules such as rate limiting and restricting the number of API calls for each user. It acts as a secure gateway…

Quotes from Members

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

Pros

"The solution has overall high performance."
"The integration process is very easy, which is crucial for our organization."
"The tool helps to manage APIs."
"It's easier to use and has more features than Google."
"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 user management is pretty seamless."
"The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"Good interface, intuitive solution."
"The tool's authentication mechanism is easy to implement. We had to define a few parameters."
"It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."
 

Cons

"The licensing part of Microsoft is always higher than other platforms, like Amazon services and other cloud services. Microsoft should work on reducing the cost."
"There is room for improvement in the user interface and workflow for hosting APIs, especially third-party APIs."
"I would like to see better scalability and better performance."
"The implementation has room for improvement and can be more user-friendly."
"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."
"Microsoft Azure API Management needs to improve stability."
"I rate the technical support from Microsoft Azure API Management a four out of five."
"One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection."
"Akana API Management needs to improve its documentation."
"Lacks an integrated billing feature."
"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."
 

Pricing and Cost Advice

"Since this is a cloud-based solution you have to abide by those financial limits, this creates some different challenges compared to other solutions."
"The licensing fees are expensive."
"This is an expensive solution."
"The solution appears cheaper because it's a cloud SaaS model."
"There are additional costs to the standard licensing fees."
"Microsoft Azure is an expensive solution not for the large enterprises but for the medium and small."
"On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten."
"Based on the resources that we are leveraging, the price we are paying to use this solution is slightly higher than other competitors. In a few cases, it has its own advantage in some resources."
"For us, the pricing and licensing policies were for an on-premise installation with a fixed cost structure, that matched our budgeting policies."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
7%
Manufacturing Company
19%
Computer Software Company
12%
Financial Services Firm
12%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise53
No data available
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
Ask a question
Earn 20 points
 

Also Known As

Azure API Management, MS Azure API Management
No data available
 

Overview

 

Sample Customers

adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
British American Tobacco, Credit Suisse, Daimler, eBay, FOX, Liberty Mutual, Marriott, Mayo Clinic, Skandia, Tata communications
Find out what your peers are saying about Microsoft Azure API Management vs. Perforce Acana and other solutions. Updated: February 2026.
881,733 professionals have used our research since 2012.