Our company uses the solution to publish services that are on Azure. There is more than one way to publish services. 

You can use the Microsoft infrastructure for app services including small programming, configurations related to obligations, and publishing. Or you can publish manually by using VMs and attaching the WAF with the solution. 

The solution does not include a security policy so you need to configure a WAF and attach it to the solution. There is an option in the Gateway to automatically go to the web. 

Customers use the product for internal and public URLs or websites. They use it with the multi-site feature. The same application gateway is being used for multiple URLs.

We're using it to expose our application but the main purpose is to make use of the web in a location.

Our company uses the solution as a gateway for our customers' application services. We currently have seven users and six customers. 

We used the solution to build our own applications, publish for clients, and provide software for service.

We use the product as an application firewall for Layer 7 security instead of directly exposing applications on any computing platform to the internet. It has enhanced security compliance for our environment.

We use the solution for isolation and load balancing.

We are using it to add an extra layer of security to our backend, protecting against denial-of-service attacks and other security threats.

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.

We are using it for application load balancing and scaling.

I use Microsoft Azure Application Gateway for publishing.

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.

We use the product in front-end and back-end applications to do the load balancing smartly. 

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

We are using Microsoft Azure Application Gateway for load balancing and for an additional layer of security.

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

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.

The solution is used to terminate the SSL configuration to do SL Inspection for securing your website, as we cannot provide the website directly to the Internet. To prevent it from attacks and to maintain authentication.

We use the solution for Internet traffic load balancing and internet traffic routing via proxies to our internal applications. It is not for user connectivity but more for the system to system integration as an application gateway.

The solution is being used from warehouse to production. In short, for everything. 

We primarily use this solution to hide all of our applications behind the firewall. The application logic and dependencies are not known to the outside world because you don't have to open your external public IP to them.

It does not particularly improve functionality but you get the benefit of the security that is offered by Azure.

I use Microsoft Azure Application Gateway from a security perspective.

We tried to integrate Microsoft Azure Application Gateway into our technology stack, but we realized that our service solution didn't see it at all during the integration. But I was played around with it for about two weeks to one month.

We were searching for a WAF solution which we could integrate into our stack and were using the management provided by the agent. We tried to integrate a vacation gateway controller, but we realized that the integration wasn't very good.

We primarily use the solution to just secure the traffic coming from the outside into our application.

It is for securing traffic. It provides security against OWASP Top 10 vulnerabilities, so there is a V2 WAF App gateway. 

The company uses this solution and I work along with security architects providing that as part of our recommendations for Azure projects. I'm a security specialist and the company has a maintenance enterprise agreement with Azure. 

We use Microsoft Azure Application Gateway for web applications and APIs.

I primarily use the solution during application deployments. I use it to protect the applications.

We primarily used the solution to try to protect a few internet-facing applications that we had.

The gateway is used to make the application connect to the internet and apply some firewall rules on Layer 7. We primarily use Azure Gateway for printers, some requests, and to apply some security rules to all the traffic that is coming from inside the Azure network. 

Microsoft Azure Application Gateway is used mainly for data transformation from on-premise to cloud or from cloud to on-premise. We are only using this solution extensively for web applications.

We use it for load balancing and web application firewall. We are using the latest version. We also have version 2.

Our primary use case of this solution is for exposing services to the internet. We are Microsoft partners and I am the company's consultant for Azure Cloud Infra & Apps.