We changed our name from IT Central Station: Here's why

Microsoft Azure API Management Room for Improvement

Vice President - Competency and Channels at Techwave.

Nothing in specific but there is always some improvements that can be made to user interface to enhance and improve the UX experience. 

As Microsoft adds more an more services to the stack will help and enable to ease the API platform integration with other ERPs and various platforms for us. There are more APIs coming out with lot more enhanced services that include IOT connected device integrations. Any help in understanding available API protocols and edge protocols easier will help us building our solutions faster.  We do see different services are being added day by day.

We are not using all of services at this point, but we are leveraging few at a time and building our solutions.  This is part of the evolutionary and exploratory based journey to transform the ecosystem of the customer to a digitally connected growth organization.

View full review »
MB
Enterprise Infrastructure Architecture at a tech services company with 1,001-5,000 employees

R&P, the publishing process could be improved. They are currently restructuring it, I believe.
I'm not technical but we noticed that the old developer portal got deprecated and they're introducing a new one. It's not polished and still requires some development. It's the same with the publisher portal which I believe they've now integrated into the Azure portal. They're just starting to work with hybrids so it still requires input. 

It would be helpful if they were to include additional features and clearer configuration when it comes to API policies.

View full review »
Senior Manager, Engineering at GlobalLogic

Pricing is definitely an aspect that can be improved. They should offer an additional free tier. For example, if there was a tier for new accounts created, it may help their services by getting people onboarded. Once you will give access to someone and they try it they'll see, "Okay, it works and you can pretty quickly add something on top of it". After that, the client will end up staying, and probably paying.

The cost is also complex in terms of calculating how much everything will ultimately be priced at. It's not straightforward as it takes into account multiple factors.

Technical support could be more flexible and try to meet the client's needs a bit more effectively.

The solution needs to provide more use cases so that we can refer them to clients. It will help answer any questions in relation to performance and load management.

View full review »
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,148 professionals have used our research since 2012.
GD
Group Manager, Solution & Technical Architect at a tech services company with 10,001+ employees

If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be.

In an upcoming release, if not already added through an update, I think dynamic provisioning of the resource would be useful. Many times these API platforms, including others, such as Apigee, are still predominantly revolving around developers. The onboarding and the API life cycle are still revolving around humans. In this context, I would not suggest DevOps, but at least automation of common pipelines. If the platform can better support this in the workflow to provision and commission an API that would be beneficial as we work towards a more automated deployment concept. Even though there are templates, graphics, and API management commands right now, you are still in a way programmed deeply, customizing that workflow, as opposed to it being part of the platform itself.

View full review »
Principal Consultant at a tech services company with 10,001+ employees

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.

View full review »
SK
Solution Architect at a sports company with 201-500 employees

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.

View full review »
IT Enterprise Architect - Middleware & Integration at a comms service provider with 10,001+ employees

The portal where we publish the APIs could be improved. Maybe this is because we didn't configure it. It is quite easy to bypass API management because we have a lot of information shared on the portal, where we publish our APIs. I worry there is potential for a security breach in the API publishing. There needs to be more security available on terms of the way we publish them.

View full review »
Enterprise Architect at Pink Brain Technologies

They're trying to implement versioning and trying to be able to manage different versions of your API all at the same time, but they're not doing that just quite right yet.

View full review »
AN
Lead Solution Architect at a tech services company with 1,001-5,000 employees

From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance. Examples include, how you manage all your clusters, the entire service communication, and having more tolerant experts.

View full review »
Managing Director at Ebiz consulting gmbh

Multi-tenant functionalities is missing from the system, especially when it comes to purpose specific requirements such as CI, branding, language, content structure. If you're aware of the details of API Management provided by Azure, there are two areas. One is for developers, and the other is for consumers. In order to support the best, or all the different use cases we have, the multi-tenant support would be appreciated.

View full review »
Integration Architect at a wellness & fitness company with 5,001-10,000 employees

Other products offer more customization options. 

View full review »
SA
Integration Architect at a translation and localization position with 11-50 employees

There is always room for improvement. There should be more analytics abilities so you can know how much traffic there is. Log Analyzer isn't well integrated with this solution. 

View full review »
PP
Senior Solutions Architect at a manufacturing company with 10,001+ employees

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.

View full review »
JL
Branch Manager at a insurance company with 1,001-5,000 employees

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. 

View full review »
Head - Data & Digital Service line(s), BFSI Cluster at slk software

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.

View full review »
CO
Executive Director Finance & Strategy at a consultancy with 51-200 employees

The licensing fees should be cheaper.

View full review »
MS
CEO at a tech vendor with 11-50 employees

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

Better integration with third-party products would helpful.

View full review »
Senior Cloud Architect at a healthcare company with 10,001+ employees

One thing that could be improved is to remove the dependency of Kubernetes as an external L4 load layer balance. It would also be useful if APIM could integrate internally with Kubernetes right out of the box.

View full review »
Technology Architect Manager at ESB

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

View full review »
KH
System Analyst at a tech services company with 51-200 employees

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

View full review »
Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,148 professionals have used our research since 2012.