The cloud’s greatest strength — you can spin up almost anything in minutes — is also how its bills get out of hand. On Azure, the difference between a controlled environment and a runaway one is rarely the technology; it is whether anyone is actively managing the spend. The encouraging news for South African businesses is that the levers to control Azure cost are real, significant, and mostly unused. Here are the five places businesses overspend, and how to stop.
This is a practical companion to our deeper Azure migration and governance whitepaper, focused purely on the money — the day-to-day discipline behind our Azure service.
1. Paying pay-as-you-go for steady workloads
The default pricing — pay-as-you-go — is the most expensive way to run anything predictable. If a server runs all day every day, paying the on-demand rate for it is like paying the walk-up price for a flight you take every week. Azure Reservations and Savings Plans let you commit to one or three years of usage in exchange for a substantial discount — Microsoft cites savings of up to around 72% versus pay-as-you-go. The trade-off is commitment, so the right approach is to reserve your stable baseline and keep only genuinely variable workloads on the flexible rate. Most businesses never make this switch and overpay on it every single month.
2. Paying for Windows and SQL licences twice
If you already own Windows Server or SQL Server licences with Software Assurance, you can apply them to Azure through Azure Hybrid Benefit instead of paying for the licence a second time, baked into the hourly rate. For a Windows- and SQL-heavy estate this is one of the largest available savings, and it is frequently left on the table simply because nobody flagged it during the move. If you migrated to Azure and never mentioned your existing licences, this is the first thing to check.
3. Oversized and forgotten resources
Cloud resources are easy to create and even easier to forget. Virtual machines get provisioned two sizes larger than they need “to be safe.” A test environment spun up for a project keeps running for a year after the project ended. Disks stay attached to machines that no longer exist. None of these announce themselves — they just quietly bill. Rightsizing (matching the resource to actual usage) and regular cleanup of orphaned resources routinely recover a meaningful slice of a cloud bill, and Azure’s own Advisor tool will point most of them out if anyone looks.
4. No tags, so no accountability
If you cannot tell which department, project, or client a cost belongs to, you cannot control it — nobody owns a number they cannot see. Tagging every resource with an owner and a cost centre turns one opaque monthly total into a breakdown you can question. It is unglamorous housekeeping, but it is the foundation of cost control: spend becomes visible, and visible spend gets managed. Untagged environments are where waste hides indefinitely.
5. No budgets, so no early warning
Most cost shocks are discovered when the invoice arrives — far too late to do anything about them. Azure lets you set budgets with alerts that fire when spend crosses a threshold, giving you the chance to investigate a spike while it is still small. A misconfigured service or a runaway process caught on day two costs a fraction of the same problem caught at month-end. Budgets and alerts are free, quick to set up, and almost universally skipped.
The South African footnote: egress
One regional quirk worth knowing: outbound data transfer — egress — is billed, and the rates for the South African region are among the higher ones globally. A chatty cross-region integration or a backup pointed at the wrong place can accumulate real cost quietly. It is another reason architecture and region choices deserve thought up front; cost is a design decision, not just an operational one.
The practical next step
If you are on Azure and have never reviewed reservations, hybrid benefit, rightsizing, tagging, and budgets, there is almost certainly money being wasted right now — often a substantial share of the bill. A short cost review will show exactly where, and most of the fixes are configuration rather than spend. For the bigger picture of running a controlled Azure environment, see our Azure migration guide.
Published 16 June 2026. Last updated 16 June 2026.