Colour theme
Book a consultation

Checking cloud savings before you commit

Compare cloud commitments, interruptible compute, storage tiers and transfer costs against your workload. Test recovery and billing assumptions first.

Stacked coins beside a calculator, notebook and pencil on a purple surface.

A lower hourly rate can come with a longer commitment, less flexibility or extra recovery work. Compare the full arrangement with the workload your business expects to keep, including quieter periods and planned changes.

Begin with the cloud-cost review to identify owners and resources that can be changed safely. Once that work is done, use the remaining usage to assess pricing and architecture options. Don’t lock in payment for an environment you intend to remove.

Model the commitment

Ask for a comparison of on-demand costs and the proposed commitment using representative usage. Include the least busy periods, planned migrations and charges the offer doesn’t cover. Record the currency and taxes so finance can reconcile the estimate with its Canadian-dollar budget.

Azure savings plans exchange an hourly spending commitment for discounted eligible usage. Unused commitment in an hour expires; it doesn’t carry forward. Purchases can’t be cancelled or refunded. Microsoft’s compute savings plan also excludes storage, networking and software charges.

Reservations have their own coverage and change terms. Check the exact service, region, term and available exchange or cancellation options. Don’t assume that buying a billing discount guarantees capacity or improves application availability.

Have the business owner approve the commitment and its downside scenario. Record who’ll check utilization and when the term ends. A recommendation based on past consumption needs review if the system is changing.

Plan for interrupted work

Some computing work can stop and resume: a repeatable batch conversion, for example, may be a candidate for interruptible capacity. A system needed continuously by staff or customers needs a different assessment.

Azure Spot VMs can be evicted when Azure needs capacity, and they have no availability SLA. Assess whether the application can save progress, retry safely and run elsewhere when capacity isn’t available.

Test an interruption during a job. Confirm how completed and incomplete items are distinguished, where results are stored and what a restart costs. Include engineering, monitoring and fallback capacity in the comparison. A cheaper rate may be unsuitable if recovery loses work or needs someone to intervene every time.

Price storage retrieval

Separate working data, required records, backups and temporary files. Their access and recovery needs differ. Decide which copies can move to a lower-cost tier and who makes that call.

Microsoft’s Azure archive-tier guidance describes offline storage that must be rehydrated before reading. Retrieval can take hours and incur charges. Moving or deleting data before the minimum storage period can also produce an early deletion charge.

Test retrieval of representative files and a recovery scenario before changing a lifecycle rule. Include the cost of reading, moving and restoring data. Keep any records you’re required to retain or preserve, whatever they cost to store.

Include data movement

Map the transfers the application needs: between regions, to another provider, to staff devices and into backup or reporting systems. Check the current rate for each route and service. A storage price comparison can be misleading when a different placement adds frequent transfers.

Review access, privacy and recovery requirements alongside cost. Moving everything into one location to reduce transfer charges can change the system’s failure and data-handling arrangements. Use the workload-placement guide to document those tradeoffs.

Verify the first bill

Keep the estimate the owner signed off, its assumptions and the measured result together. Compare the first complete billing period with the expected usage and commitments. Investigate differences before extending the change.

Azure budgets can alert on current or forecast spending; they don’t stop consumption. Send the alerts to someone who can investigate. Any automated resource change needs its own sign-off, safeguards and testing.

Talk to us if you need help comparing a cloud offer with the workload, recovery arrangements and contracts your business depends on.


Featured Image Credit