We performed a comparison between Axway AMPLIFY API Management and Microsoft Azure API Management based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"We like the portal for documentation a lot."
"The API portal capability is a valuable feature."
"This product is a ten when it comes to API management."
"This platform can be highly scalable."
"The most valuable feature of the solution is security."
"The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times."
"The administration tool for this solution is good."
"I like API Management's ability to do hybrid cloud stuff."
"The UI management is very easy to use."
"Microsoft Azure API Management is better because it has a DevOps integration by default."
"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."
"The product gives API gateway-related features, like throttling, which are easy to use and low-code/no-code."
"The most valuable features are the ease of use and it is a platform that has self-enablement for the customers to be able to register themselves."
"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."
"We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good."
"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."
"The portal still has room for improvement."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."
"It would be great if they have an asset report. It's hard to get support for that."
"The API Mocking tools need to be improved."
"This solution does have some limitations regarding the deployment model."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"The user interface needs improvement."
"Microsoft Azure API Management needs to improve stability."
"Azure API Management could be improved with better integration with all of Microsoft's tools."
"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."
"The cloud deployment performance could be better."
"In terms of improvement, it would be helpful if they could develop an on-premises option."
"When you start with Azure API management, you also need to onboard the Azure console and the Azure cloud environment, which comes with a price."
"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."
More Microsoft Azure API Management Pricing and Cost Advice →
Axway AMPLIFY API Management is ranked 11th in API Management with 12 reviews while Microsoft Azure API Management is ranked 1st in API Management with 68 reviews. Axway AMPLIFY API Management is rated 7.8, while Microsoft Azure API Management is rated 7.8. The top reviewer of Axway AMPLIFY API Management writes "An API management solution for ESB and B2B integration between systems with security". On the other hand, the top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". Axway AMPLIFY API Management is most compared with Apigee, Amazon API Gateway, Kong Gateway Enterprise, MuleSoft Anypoint API Manager and Layer7 API Management, whereas Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and Boomi AtomSphere API Management. See our Axway AMPLIFY API Management vs. Microsoft Azure API Management report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.