Microsoft Azure Application Gateway Reviews

Our client is using three to four applications. One use case is with the integration layer, which has the website running on the web app. It interacts with different applications and with their on-premise SAP solution as well. This app service works as an integration layer between the SAP solution and other different applications. The solution also has its patient application running, which is the patient appointment system, since our client is a healthcare organization. That separate application also runs on App Service and is deployed on Application Gateway.

I find its Application Gateway's WAF module valuable because it helps prevent layer 7 attacks.

Application Gateway’s limitation is that the private and the public endpoint cannot use the same port. But I believe they are working on it.

Another shortcoming is that the maximum permissive size for the request body size is two MB, and it needs to be increased up to five MB or more. Some other third-party solutions or even AWS provides better request body size in this regard.

I would like to see some more features in WAF with the next release to make it more competitive with leading web solution providers. When we compare the WAF with other solutions like F5’s WAF, Application Gateway’s WAF has fewer features.

I rate the solution's stability a seven out of ten. It took us four or five months to optimize the solution.

I rate Application Gateway's scalability a ten out of ten because it is very good. It has an autoscale feature. The solution is being used on close to 200 endpoints. My client is a medium-sized healthcare business.

Sometimes customer support puts issues in loops, where they take us through L1 and L2, and it takes some time to get to the right person who can address the issue.

Neutral

I rate the initial setup an eight-point-five out of ten because it is easy. Deploying the solution takes a day or so, but all the configurations, working with the application team, and optimizations take time. Usually, it takes three to four days.

While deploying the solution, we gathered application data first, such as the URLs which we needed to run the app services, health probe ports, the certificates from the customer, and any custom flash rules which may need to be created. We gathered all the information from the customer and the customer's development teams.

I rate the pricing seven out of ten because some third-party solutions are even costlier than this. The product's price is good considering the set of features it provides. There is no cost in licensing, but they charge us based on the size of the application gateway, the data being transferred, and the gateway's scalability.

The solution's app service and application gateway took us eight months to implement. It's a huge infrastructure.

If you are considering using Application Gateway, you have to understand the application flow thoroughly. If it will be an integration layer where you might face a lot of issues, counseling with the developers and the customer's teams is very important. The solution requires optimization from the WAF perspective as well as timeouts and other settings. It may take some time to stabilize. The product is stable, but I rate it a seven out of ten based on the features I've seen in competitors, like third-party dedicated WAF solutions, which provide a lot more flexibility and features to their customers. However, they are more costly. And when you have to design scalable solutions, they cost a lot more.

We are using Microsoft Azure Application Gateway which hosted our domain as a load balancer. We have an application visible to the public and the traffic passes through this solution.

The most valuable feature of the solution is traffic management.

The solution could improve by increasing the performance when doing updates. For example, if I change the certificate it can take 30 minutes. Other vendors do not have this type of problem.

I have been using Microsoft Azure Application Gateway for approximately three years.

We have had some issues with the stability.

I rate the stability of Microsoft Azure Application Gateway a three out of ten.

We have approximately 600 requests from one balancer and a total of 3,000 requests.

I rate the scalability of Microsoft Azure Application Gateway a three out of ten.

I rate support from Microsoft Azure Application Gateway a four out of ten.

Neutral

I have used a solution prior to  Microsoft Azure Application Gateway.

The implementation of the solution was complex, it took a few hours to complete.

I rate the initial setup of  Microsoft Azure Application Gateway a three out of ten.

The solution is paid monthly. The solution is highly expensive.

I would not recommend this solution.

I rate Microsoft Azure Application Gateway a four out of ten.

We are using it for application load balancing and scaling.

It has a filter available, although we are not currently using it because it is not part of our requirements. But it is a good option and when it becomes part of our requirements we will definitely use it. 

It takes a lot of time for a certificate to update in the system. That is a huge drawback, affecting the load-balancing side. And when there are changes to the load balancing, it affects the end-user.

I have been using Microsoft Azure Application for the last six months.

I think the scalability is okay, but I haven't tried to scale it.

Application Gateway is tied into our applications. We have about 5,000 connections into Application Gateway, on average. There are around 800 to 900 requests per minute.

I have not had to contact Microsoft tech support about Azure Application Gateway.

Previously, we were in AWS. We just migrated to Azure. 

The initial setup is straightforward. If you compare it with AWS, it's a little bit complicated, but overall, the technical aspects are very simple.

A normal Application Gateway deployment takes around 20 to 25 minutes, but again, the application of certificate changes takes around 20 to 25 minutes, so the total time involved is about one hour.

We did not use a third-party. Currently, I'm the only person handling the solution in our company. My main task in Application Gateway is configuration, as it's a service that is provided by Azure. There is not much more for me to do than configure it.

Between v1 and v2, there is a lot of change in the pricing. It is very costly compared to AWS. Our main implementation strategy is based around the pricing. If there are any technical features that we need to consider in addition, we will. If the prices for those additional features are okay then we will use them.

The features in both AWS and Azure seem to be comparable. We are enabling all the security features that were available in AWS. 

From my few months of experience with Azure, the configuration changes we are making in Application Gateway, such as a certificate change, are taking more time to apply to the service. In AWS it was very quick. It would take less than one minute, but here it takes almost 10 minutes to apply that certificate. That time difference is huge. That is the only drawback or issue that I have faced with the Azure Application Gateway. 

Other than that, the two services look the same.

There are two versions of Application Gateway. Version 2 is a seven out of 10. I would rate version 1 at three to four out of 10.

We have multiple microservices connected to App Services, which are then connected to Application Gateway. External users communicate with the gateway, which directs them to the appropriate microservices.

The automatic redirection and security features are crucial for us. The performance is the main thing. Application Gateway automatically redirects unwanted users and takes care of the security aspect. It also handles the performance side of things, which is why we use it.

The Autoscaling feature in Application Gateway is very important to us. It allows us to scale based on the number of users without compromising performance.

We have encountered some issues with automatic redirection and cancellation, leading to 502 and 504 gateway errors. We suspect the containers we use might be contributing to these issues.

So, I experienced some trouble with containers.

I joined a new project four months ago and have been using Application Gateway since then.

Since we're still in development, we haven't fully tested the stability and availability. We'll have a better understanding during testing and performance evaluation. We anticipate encountering various challenges related to stability and scalability as we expand.

Based on my experience with limited users so far, it's working well. However, we plan to expand usage in the coming weeks, so I'll be able to provide more insights after seeing how it performs under increased load. 

At this point, I haven't experienced any lagging, so I'm yet to test it more thoroughly.

We have a minimum of ten users in development. However, once the product is released, we expect a significant increase, potentially reaching hundreds of thousands of users, as it's a mandatory feature for our medical-based use cases.

We have a subscription and can reach out to their support team if needed.

I previously used the API Gateway in AWS and found it to be good.

In AWS, there's the Load Balancer, Application Load Balancer, and API Gateway, which are comparable to Azure's Application Gateway.

Deployment is done using containers since everything is saved in a container registry.

I work with the cloud-based version of Application Gateway.

The configuration was a bit tricky initially, but it has been smooth since then.

I would rate the pricing a three out of ten, with ten being cheap and one being expensive Because of some high costs. 

Overall, I would rate the solution a five out of ten. Since I haven't fully utilized all its features, I need more real-world experience to compare it with AWS in terms of pricing, features, and scaling options.

We use the tool to manage web traffic for our applications. It helps us to filter out unwanted traffic. 

Microsoft Azure Application Gateway is harder to manage than Imperva. It is not intuitive and stable compared to other products. 

I have been working with the product for two years. 

I rate the tool's stability a seven out of ten. 

I rate Microsoft Azure Application Gateway's scalability a ten out of ten. My company has more than 1000 users who use it daily. 

The tool's deployment is difficult. The time for provisioning varies depending on the company. It can range from as quick as five to ten minutes to as long as one hour or even half a day, depending on the specific requirements of the company you're provisioning for. The team depends on the size of the deployment. 

Our in-house and outsourced resources helped us with the deployment. 

The solution is cheaper than Imperva. I rate it four to five out of ten. 

The traffic must pass through the firewall server and proceed through the application gateway before reaching the application itself. I rate the product a five out of ten. 

I use the solution in my company to protect an external website.

The product's WAF was useful to protect against the OWASP attacks.

The tool is a pain to deal with when it comes to the area of configuration. Basically, users get a lot of false positives with the product. The aforementioned area can be considered for improvement in the product.

I think the reporting elements could be a bit better in terms of having built-in reports, considering how everything has to be a cluster query when you write it, making it an area where users customize the tool. The reporting elements are an area with shortcomings in the tool that could be better as it would be useful to deal with false positives.

I have been using Microsoft Azure Application Gateway for five months. I use the solution internally for my company. My company has a gold partnership with Microsoft.

It is a stable solution.

It is an easily scalable solution.

The tool is not meant for users since it is designed for public access; considering that, I would say that the solution provides protection to our company website, which has thousands of visitors.

The solution's technical support is okay and not that good, considering that my company still has some existing tickets open with the support team, which are related to some login stuff. The problem with Microsoft is they outsource their support to vendors in other parts of the world, so it is like a lucky draw system, meaning you are lucky if you get someone good.

The product's initial setup phase was easy.

The solution can be deployed in a day.

I deployed the solution by myself in my company.

The product's ROI is okay, in my opinion.

The price of the product is okay. There is a need to pay a fixed price per month to use the product. There are no additional payments to be made to Microsoft apart from the charges paid towards the monthly licensing costs attached to the solution.

My company had looked at the options offered by Cloudflare, but we decided to stick to the stack of services offered within Azure.

For most of our company's in-house resources, we are dependent on the cloud services offered by Microsoft, so it was easy to adopt Microsoft Azure Application Gateway in our organization.

To utilize Microsoft Azure Application Gateway for managing web traffic load balancing in our company, we use products within the Azure landscape like Azure Load Balancer or Azure NAT Gateway.

In our company, we don't have multiple instances of the application to utilize Microsoft Azure Application Gateway for application-level routing and URL-based content distribution. There is pretty much just one instance to deal with in our company, which makes the use of the tool quite straightforward.

The tool's WAF provides a fairly adequate level of protection against common vulnerabilities.

The solution doesn't require any maintenance once it is deployed.

Integrating Azure Application Gateway with other Azure services in our company's existing infrastructure is a fairly seamless process.

I haven't had any issues with the scalability and performance of the product.

I would ask those who plan to use the solution in the future to plan the deployment so they have more time to analyze their data when using the WAF, and you need at least six months of history to see the traffic patterns and to get an alert on false positives.

I rate the product an eight out of ten.

Azure Application Gateway is used on an AKS cluster. We don't want to expose the control plane to the public IP. We created a control plane with a private IP and then put an Application Gateway in front of it. Users can access the AKS cluster through the Application Gateway. The Application Gateway filters traffic to the AKS cluster.

If you don't want to use public IPs and expose your enterprise externally to the public world, and you want strict authorization, you should use Azure Application Gateway.

The login mechanism could be improved.

I have been using Microsoft Azure Application Gateway for a few months.

I rate the solution’s stability a seven out of ten.

The solution is scalable.

Microsoft Azure Application Gateway is an internal application that allows people to access it. We have 100s of different users working on it who can access it with their logins. We do not need to set up any database mechanism to add users.

Microsoft Support is good.

The initial setup of Azure Application Gateway is straightforward, provided you have a good understanding of networking concepts and have everything ready.

For deployment, the gateway is already available. It offers maximum protection and everything else.

If you want to build an application with standard authorization and a simple route within the organization instead of multiple routes, then Azure Application Gateway is a good option.

Overall, I rate the solution an eight out of ten.

The solution's most valuable feature is an HTTP solution and SSL certificate. It is also easy to use.  

Microsoft Azure Application Gateway's first deployment is complex. It needs to improve its pricing. 

Microsoft Azure Application Gateway is stable. 

The solution is scalable. My company has two projects that use it. 

The tool's deployment takes one week to complete. 

The tool's pricing model is pay-as-you-go. 

Microsoft Azure Application Gateway is a useful solution. I rate it a seven out of ten.