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

IBM Cloud Pak for Integration 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

IBM Cloud Pak for Integration
Ranking in API Management
24th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (16th)
Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
81
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the API Management category, the mindshare of IBM Cloud Pak for Integration is 0.5%, down from 0.6% compared to the previous year. The mindshare of Microsoft Azure API Management is 17.9%, down from 19.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Neelima Golla - PeerSpot reviewer
A hybrid integration platform that applies the functionality of closed-loop AI automation
I recommend using it because, in today's context, the cloud plays a significant role. Within the same user interface, you can develop applications and manage multiple applications, making it a more user-friendly option. Moreover, you can explore various other technologies while deploying on the cloud, broadening your knowledge of cloud technologies. In my case, the transition led to my learning of Kubernetes, enabling multi-scaling and expanding my technical skills. It was a valuable experience, and I had the opportunity to learn many new things during the migration process. I can easily rate it an eight or nine out of ten.
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

"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"It is a stable solution."
"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"API Management does not take long to deploy."
"The documentation and configuration of APIs."
"Azure APIM's best features are its straightforward access management (it's a single point of access for all monitoring and logging and for policy implementation) and its integration with the Azure Cloud infrastructure."
"Azure API is scalable."
"The most valuable feature is its role as a linchpin in AI Hub architecture, enhancing data handling."
"I like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions."
"I like API Management's ability to do hybrid cloud stuff."
"Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those."
 

Cons

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"The initial setup is not easy."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"The pricing can be improved."
"Its queuing and messaging features need improvement."
"Security could be improved."
"Price is the first thing that comes to mind. It's quite expensive, which could be a barrier for some users."
"An area for improvement in Microsoft Azure API Management is deployment, in particular, the deployment of versions in Oryx. The development to production instance isn't adequate for me and needs to be improved. Microsoft Azure API Management lacks automation, which is another area for improvement."
"They need to work on the third party integrations."
"The licensing part of Microsoft is always higher than other platforms, like Amazon services and other cloud services."
"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 pricing model needs improvement, as some enterprise features are expensive."
"The portal where we publish the APIs could be improved. Maybe this is because we didn't configure it. It is quite easy to bypass API management because we have a lot of information shared on the portal, where we publish our APIs. I worry there is potential for a security breach in the API publishing. There needs to be more security available on terms of the way we publish them."
 

Pricing and Cost Advice

"It is an expensive solution."
"The solution's pricing model is very flexible."
"Licensing fees are paid on an annual basis."
"There are no additional costs above the main license."
"Since this is a cloud-based solution you have to abide by those financial limits, this creates some different challenges compared to other solutions."
"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."
"The licensing cost for Microsoft Azure API Management is publicly available and goes from a developer edition that costs $26 to $30 per month. It may have changed, but it's in the neighborhood of $30 per month. I believe there's also the enterprise edition, which is highly capable and costs $2,500 per month."
"Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc."
"It's being paid monthly."
"It costs around 30,000 Kronas a month, which translates to about $3,000 dollars monthly."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
12%
Insurance Company
9%
Government
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

What do you like most about IBM Cloud Pak for Integration?
The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of ...
What needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...
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

CVS Health Corporation
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Find out what your peers are saying about IBM Cloud Pak for Integration vs. Microsoft Azure API Management and other solutions. Updated: April 2025.
851,604 professionals have used our research since 2012.