How findings work
How Costframe labels estimate, proof level, target type, evidence contract, and verified realized savings.
On this page
Estimate is not verification
Start with the resource, observation date and evidence limits. A detector result identifies a condition to review.
An estimated saving describes what a proposed change might avoid; approval or a closed ticket does not prove that the change happened or the bill fell. Use the displayed verification evidence when reporting realized savings.
Review an unattached disk
An unattached disk may be left over from a retired VM, or it may be retained for recovery. Check the recorded attachment state and its date, then ask the workload owner about retention and dependencies.
If the owner approves removal, carry it out through your normal Azure change process. Costframe does not delete the disk.
Governance and security findings
A missing ownership tag or a security exposure can require work without having a direct saving. Zero direct savings is intentional for these findings.
Likewise, a cost anomaly describes excess spend in an observed period; it does not establish a recurring amount you can recover each month.