This list constraint defines the set of locations where location-based GCP resources can be created.
Policies for this constraint can specify multi-regions such as asia and europe, regions such as us-east1 or europe-west1, or individual zones such as europe-west1-b as allowed or denied locations.

Every location to be allowed or denied must be listed explicitly.
Allowing or denying a multi-region or region does not imply that all included sub-locations should also be allowed or denied.
For example, if the policy denies the us-east1 region, resources can still be created in the zonal location us-east1-a.
To include sub-locations, use the in: prefix. For example, allowing in:us-east1-locations allows all of the locations that exist within us-east1.

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 organisation policy, prefix your entries with the string in:, followed by the value group.

If the suggested_value field is used in a location policy, it should be a region or a zone. If the value specified is a region, a UI for a zonal resource may pre-populate any zone in that region.
If the value specified is a zone, a UI for a regional resource may pre-populate the region enclosing the zone.

By default, resources can be created in any location.

Affected Resources:

• Cloud Storage
• Compute Engine
• App Engine
• BigQuery
• Pub/Sub
• Cloud Function
• CloudSQL

You can submit your request for the other location with the reasons.
Your request will be reviewed by Architecture team.