Skip to content
Costframe
Learning library / Practical guides

Azure cost optimization checklist

A useful Azure optimization checklist names the owner, frequency, evidence requirement, safe action, and verification method for every control. It begins with least-privilege access and financial reconciliation, then covers direct waste, rightsizing, storage, commitments, anomalies, ownership, and realized savings.

Costframe practical guide · 3 min read

Turn the checklist into a review queue

Four controls for an Azure review

01

Connect safely

Verify Reader and Cost Management Reader at the intended scopes. Record missing permissions and unsupported checks.

02

Find with evidence

Store resource identity, source, observation window, freshness, contradiction signals, and pricing basis.

03

Act with ownership

Route every finding to the workload owner with risk, approval, maintenance window, and rollback context.

04

Verify financially

Separate direct, estimated, allocation-risk, and security findings; reconcile savings after action.

A procedure with accountable owners

  1. 1 / Access and scope

    Review tenants, subscriptions, billing scopes, provider roles, credential freshness, and connection limitations.

    Owner
    Cloud security
    Cadence
    Monthly
    Verify
    Readiness checks are current and least privilege is preserved.

  2. 2 / Waste and utilization

    Review orphaned storage/networking, stopped compute, empty plans, VM/SQL utilization, and stale snapshots.

    Owner
    Platform team
    Cadence
    Weekly
    Verify
    Each finding includes dependency and false-positive checks.

  3. 3 / Pricing and commitments

    Confirm rate basis, reservation coverage/utilization, lifecycle tiers, and planned demand.

    Owner
    FinOps
    Cadence
    Monthly / quarterly
    Verify
    Calculations reproduce from named sources.

  4. 4 / Closure and reconciliation

    Record owner decision, action date, rollback outcome, expected net saving, and observed billed result.

    Owner
    Finance + engineering
    Cadence
    Monthly
    Verify
    Closed findings have outcome evidence.

Minimum finding acceptance criteria

Identity
Provider, scope, resource ID, type, region
Evidence
Checked, not checked, source, freshness, contradictions
Finance
Rate basis, direct/estimated class, period, currency
Action
Owner, readiness, approval, safe step, rollback
Outcome
Action date and realized-savings verification

Use these criteria to decide whether a finding can enter review. Missing evidence should remain a named limitation, not a completed check.

Record what was checked and what still needs evidence

For every candidate, keep the selected scope, observation period and billing basis with the evidence. Mark unavailable utilization or dependencies explicitly. A checklist entry should let another reviewer reproduce the decision without assuming that an empty result means every resource was checked.

Finish with the follow-up task, not a savings total alone. Name the workload owner, approval requirement and date when billing can be reviewed again. Allocation and governance gaps can be worth addressing while carrying no direct quantified saving.

Your next task

Turn the checklist into a review queue

Choose one subscription and assign an owner to each weekly waste review. Record missing permissions separately from checks that found no issue. Take the first candidate through dependency review, approval and billed verification before expanding the process.

Choose the resource-specific review guide

What not to do

  • ×Using a checklist without named owners
  • ×Treating missing tags as cash savings
  • ×Approving a resource change without dependency and recovery checks
  • ×Measuring completion by number of closed findings

Sources and further reading

Microsoft: cost optimization checklist

Run a monthly cloud cost review

Continue learning