Skip to content
Costframe

Microsoft Azure

Generally available

Read-only Azure billing, inventory and available utilization for included scopes. Collection and permissions determine the evidence available for each resource.

Start with CostframeAll provider scopes

Microsoft Azure

Generally available

  • Included subscriptions
  • Resource groups and resources
  • Cost Management ActualCost
  • Resource Graph inventory
  • Azure Monitor, where exposed
  • Retail Prices list context
Costframe

Included scope, permitted reads, evidence and limitations

Read-only customer-cloud access

What your team reviews

  • Native-currency cost investigation
  • Configured ownership and retained charges
  • Findings with evidence and limits
Setup and permissions

Investigate the bill and its resources.

Use the selected subscription's charges to identify the service and resource to investigate. Available configuration and metrics help the owner assess what can change.

  • Month-on-month spend by subscription, service and resource
  • Idle, oversized and stopped-but-billing machines, unattached disks, old snapshots, public IPs and storage tiers
  • Under-used SQL, idle load balancers and NAT gateways
  • Commitment coverage, with EA or MCA rates where provided
  • Chargeback, cost centres and Azure Virtual Desktop evidence

These are supported review areas, not a promise that every resource has complete evidence. Permission-limited, unavailable, stale and partial scope remain explicit.

Access and evidence

Read scopes
Reader + Cost Management Reader on the subscriptions or scopes you choose
Ready for review
Confirm the required billing, inventory and metric evidence for the selected scope. Connection validation alone does not certify complete collection.
Implementation boundary
Your team approves and implements changes outside Costframe. No customer-cloud write path is introduced.
Exact setup instructions
Azure resource example · sample dataA CPU signal starts the review.
Sandbox / rg-developmentvm-build-07

Virtual machine · West Europe

22%Peak in the public CPU sample

14 daily readings · not a capacity guarantee

Read all 14 CPU samples
Illustrative daily CPU readings, percent
DayCPU
16%
211%
38%
47%
516%
610%
78%
85%
97%
1022%
1112%
128%
136%
149%
Before a sizing decision
Available in this sample
  • Resource and billing context
  • 14-day CPU sample
  • Configured team: Developer experience
Not collected
  • Memory utilization
  • Disk IOPS and performance
Owner review still needed

Confirm peak build needs, dependencies, a safe test and rollback before changing capacity.

Existing public sample, not customer evidence. Low CPU alone does not prove spare capacity. Your team controls any external change.

Connect, validate and review the available evidence.

  1. Register an app
  2. Assign reader roles
  3. Validate the connection
  4. Run the first audit
  5. Review the evidence

Azure service costs support twelve complete months plus the current month where collection succeeds. Missing collection, empty dates and provisional data remain different states.

Prepare for the first result

Azure finance and desktop-cost guides

Follow the relevant guide for cost-center allocation, internal chargeback or Azure Virtual Desktop. These workflows explain reporting and review; they do not change Azure resources.

Start with an included Azure subscription.

Use read-only roles and inspect the first audit with your team.

Start with Costframe