The cost increase is the difference between your current and target managed-disk pricing tiers, but expanding C: will not resolve a shortage of physical memory (RAM).
Calculate the cost increase
For Standard HDD, Standard SSD, and Premium SSD, Azure generally bills according to the disk’s provisioned performance tier. If the larger capacity crosses into the next tier, billing changes to that tier; Standard disks can also have transaction charges. Premium SSD v2 instead charges per provisioned GiB, with additional charges when provisioned IOPS or throughput exceed the included baselines. ^1^
To obtain the exact difference:
- In the Azure portal, open Virtual machines → your VM → Settings → Disks.
- Select the OS disk and record:
- Disk type/SKU, such as Standard SSD or Premium SSD
- Current size
- Region
- Redundancy, such as LRS or ZRS
- Current performance tier, if shown
- Open Size + performance and note the intended new size and resulting tier, but do not select Resize yet.
- Enter the current and proposed disk configurations separately in the Azure Pricing Calculator, then subtract: Monthly increase = proposed disk estimate − current disk estimate
Azure recommends the Pricing Calculator, your account price sheet, or the portal estimate for cost planning. Signing in to the calculator can include negotiated or discounted pricing, so the exact amount depends on your subscription and region. ^2^
For example, changing a Standard SSD from one capacity tier to the next means paying for the new tier—not merely the amount of data currently stored. Changing a Premium SSD performance tier can also change billing even without increasing its capacity. ^3^
Check what “memory shortage” means first
Before resizing, inspect the exact Windows message:
- “Low disk space,” “C: drive full,” or insufficient storage: expanding C: is appropriate.
- “Low memory,” high memory usage, or insufficient virtual memory: this concerns RAM or the paging file. Increasing disk capacity alone does not add RAM. Azure describes memory pressure as demand exhausting physical RAM or virtual memory backed by the paging file; a memory-intensive workload may require a VM size with more memory. ^4^
In Windows, open Task Manager → Performance:
- Check Memory for sustained high RAM usage.
- Check Disk 0 (C:) or File Explorer → This PC for low free disk capacity.
Expand C: if disk capacity is the issue
Schedule downtime because OS disks that do not meet online-expansion requirements must be deallocated.
- Back up the VM or OS disk before making the change.
- In the Azure portal, open Virtual machines → your VM and select Stop if required.
- Go to Settings → Disks.
- Select the OS disk.
- Select Settings → Size + performance.
- Choose a size larger than the current disk and select Resize.
- Return to the VM’s Overview page and select Start.
- RDP to Windows and open Disk Management.
- Right-click C: and select Extend Volume, then complete the wizard.
Azure disk expansion is a two-stage operation: enlarge the managed disk in Azure, then extend the Windows volume so C: can use the newly allocated space. Existing disks cannot be shrunk afterward, so select the target size carefully. ^5^
References
- Understand Azure Disk Storage billing
- Plan to manage Azure costs
- Performance tiers for Azure Premium SSD managed disks
- Troubleshoot high memory issues on Azure Windows virtual machines
- Expand virtual hard disks attached to a Windows virtual machine