# Storage cost inefficiencies | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/service-category/storage 92 documented storage cost inefficiencies across Azure, GCP, AWS and more, each with detection steps and remediation. ## All inefficiencies Each entry explains the waste, the billing model behind it, how to detect it and how to fix it. / 92 inefficiencies - Azure Managed Disks CER-0338 ### [Underutilized Azure Managed Disk Reservations](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-azure-managed-disk-reservations) Azure Managed Disk reservations allow organizations to pre-purchase Premium SSD capacity at a discounted rate by committing to a one-year term. However, these reservations operate on a strict use-it-or-lose-it basis - if reserved disk... Storage - GCP GCS CER-0336 ### [Excessive API Request Cost Overhead from I/O-Intensive Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-api-request-costs-from-filesystem-style-access-on-gcs) Google Cloud Storage exposes a flat namespace through an HTTP API, but many workloads consume it through filesystem-style abstractions - FUSE mounts, Hadoop/Spark connectors, or analytic engines that enumerate prefixes to discover state.... Storage - Azure Blob Storage CER-0335 ### [Excessive Transaction Cost Overhead on Blob Storage from I/O-Intensive Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-transaction-costs-from-filesystem-style-access-patterns-on-blob-storage) Azure Blob Storage and ADLS Gen2 bill per transaction - every list, read, write, rename, and metadata operation is a separately metered API call. When organizations migrate workloads from on-premises Hadoop/HDFS environments or local... Storage - AWS S3 CER-0334 ### [Excessive S3 Request Costs from Filesystem-Oriented I/O Patterns](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-s3-request-costs-from-filesystem-oriented-i-o-patterns) Amazon S3 bills for nearly every API request - LIST, HEAD, GET, PUT, COPY, and POST - independently of storage charges (DELETE and CANCEL requests are free). Workloads originally designed for locally-provisioned storage, where listing a... Storage - Amazon FSx CER-0328 ### [Infrequently Accessed Data Retained on High-Performance FSx File Systems](https://www.pointfive.co/efficiency-hub/inefficiencies/infrequently-accessed-data-retained-on-high-performance-fsx-file-systems) Amazon FSx file systems are designed for performance-sensitive workloads such as shared enterprise file systems, high-performance computing, analytics, and machine learning. Storage costs are driven by provisioned capacity (measured in... Storage - Azure NetApp Files CER-0311 ### [Overprovisioned Azure NetApp Files Capacity Pools](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-azure-netapp-files-capacity-pools) Azure NetApp Files bills based on provisioned capacity pool size - not on the actual data stored within volumes. This means that when a capacity pool is provisioned at a size significantly larger than the sum of volume quotas allocated... Storage - AWS ECR CER-0308 ### [ECR Archive Storage Class Used Below 150 TB Threshold](https://www.pointfive.co/efficiency-hub/inefficiencies/ecr-archive-storage-class-used-below-150-tb-threshold) In November 2025, AWS introduced an Archive storage class for private ECR repositories, marketed as a way to reduce storage costs for large volumes of rarely used container images. However, Archive storage pricing is identical to Standard... Storage - AWS S3 CER-0307 ### [S3 Standard - Infrequent Access Used Where Intelligent Tiering Would Be Cheaper](https://www.pointfive.co/efficiency-hub/inefficiencies/s3-standard-ia-used-where-intelligent-tiering-would-be-more-cost-effective) Organizations often use the Standard - Infrequent Access (Standard-IA) storage class based on documentation and code that predate 2021 updates to the Intelligent Tiering storage class. Intelligent Tiering became suitable as an initial S3... Storage - AWS S3 CER-0303 ### [Orphaned Cloud Storage from Dropped External Delta Tables in Databricks](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-cloud-storage-from-dropped-external-delta-tables-in-databricks) When external Delta tables are dropped from Databricks Unity Catalog or the legacy Hive metastore, only the table metadata is removed - the underlying data files in cloud object storage (such as S3, ADLS, or GCS) remain untouched and... Storage - Azure Recovery Services Vault CER-0281 ### [Idle Recovery Services Vault Backups and Suboptimal Backup Storage Tiering](https://www.pointfive.co/efficiency-hub/inefficiencies/idle-recovery-services-vault-backups-and-suboptimal-backup-storage-tiering) Backup data remains in a Recovery Services Vault after the original protected resource has been deleted. These orphaned backups continue to consume storage and generate cost despite no longer supporting an active workload. In addition,... Storage - Azure Backup CER-0278 ### [Azure Backup Data Retained Beyond Intended Retention Period](https://www.pointfive.co/efficiency-hub/inefficiencies/azure-backup-data-retained-beyond-intended-retention-period) Backup data persists longer than intended due to misaligned or outdated retention policies. It often arises when retention requirements change over time, but older recovery points are not evaluated or cleaned up accordingly. In some cases,... Storage - Azure Backup CER-0286 ### [Retained Azure Backup Data After Resource Decommissioning](https://www.pointfive.co/efficiency-hub/inefficiencies/retained-azure-backup-data-after-resource-decommissioning) A protected resource (such as a virtual machine, database, or file share) is decommissioned without explicitly stopping backup protection. In these cases, Azure Backup keeps applying the retention policy to older recovery points, but the... Storage Showing 12 of 92 --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.