Access and scope
Review tenants, subscriptions, billing scopes, provider roles, credential freshness, and connection limitations.
- Owner
- Cloud security
- Cadence
- Monthly
- Verify
- Readiness checks are current and least privilege is preserved.
Preparing this Costframe view
Preparing this Costframe viewCostframe field guide
A useful Azure optimization checklist names the owner, frequency, evidence requirement, safe action, and verification method for every control. It begins with least-privilege access and financial reconciliation, then covers direct waste, rightsizing, storage, commitments, anomalies, ownership, and realized savings.
Framework
Verify Reader and Cost Management Reader at the intended scopes. Record missing permissions and unsupported checks.
Store resource identity, source, observation window, freshness, contradiction signals, and pricing basis.
Route every finding to the workload owner with risk, approval, maintenance window, and rollback context.
Separate direct, estimated, allocation-risk, and security findings; reconcile savings after action.
Implementation playbook
Review tenants, subscriptions, billing scopes, provider roles, credential freshness, and connection limitations.
Review orphaned storage/networking, stopped compute, empty plans, VM/SQL utilization, and stale snapshots.
Confirm rate basis, reservation coverage/utilization, lifecycle tiers, and planned demand.
Record owner decision, action date, rollback outcome, expected net saving, and observed billed result.
Worked example
Costframe only publishes detector guidance when the relevant technical accuracy threshold can be stated clearly.
Evidence standard
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.

Decision tree
If source data is missing or stale, record the limitation before quoting impact.
If no team owns the resource, assign ownership before opening a change.
Treat the number as estimated until follow-up billing evidence supports it.
Failure modes
FAQ
Use it as an operating framework, then verify the resource, owner, evidence freshness, and billing basis before approving work.
Reject or park the estimate when provider data is incomplete, confidence is low, ownership is unclear, or the action conflicts with migration, resilience, or compliance plans.
Document the evidence source, net/list basis, assumption, owner, approval state, and how follow-up cost sync will verify the result.
Put the framework to work
Costframe connects read-only, records the evidence behind each finding, and keeps list-price estimates separate from net savings.