Microsoft Azure API Management Reviews

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.

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.

Microsoft Azure API Management is used for integration across multiple services, API marketplace solutions, and information exchange solutions.

The most valuable features of the solution are its importing and publishing.

The solution’s security and performance could be improved.

I have been using Microsoft Azure API Management for four to five years.

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

Our clients for the solution are small, medium and enterprise businesses.

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

Microsoft provides good premier support, but its general customer support is not that great.

Neutral

I rate Microsoft Azure API Management a seven out of ten for the ease of its initial setup.

The solution can be deployed in five to ten minutes.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten.

Microsoft Azure API Management is a cloud-based solution. Microsoft Azure API Management is a flexible, scalable, and easy-to-use solution.

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

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.

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. 

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

I used it for six months.

It's a stable 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.

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

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

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

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

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.

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

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.

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. 

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

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

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. 

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

Positive

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

I have witnessed an ROI while using the solution. 

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.

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.

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

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. 

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. 

I have been using the solution for four years. 

The solution is stable. 

The solution is scalable. 

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. 

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

We implemented the solution in-house. 

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

The solution's support is very good. 

I rate the solution an eight out of ten. 

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.

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.

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

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

It is a stable 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.

The technical support team is easily approachable

Positive

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.

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

I rate the overall solution a nine out of ten.