![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 33%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHB%3C/text%3E%3C/svg%3E)
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Yep — as per https://free.blessedness.top/en-us/azure/application-gateway/understanding-pricing , changing the minimum instance count to 0 can reduce your variable cost (i.e. capacity unit consumption) because you remove reserved capacity when idle. But it doesn't eliminate all costs: there is a fixed cost component for the gateway itself that you'll still pay as long as the gateway is provisioned (even with zero instances). The exact dollar amount depends on your region and whether you're using the WAF version. For example:
- ~$0.246 per gateway-hour (for a non-WAF Standard_v2 gateway)
- ~$0.443 per gateway-hour (for WAF_v2)
These rates reflect the “fixed” portion you pay simply for the gateway being active (plus the public IP, etc.), irrespective of how many instances are scaled up.
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