There are two things called FOCUS in cloud cost work, and the older version of this article mixed them up. This is a rewrite. FOCUS here means the FinOps Open Cost and Usage Specification — an open standard, maintained by the FinOps Foundation, that gives every cloud and SaaS vendor a common format for billing data. It is not an Azure-specific feature.
What is the FOCUS specification?
FOCUS is an open specification that normalizes billing and usage data across technology vendors. Instead of every provider using its own column names, units, and cost definitions, a FOCUS-conformant export uses the same schema regardless of whether the data came from AWS, Azure, Google Cloud, Databricks, or Snowflake. The current version is FOCUS 1.4. The FinOps Foundation maintains it as a Linux Foundation project, with contributions from the major cloud providers and cost-management vendors.
The problem it solves is mechanical but expensive. Before FOCUS, a multi-cloud FinOps team spent most of its effort writing and maintaining per-provider parsers — mapping Azure’s CostInBillingCurrency and AWS’s lineItem/UnblendedCost and GCP’s cost into one model before any analysis could start. FOCUS moves that normalization upstream to the provider.
Verdict: if you run one cloud, FOCUS is a nice-to-have that makes your data portable later. If you run more than one, it removes a whole category of glue code.
What does FOCUS standardize?
FOCUS defines a set of columns with fixed names and meanings, grouped into cost metrics, time periods, service and resource identifiers, and pricing and usage quantities. The key ones:
| Column | What it holds |
|---|---|
| BilledCost | The amount actually invoiced for the charge |
| EffectiveCost | Amortized cost including the share of upfront commitments and reservations |
| ListCost | Cost at public on-demand rates, before any discount |
| ContractedCost | Cost at negotiated rates, before commitment discounts |
| ChargeCategory | Usage, Purchase, Tax, Credit, or Adjustment |
| ChargePeriodStart / ChargePeriodEnd | The window the charge covers |
| BillingPeriodStart / BillingPeriodEnd | The invoice period the charge belongs to |
| ServiceName / ServiceCategory | The specific service and its broad category (Compute, Storage, Databases…) |
| ResourceId / ResourceName | The individual resource the charge maps to |
| ProviderName / PublisherName / InvoiceIssuerName | Who ran the service, who made it, who billed you |
| PricingQuantity / ConsumedQuantity | Units priced vs units actually used |
The distinction that matters most in practice is BilledCost vs EffectiveCost. BilledCost is what hit the invoice this month. EffectiveCost spreads the cost of a one-year reservation or savings plan across the months it covers, so a team’s real run rate does not spike in the month they bought the commitment.
Which providers export FOCUS-conformant data?
Adoption is broad and tracked publicly on the FOCUS site. As of 2026:
- AWS, Microsoft Azure, Google Cloud, and IBM Cloud export data conformant to FOCUS 1.2.
- Databricks, Snowflake, MongoDB Atlas, and Vercel export FOCUS 1.3-conformant data.
- Oracle Cloud, Alibaba Cloud, Tencent Cloud, Huawei Cloud, OVHcloud, and Cloudflare support FOCUS 1.0.
On AWS, you turn it on in the Billing and Cost Management console under Data Exports, choosing the FOCUS 1.0 export type, which lands FOCUS-formatted files in an S3 bucket. Azure delivers it through Cost Management exports, and Google Cloud through its BigQuery billing export. Most FinOps platforms — the ones covered in the Apptio Cloudability vs Vantage comparison — can now ingest FOCUS data directly.
Verdict: the big three plus IBM are far enough along that a FOCUS-first cost pipeline is realistic today. The long tail of SaaS vendors is catching up version by version.
Why does FOCUS matter for multi-cloud cost work?
Three concrete wins. First, one report across providers: a single query answers “what did compute cost us everywhere last month” without a per-cloud subquery. Second, consistent commitment tracking: reservation and savings-plan coverage uses the same fields whether it is an AWS Savings Plan or an Azure Reservation. Third, portable tooling: dashboards and allocation logic built against FOCUS columns keep working if you add a cloud or switch cost platforms.
It does not eliminate FinOps work. You still decide how to allocate shared costs, set budgets, and act on the findings. FOCUS just means the data arrives in a shape you do not have to fight first.
Frequently Asked Questions
No. FOCUS is the FinOps Open Cost and Usage Specification, an open standard maintained by the FinOps Foundation. Azure supports it through Cost Management exports, but so do AWS, Google Cloud, IBM, and many SaaS vendors. An older Azure billing term, First-Party Offers Consumption, is unrelated.
FOCUS 1.4 is the current release as of 2026. The major cloud providers currently export data conformant to FOCUS 1.2, with several data and SaaS vendors on 1.3.
BilledCost is the amount on the invoice for that period. EffectiveCost amortizes upfront commitments and reservations across the months they cover, so it reflects the real run rate rather than spiking when a commitment is purchased.
In the AWS Billing and Cost Management console, open Data Exports, create a new export, and choose the FOCUS 1.0 export type with an S3 destination. AWS then writes FOCUS-formatted cost and usage files to that bucket on a schedule.
Quick Summary
- FOCUS is the FinOps Open Cost and Usage Specification — an open, vendor-neutral billing data format, not an Azure feature.
- Current version is FOCUS 1.4, maintained by the FinOps Foundation under the Linux Foundation.
- It fixes column names and cost definitions: BilledCost, EffectiveCost, ListCost, ChargeCategory, ServiceCategory, and more.
- AWS, Azure, Google Cloud, and IBM export FOCUS 1.2-conformant data; Databricks, Snowflake, and others are on 1.3.
- The payoff is one cost report across clouds, consistent commitment tracking, and tooling that survives adding or switching providers.
Comparing cost platforms that consume FOCUS data? The Apptio Cloudability vs Vantage breakdown covers which fits which team size.