
There is no single price for it. Your bill shifts with the SKU, region, gateway hours, capacity usage, traffic profile, WAF choice, and how many gateways and environments you run.
This guide covers current US pricing components, representative scenarios, hidden charges, budgeting steps, and when Azure Load Balancer or Front Door may cost less.
Key Takeaways
- Application Gateway v2 bills a fixed gateway-hour charge plus variable capacity-unit usage.
- WAF_v2 carries higher rates than Standard_v2, with no extra charge for WAF rules.
- Reserved minimum capacity, extra environments, IPs, transfer, and logs inflate the total.
- Right-size the SKU, consolidate workloads, and review idle gateways regularly.
How Much Does Azure Application Gateway Cost? (Pricing Overview)
Microsoft publishes per-region rates, and they differ by SKU. Here are the US figures from Microsoft's pricing page, in USD per hour:
| US region | Standard_v2 fixed | Standard_v2 CU | WAF_v2 fixed | WAF_v2 CU |
|---|---|---|---|---|
| East US | $0.20 | $0.008 | $0.36 | $0.0144 |
| West US 2 | $0.20 | $0.008 | $0.36 | $0.0144 |
| Central US | $0.246 | $0.008 | $0.443 | $0.0144 |
Billing is hourly, and a partial hour counts as a full hour. The gateway bill is the fixed cost plus capacity-unit cost.
One capacity unit (CU) equals the highest of these dimensions, not the sum:
- 2,500 persistent connections
- 1 GB/hour of throughput
- One compute unit
Pricing note: Rates and meter definitions change. Verify every figure against Microsoft's live pricing page and the Azure Pricing Calculator before committing to a budget.
Typical Cost Scenarios
The estimates below use East US rates and 730 hours per month. They are illustrations, not quotes.
Entry-level: one Standard_v2 gateway, modest traffic, about 10 CUs average
- Fixed: $0.20 × 730 = $146
- Capacity: 10 × $0.008 × 730 = $58.40
- Total: roughly $204/month, plus the public IP, outbound transfer, and logs
Standard production: Standard_v2 production plus staging and dev, with production averaging 40 CUs
- Production: $146 + (40 × $0.008 × 730 = $233.60) = about $380
- Staging and dev, each at 10 CUs: about $204 × 2 = $408
- Total: roughly $788/month. Extra environments often cost more than the production traffic itself.
Security-focused: WAF_v2 in production, 65 CUs, plus a WAF_v2 disaster-recovery gateway at 10 CUs
- Production: $0.36 × 730 = $262.80, plus 65 × $0.0144 × 730 = $683.28, about $946
- DR gateway: $262.80 + (10 × $0.0144 × 730 = $105.12), about $368
- Total: roughly $1,314/month. Add Front Door, Traffic Manager, or heavier monitoring if the design needs them.

All three scenarios exclude taxes, negotiated discounts, credits, backend compute, data transfer, Azure Monitor, Front Door, and unrelated application services.
Key Factors That Affect the Cost of Azure Application Gateway and Cost Breakdown
Think of the bill in three layers: fixed charges, usage-based charges, and adjacent infrastructure. The gateway line item is only the first layer.
Gateway SKU and Product Configuration
Standard_v2 and WAF_v2 share autoscaling, zone redundancy, and static VIP. WAF_v2 adds integrated WAF protection, custom rules, and policy associations, at roughly 1.8x the fixed and CU rates.
Application Gateway for Containers is a separate product with its own meters: resource-hours, frontend-hours, association-hours, and CU-hours. Estimate it separately. v1 retired on April 28, 2026, so v2 is the only supported option.
Traffic, Capacity, and Scaling Behavior
Compute work from TLS connections per second, URL rewrites, and WAF processing all push CU consumption up. Larger certificate keys and request sizes do too.
The formula is simple:
Monthly cost = fixed rate × hours + billable CUs × CU rate × hours
Billable CUs are the higher of utilized capacity and reserved capacity. Each configured minimum instance reserves 10 CUs. A minimum of 6 instances therefore bills at least 60 CUs, even on a quiet night. A minimum of zero reserves nothing, but the fixed charge still applies.

Model baseline, typical, and peak traffic separately. Autoscaling supports a minimum of 0 to 100 instances and a maximum of 125.
Cost Components Beyond the Headline Gateway Price
- Gateway and CUs: gateway-hours are fixed; CU-hours are variable. Count production, staging, development, and DR separately.
- Public IP: not included in the gateway charge. Standard static IPv4 runs $0.005/hour, about $3.65/month.
- Outbound transfer: the first 100 GB/month is free, then $0.087/GB for the next 10 TB. Inbound is free, and throughput CUs don't replace transfer charges.
- Diagnostics: Log Analytics bills per GB ingested, with 31 days of retention included. Check current ingestion rates on the Azure Monitor pricing page.
- Operations: certificates, rule tuning, troubleshooting, failover tests, and engineering time are internal costs, not Azure charges.
Zone redundancy adds no charge beyond standard CU pricing.
Low-Cost vs High-Cost Azure Application Gateway: How to Estimate the Right Budget
The cheapest design isn't always the right one. Match spend to routing complexity, security posture, availability targets, and workload behavior.
Lower-Cost vs Higher-Cost Designs
- Performance: a modest minimum with autoscaling costs less than a high reserved floor or multiple regional gateways.
- Security and resilience: use Standard_v2 when you don't need gateway-integrated WAF. Move to WAF_v2, zone redundancy, multi-region routing, or Front Door layering only when requirements justify it.
- Maintenance: under-sizing risks performance problems. Over-sizing, duplicate gateways, and forgotten high minimums create steady waste.
Estimating the Right Budget
- Gather inputs: region, SKU, gateway count, environments, request volume, throughput, connection patterns, peaks, WAF needs, availability targets, and any Front Door requirement.
- Build the estimate: use the Azure Pricing Calculator. Enter gateway-hours, CU-hours, public IPs, transfer, monitoring, and retention as separate lines.
- Validate after launch: compare Azure Cost Management data and gateway metrics against your baseline. Then tune minimum capacity, autoscale limits, and diagnostics.

Set budget alerts, but know their limits. Cost data typically arrives within 8 to 24 hours, and budgets evaluate every 24 hours. They notify you; they don't stop spending.
What Most People Miss When It Comes to Azure Application Gateway Cost
Looking only at the hourly rate. Reserved CUs, WAF premiums, peaks, transfer, diagnostics, and per-environment duplication all sit outside that number.
Defaulting to Application Gateway. Microsoft's decision guidance separates the options:
| Service | Layer and scope | Best for |
|---|---|---|
| Azure Load Balancer | Layer 4, regional or global | TCP/UDP and non-HTTP traffic |
| Application Gateway | Layer 7, regional | Application-layer routing |
| Azure Front Door | Layer 7, global | Global HTTP(S), caching, acceleration |

Front Door Standard starts at $35/month and Premium at $330/month, before request and transfer charges. Standard supports custom WAF rules only. Premium adds managed rule sets and bot protection.
Treating sizing as one-and-done. Microsoft's FinOps guidance notes that gateways with empty backend pools keep billing. Azure Advisor's cost workbook flags them. Review idle capacity, log retention, unused gateways, stale rules, and DR resources on a schedule.
For broader Azure spend reviews, Lucidity helps FinOps and infrastructure teams optimize cloud block storage. Its Lumen product flags four idle-disk types (unattached, reserved, unmounted, and zero-I/O) that can account for up to 70% of unused block-storage spend. It doesn't replace Azure's own tools for Application Gateway billing.
Conclusion
Application Gateway cost comes down to SKU, fixed gateway-hours, capacity-unit usage, WAF needs, traffic patterns, deployment count, and the services around it.
Model your real architecture, validate it with Azure Cost Management, and pay only for the Layer 7 routing, security, scale, and resilience your application needs.
Frequently Asked Questions
What is an Azure gateway?
Azure gateways are managed services that direct, secure, or connect traffic. Application Gateway is Azure's regional Layer 7 HTTP/HTTPS load balancer, while VPN Gateway handles encrypted hybrid connections.
How much does an Application Gateway cost in Azure?
It depends on region, SKU, gateway-hours, CU consumption, WAF, traffic, and related services. In East US, Standard_v2 starts at $0.20 per gateway-hour. Use Microsoft's pricing page and calculator for an exact estimate.
How much does a WAF cost?
There is no universal Azure WAF price. Application Gateway WAF_v2 uses higher gateway and CU rates ($0.36 fixed in East US), while Front Door WAF depends on the tier plus traffic. WAF rules carry no extra fee.
Does the Azure Front Door come with WAF?
It depends on the tier. Standard supports custom WAF rules only, while Premium includes managed rule sets and bot protection. Front Door WAF is separate from Application Gateway WAF, so check current pricing.
What are capacity units in Azure Application Gateway?
A capacity unit measures gateway capacity consumed by connections, throughput, and compute. One CU is 2,500 persistent connections, 1 GB/hour, or one compute unit. Billing follows the highest dimension.
What costs should I include beyond the Application Gateway hourly charge?
Include capacity units, WAF premiums, public IP, outbound transfer, Log Analytics ingestion and retention, extra environments, complementary services like Front Door, and engineering time.