Batch: Jobs restricted to job's location
Google Cloud Batch will enforce stricter location policies for Compute Engine resources used by jobs. Starting July 31, 2026 (or June 30, 2027 for some existing projects), new jobs cannot specify Compute Engine resources outside the job's location. This change requires users to update any jobs using the `allowedLocations[]` field to align with the job's region, otherwise, existing jobs might fail after the respective dates. No action is needed if `allowedLocations[]` is not specified.
Breaking changes (1) ›
- Batch
Starting on the following dates, you can no longer create a job that locates its Compute Engine resources outside of the job's location. For projects that have successfully submitted before July 31, 2026 at least one job that uses the allowedLocations[] field with any region or zones outside of the job's location, changes are starting on June 30, 2027 . For all other projects, changes are starting on July 31, 2026 . If none of your jobs specify the allowedLocations[] field, then no action is required. Otherwise, ensure that any region or zones specified in the allowedLocations[] field are in t
https://docs.cloud.google.com/release-notes#July_20_2026
Related releases
- Compute Engine Hyperdisk Balanced Storage IOPS Increased Google Cloud release notes ·
- GCP Compute Engine MIG Instance Distribution Monitoring Google Cloud release notes ·
- Managed Service for Apache Spark GA with Version 3.0 Google Cloud release notes ·
- Cloud SDK Update: Agent Identity GA, BigQuery S3 Service Directory, Firestore DML Google Cloud release notes ·
- GCP Compute Engine MIGs support VM repair in alternate zones Google Cloud release notes ·
- Compute Engine deprecates customer-supplied encryption keys Google Cloud release notes ·