Azure pricing for UK engineers

Azure bills at the meter level, but design decisions are made at the workload level. That gap is where most confusion appears. A service can have a simple headline price and still produce a surprising invoice once regional transfer, retention, retrieval, minimum billing thresholds, or always-on infrastructure are involved.

This site is intentionally opinionated about those trap doors. The calculators are there to provide a number quickly, but the surrounding content exists so that the number can be understood and challenged before someone relies on it.

Current coverage is strongest in the services where billing is both common and frequently misunderstood: Blob Storage, Azure Functions, App Service, Bandwidth, Log Analytics, Networking, Data Factory, Virtual Machines, and Virtual Desktop. Several pages are already paired with supporting guides so a user can move from an estimate to a deeper explanation without leaving the site.

That matters for AdSense quality as much as for search quality. A useful pricing site needs to behave like a reference resource, not only a calculator shell.

• NAT Gateway has no pause state, so a low-traffic environment can still carry a standing monthly charge.
• Log Analytics restore and search are not interchangeable. The cheaper route depends on query pattern and data size.
• Archive, Cool, and Cold storage can stop being cheapest once retrieval and minimum-retention charges are included.
• Functions pricing depends on execution shape, not only invocation count, because duration and memory drive GB-seconds.
• Bandwidth costs often come from architecture choices such as region placement, not just from raw traffic growth.

Prices are sourced from the Azure Retail Prices API for UK South in GBP where the API supports the service and meter. The site then applies service-specific logic in the calculator layer and exposes provenance through the trust bar, formula disclosure, and methodology page.

Where a service requires manual verification or special handling, the site should say so directly. That transparency is part of what makes the estimate more useful than a plain list of retail rates.