Starting in July 2024, Cloud Build has changed the default behavior for how Cloud Build uses service accounts in new projects

## Announcement Starting in July 2024, Cloud Build has changed the default behavior for how Cloud Build uses service accounts in new projects. This change is detailed in [Cloud Build Service Account Change](https://cloud.google.com/build/docs/cloud-build-service-account-updates). As a result of this change, new projects deploying functions for the first time may be using a default Cloud Build service account with [insufficient permissions](https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts#disable%5Fservice%5Faccount%5Fdefault%5Fgrants) for building a function. If you are impacted by this change you can do one of the following: * Review the Cloud Build guidance on changes to the default service account and [opt out of these changes](https://cloud.google.com/build/docs/cloud-build-service-account-updates#what%5Fdo%5Fyou%5Fneed%5Fto%5Fdo). * Add the [Cloud Build Service Account role](https://cloud.google.com/iam/docs/understanding-roles#cloudbuild.builds.builder) (`roles/cloudbuild.builds.builder`) to the default Compute Service Account. * Create a [custom build service account](https://cloud.google.com/functions/docs/securing/build-custom-sa#grant%5Fpermissions) for function deployments.