GOOGLE-WORKSPACE-56BECBA4AD885F1F release notes and known issues

Summary

Data regions are critical for helping organizations meet internal compliance, legal, regulatory, and data sovereignty obligations by controlling the geographic location of covered data at rest and through data processing. Expanding these controls to Apps Script allows organizations—including those in highly regulated industries and the public sector—to build, deploy, and automate enterprise workflows with confidence that their script data and executions remain within designated geographic boundaries. When a data regions policy is applied to an organizational unit or group, Apps Script data storage and runtime execution adhere to the specified region: Data at rest: Script project files, code definitions, manifest configurations, trigger metadata, and key-value storage (such as Property Service and Cache Service) are stored within the designated geographic region. Data processing: Script executions, container-bound automations, and associated runtime operations are processed within the selected region. Note on non-regionalized services: As Google Apps Script transitions to a regionalized data residency model, non-regionalized Apps Script services will be disabled starting in September 2026 for organizations that turn on the Drive and Docs disablement toggle in data regions advanced settings in the Admin console. Learn more about disabling non-regionalized services . Enabling Data regions support for Apps Script (Under Drive & Docs) Getting started Admins: Apps Script automatically adheres to your existing organizational data location policies configured in the Admin console under Menu > Data > Compliance > Data Regions. To manage advanced controls, such as allowing or disabling features that process data outside designated regions, navigate to Data > Compliance > Data Regions > Advanced settings. Visit the Help Center to learn more about choosing a geographic location for your data, what data is covered by a data region policy , and advanced settings for data regions . End users: There is no end user setting for this feature. Script project creation and executions will automatically follow the data region policy assigned to the user by their administrator. For custom cloud logging and external services, developers can review recommendations in the Apps Script Cloud Projects guide . Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Enterprise: Enterprise Plus (provides in-region data storage and processing) Education: Education Standard and Education Plus (provides in-region data storage only) Other Editions: Frontline Plus (provides in-region data storage and processing) Resources Admin Help Center: Select geographic locations for data residency Admin Help Center: Data covered by region policies Admin Help Center: Configure advanced regional settings Admin Help Center: Overview of Assured Controls add-ons Developer Documentation: Apps Script overview and guides Developer Documentation: Managing Google Cloud Platform projects

Improvements and security content

• Data regions are critical for helping organizations meet internal compliance, legal, regulatory, and data sovereignty obligations by controlling the geographic location of covered data at rest and through data processing. Expanding these controls to Apps Script allows organizations—including those in highly regulated industries and the public sector—to build, deploy, and automate enterprise workflows with confidence that their script data and executions remain within designated geographic boundaries. When a data regions policy is applied to an organizational unit or group, Apps Script data storage and runtime execution adhere to the specified region: Data at rest: Script project files, code definitions, manifest configurations, trigger metadata, and key-value storage (such as Property Service and Cache Service) are stored within the designated geographic region. Data processing: Script executions, container-bound automations, and associated runtime operations are processed within the selected region. Note on non-regionalized services: As Google Apps Script transitions to a regionalized data residency model, non-regionalized Apps Script services will be disabled starting in September 2026 for organizations that turn on the Drive and Docs disablement toggle in data regions advanced settings in the Admin console. Learn more about disabling non-regionalized services . Enabling Data regions support for Apps Script (Under Drive & Docs) Getting started Admins: Apps Script automatically adheres to your existing organizational data location policies configured in the Admin console under Menu > Data > Compliance > Data Regions. To manage advanced controls, such as allowing or disabling features that process data outside designated regions, navigate to Data > Compliance > Data Regions > Advanced settings. Visit the Help Center to learn more about choosing a geographic location for your data, what data is covered by a data region policy , and advanced settings for data regions . End users: There is no end user setting for this feature. Script project creation and executions will automatically follow the data region policy assigned to the user by their administrator. For custom cloud logging and external services, developers can review recommendations in the Apps Script Cloud Projects guide . Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Enterprise: Enterprise Plus (provides in-region data storage and processing) Education: Education Standard and Education Plus (provides in-region data storage only) Other Editions: Frontline Plus (provides in-region data storage and processing) Resources Admin Help Center: Select geographic locations for data residency Admin Help Center: Data covered by region policies Admin Help Center: Configure advanced regional settings Admin Help Center: Overview of Assured Controls add-ons Developer Documentation: Apps Script overview and guides Developer Documentation: Managing Google Cloud Platform projects

Affected products and versions

Recommended action

Review the official publisher document before deployment.

Official publisher evidence