Azure managed disks come in tiers, principally Premium SSD, Standard SSD, and Standard HDD, and each disk is billed by the provisioned size band it falls into, plus its performance tier, regardless of how much data sits on it. That billing model is the key fact: provisioning a 1 terabyte Premium disk to hold 200 gigabytes means paying for the full terabyte at the Premium rate. The buyer takeaway is that two levers control disk cost, the tier and the provisioned size, and most over provisioned estates have room on both. Premium where only Standard is needed, and large where small would do, are the two patterns to hunt.
Here is how the tiers differ, and how to rightsize tier and capacity together.
How are the disk tiers priced and what fits where?
Premium SSD targets production workloads that need consistent low latency and high IOPS, and it carries the highest per gigabyte rate. Standard SSD sits in the middle, suited to workloads that want SSD responsiveness without the Premium performance guarantees, at a lower rate. Standard HDD is the cheapest, fit for backups, archives, and infrequently accessed or development data where latency is not critical. The common waste pattern is Premium applied by default across a fleet, including to development disks, log volumes, and lightly used systems that would run perfectly on Standard SSD or HDD at a fraction of the cost. Tiering each disk to its actual performance need is the first pass.
Why does provisioned size matter so much?
Because you pay for the band you provision, not the data you store, and managed disks bill in size tiers that step up in fixed increments. A disk provisioned far above its real usage pays for empty capacity at its tier rate every hour. Pull actual usage against provisioned size across the fleet and the over provisioned disks stand out. As with most block storage, you cannot shrink a managed disk in place, so rightsizing capacity means provisioning a correctly sized disk, migrating the data, and retiring the oversized one, or building the right size into the next deployment. Pair the size pass with the tier pass so you fix both at once.
How do reservations and bursting fit in?
For the disks you keep, two further levers apply. Azure offers reserved capacity pricing on some disk types, which discounts the committed storage in exchange for a term, suitable for the stable production disks you are confident you will keep. And for Premium SSD, on demand bursting can absorb short spikes without provisioning a permanently larger, more expensive disk, which lets you size for the steady state rather than the peak. Use reservations on the durable base and bursting to avoid oversizing for rare spikes; neither changes the application, only the economics underneath it.
A worked example
A European SaaS company had standardised on Premium SSD across its Azure estate, including development, test, and logging disks that saw light, latency tolerant use. A review tiered the non production and low performance disks down to Standard SSD and HDD where the workload allowed, and rightsized a long tail of disks provisioned two to three times above actual usage. Production disks that stayed on Premium were placed on reserved capacity, and bursting absorbed the occasional spike that had been the excuse for oversizing. None of it touched application behaviour. It was one lever among several in the program that left the company materially lighter on cloud spend. Figures are verified against billing data and anonymised.
| Tier | Fits | Relative rate |
|---|---|---|
| Premium SSD | Latency sensitive production | Highest |
| Standard SSD | General workloads, dev and test | Lower |
| Standard HDD | Backups, archives, cold data | Lowest |
Talk it through with us
If Premium SSD is your Azure default and disks were provisioned for headroom, tiering and rightsizing together usually free up a meaningful share of the storage line. We take zero provider commissions and answer only to you, across AWS, Azure, GCP, and OCI. Our guarantee is plain: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee scoped up front or a no risk Gainshare share of verified savings. Book a strategy call to scope it for your estate, and follow more analysis in The Cloud Spend Navigator.
Frequently asked questions
Do Azure managed disks bill on used or provisioned size?
Which Azure managed disk tier should I use?
Can you shrink an Azure managed disk to rightsize it?
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.