Azure API Management cuts out a lot of concerns that developers have. Developers can leave concerns like authorization, authentication, tokens, or any data shaping layer for their APIs to the API gateway or APM service. They can then focus on creating APIs and functionality that matter for the business.

Microsoft Azure API Management has many valuable features. One is the developer portal, that's very useful for teams. The tool also provides layers of security. I also found the caching, automatic documentation, and version management functionalities of Microsoft Azure API Management most valuable.

I like Microsoft Azure API Management because it works pretty well.

We're still in the early stages of exploring its full potential. It's a new implementation, so we haven't fully formed our opinions yet. But it's promising! We're cautiously optimistic about its capabilities.

The solution's most valuable feature is the ability to create policies. You can customize the business and security rules directly with it instead of creating new systems for managing the same. With this policy, you can develop anything with them.

I like the support they provide for the APIs more than the solution itself. First of all, documentation-wise, both Microsoft Azure and even Google Cloud are up there. But in comparison, the real-time consulting and support for APIs make Microsoft stand out a little.

I also like the performance. Standard public cloud provider-built APIs are more resilient and flexible in terms of what feature you want to use and what feature you don't want to use, and they're more customizable. They are more resilient in terms of performance in that particular environment because that is the design aspect of the offering.

When public clouds build APIs and deploy them after testing them on their framework for a certain amount of time, I feel there is a massive difference in the product's performance. On the interface, everything is strong.

API gateway-related features were fulfilled by APIM. So those features, we are completely leveraging for our solution, like throttling. It is fair and easy. It's a low-code, no-code model of API hosting.

The API management is great. It comes out of the box ready to go and comes with policies. 

It is stable.

Technical support is good.

We have witnessed an ROI.

All we need to do is run our specific code because the dependencies are already there. 

In general, we started with Microsoft Azure Cloud as we needed a close integration with our internal or Office solution. In case of Microsoft, Azure Active Directory is easily integrated within the Microsoft platform, including Office. In particular, in API Management, used as front-end APIs, it's easy to manage. Now, we are looking ahead to the hosted solution, which is very nice. 

We use Microsoft due to the stability of the company. 

It's efficient enough and it's just enough for our needs to manage rules and so aforth for API management. We use it due to Microsoft's reputation. We need a stable provider. We cannot play with some providers. 

It is easy to set up. 

The solution is scalable. It is stable as a product as well. 

The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation.

I like API Management's sandbox feature. It's an environment where you can test out the API before putting it into production and connecting it to a live environment.

Access control is the most valuable aspect. It's the main reason really why a lot of clients are moving - as we are able to deploy multiple APIs and be able to also segregate who's got access to which API, who's got access to the other API. That centralized management is what the customer is really looking for.

The initial setup was okay.

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. 

It is easy to use. 

The API management is very good. You have sophisticated dashboards that help you to understand what's really going on - in addition to whatever security layer that you can bring on top of that. It is easy to manage front and backend APIs.

You can put on your own security layer so that you know only the authorized people are accessing your back-end systems through the gateway. In addition to that, you have sophisticated dashboards and reporting for storage logs or logging. That is quite useful, specifically in the banking sector. 

You can limit items by parameters such as geography or private VPMs. 

You have different pricing tiers and pricing is based depending on the traffic. You can go to basic pricing if you like. Depending on your traffic, you have licensing options.

Microsoft manages everything so you can focus on building applications and deploying them.

The platform components are quite interesting. 

The solution has pretty stable capabilities.

Their construction tool allows users to easily publish information about the API. It's basically just one click.

You can configure the subscription management onsite and link everything.

The developer portal that exposed the API documentation is great. You can just test the APIs in a very easy way. 

The web portal is useful. You can build a pretty comprehensive portal where users can sign in and you can basically leave the API there.

The API management provided offers good integration with different management systems, like OpenID, for example.

The user management is pretty seamless.

I like that security features can be integrated with API Management. I also like that you can perform rate-limiting and throttling functions.

You can host multiple API gateways in different locations. If one goes down, then another will take over. Microsoft Azure API Management is good in terms of nonfunctional requirements.

The documentation is neat and organized, and as a result, we rarely have the need to contact technical support. 

Microsoft Azure API Management is better because it has a DevOps integration by default.

I like the API management functions.

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 like API Management's ability to do hybrid cloud stuff.

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.

The most valuable features of the solution are its importing and publishing.

We use this solution for API rate limiting and for its security features against DDoS.

The most valuable features are the ease of use and the self-enablement through subscriptions for our consumers. Consumers can get into the API gateway library and register to an API from the catalog directly. 

Once the API is developed and added to the library with the registration documentation, it becomes pretty easy for consumers to access and understand the benefits and use of the API.  

The library acts as the central repository of all our APIs and use and access is pretty intuitive.

It's very easy to learn for a person not familiar with API.

The policies on offer are the most valuable aspect of the solution. 

The solution is reliable and very stable. 

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.

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 most valuable features are the API and integrations.

The basic tier is pretty good. 

It's publicly available API Management.

The price is pretty reasonable for us. 

The most valuable features are the Active Directory integration and wireless backup.

The tool's most valuable feature is the integration of CI/CD with the API gateway. 

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

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

The most valuable features are authentication and authorization. I would also argue that the mediation and translation from SOAP to REST technology is equally important because it makes it possible to open up legacy systems that couldn't be opened before.

I have found this solution to be easy to configure, simple to use, and flexible.

The integration with Azure Active Directory is a good security feature for authentication and authorization. There is multifactor authentication. You can also use all of the Azure AD features integrated with API Management. 

The most valuable feature of Microsoft Azure API Management is the developer portal because it's very quick and easy to get something published.

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

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.

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.

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.

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.

We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting.

It's easy to use compared to other products. It's easy to set up.

The package as a whole is useful for our customers.

The ease of setting up a new solution is the most valuable feature. It's very easy to set up a new solution and to deploy it to production.

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.

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.

The way the solution integrates with other Azure services is its most valuable aspect.

The tool does what it's supposed to do. 

We really like the scalability.

It’s easy to set up.

The solution has overall high performance.

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. 

• API gateway features
• AD integration
• Access management capabilities
• Usage plans
• Quotas for APIs, etc.

I like the stability and the ease of use.

The Azure Active Directory Synchronization is quite good.

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

The ability to manage user access to given API operations.

• Visibility on user usage analytics
• Set policies across API operations, which control the type of access (CORS, JSONP)
• The ability to piece together an array of services into one proxied service. Where I can create consistency to both usage and documentation

The most valuable feature would be the easy integration into the entire Microsoft environment, like Access Directory, the collaboration tooling, the development tooling, basically the integration into the Microsoft universe.

It's not the best product on the market which makes it difficult to pick a particular point that we like the best. It could be the integration in the Azure portal. In the Azure cloud it's directly connected with Azure ID, so if you stay in the Azure ecosystem, this user concept is an advantage. The solution also allows you the possibility to use VPN technology and things like that to connect your gateway directly with on-prem services and that's a valuable feature. And compared to other solutions the price is outstanding. 

This solution is very flexible, and it's very compatible with the other Azure products.

The most valuable feature of the solution is it's simplicity. It's easy to set up and is very well integrated with the Azure environment.