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

Apiary vs Microsoft Azure API Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 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

Apiary
Ranking in API Management
36th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
80
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of Apiary is 0.3%, up from 0.2% compared to the previous year. The mindshare of Microsoft Azure API Management is 18.5%, down from 19.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

PW
The ability to configure rules to check for consistency has helped
Apiary provides a free tier of the platform which allows a small group of developers to collaborate easily on the design of open source APIs. In addition to this, it provides mock endpoints allowing people to experiment with the API without depending or having to stand up a real backend. With our clients, using Apiary allows us to very quickly pull together an API definition (particularly when using API Blueprint). The whole API design process for the simpler use cases can be done in a relatively short workshop which makes it a lot easier to agree, publish, version-manage an API definition with suitable documentation. This can then be evolved and enhanced (particularly in the documentation aspects). With the ability to support Swagger (Open API v2 and introducing/ed support for v3) and API Blueprint makes it a very versatile tool.
Rajiv Bala Balasubramanian - PeerSpot reviewer
Efficiently manages and monetizes API
It is a scalable solution. You can add more computing power to your APM gateway. It also gives you the ability to have VNet integrations with your on-prem. It is one of the leading products in the API management space. It is not just software for users but software to handle requests. For example, for a B2C e-commerce store, all requests that users make from within the store pass through this API gateway. So it is defined by the number of requests to the API gateway, not by the number of actual users who use it. If you look at the number of requests, it would be a lot from all the different systems we have within Pampers.

Quotes from Members

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

Pros

"In two years, there was one time the service was down for an hour or so."
"I find the generation of mock services very useful, especially when demonstrating for new consumers."
"Quick and easy way to share a new API design with teams."
"Git integration"
"I do like the overall performance of the solution."
"The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published."
"It seems quite good so far. It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow."
"The most valuable feature of Microsoft Azure API Management is monitoring. When compared with Apigee, I prefer Microsoft Azure API Management."
"There were no scalability issues."
"The tool helps to manage APIs."
"Everything is already available and ready to operate without a lot of preparation work."
"Ease of integration into the entire Microsoft environment."
"The ease of use of the solution is excellent."
 

Cons

"The Oracle release cycle is very bad because the patches only update once a year."
"Swagger (OpenAPI Specification) and Blueprint Support"
"I would like an integrated option to download a Swagger version of the definition."
"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."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"Microsoft Azure API Management should have the ability to allow multitenancy."
"The licensing fees should be cheaper."
"The product's navigation feature needs enhancement."
"There is room for improvement in the user interface and workflow for hosting APIs, especially third-party APIs."
"They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet."
"The product needs to introduce a developer portal."
 

Pricing and Cost Advice

"It is easy to get started with personal (free) accounts, but a subscription is required for additional features."
"There is a free subscription option to start and try the service."
"The product pricing is reasonable."
"The price is comparable."
"Licensing fees are paid on an annual basis."
"Microsoft is competitively priced."
"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 solution appears cheaper because it's a cloud SaaS model."
"Because of our partner relationship, our pricing is pretty decent. But in general, if I compare pricing, I think the initial offer that we got from Microsoft until the relationship kicked in was more expensive than AWS. There were some unexpected expenses because we had to pause. This was due to our inexperience and because we were doing this significant public cloud migration for the first time. We were using SAP on a public cloud for the first time."
"The licensing fees are expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
844,944 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Insurance Company
12%
Financial Services Firm
10%
Computer Software Company
10%
Media Company
8%
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
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.
 

Also Known As

No data available
Azure API Management, MS Azure API Management
 

Overview

 

Sample Customers

Microsoft, salesforce.com, Bloomberg, GoodData, Viacom, Akamai Technologies, DigitalGlobe
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Find out what your peers are saying about Apiary vs. Microsoft Azure API Management and other solutions. Updated: March 2025.
844,944 professionals have used our research since 2012.