Microsoft Azure API Management Reviews

I'm in the telecom domain and I have used Microsoft Azure API Management in cost and order management in the order process.

Microsoft Azure API Management's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system.

I have been using Microsoft Azure API Management for approximately one year.

Microsoft Azure API Management is stable.

Microsoft Azure API Management is 90 to 99 percent scalable. We have three instances running in parallel.

We have approximately 500 to 800 internal users using this solution with three applications in operation.

We do not have plans to increase usage.

We have not contacted technical support. We have our own team.

The cloud deployment of Microsoft Azure API Management could be better.

Our team of 14 to 15 members implements and supports the solution.

I would recommend this solution to others.

I rate Microsoft Azure API Management a seven out of ten.

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.

We use this solution to integrate with a third party with API integration.

So far, we are satisfied with the product. The stability and performance are good.

It is easy to install, and it scales well too.

The technical support is good, and we get prompt support.

It could be more user friendly for developers. It would be nice if developers could view things more easily.

I've been using this solution for nearly six months.

It's a cloud-based solution.

So far, there's good stability, and we have not had any issues with it.

Because it is on the Azure platform, it is always scalable and is easy to scale as well. If you want to use it more, then we can add more resources.

We started using Microsoft Azure API Management six months ago as a POC, and now it's online. We probably have about 30,000 users.

We hope to increase usage by moving all API onto API Management.

Microsoft's technical support is good. We have the premium support package, so we get support straight away. 

The initial setup is straightforward.

Because you need to define the API contract, initially it may take about two months. However, this is not due to the Microsoft product.

We had our internal consultant handle the implementation. We had a team including an integration engineer.

We pay for a yearly license.

I would recommend Microsoft Azure API Management and would rate it at eight on a scale from one to ten. 

We are in the healthcare industry, so all the applications which are related to one hospital, it binds to Microsoft Azure API Management, and this is our use case for it.

I like the integration function of Microsoft Azure API Management. Integration of this solution is easy.

There's some area for improvement for this solution's performance. Sometimes it can be challenging. We're working with design patents and we're hoping to see the performance issues sorted out.

We've been working with Microsoft Azure API Management for a year now.

Microsoft Azure API Management is a stable product, but we have not been able to test it yet on a multi-cloud environment.

Microsoft Azure API Management is scalable. There are no issues with its scalability.

Microsoft has a good technical support team. They are very helpful.

Integration of this solution is easy. I won't call it an initial setup. It's an integration.

I was able to work with Apigee.

We used Microsoft Azure API Management only in the Microsoft environment, but not in a multi-cloud environment.

Microsoft Azure API Management is cloud-based, in particular, it is a single cloud centered around Microsoft components and not on the Cross components.

I have no idea on how long it took to implement Microsoft Azure API Management. The testing and development team is the best resource on how long it took.

The number of users of this solution in the group I'm associated with is 300,000. Increasing the number of users will depend on the mergers and acquisitions, and how the group is doing.

For maintenance, we have a backend support team that handles application support. The major point is that if the API has a lot of issues, particularly in data silos, Microsoft Azure API Management has made it more convenient to manage those.

We're still trying and testing the integration function of this solution, and we're also trying to go deeper into its performance.

My rating for Microsoft Azure API Management is a nine out of ten.

I don't have any variance data with Apigee. Apigee is better than Microsoft. I have more numbers for Apigee compared to Microsoft.

We primarily use the solution to manage our APIs.

The ease of use of the solution is excellent. It's a very user-friendly solution. 

The initial setup is quite straightforward. 

We found the solution to be very stable.

The solution can scale if you need it to.

Technical support is very helpful.

The solution has very fair pricing.

The lack of wording in the API could be improved. In the API you need to delete the suffix. It is annoying that you need to have a suffix. We can add a suffix at the API level, not at the operation level, and that could be improved on.

There are a couple of features that are lagging.

I've been working with the solution for five years or so. It's been a few years at this point. 

We have found the solution to be quite stable. There are no bugs or glitches. It doesn't crash or freeze. Its performance is reliable. 

The solution scales well. If a company needs to expand it, it can do so with relative ease.

We have about 15-20 users on the solution so far.

Technical support has been very good. They are quite helpful and responsive. We are very satisfied with the level of support provided to us.

The initial setup is straightforward. A company shouldn't have any problems during the process.

The cost of the solution is very fair. It's not overly expensive. It offers very good value.

We are Microsoft partners.

I'd recommend the solution to other individuals and organizations. Overall, I've been quite satisfied with its capabilities.

I'd rate the solution seven out of ten.

We have company-wide APIs which are hosted in Niger, and some of the external clients access the applications via the API, and we provide the post-data information. The clients get their data from our larger API.

The way the API management handles the calls and call throttling is excellent. 

The API management and the hosting of the API platform are great.

We haven't used API model that much, so I'm not in a good position to say recommendations as we are still exploring the Azure API management. We need more time to fully take in the solution before pointing our its flaws.

The documentation could be improved for the customer. The instructions on the district API and the initial stages of working with the solution need to be documented better so that users are more informed and they can have an improved experience.

I've been using the solution for three years now.

The stability of the solution is good. We haven't had any issues. I can't recall bugs or glitches. It doesn't crash or freeze. It's reliable.

The scalability of the solution is very good. If a company needs to expand it, it should be able to do so quite easily.

Currently, we have between 500-600 users in our organization on the solution.

We haven't really used technical support too often. Therefore, I can't really speak to their level of knowledge or responsiveness to issues.

We previously used IBM Open Shift. We switched due to the fact that the company was going to Azure and we didn't want multiple clients.

The initial setup isn't too difficult and doesn't take too long. You need to handle it to have the management gateway. Of course, every time it is deployed, then it needs to be configured to work with API. That could take some time.

For the deployment and maintenance, the size of the team you need depends on the project. We had a couple of developers on ours, for example.

I assisted with the implementation. I tend to handle it myself.

It's my understanding that the licensing is very clear. However, I'm not involved in it in any way, and therefore, I'm not sure what the cost structure is. 

We're just a customer. 

We do plan to continue to use the product going forward.

I'm not sure if I would recommend the solution. It depends on how their organization and architecture is, and if they're doing on-prem or cloud, depending on the requirement. It's very hard to say.

That said, I would rate it overall at 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.