Inspect the evidence
Read the source, confidence, freshness and estimated impact. Missing telemetry remains visible beside the recommendation.
Findings and evidenceSee where your cloud bill goes.
Follow a charge to its resource, put it beside the owning team and review the evidence for what can change.
Read-only access. Your team makes the changes.
Example dataCostsSeptember 2026 · EUR OwnershipSeptember 2026 · EUR Sizing reviewCPU · 14-day sample
Net billed cost
€56,148.25- Largest itemized chargevm-api-02
- €12,482.36
Commerce platform
€21,246.56Configured mapping. Current ownership is not proof of past responsibility.
Sandbox · vm-build-07
€1,090.00Estimated per month · needs review
22% peak CPU · memory and IOPS not collected
Explain the bill from its source records.
From the monthly total to a retained resource charge
Compare net billed spend by subscription and service. A charge can remain in billing after the resource leaves inventory, so retained costs stay visible.
Current configuration and configured ownership add context. They do not certify the resource’s state or responsibility in a past period.
Explore cost investigation- Billing
- The charge and its usage period
- Inventory
- Available resource configuration
- Ownership
- Configured tags and mappings
- Utilization
- Collected signals and explicit gaps
- Production
- €56,148.25
- Sandbox
- €16,848.12
- Shared services
- €11,244.23
- Net billed cost
- €84,240.60
Reconciles to the selected scope
September resource lines and other subscription charges.
Choose the next step with the owning team.
01 / Gather context
- Billing
- The charge, period and currency
- Inventory
- Available resource configuration
- Ownership
- Configured tags and mappings
- Utilization
- Collected signals and explicit gaps
02 / Review the case
What can the evidence support?
Inspect the source, confidence, freshness and estimated impact together.
Missing evidence stays visible.
A finding starts a review. It does not authorize a cloud change.
03 / Customer-controlled
Decide with the owner
Assignment and approval are separate records.
Make the change externally
Your team uses its own environment and process.
Check the result
An estimate or billing movement alone is not a verified saving.
Agree the change
Assignment and approval are recorded separately. Your team implements changes in its own environment and through its own process.
Review the handoffCheck what happened
Calculated and modeled estimates remain separate from actioned expectations and verified outcomes. An unattributed billing change is not a verified saving.
Financial statesRead-only from connection to review. The cloud stays under your control.
Azure is generally available. AWS runs in a private pilot and Google Cloud in a private preview, with different evidence coverage and setup requirements.
Provider scope and permissions- Exports
- Authorized CSV preserves selected scope. General audit PDF is unavailable during the controlled launch.
- Guidance
- Supported non-executing implementation drafts help your team prepare its work.
- Delivery
- Configured destinations and requested handoffs remain distinct from confirmed external receipt.
- AI Advisor
- Permitted evidence and sources, with limitations. Growth or Enterprise is required.
Start with a bill you need to explain.
Connect an included Azure scope, collect its available evidence and review the result with your team.