Check a BigQuery dataset before enabling Cloud Billing export
On this page
Use this read-only checklist before enabling Standard usage cost, Detailed usage cost, or Pricing data export to BigQuery, or changing its target. It prompts you to review location, encryption, project billing, billing-account linkage, the pricing API, and permissions, but it does not establish complete export readiness.
Why this is worth a look
Cloud Billing export supports all multi-region dataset locations, EU and US, but only a subset of region locations. Google-managed encryption is the default. If you use customer-managed encryption keys (CMEK) for Cloud Billing data, enable CMEK at the dataset level and follow the documented encryption and service-account requirements. Checking these settings, the hosting project, and the relevant export prerequisites before configuration can prevent avoidable setup errors. Switching datasets does not automatically backfill previously exported billing data into the new location.
Run this check
CHECKLISTRead-only Google Cloud console steps for checking a BigQuery dataset and its project before configuring Standard, Detailed, or Pricing Cloud Billing export.
Scope: Standard usage cost, Detailed usage cost, or Pricing data export. This is a manual, read-only console review.
1. In the Google Cloud console, open the BigQuery dataset you plan to use.
2. Record its location. Confirm it is EU, US, or a region listed as supported for Cloud Billing export to BigQuery.
3. Check the dataset encryption setting. Google-managed encryption is the default. If it uses CMEK, confirm CMEK is enabled at the dataset level and review the documented encryption and service-account requirements.
4. Confirm the dataset project has billing enabled and is linked to the Cloud Billing account whose data you will export. Review the Cloud Billing and BigQuery roles and permissions required for the export type.
5. If you will export pricing data, confirm the BigQuery Data Transfer Service API is enabled in the same project. Record any unmet prerequisite and review the remaining export-type permissions and service-account requirements before configuring the export.How to confirm it
- 01
Confirm the export scope
Use this checklist for Standard usage cost, Detailed usage cost, or Pricing data export. The same dataset can contain standard usage cost, detailed usage cost, and pricing data.
- 02
Verify the location
Confirm the dataset is in EU, US, or a region listed as supported for Cloud Billing export to BigQuery. An unsupported location causes a configuration problem when you try to save the export.
- 03
Review encryption
Google-managed encryption is the default. If the dataset uses CMEK, confirm CMEK is enabled at the dataset level and review the documented CMEK and service-account requirements before enabling the export.
- 04
Check project, access, and API prerequisites
Confirm billing is enabled on the dataset project and that it is linked to the Cloud Billing account whose data you will export. Review the Cloud Billing and BigQuery roles and permissions required for your export type. If you will export pricing data, confirm the BigQuery Data Transfer Service API is enabled in this project.
Before making changes
Assume this is an initial enablement or a planned dataset change for Standard usage cost, Detailed usage cost, or Pricing data export. This read-only checklist prompts a review but does not verify every permission or service-account condition. Switching datasets does not automatically backfill previously exported data. For an initial usage-cost export to EU or US, data from the current and previous month can be added retroactively unless you are re-enabling the export. Non-multi-region usage locations are not retroactive, and Pricing data is not retroactive.