The first 30 days of Azure cost control
Week 1: make the data trusted
Start with read-only billing and resource access, then confirm that subscriptions, resource groups, tags, and cost periods line up with how the business talks about spend.
The first goal is not perfect allocation. It is a shared source of truth that finance and engineering can both recognise.
- Connect every active subscription before optimising individual services.
- Check currency, billing period, and missing tag coverage.
- Capture any setup or permission issues as named actions, not vague blockers.
Week 2: set useful budgets
Budgets work best when they create an early conversation. Set thresholds that warn the team before month-end pressure arrives, and route alerts to the people who can explain or act on the movement.
Keep the first set simple: workspace-level spend, the top services, and any resource groups tied to customer delivery or internal projects.
Week 3: turn waste into decisions
Idle resources, orphaned disks, oversized workloads, and obvious reservation gaps should be triaged into actions with an owner and status.
A recommendation is only useful when the team knows whether it is planned, accepted as risk, not applicable, or done.
Week 4: report the operating story
By the end of the first month, the business should be able to see spend, forecast, open actions, resolved savings, and any risks that need leadership attention.
That monthly view becomes the baseline for a repeatable FinOps habit rather than a one-off cleanup project.