Azure cost exports are scheduled deliveries of your billing detail from Azure Cost Management to a storage account, and Azure supports exporting them in the FinOps Foundation FOCUS format. FOCUS matters because Azure's native cost detail uses meters, resource hierarchies, and amortisation conventions specific to Azure, which makes cross cloud reporting and even consistent internal allocation harder than it should be. A FOCUS export carries the same standardised columns, billed and effective cost, service, region, commitment, and tags, that the other clouds can also produce, so your Azure data lands ready to reconcile rather than needing a custom mapping each time a meter changes. Set the export to deliver the FOCUS dataset on a daily schedule, and build reporting on that table.
Here is how to configure the export, what the FOCUS schema standardises, and how to use it without forking your reporting per cloud.
How do you set up an Azure cost export?
In Azure Cost Management you create an export that writes cost data to a storage account on a schedule, daily for an operational view. Azure offers different dataset types, and the one to choose for cross cloud work is the FOCUS cost dataset rather than the legacy amortised or actual cost exports. Scope the export at the billing account or management group level so it captures the whole estate, point it at a storage account your reporting pipeline can read, and let it accumulate daily files. The native console remains useful for quick checks, but the export is what feeds durable reporting.
What does the FOCUS schema standardise for Azure?
FOCUS replaces Azure specific column names and conventions with a vendor neutral set that means the same thing everywhere:
- Billed and effective cost. One clear definition of charge and of effective cost after Reservations, the Azure Savings Plan, and negotiated discounts, so amortisation is comparable.
- Service and region. A consistent naming layer over Azure's meter and resource taxonomy, so a breakdown by service reads the same as on other clouds.
- Commitment and discount. A standard place to attribute Reservations and the Azure Savings Plan, so coverage and effective savings rate are calculable consistently.
- Tags. A normalised home for ownership and environment tags, which is what turns Azure spend into allocated spend.
How do you use FOCUS data without forking reporting per cloud?
The point of FOCUS is one reporting model, not four. Land the Azure FOCUS export alongside the equivalent exports from AWS, GCP, and OCI in a single table, and build your allocation, coverage, and trend reports once against the shared schema. When Azure changes a meter or adds a service, the FOCUS mapping absorbs it and your reports stay stable. Reconcile the FOCUS table to the Azure invoice monthly so finance trusts the figure. This is the foundation a single pane view across providers sits on, and it is why the data step comes before the dashboard.
A worked example
A European SaaS company built Azure cost reporting directly on the legacy amortised export, then had to rework every query each time Azure introduced a new meter, and could never reconcile it against the AWS view sitting in the same business review. Switching the Azure export to the FOCUS dataset and landing it in the shared reporting table removed the per change rework and let allocation and commitment coverage read identically across both clouds. The clean foundation surfaced an under used Azure Savings Plan position that the old reporting had obscured, one of several findings in the program that left the company materially lighter on cloud spend. Figures are verified against billing data and anonymised.
Frequently asked questions
What is an Azure cost export?
Why export Azure cost data in FOCUS format?
Does the FOCUS export replace Azure Cost Management?
Put your Azure data on a reconcilable footing
We help Azure teams configure FOCUS cost exports, land them in a shared model, and build reporting that reconciles across AWS, Azure, GCP, and OCI. We take zero provider commissions and answer only to you, on a Fixed Fee or a no risk Gainshare basis, with a guarantee we stand behind: we reduce your cloud spend or we reimburse our service fee. Book a strategy call, and follow more in The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.