Sample audit

The free audit produces one full Azure FinOps report, combining your connected cost and resource metadata with an Infralign practitioner’s review. The output is a prioritised decision document, not a feed of unreviewed recommendations.

Illustrative demo estate — not a customer result

Every example on this page comes from a synthetic demo estate. The screenshots show the format of a finding — they are not a customer result and not a savings promise.

Click any image to enlarge.

What each finding contains

Six fields, the same on every finding. Reading your audit report explains each one and shows how to prioritise across them.

Field	What it carries
€ impact	The estimated monthly saving in euros, from your billing data and Azure pricing. A modelled figure is labelled indicative until a change can be measured.
Evidence	Billing period, resource identifiers, the utilisation or configuration signal (for example 30-day p95 CPU or idle-day count), and source freshness. Advisor is named as an input, not as a verified answer.
Owner	The team or person best placed to approve the change, confirmed in the working session where tagging is thin.
Effort	What implementing the change involves, including any application-code changes.
Risk	The blast radius if the change misbehaves, stated plainly, with residual risk named.
Next action	Approve it, gather one missing piece of evidence, or park it with a review date.

What a finding looks like

The card below is a real commitment-coverage finding from the NovaPulse demo estate — about €226 a month, which is the largest thing the demo’s cost record alone can evidence. It is here for the format: the chips carry severity, confidence, effort and basis, and the number underneath is the estimated monthly saving.

The evidence chips reference the exact warehouse fields behind the number; the readable evidence sits behind Details in the app.

A worked example

A separate, illustrative case — a different finding type, and a larger one, because most estates carry more slack than the demo tenant does. Every figure below is indicative, not measured.

Opportunity: reduce the operating schedule of a non-production compute group.

Field	Value
Indicative annual opportunity	€18,000–€22,000
Evidence	42 of the last 45 days show low utilisation outside agreed working hours; the estimate uses the demo estate’s billed compute rate and the proposed schedule.
Confidence	Medium — dependency confirmation required.
Effort	1–2 engineering days.
Risk	Medium — test and release windows must be confirmed.
Owner	Platform engineering.
Next action	Validate dependencies, approve a two-week controlled schedule trial.
Measurement	Compare like-for-like operating hours and billed cost after the observation period.

A real finding is quantified only from your connected estate and your reviewed context. No saving is reported as verified until the agreed observation window closes — see savings measurement methodology.

Review sequence

1. An Infralign practitioner checks source coverage and reconciles the cost baseline.
2. The practitioner reviews candidate findings for duplicates, weak evidence, and operational constraints.
3. Your technical owner adds architecture and business context that read-only data cannot provide.
4. The report is finalised with accepted, rejected, or investigation-needed decisions.
5. In an engagement, selected findings move into human-led validated fixes.

What the audit is not

It is not a penetration test, compliance assessment, general architecture certification, reservation-purchase instruction, or a guarantee that every indicative opportunity will be implementable. It does not change Azure resources.

---

Next: Security and data flow — what enters Infralign, where it goes, and how you stop it.