We use this solution to integrate with a third party with API integration.
Senior Operational Technical Analyst at a construction company with 1,001-5,000 employees
Integrates with a third party and is stable and easy to install
Pros and Cons
- "The stability and performance are good. It is easy to install, and it scales well too."
- "It could be more user friendly for developers. It would be nice if developers could view things more easily."
What is our primary use case?
What is most valuable?
So far, we are satisfied with the product. The stability and performance are good.
It is easy to install, and it scales well too.
The technical support is good, and we get prompt support.
What needs improvement?
It could be more user friendly for developers. It would be nice if developers could view things more easily.
For how long have I used the solution?
I've been using this solution for nearly six months.
It's a cloud-based solution.
Buyer's Guide
Microsoft Azure API Management
December 2025
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
879,422 professionals have used our research since 2012.
What do I think about the stability of the solution?
So far, there's good stability, and we have not had any issues with it.
What do I think about the scalability of the solution?
Because it is on the Azure platform, it is always scalable and is easy to scale as well. If you want to use it more, then we can add more resources.
We started using Microsoft Azure API Management six months ago as a POC, and now it's online. We probably have about 30,000 users.
We hope to increase usage by moving all API onto API Management.
How are customer service and support?
Microsoft's technical support is good. We have the premium support package, so we get support straight away.
How was the initial setup?
The initial setup is straightforward.
Because you need to define the API contract, initially it may take about two months. However, this is not due to the Microsoft product.
What about the implementation team?
We had our internal consultant handle the implementation. We had a team including an integration engineer.
What's my experience with pricing, setup cost, and licensing?
We pay for a yearly license.
What other advice do I have?
I would recommend Microsoft Azure API Management and would rate it at eight on a scale from one to ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner.
Consulting Chief Information Officer at a tech services company with 11-50 employees
API management platform which offers scalability, stability, and easy integration
Pros and Cons
- "Easy to integrate API management platform. It is a stable and scalable solution."
- "Performance issues from this platform need to be sorted out."
What is our primary use case?
We are in the healthcare industry, so all the applications which are related to one hospital, it binds to Microsoft Azure API Management, and this is our use case for it.
What is most valuable?
I like the integration function of Microsoft Azure API Management. Integration of this solution is easy.
What needs improvement?
There's some area for improvement for this solution's performance. Sometimes it can be challenging. We're working with design patents and we're hoping to see the performance issues sorted out.
For how long have I used the solution?
We've been working with Microsoft Azure API Management for a year now.
What do I think about the stability of the solution?
Microsoft Azure API Management is a stable product, but we have not been able to test it yet on a multi-cloud environment.
What do I think about the scalability of the solution?
Microsoft Azure API Management is scalable. There are no issues with its scalability.
How are customer service and support?
Microsoft has a good technical support team. They are very helpful.
How was the initial setup?
Integration of this solution is easy. I won't call it an initial setup. It's an integration.
Which other solutions did I evaluate?
I was able to work with Apigee.
What other advice do I have?
We used Microsoft Azure API Management only in the Microsoft environment, but not in a multi-cloud environment.
Microsoft Azure API Management is cloud-based, in particular, it is a single cloud centered around Microsoft components and not on the Cross components.
I have no idea on how long it took to implement Microsoft Azure API Management. The testing and development team is the best resource on how long it took.
The number of users of this solution in the group I'm associated with is 300,000. Increasing the number of users will depend on the mergers and acquisitions, and how the group is doing.
For maintenance, we have a backend support team that handles application support. The major point is that if the API has a lot of issues, particularly in data silos, Microsoft Azure API Management has made it more convenient to manage those.
We're still trying and testing the integration function of this solution, and we're also trying to go deeper into its performance.
My rating for Microsoft Azure API Management is a nine out of ten.
I don't have any variance data with Apigee. Apigee is better than Microsoft. I have more numbers for Apigee compared to Microsoft.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Buyer's Guide
Microsoft Azure API Management
December 2025
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
879,422 professionals have used our research since 2012.
Senior Solutions Architect at a manufacturing company with 10,001+ employees
Stable with fair pricing and good technical support
Pros and Cons
- "The ease of use of the solution is excellent."
- "In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on."
What is our primary use case?
We primarily use the solution to manage our APIs.
What is most valuable?
The ease of use of the solution is excellent. It's a very user-friendly solution.
The initial setup is quite straightforward.
We found the solution to be very stable.
The solution can scale if you need it to.
Technical support is very helpful.
The solution has very fair pricing.
What needs improvement?
The lack of wording in the API could be improved. In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on.
There are a couple of features that are lagging.
For how long have I used the solution?
I've been working with the solution for five years or so. It's been a few years at this point.
What do I think about the stability of the solution?
We have found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. Its performance is reliable.
What do I think about the scalability of the solution?
The solution scales well. If a company needs to expand it, it can do so with relative ease.
We have about 15-20 users on the solution so far.
How are customer service and technical support?
Technical support has been very good. They are quite helpful and responsive. We are very satisfied with the level of support provided to us.
How was the initial setup?
The initial setup is straightforward. A company shouldn't have any problems during the process.
What's my experience with pricing, setup cost, and licensing?
The cost of the solution is very fair. It's not overly expensive. It offers very good value.
What other advice do I have?
We are Microsoft partners.
I'd recommend the solution to other individuals and organizations. Overall, I've been quite satisfied with its capabilities.
I'd rate the solution seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Senior Manager, Engineering at a computer software company with 10,001+ employees
Good user management with excellent configuration capabilities and decent stability
Pros and Cons
- "The user management is pretty seamless."
- "Technical support could be more flexible and try to meet the client's needs a bit more effectively."
What is most valuable?
The solution has pretty stable capabilities.
Their construction tool allows users to easily publish information about the API. It's basically just one click.
You can configure the subscription management onsite and link everything.
The developer portal that exposed the API documentation is great. You can just test the APIs in a very easy way.
The web portal is useful. You can build a pretty comprehensive portal where users can sign in and you can basically leave the API there.
The API management provided offers good integration with different management systems, like OpenID, for example.
The user management is pretty seamless.
What needs improvement?
Pricing is definitely an aspect that can be improved. They should offer an additional free tier. For example, if there was a tier for new accounts created, it may help their services by getting people onboarded. Once you will give access to someone and they try it they'll see, "Okay, it works and you can pretty quickly add something on top of it". After that, the client will end up staying, and probably paying.
The cost is also complex in terms of calculating how much everything will ultimately be priced at. It's not straightforward as it takes into account multiple factors.
Technical support could be more flexible and try to meet the client's needs a bit more effectively.
The solution needs to provide more use cases so that we can refer them to clients. It will help answer any questions in relation to performance and load management.
For how long have I used the solution?
I've been using the solution for about a year at this point.
What do I think about the stability of the solution?
There are some bugs that exist in this construction tool for the developer portal. We are submitting these bugs to Azure, so they already know about it. Overall, it's pretty stable.
How are customer service and technical support?
In terms of Azure technical support, we've had no issues in regards to response times. They are prompt. However, in some particular cases, they unable to be flexible. For example, with MQTT blockers, while you might want another port, they might tell you to use the hosted solution in order to get them to configure it. We'd just like them to have more flexibility with requests like this.
In terms of corporate security nowadays, it's very important to be flexible. At the end of the day we get stuck in the bureaucracy. If they could practice flexibility, it would be better for their clients, who may not have the wiggle room on their end.
That said, we're mostly satisfied with their level of service.
What's my experience with pricing, setup cost, and licensing?
The solution has a kind of calculator and it's not always straightforward to figure out the logic in pricing. There are lots of services that are managed in different ways. For a non-technical person, it's a nightmare to figure everything out.
At the end of the day, you have to build approximate pricing for the solution. According to my experiences in multiple projects, you do get preliminary pricing that is close to or the same as the estimate.
What other advice do I have?
Right now, for a particular client, we're using a managed version of the solution, however, in the future, I foresee us hosting it somewhere in the cloud.
We're using the most up to date version of the solution.
Overall, the solution has a lot of great features. There are a few bugs here and there, however, a the end of the day, there's lots of value provided.
I'd rate the solution at an eight, on a scale from one to ten. It's got a rather high cost and still has some areas that need some improvement. Otherwise, I'd rate it higher.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Social media strategist at a media company with 11-50 employees
Provides valuable configuration capabilities enhancing API security
Pros and Cons
- "The solution's configuration capabilities are the most effective features for enhancing API security."
- "The product's navigation feature needs enhancement."
What is our primary use case?
I primarily utilize the platform for integrations, monitoring, and process automation within our business workflows.
What is most valuable?
The solution's configuration capabilities are the most effective features for enhancing API security.
What needs improvement?
The product's navigation feature needs enhancement.
For how long have I used the solution?
I have been working with the platform for approximately three to four years.
What do I think about the scalability of the solution?
I rate the solution's scalability around eight or nine.
How are customer service and support?
The support services are good. However, they could be improved.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment process is not overly difficult. However, each API integration presents interface connectivity and parameters, which can introduce challenges.
The time required for deployment varies depending on the integration interface in question.
What's my experience with pricing, setup cost, and licensing?
I rate the solution's pricing between three and four, as it could be more competitive.
What other advice do I have?
The platform's insights improve over time, allowing us to monitor system health and receive notifications for updates.
We integrate it with Dynamics and other business tools, which enhances our data analysis and reporting capabilities. It facilitates better insights and easier data manipulation, although I rely on my team for detailed analytics.
I recommend the platform, particularly for organizations that require API utilization and integration, as it has proven to be effective in our experience.
Overall, I rate it an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer.
Azure Architect at a tech services company with 201-500 employees
A scalable solution that helps to manage APIs
Pros and Cons
- "The tool helps to manage APIs."
- "The product needs to introduce a developer portal."
What is our primary use case?
The tool helps to manage APIs.
What is most valuable?
The tool does what it's supposed to do.
What needs improvement?
The product needs to introduce a developer portal.
For how long have I used the solution?
I am working with the tool for ten years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
My company has around 20-30 customers for the solution. Each customer can have about 100 users for the tool.
How are customer service and support?
Microsoft support is good. We have regular sessions with Microsoft where we can have private previews of new features.
How was the initial setup?
The tool's setup depends. If you use it in the CI/CD pipeline, then the setup is complex. To deploy the solution, you need to create a template and enable the features.
What's my experience with pricing, setup cost, and licensing?
There are different tiers for pricing. You can even use the free version.
What other advice do I have?
I would rate the product an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Implementer
Software Engineer
Quick and easy to publish, but documentation lacking details
Pros and Cons
- "The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published."
- "Microsoft Azure API Management could improve the documentation. The documentation feels like marketing information and not sufficient technical information. Your easiest option is to purchase services from a Microsoft partner and this is their marketing."
What is our primary use case?
Our company has some internal APIs and we use Microsoft Azure API Management to help keep everyone on the same page.
What is most valuable?
The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published.
What needs improvement?
Microsoft Azure API Management could improve the documentation. The documentation feels like marketing information and not sufficient technical information. Your easiest option is to purchase services from a Microsoft partner and this is their marketing.
In a feature release, there could be a better Canary release. They have a release but you need to code it yourself.
For how long have I used the solution?
I have been using Microsoft Azure API Management for approximately two and a half years.
What do I think about the scalability of the solution?
We have approximately 30 people using the solution in my company.
How are customer service and support?
The support from Microsoft Azure API Management is okay.
How was the initial setup?
The initial setup of Microsoft Azure API Management took us three days.
What about the implementation team?
We did the implementation of the solution in-house.
What's my experience with pricing, setup cost, and licensing?
We are paying standard fees to use Microsoft Azure API Management.
What other advice do I have?
My advice to others is before getting into the solution, it is best to be certified so that all of the details you would need to know that are not easily available online, you would be mindful. It is a very good solution, but some features feel hidden at best.
I rate Microsoft Azure API Management an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Director at a tech services company with 11-50 employees
Easy to set up, easy to expand, and has dynamic pricing
Pros and Cons
- "It’s easy to set up."
- "The cloud deployment performance could be better."
What is our primary use case?
We primarily use the solution for storage. It’s for a database backup.
What is most valuable?
We really like the scalability.
It’s easy to set up.
What needs improvement?
The cloud deployment performance could be better.
Technical support could use some improvement.
For how long have I used the solution?
I’ve been using the solution for three years.
What do I think about the stability of the solution?
It is stable. However, its performance is not better than an on-premises deployment.
What do I think about the scalability of the solution?
The solution can scale and is easy to expand. It’s actually quite impressive.
We have about ten clients using the solution.
How are customer service and support?
Technical support could be better. There’s a lot of bouncing around. It’s not orderly.
How was the initial setup?
It is a straightforward setup. The implementation is not difficult or complex. The deployment is quick as well. It only took two or three days to get everything up and running.
We have about five technical people who can handle the setup and implementation process.
What's my experience with pricing, setup cost, and licensing?
We are a Microsoft-managed partner, so we do have some pricing from the distributor.
The licensing is dynamic as it is based on cloud usage.
What other advice do I have?
I can recommend Azure Block Storage to other people. However, they need to have an open mind in order to use cloud storage.
I’d rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Buyer's Guide
Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2025
Product Categories
API ManagementPopular Comparisons
Informatica Intelligent Data Management Cloud (IDMC)
Amazon API Gateway
webMethods.io
IBM API Connect
Kong Gateway Enterprise
IBM DataPower Gateway
MuleSoft API Manager
WSO2 API Manager
Postman Enterprise
SEEBURGER Business Integration Suite
Apache APISIX
Layer7 API Management
3scale API Management
Buyer's Guide
Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which product performs better: Kong API Gateway or Azure API Management?
- How does Apigee differ from Azure API Management?
- How does Microsoft Azure API Management compare with Amazon API Gateway?
- Which is better - Azure API Management or Amazon API Gateway?
- When evaluating API Management, what aspect do you think is the most important to look for?
- What is the difference between an API Gateway and ESB?
- In a Digital Banking Environment how do we see the role of ESB/ API Managers?
- What is an API Gateway?
- How do you protect your API from security threats?
- What should one take into consideration when choosing an API management solution to manage Microservices?

















