Microsoft Azure API Management Reviews

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.

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.

Microsoft Azure API Management provides customers with customized solutions for various use cases and situations, allowing them to deploy their API strategy and products while also managing and protecting APIs.

It provides solutions for architecting, deploying, and monitoring APIs with other Azure services. 

Users can manage their complete API lifespan using Azure API Management.

The most valuable feature of Microsoft Azure API Management is monitoring.

When compared with Apigee, I prefer Microsoft Azure API Management.

When comparing the API Gateway of Microsoft Azure API Management with those of Apigee and Vital Mikram, which are other API management solutions, I prefer, Vital Mikram, the others are similar.

I would like to see more integration with other platforms, as well as increased security.

I have been working with Microsoft Azure API Management for ten years.

Azure has both a certificate and a level certification.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is a scalable solution.

We have ten users in our organization.

We have a team of five to ten technicians to maintain this solution per unit.

Technical support is good.

The initial setup is straightforward.

It was deployed very quickly.

We deployed it ourselves. It was done in-house.

The price is comparable.

In my opinion, it is similar to Apigee.

I would rate Microsoft Azure API Management a seven 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.

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.

Microsoft Azure API Management is used for platform deployment, hosting, virtual servers, third-party integrations, and the Azure Marketplace.

Without a doubt, it has a very robust, strong marketplace where we can directly integrate with existing APIs and begin working on those.

Microsoft Azure API Management is a secure solution.

It should be easier to integrate.

We are in the process of migrating from Amazon AWS to Microsoft Azure API Management. We are just getting started, we have been using it for a few weeks.

Microsoft Azure API Management is a stable solution.

Microsoft Azure API Management is definitely a scalable product.

It is not based on how many resources will be used, but we will be using three virtual machines from the Azure platform.

We plan to increase our usage.

We are Microsoft partners, MSP, and we have our own service providers to support this activity.

We use Google Workspaces and our platform is on Microsoft Azure.

Previously, we were using AWS EC2 Instances, but because we are a Microsoft MSP and also took into account the Active Directory capabilities and the Azure Marketplace, we decided to shift more to Azure.

The initial setup is more or less straightforward.

It took a couple of weeks to complete the entire migration from Amazon AWS to Microsoft Azure API Management.

Licensing fees are paid on an annual basis.

At the moment, we are not using CRM solutions but we are looking into Zoho CRM.

We had planned to use Salesforce, but we changed our minds and decided to use Zoho CRM instead.

I would recommend this solution to others who are interested in using it.

I would rate Azure API Management a nine out of ten.

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.