Skip to content
Cloud Governance Tools

Resource location restriction

Resource location restriction is a Google Cloud guardrail written in organization Policy Service. Limits the locations where location-based Google Cloud resources can be created. What it breaks: google documents that allowing or denying a multi-region does not imply the same for its sub-locations, so a deny of the us multi-region still allows resources in us-east1.

More region and residency guardrails ยท About Organization Policy Service

constraints/gcp.resourceLocations
This list constraint defines the set of locations where location-based Google Cloud resources can be created. Important: The information on this page does not describe Google Cloud Platform's data location commitments for Customer Data (as defined in the agreement under which Google has agreed to provide Google Cloud Platform services and as described in the Google Cloud Platform Services Summary at https://docs.cloud.google.com/terms/services) to its customers. For the list of Google Cloud Platform services for which Customer Data location may be selected by customers, see Google Cloud Platform Services with Data Residency at https://docs.cloud.google.com/terms/data-residency.
By default, resources can be created in any location. For a full list of supported services, see https://docs.cloud.google.com/organization-policy/reference/restrict-locations-supported-services.
Policies for this constraint can specify multi-regions such as asia and europe , regions such as us-east1 or europe-west1 as allowed or denied locations. Allowing or denying a multi-region does not imply that all included sub-locations should also be allowed or denied. For example, if the policy denies the us multi-region (which refers to multi-region resources, like some storage services), resources can still be created in the regional location us-east1 . On the other hand, the in:us-locations group contains all locations within the us region, and can be used to block every region.
We recommend using value groups to define your policy.
You can specify value groups , collections of locations that are curated by Google to provide a simple way to define your resource locations. To use value groups in your organization policy, prefix your entries with the string in: , followed by the value group.
For example, to create resources that will only be physically located within the US, set in:us-locations in the list of allowed values.
If the suggested_value field is used in a location policy, it should be a region. If the value specified is a region, a UI for a zonal resource may pre-populate any zone in that region.
Supported prefixes: is: , in:
For more information, see Restrict resource locations .
Blocks
Limits the locations where location-based Google Cloud resources can be created. (legacy managed constraint, list.)
Breaks
Google documents that allowing or denying a multi-region does not imply the same for its sub-locations, so a deny of the us multi-region still allows resources in us-east1. (source)
Test before applying
As for every Organization Policy Service guardrail: how to test before enforcing
Mechanism
Organization Policy Service (managed and legacy constraints): Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.
Taken from
provider documentation, provider documentation

What the source says

"This list constraint defines the set of locations where location-based Google Cloud resources can be created." (read 10 Nov 2026).

On what it breaks: "Allowing or denying a multi-region does not imply that all included sub-locations should also be allowed or denied."

Sources

  1. Resource location restriction, read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.