TL
The short answer

The right Azure spend review cadence is three nested loops. A weekly loop catches anomalies and checks reservation utilization. A monthly loop reviews cost by subscription and finds rightsizing opportunities. A quarterly loop revisits commitment strategy, MACC drawdown, and architecture against the forecast. Each loop has a clear owner and reconciles against Azure cost exports, the source of truth. Without a cadence, Azure spend drifts up between invoices and the only review that ever happens is the one a surprise bill forces.

This is an Azure cost fundamentals discipline. The instruments and migrations matter, but the cadence is what keeps them working after the first optimization pass.

Start from the source of truth

Every cadence reconciles against Azure cost exports in the FOCUS format, landed in storage and queryable. Cost Management in the portal is fine for a quick look, but it summarises; the exports are the granular, line item record you can trust for allocation across many subscriptions, anomaly investigation, and commitment analysis. Stand up the export before the cadence, because a review that argues about which numbers are right never reaches the decisions.

Tagging discipline then decides how useful every review will be. If resources carry team, product, and environment tags, the monthly cost by subscription review takes minutes. If they do not, it becomes a forensic exercise nobody has time for.

The weekly loop: catch the runaway

The weekly review is short, owned by the platform or FinOps lead, and exists to catch problems while they are small. It looks at three things.

  • Anomalies against the trend. Any service or subscription spending materially above its recent pattern. A misconfigured job, a forgotten environment, or a runaway Log Analytics ingestion shows up here within days, not at month end.
  • Reservation and Azure Savings Plan utilization. Are your reservations being fully used and is coverage where it should be. Underused commitment is money already spent; uncovered steady usage is discount left on the table.
  • New and untagged resources. Fast growing or untagged resources flagged for an owner before they become a line item nobody recognises.

The weekly loop is the cheapest insurance in Azure cost management. A runaway that would have been a five figure monthly surprise becomes a same week fix.

The monthly loop: review and rightsize

The monthly review is the working session, owned jointly by the platform team and the spending teams. It closes the prior month and acts on it.

  • Cost by subscription and service. Each team sees its attributed spend against budget, in showback. Trends matter more than the absolute number, especially against a unit metric.
  • Rightsizing opportunities. Oversized virtual machines, idle resources, and orphaned disks. Azure Advisor recommends here, but it recommends, it does not decide, so a human confirms each move against real workload behaviour.
  • Standing wins. Azure Hybrid Benefit eligibility, Dev Test pricing where it applies, and burstable families for steady low usage. These change the underlying math rather than just the rate.
  • The quiet budget eaters. Log Analytics ingestion, data transfer, and premium tiers that were set for a launch peak and never lowered.

The quarterly loop: strategy and the MACC clock

The quarterly review steps back from operations to strategy, and it usually includes leadership. It revisits commitment strategy against an updated forecast, checks MACC drawdown against the clock so unspent commitment does not become a shortfall you still owe, and reviews architecture for structural savings the rate levers cannot reach.

Worked example

A European SaaS company ran no regular Azure review and found, each quarter, that spend had crept up again. Installing a monthly cost by subscription session plus a weekly anomaly check turned it around: rightsizing and Hybrid Benefit surfaced monthly, and the weekly loop caught a Log Analytics ingestion spike that had been quietly adding cost for weeks. Figures are verified against billing data and anonymised.

Frequently asked questions

How often should you review Azure spend?
Run three nested loops: a weekly check for anomalies and reservation utilization, a monthly review of cost by subscription and rightsizing, and a quarterly review of commitment strategy, MACC drawdown, and architecture against the forecast.
What is the source of truth for Azure cost?
Azure cost exports in the FOCUS format, landed in storage, give you the granular record. Cost Management in the portal is fine for a quick view, but exports are what you reconcile every review against, especially across many subscriptions.
What should the weekly Azure review look at?
Anomalies against the trend, reservation and Azure Savings Plan utilization and coverage, and new untagged or fast growing resources. The weekly loop catches a runaway Log Analytics ingestion or an idle environment before it becomes a monthly surprise.

Install the cadence with us

We help enterprises set up the Azure review rhythm, the cost exports, the tagging, and the commitment discipline that keep spend flat, then hand it to your team. It anchors the broader playbook in the Azure cost optimization guide. Our guarantee: we reduce your cloud spend or we reimburse our service fee.

Independent · buyer-side

Put a defensible number on your cloud spend.

No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.

Buyer-side intelligence, monthly.

The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.