Changes to Google Workspace Storage

[dxas90]

We're writing to inform you about upcoming changes to how Google Cloud Identity and Access Management (IAM) service accounts interact with Google Workspace Storage. You are receiving this message because your organization may have used these accounts with Workspace APIs or Workspace Storage.

Previously, Google Cloud IAM service accounts had access to 15 GB of Google Workspace Storage. However, because they aren't directly managed by administrators, any new service accounts created after April 15, 2025, won't receive this storage. Existing service accounts created before this date will retain their storage.

We’ve provided additional information below to guide you through this change.

What you need to know
Starting April 15, 2025 for new Service Accounts:

New service accounts will not be able to own any Drive items.
At this time, Google Workspace will maintain access to the My Drive of pre-existing service accounts to allow customers to keep existing internal workflows and services that rely on this storage without needing to migrate to other methods for automatic item creation.
Note: Items directly owned by service accounts do not adhere to the Google Workspace admin settings and policies since service accounts are not managed users within your Google Workspace domain.

What you need to do
We recommend that you migrate workflows and services using the Drive storage of existing service accounts for governance and security purposes.

To be able to upload items to Drive with service accounts created after April 15, 2025:

Upload items to Shared Drives
Set up OAuth consent to upload items on behalf of a human user
Use impersonation via domain wide delegation
We’re here to help
We understand that making this change may require some planning. If you have any questions or require assistance navigating this change, please feel free to contact Google Workspace support or review the Workspace Help Center.

Thanks for choosing Google Cloud.

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.

t seems like this will be a problem for current Google Drive backups

Describe the solution you like

This would be a good starting point for setting up a backup system using the S3 API (Min-io, AWS S3, cloudflare...)

Describe alternatives you considered

From my point of view, we can survive with git so far

[AdSchellevis]

I'm not sure what is needed to keep drive operational, but also wouldn't mind that much deprecating it when Google doesn't support the option in its current form.

[AdSchellevis]

Discussed internally, we are going to move the backup option to plugin, so people can use it while it lasts.