Azure prices: machines, storage, what stays on

Approximate current costs with no job running

Every machine and volume in what stays on today, added up. No compute is in these figures: a job costs the machine rate below, for as long as it runs.

With GPUs, East US

Estimates: list prices, no agreement discount, changed without notice.

With GPUs, Central US

Estimates: list prices, no agreement discount, changed without notice.

Without GPUs, East US

Estimates: list prices, no agreement discount, changed without notice.

Without GPUs, Central US

Estimates: list prices, no agreement discount, changed without notice.

Reading the machine tables

• On demand is the ordinary price: the machine is yours until the job ends.
• Spot is the same machine at a discount, which Azure can take back at any moment; the job is killed when that happens, and the spot price itself moves.
• IB is InfiniBand, part of the machine: the HB, HX and ND families carry it and it is inside the price shown. The D, E and M families have none, so a job that spans several of those machines talks over ordinary Ethernet.
• A day of a machine is 24 × the hourly figure; a month with no job running, 730 ×. $/GPU-h is the on-demand hourly figure divided by the number of GPUs.
• Core-minutes per USD is the credit arithmetic: credits are billed as core-minutes (TRESBillingWeights="CPU=1"), so one dollar buys cores × 60 ÷ the hourly rate. Standard_D2s_v5 in East US on demand is approximately 1250 core-minutes to the dollar today.
• A machine type shown as not offered has no Linux meter in that region's price list today.
• A queue may offer only one of the two purchase kinds. What each queue runs today is in /data/queues.json and on the job script builder.

Four kinds of space, per month

Each kind of space is bought from a different Azure product. The figures are what Microsoft charges for the amount in the row, approximate and per month; the amounts are worked examples, not sizes anyone is given. Home is part of the service and is not billed to the user who has it; there is no scratch on the Azure side yet.

East US

Central US

Estimates: list prices, no agreement discount, changed without notice.

Copying data in and out is done with azsync push and azsync pull, tools written by CCS for this service (not Azure tools); Globus for large datasets.

Azure Managed Lustre is sold in fixed increments, and the increment depends on the throughput tier: 4 TiB steps at 500 MB/s per TiB (4 TiB minimum), 8 TiB at 250 MB/s, 16 TiB at 125 MB/s, 48 TiB at 40 MB/s and 96 TiB at 20 MB/s. A size between two steps is rounded up, never down. See Create an Azure Managed Lustre file system.

Per TiB per month, every tier in the price list

The reference table the figures above are worked out from: one row per storage meter in the price list, and what a TiB of it costs for a month.

East US

Central US

Estimates: list prices, no agreement discount, changed without notice.

Reading the storage tables

• NetApp Files and Managed Lustre are billed on the size provisioned, by the hour, full or empty. A month is 730 hours, so a GiB-hour meter becomes a TiB-month figure as price × 1024 × 730; each row shows its own arithmetic.
• Block blob is billed on the bytes actually stored, per GB-month, and read, write and list operations are billed on top. The rows quote the first price band; above 50 TB and above 500 TB the band is cheaper. Our data account has the hierarchical namespace on, which is the meter quoted here.
• A managed disk is billed whole, whether it is full or empty and whether the machine is running or stopped.
• 1 TiB is 1024 GiB, and every figure in these tables is approximate.
• No PHI, FERPA-protected, export-controlled or CUI data may be placed on this service. There are no backups and no snapshots on the Azure side or on ECC. Keep your own copies of anything you cannot afford to lose.

East US

Estimates: list prices, no agreement discount, changed without notice.

Central US

Estimates: list prices, no agreement discount, changed without notice.

Where these figures come from

• Azure pricing calculator
• Azure Retail Prices API — the API this page reads, and /data/prices.json is what this host read from it
• Azure virtual machine sizes: Dsv5, Esv5, M, HBv3, HBv4, HX, NCasT4 v3, NC A100 v4, NC H100 v5, ND A100 v4, ND H100 v5, ND H200 v5
• Azure NetApp Files pricing
• Azure Managed Lustre pricing
• Azure Blob Storage pricing
• Azure managed disk pricing
• Azure IP address pricing

No PHI, FERPA-protected, export-controlled or CUI data may be placed on this service. There are no backups and no snapshots on the Azure side or on ECC. Keep your own copies of anything you cannot afford to lose.