Microsoft Azure API Management Reviews

The basic tier is pretty good. 

It's publicly available API Management.

The price is pretty reasonable for us. 

We need better integration with VNet. 

It would be nice to not only configure it through the interface but also with an ARM template or something like that. Maybe it's possible, but it's not that easy to find.

It took us time to get used to the interface. Now that we run it, it's a little bit hard to have a testing environment and the production environment and keep it synced. If you can do that through a script, that would be far easier. However, there was a time thing on our side. We couldn't get it done, and in the end, we just set it up manually.

The licensing tiers can be misleading. 

It would be ideal if there was a way to add monetization into the mix so that we could more easily sell our APIs.

I started using the solution about three years ago, and I use it now and again on a few projects. 

We didn't have a previous solution.

I wasn't directly involved with the implementation, and I'm not sure how long it took to deploy the product. 

Some of my colleagues implemented the solution. We did it ourselves using the documentation provided by Microsoft. 

We are using a basic tier. 

For the things we do, it's reasonable in terms of cost. You can implement it in the developer solutions. That's basically more or less free. But if you implement VNET in it there, you can only upgrade it if you use premium, and premium is so expensive. That's just no fun. That was a little bit annoying since you think you have a good solution in your development environment, and then you are in production and need a premium tier to have the same configuration. We had to reconfigure some stuff.

We also looked at Apigee, and Apigee has some integrated features, however, Apigee was very complex to get started with. Apart from that, we are a Microsoft company, and we're on the Microsoft stack. It was more logical to keep everything in Azure. That's why we chose Azure API Management.

We use Azure and it suits our case pretty well. It could be better, but we might also have to learn more. Currently, I would rate it at an eight out of ten for our use case. We might also want to use it in the future to sell subscriptions, which is not possible out of the box. You can configure subscriptions, yet you still have to do the whole selling and measuring and things like that. That's not fully integrated.

I use API Management for all of our AKS clusters.

API Management's price could be lower.

I've been using API Management for a year.

API Management is stable.

API Management is scalable based on the load.

API Management does not take long to deploy.

We used an in-house team.

I would rate API Management nine out of ten.

We use this solution to integrate with a third party with API integration.

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.

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

I've been using this solution for nearly six months.

It's a cloud-based solution.

So far, there's good stability, and we have not had any issues with it.

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.

Microsoft's technical support is good. We have the premium support package, so we get support straight away. 

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.

We had our internal consultant handle the implementation. We had a team including an integration engineer.

We pay for a yearly license.

I would recommend Microsoft Azure API Management and would rate it at eight on a scale from one to ten. 

They're doing integration work between a lot of different on-premises business platforms, like Salesforce and NetSuite. We're doing integration work, but we're putting all of our APIs into the Azure cloud and using that API manager at this time.

We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting.

They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet.

I have been using this solution for a year. 

We haven't had any issues with stability. Those things are pretty solid.

I haven't dug too deeply into how to scale it yet. My current customer doesn't have a high volume of stuff yet.

In terms of users, there are only two or three of us engineers that deal with it directly. We're running several dozen APIs that are production APIs.

I give technical support a solid B rating. They're not bad on doing support at all. They're not necessarily fast, but they're not bad.

It's very straightforward to set it up. It really is. That's one of its strengths, that it's very easy to get started.

The versioning makes deployments more complicated than you would like, so you have to build some of your own toolings.

Licensing is the tricky part. For Azure, if you have your Azure subscription, the API Management is a free tool. There's no extra cost for that. 

My advice would be to choose wisely. Look around. That's the free entry stuff, so that's why I'm kind of looking around for another tooling solution, to see if I can get more full-featured support.

In the next release, I would love to see them actually support out of the box, like a canary deployment pattern, or out of the box just a blue-green rolling deployment pattern. Right now, how you want to do your deployments, you've got to tool it yourself.

I would rate it a seven out of ten. They're not bad.

We are publishing microservices using API management. We have created various packages and policies that we are applying over there. We have also created a portal for developers so that they can see what we are doing.

The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API.

It is possible to combine APIs and make a new product, which is a very good feature.

It is very user-friendly and easy to use. 

This solution is only available as a cloud-based deployment and it would be very helpful to have an on-premises version. This is driven by the fact that some of our clients have specific requirements and they do not want to be on the cloud.

I would like to have an administrator's option that shows me API usage and can generate bills that I can send to my customers. Currently, our customers can see the usage but not how much it is going to cost. For example, assume that you get 100 calls for free and then 100 more free each month, but after than, each call costs twenty cents or one cent, whatever the price is. The administrator can generate reports when the bills are available and can charge them to the customer. This could be done with a monetization module, which would be better than the manual calculations that we have to do now.

I have been using Azure API Management for almost one year.

I think that this is a stable solution.

Microsoft handles the scalability so you don't need to worry about it.

Microsoft's technical support is okay. On a scale from one to ten, I would rate them an eight.

Your first response will be fast but after that, it will be slow. Then, the technician might just say that they are not the right contact. From opening the ticket until final closure will take time. Generally, it takes the experts some time to comment. Unfortunately, everywhere is like that.

We did not use another API management solution prior to this one. We were developing applications and then moved into APIs.

The initial setup is very simple. Within a few days, one can understand completely how to use it. It does not require deployment because it is available on the cloud and everything is ready. In fact, there is no installation at all.

It will take some time to onboard your API and define your policies, such as those for security. It should take about ten minutes to get up and running.

We considered other options; however, our client is mainly a Microsoft shop and they were already using Azure for various things. As such, we did not fully evaluate other options. 

This is absolutely a solution that I would recommend for others.

I would rate this solution a nine out of ten.

Microsoft Azure API Management provides customers with customized solutions for various use cases and situations, allowing them to deploy their API strategy and products while also managing and protecting APIs.

It provides solutions for architecting, deploying, and monitoring APIs with other Azure services. 

Users can manage their complete API lifespan using Azure API Management.

The most valuable feature of Microsoft Azure API Management is monitoring.

When compared with Apigee, I prefer Microsoft Azure API Management.

When comparing the API Gateway of Microsoft Azure API Management with those of Apigee and Vital Mikram, which are other API management solutions, I prefer, Vital Mikram, the others are similar.

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

I have been working with Microsoft Azure API Management for ten years.

Azure has both a certificate and a level certification.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is a scalable solution.

We have ten users in our organization.

We have a team of five to ten technicians to maintain this solution per unit.

Technical support is good.

The initial setup is straightforward.

It was deployed very quickly.

We deployed it ourselves. It was done in-house.

The price is comparable.

In my opinion, it is similar to Apigee.

I would rate Microsoft Azure API Management a seven out of ten.

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.

I like the integration function of Microsoft Azure API Management. Integration of this solution is easy.

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.

We've been working with Microsoft Azure API Management for a year now.

Microsoft Azure API Management is a stable product, but we have not been able to test it yet on a multi-cloud environment.

Microsoft Azure API Management is scalable. There are no issues with its scalability.

Microsoft has a good technical support team. They are very helpful.

Integration of this solution is easy. I won't call it an initial setup. It's an integration.

I was able to work with Apigee.

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.

We use the cloud model. Our primary use case is for integration between different systems. There are many use cases for the API management tool, but the most common scenario is integration between different systems.

The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production.

The developer console for external users could be improved, especially in the testing site. I would like to see the security management for the APIs to be more granular.

It is very stable.

It's quite scalable. We've tested it in different little scenarios and it's quite scalable.

For deployment, I would advise a specialist. There is no need to dedicate any staff to the maintenance of the solution.

I would rate their technical support an eight out of ten. It could use a bit of improvement. 

I previously used RabbitMQ for another project. Both solutions have different approaches. One can work on-premises. On the whole, I still prefer is Azure API Management. I believe it's an easier solution set up and run.

The initial setup was very straightforward and simple. The deployment only took a few hours. 

I deployed the solution myself. 

I would recommend this solution to someone considering it. I would rate it a nine out of ten.