Azure Firewall

The scalability of the available bandwidth prompted us to go with Azure Firewall. We were hosting ~800 high-GPU virtual machines in Azure that required significant throughput at times. The scalable approach allowed us to avoid guessing what that bandwidth maximum would be.

Integrates well with other Microsoft products like Azure as most Microsoft products do, does scale well for our organization and does not have many issues with reliability as works almost all the time efficiently. Was one of the easier deployments we have had with our organization but that is third party information I have gotten from coworkers involved with the setup can say it does seem simpler and easier in use.

I really like how this product has all of the advanced firewall techniques and modules and is in the cloud, working for cloud networks. It is amazing that we can have something like this. Thank you, Microsoft.

There are two pain points for us. The first being that when you assign multiple public IP addresses to the firewall, in our case, for inbound hosted websites, all of those public IP addresses are automatically made part of your outbound SNAT pool. This contributes to difficulties with IP whitelisting. Our second pain point is simply the representation of data in the firewall logs. I would like to see more canned reports for useful information regarding the traffic seen by the firewall.

Less feature rich that other firewalls and thus seems less useful in comparison in addition the delay for real time investigations can be grating as we must wait for logs to get populated. Does not provide as much visibility as other tools.

I don't like that the costs are higher than I'd like them to be. Also, as someone who specializes in digital forensics, I didn't find any advanced investigative techniques, which I wish it had.