What does FOCUS stand for?

FOCUS stands for the FinOps Open Cost and Usage Specification — an open-source, vendor-neutral schema for cloud and technology billing data, maintained under the FinOps Foundation. It defines consistent column names, semantics and values so billing data from different providers can be analyzed the same way.

Does Azure support FOCUS?

Yes. Microsoft Cost Management supports FOCUS-format exports natively — you create an export of type 'Cost and usage details (FOCUS)' to a storage account. All major clouds, including AWS, Google Cloud and Oracle, now generate FOCUS data natively.

What's the difference between BilledCost and EffectiveCost in FOCUS?

BilledCost is what appears on the invoice for the charge period, including one-time reservation purchases. EffectiveCost amortizes those upfront commitment purchases across the resources and periods that consume them — the FinOps-preferred view for allocation and unit economics.

Standards · Updated June 2026

What is FOCUS? The FinOps billing-data standard, explained

By the CloudFinOpsKit team. 7 min read.

FOCUS — the FinOps Open Cost and Usage Specification — is the open, vendor-neutral standard for cloud billing data. Every cloud historically invented its own billing schema: different column names, different meanings for "cost", different ways of representing discounts. FOCUS replaces that babel with one consistent schema, so the same query, dashboard, or AI prompt works on billing data from any provider.

It stopped being a nice idea and became table stakes recently: every major cloud now generates FOCUS data natively — Microsoft, AWS, Google Cloud and Oracle, with Alibaba, Tencent, Databricks and others joining. The 2026 State of FinOps survey calls it out as the consistent data foundation practitioners need as FinOps expands beyond cloud into SaaS, licensing and AI spend.

The problem it solves

Ask three clouds "what did this resource cost last month?" and you historically got three schemas, three discount models, and at least two definitions of "cost". Multi-cloud reporting meant a custom normalization pipeline that broke every time a provider changed a column. FOCUS pushes that normalization upstream: providers emit the standard directly.

The core columns worth knowing

FOCUS column	What it means
`BilledCost`	What hits the invoice for the period — includes one-time purchases like reservation buys.
`EffectiveCost`	The amortized view — upfront commitments spread across the usage that consumes them. The FinOps-preferred basis for allocation and unit economics.
`ChargePeriodStart / End`	The window the charge covers.
`ServiceName / ServiceCategory`	What was used, normalized across providers (e.g. "Compute", "Storage").
`SubAccountId / SubAccountName`	The provider's sub-scope — in Azure, your subscription.
`ResourceId / ResourceName`	The specific resource — the join key for tying findings, tags and usage together.
`RegionId`, `PricingQuantity`, `ListCost`, `ContractedCost`	Where, how much, at list, and at your negotiated rate — discount visibility built in.
`Tags`	Your allocation metadata, in one consistent shape.
`x_*` columns	The extension convention: provider- or tool-specific fields, clearly namespaced so they never collide with the standard.

How to turn it on in Azure (5 minutes)

Portal → Cost Management → Exports.
Create a new export and choose the template "Cost and usage details (FOCUS)".
Pick daily frequency and a destination storage account.

You now have standards-shaped billing data landing daily — the input format every modern FinOps platform, query engine, and (increasingly) AI assistant expects. The same three steps in AWS or GCP produce the same columns, which is the whole point.

Why FOCUS makes your cost data AI-ready

Large language models are remarkably good at analyzing tabular cost data — when the columns mean something consistent. A prompt like "group EffectiveCost by ServiceCategory and flag week-over-week anomalies" works on any FOCUS dataset with zero schema explanation. Proprietary exports make you teach the model the schema every time; FOCUS makes the knowledge reusable. This is why we treat FOCUS-alignment as an AI feature, not just a reporting feature.

Findings that join your FOCUS data. The CloudFinOpsKit Tool's report includes a FOCUS-aligned CSV export — standard columns (ResourceId, SubAccountName, RegionId, ChargePeriodStart/End, Tags) plus x_-prefixed assessment fields — so its savings findings join your FOCUS billing export on ResourceId in one line of SQL, Power BI, or an AI prompt.

FOCUS vs what you use today

vs Azure's "actual cost" export: same underlying data, standardized names and semantics, plus amortized cost as a first-class column.
vs Cost Management UI: the UI is for humans; FOCUS is for pipelines, tools and AI.
vs your custom normalizer: retire it. The providers now do it for you, with a versioned public spec.

FAQ

Is FOCUS only for multi-cloud?

No — single-cloud teams benefit from the amortized/billed split, the discount-visibility columns, and tool portability. Multi-cloud just makes it indispensable.

Does FOCUS cover SaaS and AI spend?

That's the direction of travel: the spec is evolving with the FinOps scopes (SaaS, licensing, AI) so all technology spend can land in one schema.

Do I need a platform to use FOCUS?

No. A FOCUS CSV in a storage account is immediately queryable with SQL, Power BI, Python — or pasted straight into an AI assistant.