Microsoft Azure API Management vs OpenLegacy comparison

Microsoft Azure API Management

Read 5 OpenLegacy reviews

2,320 Views
1,438 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: August 2026).

Microsoft Azure API Management vs. OpenLegacy

Download the complete report

Helped 909,725 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

6.8

Number of Reviews

Ranking in other categories

No ranking in other categories

OpenLegacy

Ranking in API Management

33rd

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

AI Software Development (78th)

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of Microsoft Azure API Management is 11.9%, down from 16.6% compared to the previous year. The mindshare of OpenLegacy is 1.4%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.

API Management Mindshare Distribution
Product	Mindshare (%)
Microsoft Azure API Management	11.9%
OpenLegacy	1.4%
Other	86.7%

API Management

Featured Reviews

Amit Das

Technical Solution Architect at liwa

Has supported smooth channel partner integration and data analysis for several years

We use the existing services hosted in Microsoft Azure API Management without making any changes. For transformation capabilities, we utilize ADF, Data Factory instead of Microsoft Azure API Management. Regarding security features in Microsoft Azure API Management, we utilize token bearer authentication. As retailers with integration to our channel partners, we haven't experienced any security issues with Microsoft Azure API Management since it isn't exposed to external parties. We use a basic Azure function hosted in Microsoft Azure API Management rather than the integrated developer portal. Tracking analytics and performance analytics in Microsoft Azure API Management is straightforward. We use basic features for performance analytics and log analytics due to additional subscription charges. We enabled log analytics for Microsoft Azure API Management in the past month to investigate issues such as unreachable endpoints or request timeouts.

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

"Everything is already available and ready to operate without a lot of preparation work."

"The Azure Active Directory Synchronization is quite good."

"I like the support they provide for the APIs more than the solution itself. First of all, documentation-wise, both Microsoft Azure and even Google Cloud are up there. But in comparison, the real-time consulting and support for APIs make Microsoft stand out a little. I also like the performance. Standard public cloud provider-built APIs are more resilient and flexible in terms of what feature you want to use and what feature you don't want to use, and they're more customizable. They are more resilient in terms of performance in that particular environment because that is the design aspect of the offering. When public clouds build APIs and deploy them after testing them on their framework for a certain amount of time, I feel there is a massive difference in the product's performance. On the interface, everything is strong."

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

"Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time."

"So far, we are satisfied with the product."

More Microsoft Azure API Management pros

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

"The product has helped our business by allowing us to become more efficient in data handling."

"OpenLegacy opens the door to connect modern web products to our old legacy system."

"Without OpenLegacy, it would take us several months to create the same services."

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

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

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

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

More OpenLegacy pros

Cons

"We figured out that for our productive usage, we will select a different vendor."

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

"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 API gateway can be very complex."

"Expansion to global regions is a point for improvement, as licensing is costly."

"I could that the UI could be improved."

"The licensing fees are expensive. I would like it to be cheaper."

"I would like to see more integration with other platforms, as well as increased security."

More Microsoft Azure API Management cons

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

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

"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."

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

"Debugging and logging for programmers could be better."

Pricing and Cost Advice

"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 additional costs to the standard licensing fees."

"The price of the solution is reasonable compared to others."

"Microsoft is competitively priced."

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

"It's pay as you go. The subscription packages have room for different scales. It's calculated by the number of apps or computers you use. You do not have to use the enterprise subscription. These subscriptions have different pricing, so you can find one to meet your needs for scalability."

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

"Microsoft Azure is an expensive solution not for the large enterprises but for the medium and small."

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

909,725 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

14%

Manufacturing Company

10%

Computer Software Company

Insurance Company

Construction Company

26%

Financial Services Firm

13%

Comms Service Provider

12%

Manufacturing Company

11%

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	23
Midsize Enterprise	11
Large Enterprise	54

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

See all answers

Ask a question

Earn 20 points

Comparisons

Amazon API Gateway vs Microsoft Azure API Management

Compared 49% of the time

Apigee vs Microsoft Azure API Management

Compared 17% of the time

Kong Gateway Enterprise vs Microsoft Azure API Management

Compared 4% of the time

MuleSoft API Manager vs Microsoft Azure API Management

Compared 3% of the time

IBM API Connect vs Microsoft Azure API Management

Compared 3% of the time

More Microsoft Azure API Management Competitors

IBM DataPower Gateway vs OpenLegacy

Compared 18% of the time

Pipedream vs OpenLegacy

Compared 11% of the time

IBM API Connect vs OpenLegacy

Compared 9% of the time

MuleSoft API Manager vs OpenLegacy

Compared 8% of the time

Fiorano API Management vs OpenLegacy

Compared 8% 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 offers a comprehensive solution for managing APIs, ensuring security, integration, and access across cloud environments. It enables seamless API orchestration and supports flexible management systems, making it valuable for API-driven architectures.

Microsoft Azure API Management is an advanced platform designed for seamless API integration and management within Microsoft's ecosystem. It provides robust security capabilities, including access control and Active Directory integration. The platform features a developer portal for easy API documentation and testing, along with real-time monitoring, analytics, and configurable policies to enhance API behavior. With hybrid cloud support and API orchestration, users gain flexibility and the ability to monetize APIs through subscriptions. The platform aids businesses in modernizing their applications and processes, but users have highlighted the need for enhanced scalability, third-party integration, improved documentation, and more comprehensive pricing models.

What are the most important features of Azure API Management?

User-friendly setup facilitating ease of integration
Robust security with access control and Active Directory
Comprehensive developer portal for API documentation and testing
Real-time monitoring and analytics
Flexible policy configuration for API orchestration
Hybrid cloud connectivity support
Monetization through subscription models

What benefits or ROI should users look for in Azure API Management reviews?

Enhanced API security and governance
Efficient backend system connections
Improved application monitoring and orchestration
Seamless migration from legacy to API-driven interfaces
Support for modernizing applications and automating processes

Azure API Management is widely implemented across industries like finance, healthcare, and retail to integrate and manage internal and external APIs. Businesses use it for secure connections, microservices support, and modernizing legacy systems. It's also adopted for subscription models and access control, aiding companies in automating and enhancing their operational processes.

Microsoft

OpenLegacy integrates legacy customer data with REST APIs, speeding up mobile transactions and code updates while simplifying API development. Its open-source platform offers flexibility, benefiting mainframe environments and Tomcat server deployments.

OpenLegacy is crucial for organizations aiming to integrate modern web applications with legacy systems. The platform is widely used in financial and logistics sectors to enable quick access to customer data and transactions, effectively monetizing mainframe assets. By facilitating the rapid creation of numerous APIs, OpenLegacy supports seamless interactions between applications, allowing modern web form inputs into legacy systems. Its flexibility and extensive capabilities simplify API development and deployment, proving valuable for those managing day-to-day banking and transaction data. However, room for improvement includes better debugging, logging, SSL integration, flexible pricing options, and support availability, especially for Hogan mainframe users.

What features define OpenLegacy?

REST API Integration: Facilitates integration with mobile transactions.
Faster Code Updates: Delivers efficiency in code changes for mainframe environments.
Open-Source Flexibility: Offers customization and broad capabilities.
Tomcat Deployment: Supports straightforward deployment via Tomcat servers.
Rapid API Development: Enables swift creation of multiple APIs.

What ROI benefits should users expect?

Legacy System Monetization: Transforms mainframe assets into profit.
Improved Integration: Enhances access to critical customer data and transactions.
Efficient Operations: Streamlines daily banking and transaction management.
Cost-Effectiveness: Flexibility and open-source nature reduce expenses.
Enhanced Interoperability: Allows seamless interaction between old and new applications.

Financial and logistics companies leverage OpenLegacy to link web applications with legacy systems, ensuring quick customer data and transaction access. This integration supports rapid solution building and efficient management of banking and transaction data, particularly benefiting institutions like US Bank and Wells Fargo needing comprehensive Hogan mainframe connectors.

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