Microsoft Azure API Management Reviews

We use Microsoft Azure API Management for integration. We use it for managing, monitoring, and integrating with other systems, for example, for asset management and monitoring tools. If we want to integrate or enable monitoring and management, we use Microsoft Azure API Management.

What I like most about Microsoft Azure API Management is that it's flexible and user-friendly. The solution also has rich documentation and guides available, so users can configure and use it.

What would make Microsoft Azure API Management better are more APIs. They keep updating their APIs, but it would be better if the solution had more APIs for the services and more integration with other platforms.

I've been using Microsoft Azure API Management for the last six to eight months.

Microsoft Azure API Management is a scalable solution. You can customize it, and you can also use your scripts with it.

The installation process for Microsoft Azure API Management was easy.

I don't remember licensing information or costs for Microsoft Azure API Management.

Microsoft Azure API Management is used by over a hundred development teams for developing solutions, including integrations. Currently, there's no plan to increase its usage.

I would recommend the solution to other people who want to start using it.

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

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.

We are publishing microservices using API management. We have created various packages and policies that we are applying over there. We have also created a portal for developers so that they can see what we are doing.

The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API.

It is possible to combine APIs and make a new product, which is a very good feature.

It is very user-friendly and easy to use. 

This solution is only available as a cloud-based deployment and it would be very helpful to have an on-premises version. This is driven by the fact that some of our clients have specific requirements and they do not want to be on the cloud.

I would like to have an administrator's option that shows me API usage and can generate bills that I can send to my customers. Currently, our customers can see the usage but not how much it is going to cost. For example, assume that you get 100 calls for free and then 100 more free each month, but after than, each call costs twenty cents or one cent, whatever the price is. The administrator can generate reports when the bills are available and can charge them to the customer. This could be done with a monetization module, which would be better than the manual calculations that we have to do now.

I have been using Azure API Management for almost one year.

I think that this is a stable solution.

Microsoft handles the scalability so you don't need to worry about it.

Microsoft's technical support is okay. On a scale from one to ten, I would rate them an eight.

Your first response will be fast but after that, it will be slow. Then, the technician might just say that they are not the right contact. From opening the ticket until final closure will take time. Generally, it takes the experts some time to comment. Unfortunately, everywhere is like that.

We did not use another API management solution prior to this one. We were developing applications and then moved into APIs.

The initial setup is very simple. Within a few days, one can understand completely how to use it. It does not require deployment because it is available on the cloud and everything is ready. In fact, there is no installation at all.

It will take some time to onboard your API and define your policies, such as those for security. It should take about ten minutes to get up and running.

We considered other options; however, our client is mainly a Microsoft shop and they were already using Azure for various things. As such, we did not fully evaluate other options. 

This is absolutely a solution that I would recommend for others.

I would rate this solution a nine out of ten.

• 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.

The tool helps to manage APIs. 

The tool does what it's supposed to do. 

The product needs to introduce a developer portal. 

I am working with the tool for ten years. 

The solution is stable. 

My company has around 20-30 customers for the solution. Each customer can have about 100 users for the tool. 

Microsoft support is good. We have regular sessions with Microsoft where we can have private previews of new features. 

The tool's setup depends. If you use it in the CI/CD pipeline, then the setup is complex. To deploy the solution, you need to create a template and enable the features. 

There are different tiers for pricing. You can even use the free version. 

I would rate the product 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.

• 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.

We primarily use the solution for storage. It’s for a database backup.

We really like the scalability.

It’s easy to set up.

The cloud deployment performance could be better.

Technical support could use some improvement.

I’ve been using the solution for three years.

It is stable. However, its performance is not better than an on-premises deployment.

The solution can scale and is easy to expand. It’s actually quite impressive.

We have about ten clients using the solution.

Technical support could be better. There’s a lot of bouncing around. It’s not orderly.

It is a straightforward setup. The implementation is not difficult or complex. The deployment is quick as well. It only took two or three days to get everything up and running.

We have about five technical people who can handle the setup and implementation process.

We are a Microsoft-managed partner, so we do have some pricing from the distributor.

The licensing is dynamic as it is based on cloud usage.

I can recommend Azure Block Storage to other people. However, they need to have an open mind in order to use cloud storage.

I’d rate the solution an eight out of ten.