Microsoft Azure API Management Reviews

I have been using Microsoft Azure API Management as a consultant, primarily recommending it for enterprises.

The solution helps in securing AI projects by providing governance and control through API management.

The most valuable feature is its role as a linchpin in AI Hub architecture, enhancing data handling.

The pricing model needs improvement, as some enterprise features are expensive.

I have been dealing with Microsoft Azure API Management for a few years.

Generally, I am satisfied with the performance, scalability, and technical support.

The performance and scalability of the solution are good.

The technical support quality could be better, although the issue is not significant.

I did not work with anything similar before Microsoft API Management.

I did not face any issues during the initial setup.

I did not face any challenges with the implementation.

Some of the enterprise features are quite expensive. A better pricing model is needed.

I recommend considering Kong if Microsoft API Management does not fit the budget.

I would recommend Microsoft Azure API Management to those on the Microsoft platform. If not on Azure, consider looking into Kong.

I'd rate the solution eight 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.

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.

We use Microsoft Azure API Management with our coding.

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

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.

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

I am finding Microsoft Azure API Management stable.

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

My current experience with technical support has been good.

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.

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

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

There is no investment funding or upfront cost needed. 

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

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

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.

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.

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. 

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. 

I've used the solution for about three years. 

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

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. 

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.

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.

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

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

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

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. 

We use this product for Epics, Story and Function Management for Products and Accelerator Development, Deployment and Operations Management.

This is a One Place solution for the majority of needs in an IT and Software development environment.

Microsoft Azure API Management is better because it has a DevOps integration by default.

It would be better if it were easier to transition to Azure from JIRA. For example, there are different nomenclature that must be addressed when you shift to Azure from JIRA. JIRA's storage, tasks, and epics are treated differently from Azure. 

Here they might become functions, which is not an option in JIRA because that nomenclature difference is there. 

JIRA has sub-tasks, but sub-tasks don't exist in Azure. The nomenclature and the linking between Epics and a function and a story are different, and people may have to learn to adapt to the new nomenclature.

I have been using Microsoft Azure Project Management for about Two and a half years.

Microsoft Azure API Management is pretty stable. We are Microsoft gold partners, so we have not faced any issues until now.

Microsoft Azure API Management is scalable. The Microsoft platform supports my organization, which is 35,000 employees strong.

Technical support is pretty good. 

We were using JIRA which can be enhanced by using third-party tools, this is a costly business so we shifted to the Microsoft platform, which was integrated for development as well as management. So that's a better way of doing things.

The initial setup is straightforward. It was an organization-wide integration, so we have never faced any issues.

It's free for less than ten users. If you want to go beyond that, its paid. But when you use all features of Azure its a very cost effective solution.

Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all enterprise flavor with very optimum cost, when compared to multivendor environment.

I would tell potential users to go for it. It's a good platform. Even though the ecosystem may not be that strong, it's a better option for a software development company. You can explore other options to save some bucks if you are not into software development. However, for an IT company, Microsoft Azure is the better option.

On a scale from one to ten, I would give Microsoft Azure API Management an eight.

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. 

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. 

We've been using Microsoft Azure API Management for integrations across different platforms.

Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.

The solution's integration suite needs improvement.

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

Microsoft Azure API Management is a stable solution.

Microsoft Azure API Management is a scalable solution.

We have previously used a lot of solutions, including GCP (Google Cloud Platform).

The solution's initial setup is pretty straightforward. However, more public documentation could have been available from other open communities. The solution is still being improved, and insufficient documentation is available on public forums.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven or seven and a half out of ten.

Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation. Therefore, big organizations should definitely consider using it.

Overall, I rate the solution an 8 out of 10.

We use the solution for API management. 

The tool's most valuable feature is the integration of CI/CD with the API gateway. 

Microsoft Azure API Management needs to improve stability. 

Microsoft Azure API Management is stable; I rate it an eight out of ten. 

I rate the product's scalability a six to seven out of ten. 

The cloud-based version is not difficult to deploy. Microsoft Azure API Management's deployment depends on the API numbers customers want to onboard. It takes around four to six months. 

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