Normalized pricing ($/vCPU, $/GB)
On-Demand price divided by vCPU or by GiB of RAM, so sizes of different shapes compare fairly.
Two sizes with different vCPU and memory are hard to compare on sticker price alone. The $/vCPU/hr and $/GB/hr columns divide the Linux On-Demand rate by the vCPU count and by the memory, giving a per-resource unit price.
Compute-heavy work reads best on $/vCPU; memory-heavy work reads best on $/GB. Both columns are sortable so you can rank the whole catalog by whichever resource dominates your cost.
More Azure pricing terms
On-Demand (Pay-As-You-Go)Reserved VM Instance (RI)Savings Plan for ComputeAzure Hybrid Benefit (AHB)Spot Virtual MachinesSpot eviction & eviction policyDev/Test pricingARM region nameMeter & SKUVM series naming (D, E, F, B and s/a/p)Constrained-vCPU sizesB-series burstable & CPU creditsEphemeral OS diskCobalt & Ampere (Arm on Azure)vCPUEffective hourly rateWindows vs Linux pricingMax saving %Best price region