We explored different options and found that APM was the most suitable for our scenarios.

We compared it with DIS because most of the time we were using DIS, for such kind of deployment.

I'm aware of Google, or Apigee, and it's quite a robust product. 

I was looking into Azure API Management and the equivalent and in AWS.

I wanted to compare the functionality between Azure API Management and Amazon API Gateway, as there's a customer that wants AWS API Gateway instead of Azure. I just wanted to see if the features are similar. I'm looking into that now. 

I also use WSO2 and Kong. Of all the options, Kong is my preference because it is easier to use. 

I did not compare this solution to others since I was promoting Microsoft at the time. 

The other option is API Apigee. It is the best in class and less expensive. Its deployment to API Gateway from AWS is easy and fast. 

In AWS API Management you can build everything from open API specification files. AWS has Swagger extensions that are built in that can define everything in Swagger.

I would switch solutions if I could. 

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.

We have evaluated WSO2, APIGEE, MuleSoft with API Manager

We also looked at Apigee, and Apigee has some integrated features, however, Apigee was very complex to get started with. Apart from that, we are a Microsoft company, and we're on the Microsoft stack. It was more logical to keep everything in Azure. That's why we chose Azure API Management.

I was able to work with Apigee.

We did evaluate a few other solutions before ultimately going with Microsoft. We looked at MuleSoft, for example, but it was a totally new environment for us. Another solution didn't have the level of maturity we wanted in a cloud product. Microsoft was also new, however, we had a lot of contacts there and we had all of their interfaces. After looking at the pricing and features, it ended up being the best option.

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

We considered other options; however, our client is mainly a Microsoft shop and they were already using Azure for various things. As such, we did not fully evaluate other options. 

Before choosing this product, I evaluated NGINX, Apigee, and ForgeRock (OpenAM/OpenIG).

I have evaluated GCP and AWS.

No. I was evaluating Azure PAS offerings and producing proof of concept solutions just before the project kicked off.

As mentioned, this is the only option we looked at. We chose Azure because it's easy to deploy and it's cheap. It's a good starting point and if they develop it further, it might be good for productive usage, especially if you are planning to use it as an API management platform for the services that are running in Azure. I think then there's no question.