Method
How we measure savings
An identified saving is an estimate; a measured saving shows on your Azure bill. Here is how Finozio gets from one to the other, and what it does not measure.
- Identified or measured
- 30 days before, 30 days after
- Each saving counted once
Two figures
Identified and measured: two separate figures
They do not add up: they do not say the same thing.
Identified savings
- What the recommendations still open (new, in progress, approved) can save.
- Priced as close as possible to what each resource cost you over 30 days, as collected in Azure Cost Management.
- A rejected recommendation never counts.
Savings measured on your bill
- What the bill says, for the recommendations your team marked as applied.
- The collected cost of each resource concerned, before and after the fix.
- It can be negative: if the bill went up, Finozio shows it.
The measurement
A 30-day window, before and after
From Pilot on, Finozio re-reads your inventory every week. Each reading carries, for the resources it prices from measurements, their cost over the last 30 days as read in Azure Cost Management.
The date of the change
When a recommendation is marked as applied, Finozio records the date. If it is moved back, the date is removed.
The cost before
For each resource concerned, its 30-day cost in the last reading taken before that date.
The cost after
Its 30-day cost in the first reading taken at least 30 days later: a window entirely after the change. A deleted resource counts as 0, if the reading did read its type.
The difference
The measured saving, per month: the sum of the costs before, minus the sum of the costs after. Until then, the measurement is pending, with the date it becomes possible.
In your workspace, each applied recommendation says whether its saving is measured, pending or not measurable, and why.
No double counting
Each saving, counted once
- One resource, one amount: when Azure Advisor and a Finozio rule target the same resource, the total counts it only once.
- Two changes on the same resource, shutting it down at night and resizing it: the total keeps the larger of the two, never their sum.
- Deleting a resource rules out the other changes on it and on what goes with it (disks, IP addresses).
- A reservation or a Savings Plan, and a change that reduces the same usage: the total keeps the better of the two combinations, never both.
- On the bill, a resource targeted by two applied recommendations is measured once: from its cost before the first change to its cost 30 days after the last.
Source
Where each recommendation comes from
Imported from Azure Advisor
Finozio re-reads Azure Advisor on every scan and keeps its recommendations, labeled as such.
From Finozio's rules
Finozio's rules complement Advisor, based on your inventory, your collected costs and your Microsoft 365 usage.
From Finozio's rules does not mean invisible to Microsoft: some cases, such as Azure Hybrid Benefit or stopped VMs, also show up in Microsoft's tools.
Limits
What Finozio does not measure
When a saving cannot be measured, Finozio says so. It never replaces a missing measurement with a list price, or with €0.
- Reservation and Savings Plan purchases: they lower a price, with no resource whose cost could be compared before and after.
- Findings that point to no resource: a service or resource group that costs more, tagging, empty load balancers.
- Azure Advisor recommendations outside cost: reliability, security, performance.
- A resource with no collected cost before or after the fix, such as an attached Premium disk or a SQL database.
- A recommendation marked as applied before Finozio recorded the date of the change.
- Microsoft 365 and Copilot licenses: their savings are estimated from the seats collected, not measured on the Azure bill.
- The cause of a difference: the measurement compares two billing periods; higher traffic or a Microsoft price change weighs on it too.
See what Finozio finds, then measure it.
Free report · Read-only · No credit card