Skip to content

See which Azure costs deserve a closer look.

Follow a finding from its cost estimate to the evidence and the next decision for your team. Explore the example without connecting a cloud account.

Example data

What to look for

  • Which resources are worth reviewing?
  • What evidence does engineering still need?
  • What should finance verify after a change?

Explore the audit evidence, step by step.

Synthetic · no customer data

Estimated per month

$1,926.60

Findings

58

Evidence gaps kept

22

Synthetic Azure audit

58 public-safe detector results from a synthetic Azure fixture. No tenant, user, secret, or customer billing data is represented.

The audit reel will start when it enters the viewport.

The audit reel will start when it enters the viewport.

Sample audit · USD

Active frame

Commitment coverage gap

Steady synthetic VM spend is large enough to review committed-use coverage before buying more on-demand compute.

contributes to savings

$777

Financial findings

5 saving

Synthetic subscription

reservation_gap · Financial optimization

$777/mo

Synthetic VM: vm-idle

idle_compute · Financial optimization

$280/mo

Synthetic VM: vm-oversized

oversized_vm · Financial optimization

$280/mo

Synthetic VM: vm-stopped

stopped_vm · Financial optimization

$150/mo

Synthetic AKS cluster: aks-prod

aks_underused · Financial optimization

$105/mo

Evidence ledger

MEDIUM confidence
Source
Azure Resource Manager/Resource Graph
Window
30-day analysis projection

Evidence checked

  • On-demand compute baseline

Evidence unavailable

  • Existing private pricing and commitments
  • Hourly utilization stability

Annualized estimate

$23,119.20

Non-financial

42

Severity mix

5 HIGH · 10 MEDIUM · 43 LOW

The preview shows five financial and five risk examples from the 58-result audit. Use the step controls to inspect the source and review state.

Compare a savings estimate with a risk finding

Two findings, different decisions. A monetary estimate and a risk condition need different kinds of review.

Financial optimization · LOW severity

Commitment coverage gap

Steady synthetic VM spend is large enough to review committed-use coverage before buying more on-demand compute.

Estimated monthly impact
$777
Financial basis
Included in the savings total as estimated_savings.
Still unavailable
Existing private pricing and commitments; Hourly utilization stability

Security posture · HIGH severity

Broad inbound management access

A synthetic network rule allows public inbound access to a sensitive management port. It is a HIGH risk signal, not a savings claim.

Monetary impact
$0
Financial classification
Security posture findings are risk signals and are never counted as monetary savings.
Evidence caveat
Whether downstream virtual machine firewalls, OS-level packet filters, or secondary subnet-level NSGs intercept or block this traffic.; The associated VM might be stopped, not listening on these ports, or protected by an upstream NVA firewall.

Your team reviews the evidence and implements any approved change in its own environment. Dedicated sources are required to verify the outcome.

Read the product limitations

Bring your own question to the next audit.

Start with an included Azure subscription and read-only access, or compare plans before connecting.

Start with Costframe