To build a multicloud cost dashboard with FOCUS and BigQuery, enable the FOCUS-formatted billing export in each cloud, land all of them in one BigQuery dataset, union them into a single FOCUS table on the shared columns, validate the totals against each provider invoice, then point a BI tool at the unified view. FOCUS does the hard part: because every provider emits the same columns with the same meanings, you skip the custom per-cloud mapping that usually consumes a multicloud dashboard project. The one step teams skip and regret is reconciliation, so sum BilledCost per provider per month and match each invoice before trusting a single chart. This is the See stage of our work across 500+ environments, where one normalized view is what makes a 31% average bill reduction measurable.
A multicloud cost dashboard built on FOCUS and BigQuery gives you one view of spend across AWS, Azure, and Google Cloud without stitching three incompatible billing formats together by hand. FOCUS, the FinOps Open Cost and Usage Specification, normalizes the schema so every provider speaks the same language, and BigQuery is the natural place to land and union it. This guide walks the build end to end. It is part of our complete guide to cloud cost visibility and tooling, the cluster this article links up to.
Why use FOCUS and BigQuery for a multicloud dashboard?
FOCUS is worth using because it removes the single hardest part of multicloud reporting: making each provider's billing data mean the same thing. The FinOps Open Cost and Usage Specification defines a common set of columns, such as BilledCost, EffectiveCost, ServiceName, and ChargePeriodStart, with identical names and semantics across clouds. Without it, AWS, Azure, and Google Cloud each label cost, account, and service differently, and most of a dashboard project is spent reconciling those differences. BigQuery is the natural home because Google Cloud exports FOCUS billing directly into it, it scales past anything a spreadsheet can hold, and it unions tables with plain SQL. Together they turn a months-long integration into a few well-defined steps.
How do you build the dashboard? Step by step
Follow these five steps in order. The reconciliation step in the middle is the one that separates a dashboard people trust from one finance quietly ignores, so do not skip it.
- Enable FOCUS billing exports per cloud. Turn on the FOCUS-formatted export in each provider: the FOCUS view of Data Exports CUR 2.0 in AWS, the FOCUS export in Microsoft Cost Management, and the FOCUS-formatted BigQuery billing export in Google Cloud. Verify the FOCUS version each provider currently emits against its own docs, since support advances over time.
- Land all exports in BigQuery. Route every provider export into one BigQuery dataset. Google Cloud writes its FOCUS export to BigQuery natively; AWS and Azure files land in cloud storage and load in through scheduled transfers or a storage load job.
- Union into one FOCUS table. Create a single view that unions the provider tables on the shared FOCUS columns. Because FOCUS already aligns the schema, BilledCost, EffectiveCost, ServiceName, and the rest line up without per-cloud mapping; you add one ProviderName column if it is not already present.
- Validate totals against each invoice. Sum BilledCost per provider per month in the unified view and reconcile against each provider invoice before trusting any chart. A dashboard that does not tie to the invoice is worse than no dashboard, because it looks authoritative while being wrong.
- Build the views on the unified table. Connect Looker Studio or your BI tool to the unified FOCUS view and build the cuts that matter: spend by provider, by service, by tag or cost center, and effective versus billed cost so commitments are visible. Every view draws from the same columns, so definitions stay consistent.
Want the normalized view without the build?
Our FinOps implementation stands up FOCUS-normalized multicloud visibility, reconciles it to the invoice, and turns it into the savings the dashboard only measures. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →What should the dashboard actually show?
The dashboard should answer the questions a FinOps program asks every week, all from the unified FOCUS table. Show total spend and trend across all providers, then break it down by provider, by service, and by the tag or account that maps to a team or product so every dollar has an owner. Put effective cost next to billed cost so the value of commitments is visible, and add an unallocated line that surfaces spend missing a tag, since that gap is usually the fastest visibility win. Building the allocation discipline that makes those tag cuts meaningful is its own topic, and the unified view is only the See stage of our See, Cut, Lock, Run method; turning it into a falling bill is the work a FinOps implementation sequences next. If you are still choosing between building this yourself and buying it, weigh it with our FinOps platform buyer scorecard, the sibling guide to this one.
The Multicloud Visibility and FOCUS Guide includes the reference data model and reconciliation checks we use to stand up a trustworthy FOCUS dashboard across AWS, Azure, and Google Cloud.
Common questions about FOCUS multicloud dashboards
Why use FOCUS for a multicloud dashboard?
FOCUS gives every provider's billing data the same column names and meanings, so you can union AWS, Azure, and Google Cloud spend into one table without writing custom mapping for each. Without FOCUS, every cloud labels cost, account, and service differently, and most of the dashboard build is reconciling those differences. With FOCUS, the schema is already aligned and you spend your time on analysis instead.
Do all three clouds support FOCUS exports?
Yes. AWS offers a FOCUS view of the Data Exports CUR 2.0, Microsoft Cost Management offers a FOCUS export, and Google Cloud offers a FOCUS-formatted BigQuery billing export. Verify the exact FOCUS version each provider currently emits against their documentation, since providers update support over time, but all three majors emit FOCUS today.
Why BigQuery rather than a spreadsheet?
Multicloud billing data is too large and too frequently refreshed for a spreadsheet. BigQuery handles the volume, lets you union providers with SQL, refreshes on a schedule, and connects natively to BI tools. Google Cloud also exports FOCUS billing directly into BigQuery, so for at least one provider there is no extra load step.
Written by Fredrik Filipsson and reviewed by Morten Andersen, applying our See, Cut, Lock, Run method. Independent and vendor neutral.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: Google Cloud pricing ↗, Google Cloud documentation ↗, FinOps Foundation Framework ↗ and FOCUS billing specification ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.