Microsoft Azure API Management Reviews

I mainly use Azure APIM for access management.

Azure APIM's best features are its straightforward access management (it's a single point of access for all monitoring and logging and for policy implementation) and its integration with the Azure Cloud infrastructure.

In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment. They could also improve their access management portal.

I've been using Azure APIM since 2017.

Azure APIM is pretty stable.

Azure APIM is scalable.

If your services are built on the cloud, I think APIM is the best tool. I would rate APIM eight out of ten.

This solution is very flexible, and it's very compatible with the other Azure products.

The developer portal can be improved. There should be more resources available for the developers.

Better integration with third-party products would helpful.

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

This is a stable product and we intend to continue using it in the future.

We have more than ten users and there are five developers.

The support for Azure is excellent and we are satisfied with it.

The initial setup is very simple. It doesn't take longer than one or two hours to deploy.

A consultant assisted us with the deployment.

I would rate this solution an eight out of ten.

The Azure Active Directory Synchronization is quite good.

They should improve the inbuilt policies that they have and that should properly create a deployment architecture as well.

We have been using Azure for about a year. 

It is stable.

It is scalable. 

The price could be lower.

At the end of the day, all the products are one and the same, just that some of them have more features than others. That's all.

I would rate Azure a seven out of ten. Not a ten because I would like for them to improve on the number of policies it has inbuilt and for it to have better deployment architecture.

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. 

Our primary use case is to provide API mapping for our clients. We're a customer of Azure and I'm a system analyst. 

The most valuable feature of the solution is it's simplicity. It's easy to set up and is very well integrated with the Azure environment.

In terms of improvement, it would be helpful if they could develop an on-premises option. 

I've been using this solution for one year. 

I would rate this product a seven out of 10. 

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.

• Monitoring: It gives us a detailed overview of how clients are using the API and it allows us to see the consumption trends in real-time.
• Policies: It allows us to control and enrich the API behavior without the need to make code changes
• The documentation and configuration of APIs.

Internally, we use this product to give our employees a catalog of all the APIs that we implemented over the years. They get detailed documentation on how to use those APIs and can develop their own solutions on top.

Security could be improved.

I have used this solution for a year.

There were no stability issues.

There were no scalability issues.

I would give the technical support team a rating of eight out of 10 .

The setup was straightforward, setting up a basic API management portal is only a few clicks in the Azure Portal. Once it is set up, the APIs can directly be added by just importing the Swagger file.

The developer and standard pricing tiers of Azure API Management are very competitive compared to other products. If a customer wants to expose their internal APIs to the Azure API Management Portal, then they would require a VPN connection which requires the Premium Pricing tier. This can be expensive and we currently recommend our customers to not use a VPN connection, i.e., if they don’t need additional Premium features; and we suggest they expose their APIs publicly through other technologies such as the relay services.

Learn how policies work since this is where the real added value of Azure API Management is.

• API gateway features
• AD integration
• Access management capabilities
• Usage plans
• Quotas for APIs, etc.

It is a simple and effective way to enable micro-services architecture. The Standard Tier is cost effective.

• An IaaS option is needed. The SaaS option limited our requirement, as we wanted more control on our data, and integration with our virtual LAN. Integration with our VLAN was possible only with the premium version and expensive gateway controllers.
• PCI compliance

I evaluated it for one month.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Technical support is 7/10.

I did not previously use a different solution. However, I evaluated other API gateways and shortlisted ForgeRock - OpenAM/OpenIG, because it has an IaaS option.

Initial setup was fairly straightforward; excellent documentation.

The Standard Tier is cost effective.

Before choosing this product, I evaluated NGINX, Apigee, and ForgeRock (OpenAM/OpenIG).

Code impact: Required services to import Swagger library.

Being SaaS, if you are running services on IaaS, communication between APIM and your services will be through the public internet (if that’s a cause of concern).

APIM was available in classic mode only (as of April 2016). Our infrastructure was ARM. Connectivity was complex and expensive.