Loading
Preparing this Costframe view
Preparing this Costframe viewAzure field manual
Cloud waste guidance with the failure modes included.
Eleven Azure finding guides that explain what the signal means, what Costframe checks, why it might be wrong, how to remediate safely, what rollback requires, and how finance should verify the result.
Updated 11 July 20266 min readReviewed by Costframe product & engineering
Publishing standard
Every guide answers the same safety questions.
- 01What does the signal actually prove?
- 02Which source and observation window support it?
- 03What was not checked or could be stale?
- 04Why could this be a false positive?
- 05Who owns approval and rollback?
- 06How will billed savings be verified?
Finding library
Review by resource type
AllStorageComputeNetworkingPaaSDatabaseCommitmentsGovernance
Evidence standard
A recommendation should explain its limits.
Costframe separates observed evidence from inference. Every finding can show what was checked, what was unavailable, why confidence may be lower, and whether the action still needs approval.
- Checked
- Resource state, associations, utilization, billing, and pricing sources that the detector actually evaluated.
- Not checked
- Signals the current connection or provider API could not supply. Missing evidence is never presented as proof.
- Freshness
- The observation window and last successful check, so reviewers can judge whether the finding is still current.
- Contradictions
- Signals that weaken the recommendation, lower confidence, or require a manual owner review.
Check your environment
Run this check with the evidence attached.
Review the resource state, source, freshness, confidence limits, and safe next action before anyone changes production.