An Azure network security service that is used to protect Azure Virtual Network resources.
Azure Firewall costs are primarily driven by two components: the fixed hourly deployment charge and variable data-processing charges based on the amount of traffic processed in gigabytes (GB). A sudden daily increase of approximately $100 typically indicates a significant rise in network throughput, increased diagnostic log ingestion into Log Analytics, or changes that caused the firewall to scale out or process additional traffic.
To identify the cost driver, review Azure Cost Analysis and separate the charges associated with the firewall deployment fee, data processing volume, and Log Analytics ingestion. Firewall metrics and structured logs should also be examined for unusual traffic patterns, such as unexpected outbound activity from compromised resources, network routing loops, excessive retries, or overly verbose diagnostic logging that is increasing ingestion volume.
To reduce costs, optimize firewall logging by reviewing which logs are required and routing them appropriately. Using resource-specific Log Analytics tables or the Basic Logs plan can reduce ingestion costs for applicable data. For development and test environments, consider deallocating the firewall outside of required usage periods through PowerShell or automation runbooks, since the hourly deployment cost continues while the firewall is provisioned. Review network and application rules for misconfigurations that may be causing unnecessary traffic flows, repeated connection attempts, or large data transfers through the firewall.
The description of the Azure Firewall pricing model and available SKUs is available at https://azure.microsoft.com/en-us/pricing/details/azure-firewall/
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin