Every cost report stands on its tag coverage. This is how to audit tag coverage across clouds: measure the share of spend that is properly tagged, find the gaps by service and account, and close them so the numbers can be trusted.
A tag coverage audit answers one question in a number: what share of your cloud spend is attributable to an owner through tags, and what share is floating untagged? You measure coverage by cost rather than by resource count, find where the gaps concentrate, and close them in priority order. Until you do, every cost report by team or product is understated by exactly the amount you cannot see, and no allocation or chargeback program can be trusted.
This guide belongs to the complete guide to cloud cost governance. It is the diagnostic step that comes before reporting and chargeback work: if you cannot show high tag coverage, you cannot defend the numbers in a cost report by team, product, and environment. Across the environments we have audited since 2019, untagged spend on a first pass is routinely 15 to 40 percent of the bill.
The most common mistake is measuring the percentage of resources that carry a tag. That flatters the number, because a thousand tiny tagged resources can mask a handful of untagged but enormous ones. Measure coverage as tagged spend divided by total spend. A 95 percent resource-count coverage can still mean 30 percent of the dollars are untagged if the untagged resources are the expensive ones.
Run the audit from the authoritative billing data, not the console summaries. Each provider exposes per-line-item cost with tags attached:
| Cloud | Source | Coverage approach |
|---|---|---|
| AWS | Cost and Usage Report (CUR) | Sum cost where the required cost-allocation tag is null vs total |
| Azure | Cost Management exports / amortized usage | Group cost by tag key presence across resources |
| Google Cloud | BigQuery billing export | Query cost where the required label is missing |
| OCI | Cost reports / Cost Analysis | Compare tagged vs untagged cost by compartment |
To get one cross-cloud number, normalize the exports to a common schema, which is exactly what the FOCUS specification is designed for. The mechanics of normalizing billing data are covered in how to normalize cost data across clouds.
A single coverage percentage tells you there is a problem; the slices tell you where to fix it. Break untagged spend down three ways: by service (some services do not propagate tags to all their sub-resources, a common silent gap), by account or subscription (often one team or one legacy account is the bulk of the gap), and by the resources that are untaggable at all, marketplace charges, support, some data-transfer line items, which need a different treatment entirely. That last bucket is covered in how to allocate untaggable costs fairly.
We run the audit across all four clouds from the billing exports, show you exactly where the untagged dollars are, and close the gaps with enforcement. On the performance model, if we do not save you money, there is no fee.
Get a cost audit →Fix the biggest dollar gaps first. Backfill tags on existing high-cost resources, then prevent new gaps with enforcement so coverage does not erode the moment you look away. Preventing untagged resources at creation time is the job of enforcing tagging with policy as code, using AWS tag policies and SCPs, Azure Policy, GCP organization policy, and OCI tag defaults. Backfilling plus enforcement is what turns a one-time audit into durable coverage.
Tag coverage decays. New teams, new services, and new accounts all introduce gaps, so a one-off audit is worthless within a quarter. Put coverage on a dashboard and review it on a cadence, the same way you would any operational metric. Building that view is covered in how to build a tag compliance dashboard, and the policy that keeps it enforced belongs in a cloud cost policy framework.
On a multicloud audit, the headline coverage looked acceptable at 88% of resources, but by cost only 71% of dollars were tagged, because a single untagged data-platform account carried nearly a fifth of the spend. Measuring by cost rather than count is what surfaced it. Closing that one gap made the entire allocation report defensible.
A tag coverage audit is the foundation everything else in governance rests on. Read the complete guide to cloud cost governance for the full system, and download The Cloud Cost Governance and Tagging Toolkit for the audit queries and taxonomy templates. When you want the audit and enforcement run for you, see our FinOps implementation service.
New commitment instruments, FOCUS changes, hyperscaler pricing shifts, and the plays that actually move a bill. No schedule, no filler.