What a FinOps audit covers
- The bill: breakdown by service, application and environment, trends, current commitments (reservations, savings plans, MACC, EDP).
- Real usage: utilization metrics (CPU and RAM P95 over 30 days), disk fill rate, log volumes, data processing frequency.
- The top 10 most expensive services, analyzed in depth with the teams involved.
- Governance: tagging, budget alerts, owners, steering committees.
How it runs
| Step | Content |
|---|---|
| 1. Access | Read-only access (Reader) to billing and metrics. Nothing changed without your approval. |
| 2. Mapping | Costs by application, owner and environment; drifts identified. |
| 3. Top 10 services | In-depth analysis of the heaviest services, workshops with application teams. |
| 4. Recommendations | A quantified list: annual savings, difficulty, implementation time, risk. |
| 5. Readout | Quick wins to apply right away, an action plan for the rest. |
| 6. Measurement | A final pass to measure the savings actually achieved on the bill. |
What you get
- The complete list of optimizations, each action quantified and prioritized.
- The quick wins applied or ready to apply: reservations, Stop/Start, cleaning, log retention.
- The re-architecture topics for the most expensive services, with their order of magnitude.
- Results comparable to our case studies, measured on the bill.
- An assessment of your FinOps maturity, with FinOps scoring.
What it costs
The audit is part of both our offers. For an SME, it is paid on results: 20% of the annual savings achieved, charged once, and nothing if there are no savings. For a large enterprise, it is billed at a day rate, on quote, depending on scope. In both cases, the engagement pays for itself in less than 3 months of savings.
For a first look, with no access and no commitment, our analysis tool reads an Azure cost export in your browser. It only sees the bill: the audit goes much further.