I use the solution as a firewall. We use it for segmentation and zero-trust security. 

We use it to improve our security posture. We wanted to have an Azure-native solution for our security offerings, and that's why we went for Azure Firewall.

We use Azure Firewall for designing infrastructure for big data integration applications or for applications on Kubernetes. The firewall is only on the edge of our architecture.

The problem we were trying to solve was mostly around configuration. Azure Firewall is a PaaS offering, so it's not about the technical aspects. We need, of course, to know what threats need to be protected against, who should have access to the firewall, and which applications do have access. We also have to look at how it fits with centralized management. We also must be able to state if the solution we provide as a firewall is compliant with the standards of the organization and for auditing.

We use it in a mission-critical environment. It's highly secured.

We primarily use the solution as a firewall. 

We implemented Azure Firewall to secure edges and gain access control to the internet for BNS and Bitcoin. It's used to access the internet in a safe way. It allows us to access services from Azure via the firewall within Azure.

The use cases are related to internet-based traffic restriction. Generally, when it comes to gaining access to web applications hosted on Azure from the outside world, and the traffic restriction between the internal supplements.

We use it to do the network traffic filtering between our private network and a public network. So, it is a boundary. Because of our IDS and IPS needs, the advanced features are enabled in Azure Firewall.

There are two types of versions. In China, there is only the standard tier, but in the rest of the regions, there is the premium tier.

We have multiple applications that are deployed on Microsoft Azure. Azure Firewall helps us to prevent any vulnerabilities or security issues and block attacks.

When we started using Azure Firewall, we learned quickly that it couldn't do much. As I remember, it was essentially a layer 3 or layer 4 firewall that couldn't distinguish recognized applications and things like that. But it was inexpensive compared to the Palo Alto stuff we were looking at, so we wound up staying with the firewall. Mainly it was just inspecting ports between virtual machines.

We are a technical services company and we are in the data center space. We provide different solutions, including firewalls such as Azure Firewall, to our clients depending on their needs.

We have a large customer base that is global in scope and we provide hosting services as well as managed services. We have solutions deployed in both public cloud and private cloud environments. 

We typically use this solution in the perimeter layer, although we do have some use cases where we handle East-west traffic.

I have deployed Azure Firewall for a couple of my clients. They primarily use it for protecting their workloads and limiting incoming connections.

I also have a subscription but I use it primarily for testing.

I've been using Azure Firewall for one or two customers in the UAE to protect against security threats. It protects the Azure infrastructure and PaaS, applications, network, and ports. It's the same as the things we configure with other firewalls.

Basically, our organization is using the solution to inspect the traffic. I'm using the solution as the main defense system prior to de-traffication on the NGX layer (layer seven). Then, of course, we're forwarding to the Kubernetes cluster.

We use the solution as an internal firewall device.

We are currently working with Microsoft, trying to develop a new solution which is based on VeloCloud. It's an SD-WAN solution. This product has not been launched in China yet and we still have some work to do. I'm the company owner and five of my team use Azure Firewall. It's a startup team and I work with Microsoft directly.  

We use the solution for application and server deployment. 

We use it to protect the Azure space and to be the bridge between on-premise and the cloud.

When I have had a site-to-site VPN set up and configured, and would use it to allow ordinary traffic from the on-premise device to the cloud and from other third-party suppliers to the Azure platform.

We also use it to provide connectivity to various network security groups that have been created within Azure.

I used it for two of my clients. One of the clients used it for Azure Virtual Desktop implementation and for blocking the internet for the other applications in the IaaS. The use case for the other clients was also similar. It was put in there for holding up traffic and filtering traffic.

It is associated with our web resources, such as PaaS applications. I don't use it that much. I spend way more time working with function apps or something else on the Azure platform.

I am using its latest version.

We mostly use it as part of a hybrid cloud solution. For example, for a client with on-premises and cloud solutions, our recommendation is that Azure Firewall be used.

We use Azure Firewall to protect customer workloads. 

We're SaaS providers. We use these firewalls to route our traffic from our partner to us.

We mostly utilize the solution for effectively controlling the networks.

On-premise to cloud <-> Cloud to on-premise

Azure Firewall makes up part of our security solution. We use it internally but we are a consulting company and also advise our customers on the use of it.

I design the architecture and it's an extension of the on-premise that we house on the cloud. We secure the entry point to the virtual data center with the firewall.

I'm a consultant and our primary use case is for traditional corporate networks. We have about 100 people using the solution.