Microsoft Azure API Management vs OpenLegacy comparison

Microsoft Azure API Management

Read 5 OpenLegacy reviews

444 Views
268 Comparison Views

80% willing to recommend

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

Microsoft Azure API Management and OpenLegacy compete in the API management category. Azure API Management seems to have the upper hand with its strong integration within Microsoft ecosystems and competitive pricing, while OpenLegacy provides unique legacy integration capabilities that some users find valuable despite its higher cost.

Features:Azure API Management provides API gateways, developer portals, and security features that integrate efficiently with Azure services. It also offers robust monitoring, access control, and subscription management for easy tracking and usage analysis. On the other hand, OpenLegacy focuses on legacy system integration, providing API generation without revamping existing systems. It enables seamless connections to older platforms, making it adaptable and open-source, which is beneficial for customization requirements.

Room for Improvement:Azure API Management could improve in offering more flexible multi-cloud integration outside the Microsoft environment, enhancing real-time customization features, and reducing complexity in large-scale deployments. OpenLegacy can work on simplifying its technology to make it more user-friendly, offering more streamlined support for non-legacy systems and improving documentation for better usability with mainstream cloud services.

Ease of Deployment and Customer Service:Azure API Management is straightforward to deploy within Microsoft environments, with comprehensive support resources and a broader service network. OpenLegacy, although complex due to legacy interactions, offers expert support and flexible deployment options tailored to customer needs, facilitating smoother legacy transitions.

Pricing and ROI:Azure API Management provides a clear pricing model with attractive ROI potential, especially for businesses using Azure services. OpenLegacy’s pricing mirrors its special legacy integration abilities, requiring a significant initial investment but promising high ROI by lessening modernization costs. Azure offers a lower entry cost, while OpenLegacy justifies its price with specific integration benefits.

To learn more, read our detailed Microsoft Azure API Management vs. OpenLegacy Report (Updated: April 2025).

Microsoft Azure API Management vs. OpenLegacy

Download the complete report

Helped 851,371 peers since 2012

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

Ranking in other categories

No ranking in other categories

OpenLegacy

Ranking in API Management

35th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

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

API Management

Featured Reviews

Rajiv Bala Balasubramanian

Specialist PCC at Danfoss

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.

Read full review

reviewer1042905

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.

Read full review

Quotes from Members

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

Pros

"Microsoft Azure API Management has many valuable features. One is the developer portal, that's very useful for teams. The tool also provides layers of security. I also found the caching, automatic documentation, and version management functionalities most valuable."

"The most valuable features are the API and integrations."

"The ability to create a subscription model for APIs allows companies to monetize valuable data and share it securely."

"Easy to integrate API management platform. It is a stable and scalable solution."

"Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those."

"I like API Management's ability to do hybrid cloud stuff."

"The tool helps to manage APIs."

"The API management is very good."

More Microsoft Azure API Management pros

"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."

"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."

"It is possible to solve larger legacy API issues on an enterprise level with this product."

"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."

"Opens the door to connect modern web products to an old legacy system."

"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."

"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."

"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."

Cons

"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."

"Technical support could be more flexible and try to meet the client's needs a bit more effectively."

"The API gateway can be very complex."

"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."

"I'd like to have better flexibility and more capabilities."

"The developer portal can be improved."

"They need to work on the third party integrations."

"It could be more user friendly for developers. It would be nice if developers could view things more easily."

More Microsoft Azure API Management cons

"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."

"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."

"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."

"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."

Pricing and Cost Advice

"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."

"Since this is a cloud-based solution you have to abide by those financial limits, this creates some different challenges compared to other solutions."

"It's an expensive solution"

"The product pricing is reasonable."

"It's being paid monthly."

"The solution appears cheaper because it's a cloud SaaS model."

"Since everyone is isocentric here, it is reasonable for me."

"The developer and standard pricing tiers of Azure API Management are very competitive compared to other products."

More Microsoft Azure API Management pricing and cost advice

"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."

See which vendors are best for you

Use our free recommendation engine to learn which API Management solutions are best for your needs.

See recommendations

851,371 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

16%

Computer Software Company

13%

Manufacturing Company

Insurance Company

No data available

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

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...

See all answers

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 ...

See all answers

What do you like most about Microsoft Azure API Management?

Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.

See all answers

Ask a question

Earn 20 points

Comparisons

Amazon API Gateway vs Microsoft Azure API Management

Compared 44% of the time

Apigee vs Microsoft Azure API Management

Compared 20% of the time

IBM API Connect vs Microsoft Azure API Management

Compared 6% of the time

Kong Gateway Enterprise vs Microsoft Azure API Management

Compared 5% of the time

MuleSoft API Manager vs Microsoft Azure API Management

Compared 4% of the time

More Microsoft Azure API Management Competitors

Kong Gateway Enterprise vs OpenLegacy

Compared 30% of the time

MuleSoft API Manager vs OpenLegacy

Compared 19% of the time

IBM API Connect vs OpenLegacy

Compared 16% of the time

Amazon API Gateway vs OpenLegacy

Compared 13% of the time

webMethods.io vs OpenLegacy

Compared 12% of the time

More OpenLegacy Competitors

Product Reports

Microsoft Azure API Management

Download Microsoft Azure API Management product report

Download OpenLegacy product report

Also Known As

Azure API Management, MS Azure API Management

No data available

Overview

Microsoft Azure API Management is essential for managing APIs, facilitating integration, and ensuring secure internal and external communication.

Organizations leverage Microsoft Azure API Management for seamless integration and effective API management. It supports microservices, legacy modernization, and platform orchestration in sectors like healthcare, telecom, and finance. Features such as developer portals and centralized libraries simplify usage. While it showcases strengths in hybrid cloud support and scalability, improvements are suggested in versioning and multi-tenancy.

What key features does it offer?

Integration with Microsoft services ensures robust access control and user-friendly deployment.
Developer portal and documentation improve usability and learning.
Hybrid cloud support offers seamless on-premise connectivity.
Scalability and security features are well-regarded.
Centralized API library simplifies management.

What benefits or ROI should users consider?

Facilitates API lifecycle management enhancing user experience.
Simplifies authentication and subscription models.
Enhances data exchange and real-time monitoring.
Streamlines API mapping and orchestration across platforms.
Promotes flexibility and transparency in system integration.

Microsoft Azure API Management aids modernization across healthcare, telecom, and financial services by enabling legacy system updates and facilitating smooth platform orchestration.

Microsoft

OpenLegacy helps organizations quickly launch innovative digital services by extending their core back-end systems to the web, mobile and cloud in days or weeks versus months. Our microservice-enabled API integration and management software quickly reduces project backlog by automating and accelerating microservices and API creation, deployment, testing and management from core applications, mainframes and databases. Together, business and IT teams can quickly, easily and securely meet consumer, partner or employee demands for digital services without modernizing or replacing core systems, and without special programming skills or invasive changes to existing systems and architectures. OpenLegacy is designed for ongoing management of microservices APIs and is based on open standards, so our software plays nice with your current technology stack and supports agile, DevOps and continuous development. Learn why leading companies choose OpenLegacy at www.openlegacy.com.

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...

Microsoft Azure API Management vs. OpenLegacy