Turn cloud cost review into an operating routine

This page records a 2021 webinar presented by Rodney Joyce on cloud cost management. The event and its old download form have closed. The retained material is a discussion framework, not a current savings forecast.

Rodney Joyce’s speaker profile is preserved from the original page.

The five-part review

The webinar organised cloud cost work into five activities:

1. understand the costs;
2. assess improvement options;
3. optimise usage and cost;
4. establish governance;
5. educate the people who create and approve spending.

The sequence is still useful when each step has a defined scope, evidence, and owner.

Start with cost visibility

Agree on the billing scope, time period, currency, and allocation method. Map material cost to workloads and teams. Separate expected demand, one-time changes, price effects, and commitment coverage before calling movement waste.

Test every recommendation

Rightsizing, schedules, architectural changes, reservations, and savings plans carry different risks. Review performance, resilience, security, licenses, contracts, and future demand with the workload owner before applying an action.

Microsoft’s current Cost Management best-practices guide should replace old portal instructions or feature assumptions.

Make governance operational

A useful cost routine defines:

• who reviews budgets and anomalies;
• who can approve a service change;
• which actions require architecture or security review;
• how expected and actual effects are compared;
• when an accepted exception is reviewed again.

Training should match these responsibilities. Engineers need the cost effect of design choices; finance teams need workload context; leaders need a clear decision path.

Retained slides

The original presentation remains available on SlideShare. Treat product screenshots and service claims in those slides as dated to 2021.