One Azure Private Endpoint shows roughly 50 TB processed in each direction over 30 days, but the Private Link data charges are under $100. At the documented $0.01 per GB, I expected about $500 per direction. What should I check?
Why is my Private Endpoint traffic charge so much lower than the metrics suggest?
Answers
Start by lining up the metric and billing periods exactly. A rolling 30-day metric and last month's bill can cover different dates, so compare the same calendar window, subscription, region and endpoint.
In Cost Analysis, break out the Private Link data processed ingress and egress meters and check both the billed quantities and effective rates. Both directions can be charged. At $0.01 per GB, 50 TB in each direction suggests roughly $1,000 total before any applicable pricing differences, not under $100.
Reply to this answer
Make sure the bytes metric and the billing meter are measuring the same thing before assuming they should match. Service-level traffic, replication or other internal traffic could be different from bytes processed through a private endpoint.
That explanation is not enough on its own, though. If the 50 TB is specifically the endpoint's Bytes In or Bytes Out metric, it needs closer investigation rather than just being written off as service traffic. DNS resolving to the private endpoint also doesn't by itself prove what every metric or billing line includes.
Reply to this answer
Check the effective rate under your agreement, but don't assume a discount explains a tenfold gap. The reported volume is well below the 1 PB threshold mentioned for the pricing tiers, so compare the actual billed rate and quantity against the applicable pricing for your region and agreement.
Reply to this answer
If the dates, scope, meter quantities and rates still don't reconcile, gather the endpoint resource ID, metric sums, time window and cost breakdown and raise it with Azure support. There isn't enough here to tell whether the difference is in the metric, the billing scope or the charge itself.
Reply to this answer
Service endpoints may be worth considering for some workloads if Private Endpoint costs are a concern. They aren't an automatic substitute, though. Check how administration over VPN, private addressing and any required private connectivity would work before changing the design.
Dovren-5x:
Some integrations or access over ExpressRoute may depend on private connectivity, so cost alone shouldn't drive that switch.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_b73+drumgauge.8:
Checking the quantities is the useful bit here. It separates a rate or discount difference from a mismatch in what was metered.