Colour theme
Book a consultation

Keeping cloud costs under control

Find unused cloud resources, assign owners and test cost changes without losing recovery options. Check budget alerts and commitments before relying on them.

A light blue cloud inside a blue circle with a long diagonal shadow.

A rising cloud bill can reflect more customers, a new project or resources that no longer serve a purpose. Before cutting anything, identify which services produce the increase and who depends on them.

Start with one billing period and compare it with the previous one. Separate usage changes from price, currency and contract changes. Record the billing currency so finance can reconcile the forecast with its Canadian-dollar budget.

Give each cost an owner

Group charges by service, project and environment using billing reports and tags where supported. For each significant group, record its business purpose, technical owner and the person who decides on changes.

Include attached storage, backups, logging, network services and support. A server’s compute charge is only part of its cost. Mark resources with no known owner for investigation. Don’t delete something just because you don’t recognize its name.

Ask project owners whether a development environment still needs to run, whether temporary exports can be removed and when a trial should end. Keep those decisions with the resource record.

Check what a shutdown saves

Scheduling a test environment to stop outside working hours may reduce cost, but verify the provider’s billing behaviour and the team’s restart needs. Microsoft distinguishes stopped and deallocated Azure VMs: a stopped VM can still incur compute charges. Deallocation releases compute resources, while charges such as disk storage can continue.

Before deleting an apparently unused disk or database, check its links to applications, backups, recovery procedures and retention requirements. Get the owner’s approval and record the recovery option. Don’t remove the only usable copy of a business record to lower an invoice.

Resize against the workload

Review memory, processor use, storage performance and application response times over representative busy periods. A server with low average CPU use may still need its size for a peak or a memory-heavy job.

Try a change in a test environment or an agreed maintenance window. Record the original configuration, expected saving and rollback steps. Ask users to check the work the system supports, then compare performance and billed usage after the change.

Check backup and archive costs separately. Lower-cost storage can have retrieval delays or charges that matter during recovery.

Treat alerts and commitments separately

Azure Cost Management budgets can notify you when spending crosses a threshold. Creating a budget doesn’t stop consumption. Billing data and notifications also have delays. Assign someone to act on alerts; any automated shutdown needs its own design and tests.

Before buying a reservation or savings commitment, compare its terms with the usage you expect to keep after cleanup. Include existing commitments when estimating savings. Reducing a resource doesn’t necessarily reduce a payment you’ve already committed to make.

Keep a short change record

At the next cost review, compare expected and observed savings and note any performance or support effects. Keep the list of owners current as projects finish. Use that record to inform your IT budget.

Talk to us if you need help tracing cloud charges to the systems your business uses and planning changes with recovery in mind.


Featured Image Credit