Microsoft Azure API Management Reviews

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.

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.

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. 

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

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. 

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. 

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.

I am using Microsoft Azure API Management to connect external systems.

The solution has overall high performance.

Microsoft Azure API Management could improve by having better integration with third-party solutions.

In an upcoming release, there should be more focus on API lifecycle management, such as MuleSoft provides and the API gateway is not comprehensive enough, we need to put a lot of extra effort doing manual work. 

I have been using Microsoft Azure API Management for half a year.

The solution is stable.

For what we have been using the solution for it has been scalable.

Our company is a medium-size using this solution.

We have found some configuration that is not supported by the solution yet. There is room for improvement in their support.

I would rate the technical support of Microsoft Azure API Management a four out of five.

The setup and configuration are very quick.

The price of the solution is reasonable compared to others. 

We are still looking for a better API-optimized solution.

I would recommend this solution for some small and medium-sized projects, as it is quite easy and effective to start with. I am not sure if it is suited for large companies that have heavily loaded APIs which the solution might not be able to support.

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