Skip to content
Big Data SA
Cloud

How to Cut Your Cloud Bill in South Africa: A Practical Guide for Azure and AWS

Big Data SA Team · 3 November 2026 · 4 min read

Last updated

Illustration of a cloud bill coming down

Most cloud bills don't grow because of one big mistake. They grow because of lots of small ones: a test server nobody switched off, storage nobody cleaned up, a machine sized for a peak that happens twice a year. In South Africa there's a twist. Cloud prices are set against the US dollar, so when the rand weakens, your bill goes up even if nothing else has changed.

The good news is that most organisations can cut their bill without touching performance. Here's where we usually start.

Four common causes of wasted cloud spendWhere cloud money leakszIdle machinesOversized serversForgotten storageData transfer

1. Find out where the money goes

You can't cut what you can't see. Start by tagging every resource with an owner, a project and an environment (production, test or development). Then use the built-in tools, Azure Cost Management or AWS Cost Explorer, to see spend by tag.

Set budgets and alerts too. A message when a project hits 80% of its monthly budget is far better than a surprise on the invoice.

2. Switch off what you don't use

This is the quickest win. Look for:

  • development and test machines running overnight and over weekends
  • virtual machines that were stopped but still have disks attached
  • old snapshots and backups nobody needs
  • public IP addresses and load balancers left over from old projects

Scheduling dev and test machines to run only during office hours can cut their cost by well over half on its own.

3. Right-size your machines

Many servers are still sized on a guess made on migration day. Check actual CPU and memory use over a few weeks. If a machine rarely goes above 20% CPU, a smaller size will probably do. Azure Advisor and AWS Compute Optimizer will both suggest changes for you.

Need a second opinion?

Book a free 30-minute consultation with a senior specialist.

Book a free consultation

4. Commit to what you'll definitely use

For servers that run all day, every day, paying on demand is the most expensive option. Reservations and savings plans give you a big discount in exchange for a one or three-year commitment. Microsoft says Azure Reservations can cut costs by up to 72% compared with pay-as-you-go prices, and AWS offers similar discounts through Savings Plans and Reserved Instances.

A few tips:

  • Only reserve the steady baseline you're sure of, not your peaks.
  • Right-size first, then reserve. Otherwise you lock in waste.
  • If you already own Windows Server or SQL Server licences, check whether Azure Hybrid Benefit lets you use them in the cloud.

5. Use cheaper capacity for flexible work

Batch jobs, data processing and test workloads that can cope with interruptions can run on spot capacity (Azure Spot VMs or AWS Spot Instances) at a steep discount. It's not for your production database, but it's great for overnight jobs.

6. Tidy up storage

Storage is cheap per gigabyte, which is exactly why it piles up. Move older data to cooler, cheaper tiers, set lifecycle rules so that happens automatically, and delete what you genuinely don't need. POPIA also expects you not to keep personal information for longer than you need it, and our guide to POPIA and backups covers retention in more detail.

7. Watch data transfer costs

Moving data out of the cloud, or between regions, costs money. Keep services that talk to each other in the same region. Where it makes sense, use South African regions for South African users: Azure has regions in Johannesburg and Cape Town, and AWS has a region in Cape Town. That helps with speed and data residency too.

8. Make it a habit

Cloud costs aren't a one-off clean-up. Set up a monthly review where someone from IT and someone from finance look at the bill together. This practice is often called FinOps, and the idea is simple: the people spending the money and the people paying for it talk regularly.

Where to start this week

  • Tag your 20 most expensive resources.
  • Set a budget alert on each subscription or account.
  • Schedule dev and test machines to shut down after hours.
  • Pull a right-sizing report from Azure Advisor or AWS Compute Optimizer.
  • List the servers that run 24/7 and could be reserved.

How we can help

At Big Data SA, our cloud cost review usually takes one to two weeks and ends with a ranked list of savings, so you can see what each change is worth. We also help businesses move to Azure or AWS and run it well, and we can embed a cloud specialist in your team if you need an extra pair of hands. Book a free consultation to get started.

Frequently asked questions

Cloud prices are set against the US dollar, so a weaker rand pushes local costs up. Waste, such as idle servers and oversized machines, then adds to the bill.

Switch off idle resources and schedule development and test machines to run only during working hours. Then right-size your servers before you commit to reservations or savings plans.

Reservations usually give the biggest discount for steady, predictable workloads. Savings plans are more flexible across machine types and regions. Many organisations use both, after right-sizing.

Related services

Or contact us directly →

Related articles

Analytics & BIMicrosoft Fabric vs Power BI: What's the Difference, and Do You Need Fabric?Data ProtectionDoes Microsoft 365 Back Up Your Data? What South African Businesses Need to Know
Get in touch