Azure Firewall Manager is good most of the time, but it could be improved regarding cost. The cost is a significant concern because we are in a region where the dollar is not our default currency, and converting to dollars makes it very expensive. Microsoft should calculate and show the products in local currencies, such as PKR or Bangladesh currency, and also introduce Indian currency similarly for Pakistan. The technical support could be improved. When a resource is assigned, that resource should follow the ticket and respond swiftly, including sending an email to inform me that an agent has been assigned. I still find myself waiting for an agent to connect with me and resolve my issues. I have not been integrating Azure Firewall Manager with Azure Virtual WAN.
Enterprise solutions architect at InfoDeltaSys Software Solutions (OPC) Pvt. Ltd.
Real User
Top 20
2025-06-13T07:51:11Z
Jun 13, 2025
For Azure Firewall Manager, the learning curve for new people is a bit challenging, but the integration should be more straightforward for configuring a centralized system. We use Biceps, Infrastructure as Code, to create the infrastructure automatically, which we copy and paste across all environments such as QA, UAT, pre-production, and production. The same approach can be applied here, making it easier for any new team members to utilize the change management system we put in place. However, it is manageable and could be refined in the future.
The configuration and settings require substantial time for learning, particularly for new users. Improvements in ease of configuration would benefit users significantly.
The tool's security features need to improve. It needs also to include a monitoring system for logs. It is also complicated to find a query on the Azure firewall.
There should be a simple one-click deployment for a firewall, rather than a set of setup instructions that include steps such as the DNS configuration, et cetera. It should be a friendly one-click process that is easy for non-technical or business people to do. By bringing in an autonomous or semi-autonomous system, we would not have to supply several different parameters. Alternatively, if it were a query-based configuration then it would still be a benefit on top of what they have now. Microsoft was unable to fully solve the problem with email phishing and spamming. Irrespective of whatever endpoint security solution you bring in from a third party, it requires constant AI and learning. This is something that is missing, and it is one place where you are forced to use a third party.
Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Palo Alto Networks and others in Firewall Security Management. Updated: June 2025.
With Azure Firewall, the problem is that the NAT-ing still has to be improved. They need reverse network address translation (NAT) capabilities. We cannot get the same NAT-ing capability as what we had in the on-premise deployment, where we could have multiple sources of IP coming in and could be NAT-ed to a specific IP. Similarly, we couldn't use the reverse NAT-ing of the scenario. We could do only one-way NAT-ing, where the traffic comes from outside to internal, to Azure, which is fine. However, when we actually do NAT-ed traffic to hit the firewall, that way is not working.
CIT at a tech services company with 51-200 employees
Real User
2021-06-15T13:04:00Z
Jun 15, 2021
When we initially started using the solution around five years ago there was no wizard for setting things up, although now there is a very nice one. When it comes to configuration, a few steps is all it takes. However, beforehand, there was a need to enter and understand everything that was necessary for configuring the firewall. There is no additional documentation or training required. When we first started using the product there was a need to enter everything on one's own and the initial setup was not easy. Now, after a few clicks, everything is fine.
Firewall Security Management offers comprehensive control and oversight of network traffic across organizational boundaries, enhancing network security and ensuring compliance with policies. It addresses the complexity of managing firewalls through automation and centralized monitoring.
Managing firewalls effectively is essential for safeguarding digital assets. Given the increasing sophistication of cyber threats, businesses require robust solutions that facilitate real-time...
Azure Firewall Manager is good most of the time, but it could be improved regarding cost. The cost is a significant concern because we are in a region where the dollar is not our default currency, and converting to dollars makes it very expensive. Microsoft should calculate and show the products in local currencies, such as PKR or Bangladesh currency, and also introduce Indian currency similarly for Pakistan. The technical support could be improved. When a resource is assigned, that resource should follow the ticket and respond swiftly, including sending an email to inform me that an agent has been assigned. I still find myself waiting for an agent to connect with me and resolve my issues. I have not been integrating Azure Firewall Manager with Azure Virtual WAN.
For Azure Firewall Manager, the learning curve for new people is a bit challenging, but the integration should be more straightforward for configuring a centralized system. We use Biceps, Infrastructure as Code, to create the infrastructure automatically, which we copy and paste across all environments such as QA, UAT, pre-production, and production. The same approach can be applied here, making it easier for any new team members to utilize the change management system we put in place. However, it is manageable and could be refined in the future.
The configuration and settings require substantial time for learning, particularly for new users. Improvements in ease of configuration would benefit users significantly.
The solution can improve the integration with open-source tools.
The tool's security features need to improve. It needs also to include a monitoring system for logs. It is also complicated to find a query on the Azure firewall.
There should be a simple one-click deployment for a firewall, rather than a set of setup instructions that include steps such as the DNS configuration, et cetera. It should be a friendly one-click process that is easy for non-technical or business people to do. By bringing in an autonomous or semi-autonomous system, we would not have to supply several different parameters. Alternatively, if it were a query-based configuration then it would still be a benefit on top of what they have now. Microsoft was unable to fully solve the problem with email phishing and spamming. Irrespective of whatever endpoint security solution you bring in from a third party, it requires constant AI and learning. This is something that is missing, and it is one place where you are forced to use a third party.
With Azure Firewall, the problem is that the NAT-ing still has to be improved. They need reverse network address translation (NAT) capabilities. We cannot get the same NAT-ing capability as what we had in the on-premise deployment, where we could have multiple sources of IP coming in and could be NAT-ed to a specific IP. Similarly, we couldn't use the reverse NAT-ing of the scenario. We could do only one-way NAT-ing, where the traffic comes from outside to internal, to Azure, which is fine. However, when we actually do NAT-ed traffic to hit the firewall, that way is not working.
When we initially started using the solution around five years ago there was no wizard for setting things up, although now there is a very nice one. When it comes to configuration, a few steps is all it takes. However, beforehand, there was a need to enter and understand everything that was necessary for configuring the firewall. There is no additional documentation or training required. When we first started using the product there was a need to enter everything on one's own and the initial setup was not easy. Now, after a few clicks, everything is fine.