Google CloudCommitments5 min read

Check whether resource-based CUD sharing matches your billing setup

Sources checked September 9, 202610 minutes
On this page
THE SHORT ANSWER

Before moving a project or relying on a shared reservation, read the Cloud Billing account's resource-based CUD scope and confirm reservation sharing is limited to projects linked to that same account.

Why this is worth a look

Resource-based CUD scope determines where a commitment's eligible discounts apply. Project scope limits them to the purchasing project, while Billing account scope applies them across eligible usage in projects linked to that Cloud Billing account. A project moved to another billing account inherits the destination account's CUD sharing and attribution settings. Shared reservation usage is eligible for shared CUDs only when the reservation is shared with projects linked to the same Cloud Billing account. Otherwise, that usage might be charged at on-demand rates.

Run this check

CHECKLIST

Use this console checklist to read the current resource-based CUD scope and verify same-Cloud-Billing-account reservation sharing. It makes no changes, uses no query columns, and reviews the current configuration rather than a usage or billing time window.

Read-only CUD sharing review
Execution surface: Google Cloud console, CUD analysis page.
Scope: one selected Cloud Billing account and its linked projects.
Required access: permissions on the Cloud Billing account to access Cloud Billing information. Updating the scope requires billing.subscriptions.update, but this review does not update it.
Units and time window: scope and project linkage are configuration values; no usage units or time window are queried.

1. Open the Google Cloud console and go to CUD analysis.
2. Select the Cloud Billing account to review.
3. In Analyze, select Resource-based CUDs.
4. Open CUD scope & settings and read Resource-based CUDs scope.
5. Record Project or Billing account.
6. If shared reservations are used, verify that each shared project is linked to the same Cloud Billing account.
7. Before moving a project or changing reservation sharing, compare these settings with the intended billing account.

How to confirm it

  1. 01

    Open the CUD analysis page

    In the Google Cloud console, open CUD analysis and choose the Cloud Billing account you want to review. You need the account access required to view Cloud Billing information.

  2. 02

    Read the resource-based scope

    In Analyze, select Resource-based CUDs. Open CUD scope & settings and record whether Resource-based CUDs scope is Project or Billing account.

  3. 03

    Verify reservation project links

    If you use shared reservations, verify that every project receiving the shared reservation is linked to the same Cloud Billing account as the commitment. Do not change the reservation during this review.

  4. 04

    Review before a billing move

    Before moving a project to another Cloud Billing account, compare the source and destination sharing intent. A moved project inherits the destination account's CUD sharing and attribution settings.

Before making changes

Assume you are reviewing Compute Engine resource-based commitments and have permission to access Cloud Billing information for the selected account. This is a read-only console review of configuration, not a usage or billing analysis, so it has no units or time window. Spend-based CUDs are pooled at the Cloud Billing account level, always use proportional attribution, and have no separate CUD sharing configuration.

Ignore this check if you use only spend-based commitments, or if you already confirmed the resource-based CUD scope and shared-reservation project links match the intended Cloud Billing account.

Primary sources

1
Share resource-based CUDs across projectscloud.google.com