Microsoft Azure API Management Reviews

Our company has some internal APIs and we use Microsoft Azure API Management to help keep everyone on the same page.

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.

In a feature release, there could be a better Canary release. They have a release but you need to code it yourself.

I have been using Microsoft Azure API Management for approximately two and a half years.

We have approximately 30 people using the solution in my company.

The support from Microsoft Azure API Management is okay.

The initial setup of Microsoft Azure API Management took us three days.

We did the implementation of the solution in-house.

We are paying standard fees to use Microsoft Azure API Management.

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.

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 primarily use the solution for storage. It’s for a database backup.

We really like the scalability.

It’s easy to set up.

The cloud deployment performance could be better.

Technical support could use some improvement.

I’ve been using the solution for three years.

It is stable. However, its performance is not better than an on-premises deployment.

The solution can scale and is easy to expand. It’s actually quite impressive.

We have about ten clients using the solution.

Technical support could be better. There’s a lot of bouncing around. It’s not orderly.

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.

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.

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.

We have been using this solution to protect our APIs and to decouple our APIs between the host versus the outside world. It operates as a gateway pattern in front of the APIs.

We use this solution for API rate limiting and for its security features against DDoS.

The scalability of this solution could be improved. The volume which the API Management task service can handle needs to be improved. Cost wise, this solution could be optimized.

This is a stable solution.

This is not a scalable solution. 

The customer service and support for this solution is average. They have not been able to provide a solution to some of the challenges we have faced. 

Neutral

The initial setup is not complex as this is a PaaS-based solution.

This is an expensive solution. 

I would advise others to evaluate their volumes, nonfunctional requirements, and just check whether the NFR performance metrics of API Management has been met. Otherwise, better take a trade-off between, because we have gone through the hard path, tried everything using it, and then we have moved from API Management to Apigee.

I would rate this solution a seven out of ten. 

My primary use case is application monitoring.

We had all our Saas applications on the cloud, so it's easier to centralize everything in Azure, including configuration and maintenance. There's also no need to get another portal for maintenance on additional things, so we can monitor the issue directly.

The most valuable features are the Active Directory integration and wireless backup.

Azure API Management could be improved with better integration with all of Microsoft's tools. They should also provide basic cybersecurity tools in the package.

I've been using this solution for two years.

Azure API Manager is stable.

This solution is scalable.

Microsoft's technical support is helpful, although there are some issues with time zones.

Positive

The initial setup was easy - it didn't take long, and the additional features were added normally.

We implemented using an integrator.

There are no additional costs above the main license.

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. I would rate this solution nine out of ten.

I'm in the telecom domain and I have used Microsoft Azure API Management in cost and order management in the order process.

Microsoft Azure API Management's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system.

I have been using Microsoft Azure API Management for approximately one year.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is 90 to 99 percent scalable. We have three instances running in parallel.

We have approximately 500 to 800 internal users using this solution with three applications in operation.

We do not have plans to increase usage.

We have not contacted technical support. We have our own team.

The cloud deployment of Microsoft Azure API Management could be better.

Our team of 14 to 15 members implements and supports the solution.

I would recommend this solution to others.

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

The main uses of this solution are sharing data, internal integrations, and combining different backend services into one API proxy. In the latter case, we extract the whole complexity of the integration, and after the work is done, there's a proxy available that can be used and reused by API consumers.

The most valuable features are authentication and authorization. I would also argue that the mediation and translation from SOAP to REST technology is equally important because it makes it possible to open up legacy systems that couldn't be opened before.

An improvement would be to provide more information about additional prices and the onboarding process.

I've been using this solution since 2016.

Azure is very much stable.

This solution is very scalable.

You really need an expert to onboard the solution because it comes with more complexity than you might think. Also, internal teams often start playing with the solution during onboarding instead of sticking to best practices, which can result in having to start the process over again.

The ROI on API management as a concept metric that we are using in conversations is that we can reduce integration lead times by 90%. So, where an integration would take a hundred days before, we can deliver that same integration in ten days after implementing Azure.

Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft. However, 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.

Azure is the best-priced quality solution in the market. If you have business-critical processes running over API management, I would advise installing managed services either internally or from a partner to have that very close follow-up. I rate this solution eight out of ten.

I work with an enterprise and they needed to manage lots of APIs. They needed to manage information and they use this product to meet their needs.

The policies on offer are the most valuable aspect of the solution. 

The solution is reliable and very stable. 

I don't really have anything in mind at the moment in terms of areas of improvement. It does what we need it to do for the most part.

Technical support could be more helpful and responsive. They are quite slow. 

The documentation around the solution is lacking. Users will need to do a lot of digging and googling in order to get the answers they need. 

The premium version is very expensive. 

I've been using the solution for about two years now. It hasn't been too long at this point. 

The solution was stable. We didn't have issues with bugs or glitches. It didn't crash or freeze. it was pretty reliable and the performance was pretty good. 

Technical support was a bit slow, actually. We did engage technical support once or twice and it took quite a bit of time for them to come back to us. By the time they'd come back, we'd kind of solved the problem ourselves. They weren't overly helpful.

I'm just a developer, so I didn't really get involved in the pricing. Therefore, I can't speak to the exact costs of the agreements involved in terms of licensing. That said, I do know that we used the developer license just to try things out. My understanding is that the premium version is quite expensive.

I'm a customer and an end-user. My company does not have a special business relationship with Microsoft.

I'd rate the solution at a seven out of ten.

While technical support and documentation are lacking, I would still recommend the product to others.