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

Microsoft Azure API Management vs SwaggerHub 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

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
SwaggerHub
Ranking in API Management
14th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
10
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the API Management category, the mindshare of Microsoft Azure API Management is 19.1%, down from 19.7% compared to the previous year. The mindshare of SwaggerHub is 1.2%, down from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

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.
SwaminathanSubramanian - PeerSpot reviewer
Facilitating enterprise-wide API governance and management
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. Additionally, the versioning management could be improved to be on par with source code management tools.

Quotes from Members

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

Pros

"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The Azure Active Directory Synchronization is quite good."
"I like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions."
"The Application Gateway we have found to be the most useful in Microsoft Azure API Management. We have integrated the Microsoft Azure API Management with Application Gateway. Application Gateway is a type of load balancer that we are using for the high availability of our API calls."
"Microsoft Azure API Management is better because it has a DevOps integration by default."
"The most valuable feature of Microsoft Azure API Management is monitoring. When compared with Apigee, I prefer Microsoft Azure API Management."
"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."
"We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"The tool's most valuable feature is licensing."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."
"It is a stable solution."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"The product's initial setup phase was easy and not at all difficult."
"I rate the solution's stability a ten out of ten."
 

Cons

"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 is lagging behind Apigee and should also have a better CICD process."
"Some of the DevOps stuff could be easier to work with. The migration paths are a little complicated, and moving code around could be more seamless. There should be less manual migration when several teams work together to publish code to the DevOps."
"I rate the technical support from Microsoft Azure API Management a four out of five."
"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."
"Azure API Management could be improved with better integration with all of Microsoft's tools."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"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."
"More integration and usability with the cloud microservices would be nice"
"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."
"We have to use additional tools to test APIs."
"It could be more intuitive compared to one of its competitors."
"SwaggerHub could be improved with better integration for tools."
"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."
"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."
"It has limited functionality...Unfortunately, some of its features are not what we need."
 

Pricing and Cost Advice

"Since everyone is isocentric here, it is reasonable for me."
"I would describe the tool's price as being in the mid-range category."
"Microsoft Azure is an expensive solution not for the large enterprises but for the medium and small."
"It's free for less than ten users. If you want to go beyond that, it's around $3.50 per user per month. If you want a DevOps integration, it's about $7.50 per user per month. Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all three flavors for $7.50 per user per month."
"There are no additional costs above the main license."
"It's an expensive solution"
"Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft."
"This is an expensive solution."
"It has a yearly subscription, but I am not sure."
"The tool is cheap."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
842,296 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Insurance Company
7%
Financial Services Firm
23%
Computer Software Company
14%
Retailer
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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.
What do you like most about SwaggerHub?
The tool's most valuable feature is licensing.
What needs improvement with SwaggerHub?
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account....
What is your primary use case for SwaggerHub?
I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock web services to test web services and create test scripts and mock APIs. This usa...
 

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
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about Microsoft Azure API Management vs. SwaggerHub and other solutions. Updated: March 2025.
842,296 professionals have used our research since 2012.