Free visibility
Reports
Monthly FinOps audit reports, expert-authored and finance-ready, served on the in-app Audits page.
Reports are the written companion to the dashboards: monthly FinOps audit reports explaining what your Azure estate cost, what changed, and what is worth attention. They are served in-app on the Audits page as finance-ready HTML you can read on screen or forward without editing. The dashboards answer “what is it now?”; the report answers “what changed, why, and what should we do about it?”.
Click any image to enlarge.
What a FinOps audit report contains
Section titled “What a FinOps audit report contains”The NovaPulse demo report below says so itself, in its own bottom line: it ran entirely from the FOCUS cost record, with no access to the tenant. Rightsizing, Advisor and waste verification all need tenant access, so they are absent by construction — not because the estate is clean. What the cost record alone can evidence is a €226-a-month commitment-coverage adjustment against €78K of monthly spend, and the report labels that as a property of its evidence rather than of the estate. A connected estate is where the numbers in the FAQ’s results answer come from.
Each report is authored by an Azure FinOps expert on the same data your dashboards read, so the numbers reconcile against the boards. It covers:
- Spend summary — totals for the month against the prior month, by subscription and service, in your billing currency.
- Month-on-month cause analysis — the cost lines that moved most, with the resource-level detail behind each movement, so a change is explained rather than flagged.
- Commitment position — Reservation and Savings Plan coverage against target, and where the position is worth reviewing.
- Savings opportunities — findings surfaced from the estate (idle VMs, rightsizing candidates, orphaned disks, and more). The full set is in what the audit covers.
Reconciling to your Azure invoice
Section titled “Reconciling to your Azure invoice”Your Azure invoice is a billed number. Match it to the board’s Billed series — the billed-by-month tile on the Executive board, or the Billed cost column in the drill-down. The headline effective (amortised) figure spreads commitment purchases across time and will not match line-for-line.
Expect small gaps: amortisation, credits, tax, and marketplace charges each move the two apart. If it will not tie out, raise it in the working session.
Who reports are written for
Section titled “Who reports are written for”Both sides of the table: the platform engineer who owns the resources, and the finance owner who sees the invoice.
- Numbers are in your billing currency, with K/M abbreviations — euros in the demo estate above.
- Movements name the specific resources responsible rather than generalising.
How reports relate to the audit findings
Section titled “How reports relate to the audit findings”The report is where the audit lands each month. Every finding it carries uses the same six fields — see reading your audit report. Approved findings then move into the engagement, where the change is prepared and merged by your team.
Working with reports
Section titled “Working with reports”- Reconcile the report’s Billed series against your invoice once, early — see reconciling to your Azure invoice. After that, trust the pipeline.
- Review the month-on-month cause analysis each month; anything unexplained is a question for the chatbot before it becomes a budget conversation.
- Note the findings you’d prioritise — the audit session starts faster when your team arrives with a view.
Monthly report figures can be provided as a spreadsheet on request during the engagement, and chart-level CSV export is available from the dashboards BI view. A self-serve export API is on the roadmap.
Reports continue for as long as your Azure connection stands, whether or not you proceed to an engagement.
Next: The chatbot — ask your billing data a question in plain language.