No more typing reviews! Try our Samantha, our new voice AI agent.

Microsoft Azure API Management vs OpenLegacy comparison

Why PeerSpot?
 

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
6.8
Number of Reviews
83
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
34th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (58th)
 

Mindshare comparison

As of November 2026, in the API Management category, the mindshare of Microsoft Azure API Management is 10.3%, down from 16.2% compared to the previous year. The mindshare of OpenLegacy is 1.5%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Microsoft Azure API Management10.3%
OpenLegacy1.5%
Other88.2%
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.
reviewer1042905 - PeerSpot reviewer
VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.

Quotes from Members

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

Pros

"We use the solution to have an API that is calling internal resources to expose data on the internet, and we also use API Management for partners and mobile apps."
"Ease of integration into the entire Microsoft environment."
"The solution has overall high performance."
"Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation."
"The package as a whole is useful for our customers."
"The simplicity to learn and apply using API Management is valuable."
"The solution is secure and has all the components that we require."
"The solution's configuration capabilities are the most effective features for enhancing API security."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"Without OpenLegacy, it would take us several months to create the same services."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"The product has helped our business by allowing us to become more efficient in data handling."
 

Cons

"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."
"Specific to API development, I think Microsoft is still far behind AWS. AWS has grown by leaps and bounds, and Microsoft is a close second."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
"I did follow the prescribed steps to export our Test subscription setup to import into a production subscription environment, but I was unable to achieve the export within the short amount of time I had to achieve it."
"Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process."
"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."
"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."
"This solution is only available as a cloud-based deployment and it would be very helpful to have an on-premises version."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Debugging and logging for programmers could be better."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
 

Pricing and Cost Advice

"This is an expensive solution."
"We pay for a yearly license."
"Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft."
"The solution is highly expensive. Our customers worry about the costs. The price should be a lot less."
"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."
"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."
"The licensing fees are expensive."
"There are additional costs to the standard licensing fees."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
11%
Outsourcing Company
9%
Computer Software Company
7%
Construction Company
24%
Comms Service Provider
16%
Financial Services Firm
13%
Manufacturing Company
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise54
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 is your experience regarding pricing and costs for Microsoft Azure API Management?
The pricing is medium, which I find to be reasonable for the value we receive.
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
Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Find out what your peers are saying about Microsoft Azure API Management vs. OpenLegacy and other solutions. Updated: September 2026.
920,769 professionals have used our research since 2012.