Microsoft Azure API Management Reviews

Most of the features are valuable to me. We are actively exploring the monetization aspect of Azure, and we are also working on a proof of concept to accomplish this.

The only complication I encountered was configuring the authentication in the API Management. That was a little difficult for me, but it gets better after that.

I could that the UI could be improved. All services have the use of Visual Studio to do the coding and to change the configuration. It would be beneficial to include that with Microsoft Azure API Management.

I have been working with Microsoft Azure API Management for more than two years.

Microsoft Azure API Management is a stable product.

It is easy to scale Microsoft Azure API Management.

We have fast-track support from Microsoft, which we do receive.

We are satisfied with the technical support of Microsoft.

The initial setup was simple, with no complications, other than the configuration of the authentication in the API Management.

Since everyone is isocentric here, it is reasonable for me. Rather than getting complicated with other licensing, and other products' licensing. There are many, many different types of licensing available in other products, such as perpetual for ten users. If you want more than ten users, you'll have to pay a higher license fee. As a result, we are not falling into those kinds of traps. Previously, we had to pay as you go.

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

My primary use case is as part of a multi-channel strategy wherein APIMs are being used with micro-products or third-party clients. Our web application firewall receives all the external and public traffic, and it re-routes to the APIM, which is on the private subnet. The APIM manages both in authentication and authorization service composition layer.

One thing that could be improved is to remove the dependency of Kubernetes as an external L4 load layer balance. It would also be useful if APIM could integrate internally with Kubernetes right out of the box.

I have been using this solution for around two years.

General support has been very good, but sometimes when immediate support is required, it isn't available.

The initial setup was quite easy as it is a managed service.

I used a managed service to implement.

I would rate this product as seven out of ten.

We use the solution for API management.

The most valuable features are the API and integrations.

The implementation has room for improvement and can be more user-friendly.

I have been using the solution for one year.

I give the stability an eight out of ten.

The technical support team is good.

Positive

I give the initial setup an eight out of ten. The deployment took one business day. We require two people to complete the implementation.

The implementation is completed in-house.

Compared to other solutions the cost is a seven out of ten.

I give the solution an eight out of ten.

We have an Enterprise Agreement with Microsoft, so they are providing whatever support or help is needed.

For people that are already using other Microsoft Azure solutions, I recommend Microsoft Azure API Management.

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.

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 use it to manage the API. We have a backend API with service in the backend. We use API Management in the front to manage the vendors. They can do their own testing. It's quicker for us to put in the specifications so we can knock off the responses. We build the specs and then get an external developer to start the development without the web service being ready. 

We also use it for the security and for the clock in features.

It's easy to use compared to other products. It's easy to set up.

Other products offer more customization options. 

I have been using this solution for six months. 

We haven't had any issues with it since we set it up. It's quite stable. 

We don't need to worry about scalability. We just use it. It works on demand because it's on the cloud. 

We are not a Microsoft shop, we just started using it. We haven't contacted technical support yet. 

I also used Tibco Mashery. There aren't so many differences. The biggest difference is that you can run it on-prem while you can't do that with Microsoft Azure API Management. 

The initial setup was pretty straightforward. It took less than one day, around a couple of hours total. It's pretty quick. I deployed it myself with some product documentation. 

You can't use this on-premise. If you want to run on-premise you would have to get a different product. Other than that, it's easy to use and start up. There is a lot of support available from the community online. You can do a domain name yourself with Microsoft, as opposed to other products where you need to contact support in order to set up a domain. 

I would rate it an eight out of ten.  

I can't give a ten out of ten because I'm not experienced enough with it. So far so good, though. 

We are a software firm and this is one of the solutions that we provide for our customers.

The package as a whole is useful for our customers.

The API gateway, when it is deployed, is not as robust as Apigee.

I would like to see better scalability and better performance. Performance is important for us.

I have been using Azure API Management for the past two or three years.

Stability-wise it has a ways to go, although it has also come a long way since we first started using it. The issues that we have had are related to performance. Otherwise, it should be fine.

Scalability is something that is still maturing.

I have been in contact with Microsoft technical support and I would say that it's good overall.

We have also used Apigee and Azure API Management is not as robust.

I would not say that the initial setup is easy or tough, but in the middle. It can be difficult in that you need to know the components in order to use this solution to its full extent.

The length of time required for deployment depends on the use case and what we are building. It can take a month or sometimes, three months.

We do not use one particular feature over another. Rather, it is the whole package that is useful.

I would rate this solution a six out of ten.