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.

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.

Microsoft Azure API Management is used for making the API calls from our internal application to another available internal application or to the external third-party applications. It can be hosted in the public environment or it can be a client application to which we are making a call and teaching the information. This solution is useful for making the API calls between the application. 

The Application Gateway we have found to be the most useful in Microsoft Azure API Management. We have integrated the Microsoft Azure API Management with Application Gateway. Application Gateway is a type of load balancer that we are using for the high availability of our API calls. 

Microsoft is releasing new features approximately every three to four months on each and every solution. Although it's not mandatory that we are using all the features of this particular solution because it depends on the business requirements. Whatever the features the Microsoft Azure API Management has, we are happy with them and we are using them.

The solution is secure and has all the components that we require. We are using the solution with the best practices.

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

Microsoft Azure API Management is a stable solution, it has high availability.

The solution is scalable.

We have used technical support once or twice a year. However, there is not much technical assistance required.

I rate the technical support from Microsoft Azure API Management a four out of five.

The initial setup of Microsoft Azure API Management is straightforward. It took us approximately 30 minutes to complete.

I would rate the initial setup of Microsoft Azure API Management a four out of five.

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

The ability to easily connect back to Service Fabric is the most important for us.

The importing of existing APIs is extremely easy. It's one of the better products.

The main benefit is that we are already on ExpressRoute. It is easy to integrate into our local network. Because we are mostly a Microsoft shop, we mostly use Azure API management because we don't want to run in different cloud providers right now since we are a financial company.

Microsoft Azure API Management should have the ability to allow multitenancy.

While the solution works well for us, I would like to see simple or integrated reporting built into the solution.

There is always room for improvement.

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

Microsoft Azure API Management is extremely stable.

Microsoft Azure API Management is very easy to scale.

I don't have any prior experience. We haven't had any issues or needed to contact the product's technical support.

The initial setup is straightforward. It is very easy to set up.

Because everything is automated directly from our pipelines, maintenance is a very small task that we require.

It is very easy to deploy, and configure.

We are partners.

I would rate Microsoft Azure API Management an eight out of ten.

We primarily use the solution to manage our APIs.

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.

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.

I've been working with the solution for five years or so. It's been a few years at this point. 

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. 

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.

Technical support has been very good. They are quite helpful and responsive. We are very satisfied with the level of support provided to us.

The initial setup is straightforward. A company shouldn't have any problems during the process.

The cost of the solution is very fair. It's not overly expensive. It offers very good value.

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.

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.

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.

I've been using the solution for about a year at this point.

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.

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.

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.  

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.

I primarily utilize the platform for integrations, monitoring, and process automation within our business workflows.

The solution's configuration capabilities are the most effective features for enhancing API security.

The product's navigation feature needs enhancement. 

I have been working with the platform for approximately three to four years.

I rate the solution's scalability around eight or nine.

The support services are good. However, they could be improved. 

Positive

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.

I rate the solution's pricing between three and four, as it could be more competitive.

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.