A file server has 400 GB free. That sounds comfortable until a new project starts adding 20 GB a day and the next expansion needs a purchase approval, a maintenance window and a backup check. The useful question at your next managed service review is how long that space will last, and who will act before the business runs out.
For a Malaysian SME, the impact might first appear as a failed document upload, an application unable to write a log, or staff waiting while IT clears space. A capacity review gives your MSP and business team a chance to decide what to retain, archive or expand while there is still room to work.
Ask which layer the number describes
A physical storage pool, a virtual disk and the filesystem inside a virtual machine answer different questions. A healthy-looking host chart does not establish that the drive holding an application's data has enough free space. Microsoft's Azure monitoring documentation distinguishes host measurements from guest operating system data. Its low free space alert examples use guest disk counters. Ask your provider to identify the actual volume or mount point being monitored and show a recent reading, rather than relying on a server-wide average.
On a clustered platform, add the storage pool to that review. Microsoft's Storage Spaces Direct guidance distinguishes usable volume size from its physical footprint, which depends on the resiliency layout. It also calls for unallocated pool capacity so repair can take place after a drive failure. Ask the engineer to explain how much of the apparent free space is available for business growth after the platform's repair reserve. The answer is specific to that design; it should not be guessed from the headline raw disk capacity.
Turn free space into a decision date
Start with the systems that hold active business data. For each, ask for current free capacity, recent net growth, the date of the last measurement and the largest expected near-term increase. Separate ordinary growth from one-off events such as importing a project archive, staging a migration or keeping extra export files. Include the application owner: IT may see the disk graph without knowing that a department plans to upload a large set of drawings next week.
Hypothetical example: a Penang distributor has 400 GB free on its order-document volume and expects net growth of 20 GB per day. At an unchanged rate, that is roughly 20 days to exhaustion. If the team agrees to preserve 100 GB as an operating buffer, there are only about 15 days before that buffer is reached: (400 − 100) ÷ 20. These figures are illustrative, not recommended thresholds or an AXO client result. A batch import or a failed cleanup could change the forecast immediately.
Compare that estimate with the time needed to approve, procure, implement and verify the chosen response. Set the decision date before those activities consume the remaining room. A forecast based on a recent trend is a planning aid, not a guarantee; give fast-growing workloads a shorter review interval and revisit the estimate after an unusual increase.
Make the alert point to an agreed action
Ask for both percentage and absolute free space when they are useful. Ten per cent of a small system disk and ten per cent of a large data volume leave very different working margins. Agree warning and escalation points around the workload's write activity and the time the team needs to respond. Record who checks the cause, who approves extra capacity or archival work, and which business owner can decide what may be moved.
The first response should explain the growth. Removing files without understanding their purpose can destroy records or leave an application unsupported. A short-term cleanup needs an owner, an approved scope and a follow-up date. Keep an agreed retention policy alongside any archival proposal, including how authorised staff will retrieve older material when they need it.
Verify the extra space where the application uses it
An expansion is complete when the intended workload can use the capacity. Microsoft's Storage Spaces Direct management guide describes several stacked storage objects and product-specific expansion procedures; adding physical capacity and expanding a volume are separate operations. Have your provider follow the supported method for the actual platform, record the before-and-after sizes at the relevant layers, and check a representative write or upload with the business team.
Close the change by confirming monitoring covers the new or resized volume and that the next forecast uses the new baseline. Keep a small register of capacity decisions with the forecast date, named owner, approved action and evidence of completion. At the next service review, start with the workloads closest to their decision dates. To discuss how a capacity review could fit your managed infrastructure, contact AXO Technologies.
Sources and dates
Published 11 November 2026. Official documentation accessed 11 November 2026. Operational examples and review suggestions are editorial guidance.
- Microsoft Learn: Monitor virtual machines with Azure Monitor — Alerts — guest disk free space alert examples.
- Microsoft Learn: Monitoring data reference for Azure Virtual Machines — platform and guest measurements.
- Microsoft Learn: Plan volumes on Azure Local and Windows Server clusters — usable capacity, footprint and repair reserve.
- Microsoft Learn: Manage volumes in Azure Local and Windows Server — storage layers and supported expansion.