Microsoft Azure Application Gateway Reviews

I've used the solution for a simple at-home application where I just wanted to host something live and have load balancing built into it. I can't remember where the firewall came in. I know there's some sort of blocking for certain attacks through that firewall, but that was about as far as I really used it.

Microsoft Azure Application Gateway is an easy-to-use solution.

The solution can sometimes feel a little cumbersome unless you're a professional infrastructure person. I think the tool is just inherently complicated. You have to manually decide things that could have been done best by default.

I haven't seen any outages with Microsoft Azure Application Gateway.

The solution should be able to handle any load.

I've used all three cloud providers for side projects, including Microsoft, Google, and Amazon. If you have a docker container or an image and want to deploy it somewhere, they're all fairly similar. I would choose to stay on a cloud platform because of cost and convenience purposes. If I already have a database running in one cloud, I might deploy an application with that same cloud provider.

The solution's initial setup is really easy, but it takes a long time to get that comfort.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup ten out of ten.

The solution is fairly priced.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten.

The solution's documentation was pretty good and useful. The solution is well-integrated, and I don't think any challenges exist. We are hosting an LOM application for internal use only, but I don't know the details. As an internal user of the LOM, I find it nice and fast. I would recommend the solution to other users.

I think some things in the tool are multi-step when they could have been a single step. Obviously, I understand that design decisions go into that. The solution can sometimes feel a little cumbersome unless you're a professional infrastructure person.

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

I use Application Gateway because I need to integrate different resource management. In one project, I had two to three applications to integrate using the API Gateway for security and networking solutions.

The solution integrates different applications and APIs securely, enhancing overall security and network optimization.

It creates security, manages installations, and integrates different applications and solutions. It is flexible and scalable, provides better business solutions and controlled versions, improved security, and comprehensive documentation.

The solution needs improvements in integrating different services and creating a better application balance.

It is scalable, allowing integrations with different cloud platforms like GCP and AWS, and creating varied environments in the Azure platform.

Microsoft does not have personal tech support but contracts external consultants for deployment and support. When a client has an issue, Microsoft sends emails to different MVP architects around the world to provide the best support.

Positive

AWS has many features but presents issues with Microsoft applications integration. Azure is preferred for its flexibility, scalability, and strength as a cloud solution.

The initial setup process is straightforward for me. However, depending on the project requirements, it might be complex for others.

Deployment requires two developers and one architect. Maintenance can be handled by one person.

Depending on the project, the return on investment varies. As an Azure cost management specialist, I can provide detailed cost assessments using the Azure calculator.

Using the Azure calculator, I evaluate projects and create cost prospects. The process is defined by Microsoft's framework and needs specific project assessments.

I have used other ADC or WAF products like AWS. However, Azure is preferred due to its flexibility, scalability, and strength.

I recommend using Azure for its flexibility, scalability, and strong solutions. It is the best cloud solution for various organizational needs.

I'd rate the solution eight out of ten.

I use Microsoft Azure Application Gateway for publishing.

The most valuable feature of the solution is the web application firewall (WAF).

We got other additional application delivery controllers. Implementing and standardizing the solution across the IT landscape in a heterogeneous environment is painful. Some websites are published through an application delivery controller, which is not Azure or Microsoft. Having a standard implementation across the IT landscape is what we're trying to address at the moment.

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

I rate the solution a nine out of ten for stability.

We previously used Citrix NetScaler.

The solution’s initial setup was straightforward.

The solution can be implemented in a couple of hours.

We've implemented Microsoft Azure Application Gateway for web traffic management in our organization for inbound HTTPS access.

We use a standard app service plan on the back end. We're talking about some 6,000 to 7,000 concurrent connections, and we haven't faced any scaling issues so far.

The web application firewall feature has proven most beneficial for our security and load-balancing needs. There was a compliance and security requirement to enable OWASP. That's why we enabled SQL injection and other features on WAF.

I rate the solution an eight out of ten for its ease of configuration and management. Microsoft Azure Application Gateway is a great product, and I would encourage everyone to use it if they have a presence in Azure.

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

Application Gateway is a tool service that provides high availability, redundancy, and load balancing for deployed applications on the cloud.

Application Gateway is cost-effective and has autoscaling. We can autoscale it.

The application gateway is good, but performance improvement in the containerization environment is needed. 

The traffic that relies on HTTP for a website is being manually configured to HTTPS. This process should be automated. If the protocol is HTTP, it should automatically redirect to HTTPS.

I have been using Microsoft Azure Application Gateway for one and a half years.

The stability is acceptable, but we are encountering issues configuring the container environment. Apart from that, the performance is satisfactory.

 I rate the solution’s stability as seven out of ten, but I rate it as nine out of ten for normal applications.

We have over three hundred customers, most of whom utilize Azure Application Gateway. Some are in the government sector, while others are in the private sector.

I rate the solution’s scalability a ten out of ten.

Microsoft's support is lacking. Their technical expertise seems insufficient, and when issues arise, the support personnel often request screenshots and provide only minimal information. Despite numerous emails and interactions with various technical support personnel, the initial support experience is subpar. The response is very fast, but they're not technical questions, as we need.

Positive

I rate the initial setup a ten out of ten for technical users and an eight out of ten for non-technical users. It's a one-time application. However, once configured, it becomes very easy to manage. Deployment takes 20-30 minutes, depending on the number of applications and servers we are configuring.

The product is cheap.

A WAF, a robust firewall solution, has been built into the Azure portal. Two models are available. The WAF is also integrated with the Application Gateway, providing comprehensive security for your cloud applications.

This security feature applies to traditional VM applications running on VMs and extends to autoscaling nodes in containerized environments.

The Microsoft Azure Application Gateway is a highly beneficial and flexible feature for facilitating the development of our applications and obtaining necessary certifications, thus sustaining our business operations. It offers scalability and high availability, which are crucial for meeting our growing needs. The Application Gateway serves as the sole solution for providing these capabilities, eliminating the need for developing such features in-house. It's an all-in-one solution that perfectly fulfills our requirements.

Overall, I rate the solution a nine out of ten.

It's really useful, and I have used it for API applications as well as web applications. Apart from that, you can write your custom rules. 

I have widely used it for applications. It's good if you have a single application, as well as a number of applications. You can have one application and configure everything in one application gateway. 

Microsoft can work on it as the pooling size as the max pool size is two hundred. Sometimes, when there's heavy traffic, it gives a bad gateway error. 

If you are using a third party application and have network constraints, you can use the API in your network and then create a proxy out of it. It is URL-based. 

The solution's integration is very good.

The troubleshooting feature is also good, as it gives you a fair amount of permission.

Microsoft needs to work on their documentation.

The scalability needs improvement.

I have been using Microsoft Azure Application Gateway for almost four years. 

It is a highly stable solution. I rate the stability a nine out of ten.

The solution can be made more scalable. 

The technical support team is quick in their responses.

Positive

The initial setup is complex at the beginner level due to lack of documents. 

The solution is reasonably priced. 

Overall, I rate the solution a nine out of ten. 

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 are regular users of Azure Application Gateway. It is a very cost efficient option for customers and it has its own advantages. However, when there are urgent concerns regarding security I recommend utilising the web application firewall for its enhanced features and configuration options since Azure lacks functionalities and has its own limitations when handling suspicious requests. 

Usually, there is a recommendation from Microsoft about integrating Azure Application Gateway with other services like Monitor and Sentinel, so that there is seamless log forwarding and rule management. However, other options involve much more extensive configuration and scripting. In my experience, Microsoft products have a smooth integration and facilitate easy management and monitoring. Using Azure Application Gateway allows us to efficiently handle the system loads.

There is a recent feature called Application Policies which has been available. This policy allows us to enable or disable specific security signatures or features related to backend operations. According to the manual provided by Microsoft, this feature is very flexible in managing security and strategies for maintenance. However, in our experience, we have found that modifying these policies has a tremendous impact on the functionality of the application gateway. While it is necessary to adjust the settings, it should be a process of caution since these rules could potentially expose applications to security risks.

Multiple options exist to configure the number of instances and scale responses based on load increases. However, I believe that there is room for improvement in terms of additional functionality. It is an advantage to have features readily available for configuration without needing customer-defined rules. This feature is already available in products like Barracuda and would be great if they are included in the future versions of Application Gateway.

I have been working with Microsoft Azure Application Gateway for the past two years. 

I would rate the stability a six out of ten because there are some malicious requests. 

I would rate the scalability a ten out of ten.

Sometimes, technical support may require escalation to higher-level experts, particularly when dealing with complex issues. 

Neutral

I would rate the initial setup a seven out of ten, since it is simple and does not take a lot of time. 

I would rate the pricing a seven out of ten.

I would rate the integration with other applications a nine out of ten. Overall, I would rate the solution a seven 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.