Try our new research platform with insights from 80,000+ expert users
KiranCheriyala - PeerSpot reviewer
Architect at a outsourcing company with 201-500 employees
Real User
Performs boilerplate functions without disturbing the backend business logic
Pros and Cons
  • "I like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions."
  • "Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process."

What is our primary use case?

There were legacy APIs running on-premises, and we wanted a modernized layer without disturbing the existing legacy layer. Microsoft Azure API management helps with that. We can wrap the modernized API layer. The modernized API layer can perform rate-limiting, monitoring, throttling, aggregating, and other boilerplate functions without disturbing the backend business logic.

What is most valuable?

I like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions.

You can host multiple API gateways in different locations. If one goes down, then another will take over. Microsoft Azure API Management is good in terms of nonfunctional requirements.

The documentation is neat and organized, and as a result, we rarely have the need to contact technical support. 

What needs improvement?

Microsoft Azure API Management is lagging behind Apigee and should also have a better CICD process.

For how long have I used the solution?

I used it for six months.

Buyer's Guide
Microsoft Azure API Management
August 2025
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,445 professionals have used our research since 2012.

What do I think about the stability of the solution?

It's a stable solution.

What do I think about the scalability of the solution?

Because it is on Microsoft Azure, we don't have to worry about scalability. I would give scalability a rating of ten out of ten.

How are customer service and support?

Technical support is very poor and needs a lot of improvement. The process is not straightforward, and they are hard to reach.

How was the initial setup?

Because it is a cloud solution, the initial setup is straightforward.

What's my experience with pricing, setup cost, and licensing?

It is an expensive solution, but any API solution will be expensive.

What other advice do I have?

Overall, I would rate Microsoft Azure API Management at nine on a scale from one to ten.

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 does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer2093580 - PeerSpot reviewer
Solutions Architect at a insurance company with 10,001+ employees
Real User
Good API management with out of the box functionality and good support
Pros and Cons
  • "The API management is great."
  • "I'd like to have better flexibility and more capabilities."

What is our primary use case?

The main use case is if you want to be exposed to an external endpoint. We use it for access. It can only be used by Azure API.

How has it helped my organization?

If I want to expose API endpoints to clients, we use this solution. 

What is most valuable?

The API management is great. It comes out of the box ready to go and comes with policies. 

It is stable.

Technical support is good.

We have witnessed an ROI.

What needs improvement?

We have to put the logs in Datadog. We need to use some other product to do all of the things we want. That costs extra. However, there are other solutions, like Dynatrace, that offer more features and have more functionalities. Right now, we have to use logic apps. You need more third-party apps to fill in the gaps. 

If I want to connect to other apps to Saleforce or Snowflake, et cetera, I need a quicker way to do mapping and to integrate everything together. 

I need to have microservice access. 

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

For how long have I used the solution?

I've been using the solution for three to four years. 

What do I think about the stability of the solution?

I'd rate the stability seven or eight out of ten. It's reliable. There are no bugs or glitches. 

What do I think about the scalability of the solution?

We do not scale the solution. We don't need multi-tenancy or anything like that. Our understanding is that if we did need to scale it would cost more. 

How are customer service and support?

Technical support is very good and is available around the clock. 

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I'm familiar with a variety of other solutions, including Mulesoft.

What was our ROI?

I have witnessed an ROI while using the solution. 

What's my experience with pricing, setup cost, and licensing?

The pricing is expensive, however, it does offer great value. I'd rate the solution seven or eight out of ten in terms of value for money.

What other advice do I have?

I'm not sure which version of the solution I'm using. 

The product covers all of the basic needs you will need. If you need more robust options, Mulesoft might be a good option. However, this is a pretty good tool

I'd rate the solution an eight out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Microsoft Azure API Management
August 2025
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,445 professionals have used our research since 2012.
reviewer2016312 - PeerSpot reviewer
Solution Architect at a computer software company with 1,001-5,000 employees
Real User
UI management is easy to use and technical support is very good
Pros and Cons
  • "The UI management is very easy to use."
  • "The API gateway can be very complex."

What is our primary use case?

Our company uses the solution for API orchestration and UI management. We currently have 50,000 users. 

What is most valuable?

The UI management is very easy to use. 

The solution provides good management of API orchestrations. 

Technical support is very good and moves very fast. 

What needs improvement?

The API gateway can be very complex. We had difficulty managing end users for a very, very complex project. 

I am not sure that another API gateway would have better handled this difficult project. 

For how long have I used the solution?

I have been using the solution for four 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?

The solution is scalable. 

How are customer service and support?

We have a partnership with Microsoft. Their support is very good and moves very fast. They are available to us in a maximum of ten to twenty minutes. 

How was the initial setup?

The setup is very easy and doesn't take long. 

What about the implementation team?

We implemented the solution in-house. 

Which other solutions did I evaluate?

I also use WSO2 and Kong. Of all the options, Kong is my preference because it is easier to use. 

What other advice do I have?

The solution's support is very good. 

I rate the solution an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Rampal Yadav - PeerSpot reviewer
Sr. Manager- Cloud & Virtualization at IIFL
Real User
Straightforward and basic deployment, initial preparations are minimized, with good stability
Pros and Cons
  • "Everything is already available and ready to operate without a lot of preparation work."
  • "I would like to see more security features become available."

What is our primary use case?

We use Microsoft Azure API Management with our coding.

What is most valuable?

All we need to do is run our specific code because the dependencies are already there. 

What needs improvement?

I would like to see more security features become available. For example, the integration on premises could be better. Things could be more user-friendly. Currently, the integration we work with is more complex than it needs to be.

For how long have I used the solution?

I have been using Microsoft Azure API Management for the past thirteen months.

What do I think about the stability of the solution?

I am finding Microsoft Azure API Management stable.

What do I think about the scalability of the solution?

Day by day we are increasing the usage of Microsoft Azure API Management.

How are customer service and support?

My current experience with technical support has been good.

Which solution did I use previously and why did I switch?

We were using DIS. We needed to install the run times, libraries, and install operating systems. We had to make a lot of initial preparations to get the process ready to operate. Now it is already available and ready to operate with Microsoft Azure API Management.

How was the initial setup?

I would rate the initial setup process a four out of five.  The setup was basic and good.

What about the implementation team?

We do our implementation through one of our partners. The configuration was around fifteen to twenty minutes long.

What was our ROI?

There is no investment funding or upfront cost needed. 

What's my experience with pricing, setup cost, and licensing?

There are no licensing fees we pay on a monthly basis.

Which other solutions did I evaluate?

We compared it with DIS because most of the time we were using DIS, for such kind of deployment.

What other advice do I have?

Many people are using the API, and it is a prominent feature currently being used. I would rate Microsoft Azure API Management an eight out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Aurel Avramescu - PeerSpot reviewer
Software Architect at a transportation company with 51-200 employees
Real User
High priced solution with limited ability to use other technologies
Pros and Cons
  • "Azure API is scalable."
  • "The external policies are impossible to look at and configure."

What is our primary use case?

I am a software architect. The organization upgraded to API premium in order for us to be able to use virtual networks and security growth. We migrate things from Google Cloud. We use the solution to have an API that is calling internal resources to expose data on the internet. Furthermore, we also use API Management for partners and mobile apps.

What is most valuable?


What needs improvement?

Other than the cost, it is difficult to customize. The external policies are impossible to look at and configure.

The deployment time is too long. It is difficult to have multiple authentication mechanisms and authorization mechanisms at the same time.

Microsoft Azure API Management has not improved since I last used it in 2017.

By using Azure you are forced to use their technologies. For example, I wanted to use PostgreSQL, but I could only use SQL server. I also wanted to use Java or TypeScript, but the only option is .NET, which we do not use. They are very difficult to collaborate with as the solution does not integrate with other products. 

They do not offer extensions, if you want to use a Swagger extension you have to use XMLs, which are very complicated.

Another concern is that Microsoft Azure often does not have enough Linux machines in the region. If you want to deploy on Linux, and there are not enough, they will tell you to deploy in another region, or it has to be on the Windows server instead.

For how long have I used the solution?

I have been using Microsoft Azure API Management for two years.

What do I think about the stability of the solution?

The solution is a bit more stable than it was in 2017. It is reliable.

What do I think about the scalability of the solution?

Azure API is scalable. We have 20 people working with this product as a gateway to the outside world.

How are customer service and support?

Technical support with Microsoft is poorer than AWS, but better than the one from Google Cloud. They reply too late. We had premium technical support at one point, however, they did not reply with anything we needed at the time. There is a concern with the knowledge base as well as the procedure in how they are instructed to reply.

I would rate technical support a three out of five.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

We switched to Microsoft Azure API Management because two years ago, someone in the organization decided to use this solution. I would never have made that decision.

I have had prior experience with API Gateway and Apigee.

How was the initial setup?

The solution takes one hour to deploy. Like everything on Azure, it is difficult to create the deployment scripts because the ARM and Bicep that they use are awful. Deployment is very complex.

I would rate the experience of the setup of Azure API Management a two out of five.

What about the implementation team?

The solution doesn't require maintenance as it is cloud-based. However, it does require monitoring.

What was our ROI?

The upgrade to Azure API costs 2000 euros per month, per instance, per unit. Our finance department asked us to find cost reductions. After conducting an analysis, I came to the conclusion that it was impossible unless we sacrificed security.

What's my experience with pricing, setup cost, and licensing?

Azure API Management is the most expensive solution on the market. AWS is at least four times less expensive. Any price comparison needs to include the additional cost of the security you will need to purchase from Microsoft, which comes from their premium plan. The only way to reduce the cost is to sacrifice security when using Microsoft data.

I rate the pricing a one out of five.

Which other solutions did I evaluate?

The other option is API Apigee. It is the best in class and less expensive. Its deployment to API Gateway from AWS is easy and fast. 

In AWS API Management you can build everything from open API specification files. AWS has Swagger extensions that are built in that can define everything in Swagger.

I would switch solutions if I could. 

What other advice do I have?

Any organization looking to implement Microsoft Azure API Management should look at other alternatives. Be cautious of the marketing behind Azure products. Once you decide on your solution, it is difficult to change.

I would rate this product a four out of 10 overall.

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 does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Rajendra Dhaundiyal - PeerSpot reviewer
Technical Solutions Architect at a computer software company with 201-500 employees
Reseller
Top 10
Helps developers to securely expose their APIs to external and internal customers
Pros and Cons
  • "It's a very robust tool. So you see that there is a developer portal which can be used by developer or the vendors as well. And other external partners to create keys and manage their own APIs. The other thing is that they have a lot of policies there are too many options within API. So I do the difficult to tell one, but probably I would say, like, proxy sorry. The policies is one of the thing wherein you can just configure the policies and modify the behavior of the APIs."

    What is most valuable?

    It's a very robust tool. There is a developer portal that can be used by developers, vendors and other external partners to create keys and manage their APIs. 

    Enables you to configure the policies and modify the behavior of the APIs.

    What needs improvement?

    VNet integration facility is only available in the premium version so that is a drawback.

    For how long have I used the solution?

    I have been using Microsoft Azure API Management for six to seven years.

    What do I think about the stability of the solution?

    It is a stable solution.

    What do I think about the scalability of the solution?

    It is a scalable solution. The size of the clients depends mostly on the type of solution they are using. I rate the scalability an eight out of ten.

    How are customer service and support?

    The technical support team is easily approachable

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    The initial setup is easy. It takes a lot of time to deploy it. They are coming out with a feature that is supposed to shorten how long it takes.

    What's my experience with pricing, setup cost, and licensing?

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

    What other advice do I have?

    I rate the overall solution a nine 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.
    PeerSpot user
    Dmitri Efimov - PeerSpot reviewer
    Integration Architect at MiBanco
    Real User
    Reliable, easy to set up, and efficient
    Pros and Cons
    • "We use Microsoft due to the stability of the company."
    • "One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection."

    What is our primary use case?

    In general, we use it for the front application, like the mobile banking application or some other service stuff. We found that it's easier to maintain these internet connections and so on, on the cloud.

    What is most valuable?

    In general, we started with Microsoft Azure Cloud as we needed a close integration with our internal or Office solution. In case of Microsoft, Azure Active Directory is easily integrated within the Microsoft platform, including Office. In particular, in API Management, used as front-end APIs, it's easy to manage. Now, we are looking ahead to the hosted solution, which is very nice. 

    We use Microsoft due to the stability of the company. 

    It's efficient enough and it's just enough for our needs to manage rules and so aforth for API management. We use it due to Microsoft's reputation. We need a stable provider. We cannot play with some providers. 

    It is easy to set up. 

    The solution is scalable. It is stable as a product as well. 

    What needs improvement?

    It's okay. It's not as good as Google. For instance, in Apigee, in Google.

    One of the most important improvements for us would be if it supported the HTTP/3 version and new protocol over a quick connection. It's a relatively new standard since 2020. 

    For how long have I used the solution?

    I've used the solution for about three years. 

    What do I think about the stability of the solution?

    It is a stable product. It's reliable. There are no bugs or glitches. It doesn't crash. The performance is good. 

    What do I think about the scalability of the solution?

    While it is scalable, there is some costs involved with expanding. 

    We have about 100 people using the solution at the company in terms of deployment. In terms of clients using the solution, that's in the millions. 

    How are customer service and support?

    We have a premium subscription. We have a local company, a local Microsoft office. We do not have a problem with the support from Microsoft.

    Which solution did I use previously and why did I switch?

    We used a CA solution before, and CA was sold to Broadcom and everything changed, politics and so and so. We had to disable CA platform due to the provider. We believe the same issues will not happen to Microsoft.

    How was the initial setup?

    The initial setup is very easy. It's not complex at all. 

    What about the implementation team?

    There is a special group that is  responsible for the support and implementation of the platform.

    Which other solutions did I evaluate?

    I'm aware of Google, or Apigee, and it's quite a robust product. 

    What other advice do I have?

    We are a customer and end-user.

    It is a subscription service. It's definitely not on-premises in our organization. We do have our core system on-premises, of course.

    I would recommend the solution. People have to first understand the different types of subscriptions, however. There are four of them, developer, and intermediates, and then premium, and it's costly. That said, it's not that expensive. It's a very technical piece of software. I can say it's stable and it satisfies our needs. It's just a bit complex. 

    I'd rate the solution eight out of ten. 

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    Cxa Asda - PeerSpot reviewer
    Lead Cloud Operations at Liquid Telecom
    Real User
    Easy to set up with good access control but support could be better
    Pros and Cons
    • "Access control is the most valuable aspect."
    • "The integration with other API gateways is where they might try to improve."

    What is our primary use case?

    There's a customer who wanted to migrate their API from their on-prem environment to Azure. They're looking at utilizing Azure API to manage all their other APIs. We just started with migrating one of their APIs. They're still working with it, still trying to learn the difference between what they had for on-prem and Azure. We are in the process of actually migrating a lot of their APIs.

    What is most valuable?

    Access control is the most valuable aspect. It's the main reason really why a lot of clients are moving - as we are able to deploy multiple APIs and be able to also segregate who's got access to which API, who's got access to the other API. That centralized management is what the customer is really looking for.

    The initial setup was okay.

    What needs improvement?

    The solution isn't missing anything. For the use case that we have right now, it's perfect. It offers everything that you'd look for in an API Management solution.

    There's a new developer portal that's been added before they rolled out the new updates. I haven't really checked it out, however, the developer portal that they introduced is better than before. They've really improved on that one. If you are using the old portal, it's not as good. 

    We have two different customers. The other customer wants us to move completely, to migrate their APIs to Azure. The other one wants to manage their APIs, which are running on-prem. I've explored that in the flexibility, in terms of integration with an on-prem environment. The integration could be improved for those on-prem use cases. 

    The integration with other API gateways is where they might try to improve.

    Support could be better. 

    For how long have I used the solution?

    I started using the solution six months ago.

    What do I think about the stability of the solution?

    In terms of stability, I have seen that it is packaged into four different plans. If I'm not mistaken, there should be basic, standard, conception, and developer. I wanted to try to avoid deploying a lot of units, it uses a concept of compute units or scaling units. I was using the conception tier, which is not designed to be highly available. I was testing features, I didn't mind the level of availability. I suspect that if you choose the high-end SQL, it's most likely to be available. However, in terms of cost, I'm yet to find that out.

    What do I think about the scalability of the solution?

    If you compare the SQL, and that's one that really supports scalability across regions, it's good. It's very scalable.

    We have ten developers using the solution right now. 

    We do plan to increase usage. 

    How are customer service and support?

    Microsoft is huge, and when it comes to support, it's not so great as compared to, if you have something software specific. Whenever you ask them a question, they assume you to know everything. It's challenging to get the level of support that you'd want.

    How would you rate customer service and support?

    Neutral

    Which solution did I use previously and why did I switch?

    We used to use Kong. 

    Kong is more of an on-prem API gateway, and this one is cloud-based. And given that many customers are migrating to the cloud, it was actually one of the reasons why we're convincing the customers that we have used their APIs to migrate to the cloud. 

    How was the initial setup?

    The initial setup was pretty straightforward. 

    I have a basic understanding of the API fundamentals. Those were what I was looking for; that's what I was looking for first, just to see if my understanding of the fundamentals. With my level of knowledge, it was fine. 

    For someone with basic knowledge, you can deploy the solution within a week. 

    There is some maintenance needed. However, that person is supposed to be someone who's more DevOps inclined.

    What about the implementation team?

    We handled the initial setup in-house. 

    What's my experience with pricing, setup cost, and licensing?

    I've been using the conception tier. If you choose the lower-end tiers, it'll be fine, cost-wise. However, those tiers are just for development purposes; they're not really for the production environment. I would suspect if you move onto the higher tiers, it'll be pretty pricey.

    Which other solutions did I evaluate?

    I was looking into Azure API Management and the equivalent and in AWS.

    I wanted to compare the functionality between Azure API Management and Amazon API Gateway, as there's a customer that wants AWS API Gateway instead of Azure. I just wanted to see if the features are similar. I'm looking into that now. 

    What other advice do I have?

    We're a Microsoft partner. 

    The role that I have right now is a role where I'm a deployment engineer for cloud services, so depending on what the customer wants, someone's migrating from their on-prem, from VMware, the Linux, the Hyper-V to Azure, someone has to design highly available solutions, like applications that are tiered, that is three-tiered or two-tiered. Some want to utilize API Management. With API Management, we don't have a lot of customers on that front, as they sort of don't understand how it works. Right now, it's an area where we've worked with two of our biggest customers that have got multiple APIs on their on-prem environment. I've got basic experience, especially on what an API is and the benefits of Azure API Management as compared to what they have.

    We're using the latest version of the product.

    We are completely moving our customers from their on-prem APIs. It's a complete cloud solution; they don't want any hybrid solution.

    I'd rate the solution six out of ten based on the level of knowledge I have. The learning curve is pretty high. It's API Management and it also supports API gateways. It didn't decentralize those features, so the learning curve that's there for someone is a bit much.

    I would recommend the solution to others. 

    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
    PeerSpot user
    Buyer's Guide
    Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros sharing their opinions.
    Updated: August 2025
    Product Categories
    API Management
    Buyer's Guide
    Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros sharing their opinions.