Azure Firewall Reviews

I used Azure Firewall for a few months in a project because of specific requirements, but I am not currently using it.

Azure Firewall deployment was not difficult because it has instructions and documentation available on the internet. I faced few problems with the configuration initially, but the documentation was rich enough that I went through that hurdle easily.

The only trouble I faced with Azure Firewall was related to configuration. When I started using Azure Firewall, I had no idea about how to configure it. Later, after passing both the Azure administrator exam and Azure solution architect exam, I went through important requirements and information regarding Azure Firewall, which made it easier.

From a development perspective, I worked with one network person, along with my development team. Overall, we had around three people with network and infrastructure expertise who were mainly responsible for the deployment of Azure Firewall.

We initially investigated pricing details because we needed the costing information for Azure Firewall. We then implemented basic traffic filtering using Azure Firewall standard features. We used a hub and spoke topology to centralize the security controls, setting up Azure Firewall in our hub and spoke topology with standard features.

Azure Firewall has a feature for filtering traffic from suspicious IPs or other threats. We needed to prevent those calls from accessing our API, which required us to route our requests in a filtering way.

For logging in our project, we use a logging mechanism in our internal environment. We integrated our logging module into Azure Firewall, ensuring only specific authenticated users can access this logging for auditing purposes.

Azure Firewall makes our tasks easier; otherwise, we would have to do many extra things manually to secure our APIs and requests. We have integrated Azure Monitor and Log Analytics, making logs easily visible in our Log Analytics. Azure Firewall is very compatible with integrating with other Azure services, which made our tasks for logging and development security much easier overall.

Diagnosing blocked traffic was initially challenging because we didn't know how to diagnose and integrate Azure Firewall with other Azure services for storing logs in Log Analytics. Tracking suspicious activities was also challenging at first because we had to learn to use Azure Firewall effectively.

The threat intelligence-based filtering in Azure Firewall uses Microsoft threat intelligence, which leverages AI and machine learning. There are some threat intelligence-based filtering features in the app and integration with Microsoft Sentinel. Currently, the AI-related features supported by Azure Firewall seem sufficient, though I cannot recommend too much as I have not thoroughly tested all those features.

I recommend Azure Firewall because any development activities or software must address security, threat intelligence, filtering, and TLS termination. Doing these manually or programmatically would be very difficult. Azure Firewall simplifies everything, securing our APIs and systems so that suspicious IPs do not access our sophisticated systems.

I use Azure Firewall for directing all internet traffic, including controlling URL-based access. I enable premium features such as DDoS protection.

The most valuable features of Azure Firewall for me are its URL-based internet access control and DDoS protection for incoming traffic. The premium version includes all traditional firewall features, reducing the need for separate compute resources. Being a SaaS solution, it requires less platform management and ensures maximum availability.

We use Azure Firewall to protect our cloud assets that are hosted on the internet.

There is not a single feature or single product that can ensure security. We have to combine multiple features and multiple products, and then we can say that this is more cost-effective and works properly to ensure the security posture of our cloud deployments.

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

It's helped us improve our security posture. 

Currently, in the team I am working on, we are not using AWS. I used to work with it, but now I am focusing on Microsoft Azure. We have two teams in our company, one focusing on infrastructure on Azure and the other on AWS. Previously, one of my assignments required looking into security tools for AWS to get an idea of what can be used.

I like that you can deploy the policies separately from the firewall. The management capabilities in this aspect are helpful for me. We do not use the version with security features like IDS and IPS as it proved expensive, and we did not get approval for the full-featured firewall.

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.

There are constant feature additions. They add features every three to six months. They add a lot of new features to it, and its cost is comparatively cheaper than the traditional ones.

There are constant feature additions. They add features every three to six months. They add a lot of new features to it, and its cost is comparatively cheaper than the traditional ones.

The threat intelligence aspect of this particular firewall is not at par with other providers. The load balancing and high availability could be better.

Something like Panorama can also be a part of this solution. 

Azure Firewall has a lot of features that are comparable to Palo Alto and other firewalls. One of them is security incidents and event management. The SIEM that Azure Firewall provides us is very robust.

There are constant feature additions. They add features every three to six months. They add a lot of new features to it, and its cost is comparatively cheaper than the traditional ones.

I have hands-on experience with Azure Firewall. My company is developing a product called Mondo with Azure Firewall. The tools that we are developing use all sorts of products inside Azure or AWS. For example, we are checking for vulnerabilities inside the cloud and whether the customer configures the firewall properly or not. Indirectly, we are using the Azure Firewalls, but mainly it is for scanning and to check the misconfigurations of the cloud.

The solution's most valuable feature is its ranking of some web categories. The tool also does URL filtering and uses SSL and TLS inspection.