Google Apps Script Data Regions: Complete Admin Guide for 2026 Compliance
If your organization operates under strict data sovereignty rules—whether in healthcare, finance, government, or education—you already know that “where your data lives” is not a minor technical detail. It is a compliance requirement.
Google Apps Script has historically been a flexible automation layer across Workspace, but it lacked the same geographic controls that admins apply to Drive, Gmail, and other core services. That gap closed on September 16, 2026, when Google announced the general availability of data regions support for Google Apps Script
This guide explains exactly what this means for admins, which editions are eligible, how to configure the settings, and what critical deadline arrives in September 2026 for organizations that disable non-regionalized services.
What Are Google Workspace Data Regions?
Data regions are administrative policies that let you choose the geographic location where covered Google Workspace data is stored and processed. The available location options are the United States, Europe, or no preference (globally distributed).
These policies exist to help organizations meet:
- Internal compliance frameworks
- Legal and regulatory obligations
- Data sovereignty requirements
- Sector-specific mandates in regulated industries
When a data region policy is applied to an organizational unit (OU) or group, the covered services in that scope automatically follow the assigned geographic boundary. There is no end-user setting for Apps Script—the platform follows the administrator-assigned policy automatically.
What Changed for Apps Script in September 2026?
Before this update, Apps Script operated without geographic guarantees. Script project files, execution runtime, and key-value storage could be distributed across Google’s global infrastructure without admin-level geographic control.
With general availability, Apps Script now adheres to the same data region policies that already cover services like Drive and Gmail. The change affects two dimensions:
- Data at rest — where script-related data is stored.
- Data processing — where script executions and runtime operations occur.
Both dimensions matter for compliance. A policy that only guarantees storage location but allows processing elsewhere may not satisfy certain regulatory frameworks. Google now supports both for eligible editions.
Data at Rest: What Gets Stored In-Region
When a data region policy is active, the following Apps Script elements are stored within the designated geographic region:
- Script project files — the actual code files and project structure.
- Code definitions — function definitions and script logic.
- Manifest configurations — appsscript.json settings and OAuth scopes.
- Trigger metadata — information about installed triggers and their configuration.
- Properties Service data — key-value pairs stored via Properties Service.
- Cache Service data — temporary cached values stored via Cache Service.
This means that even script metadata and temporary cache data fall under the regional boundary, not just the source code itself.
Important: In-region storage applies to covered data. Google’s documentation explicitly limits the promise to listed covered data and services. Do not assume that every external API, connected system, or third-party log is automatically regionalized.
Data Processing: What Runs In-Region
Data processing coverage is separate from storage coverage and depends on your Workspace edition.
For editions that support in-region processing, the following operations occur within the assigned region:
- Script executions — when a script function runs, it runs in-region.
- Container-bound automations — scripts attached to Docs, Sheets, Forms, or Slides execute in-region.
- Associated runtime operations — supporting runtime tasks stay within the boundary.
If your edition only supports in-region storage (not processing), your scripts still benefit from storage residency, but execution may occur outside the region. This distinction is critical when evaluating whether a specific compliance framework is satisfied.
Which Google Workspace Editions Are Covered?
Not every Workspace edition receives the same level of Apps Script data region support. The following table summarizes the officially stated coverage:
| Google Workspace Edition | In-Region Storage | In-Region Processing |
|---|---|---|
| Enterprise Plus | ✅ Yes | ✅ Yes |
| Frontline Plus | ✅ Yes | ✅ Yes |
| Education Standard | ✅ Yes | ❌ No |
| Education Plus | ✅ Yes | ❌ No |
This table reflects the Apps Script availability list in the launch notice. Advanced settings availability may also depend on your organization’s edition or a Data Regions add-on. Always confirm what controls are actually visible in your Admin console before planning a compliance change.
The September 2026 Deadline: Non-Regionalized Services
This is the part that requires immediate attention from admins.
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 the data regions advanced settings in the Admin console.
In simpler terms:
- If your organization enables the “Drive and Docs” disablement toggle under Data regions → Advanced settings, certain Apps Script features that rely on cross-region processing will stop working.
- This is a hard deadline, not a gradual deprecation.
- Scripts using non-regionalized classes or advanced services may fail after September 2026.
The advanced settings allow admins to disable non-regionalized features on a per-service basis. Apps Script is now included in that framework alongside Calendar, Docs, Drive, Gmail, Chat, and Meet.
Action required: If you rely on Apps Script automations, audit your scripts for non-regionalized service usage before September 2026. Testing with a small OU first is strongly recommended.
How to Configure Data Regions for Apps Script
Configuration happens entirely in the Google Admin console. There is no per-user or per-script setting. Follow these steps:
- Open the Google Admin console at admin.google.com and sign in with a super admin account.
- Navigate to Data regions. Go to Menu → Data → Compliance → Data regions.
- Confirm the geographic policy assigned to the intended organizational unit or group. Options are United States, Europe, or No preference.
- Verify processing coverage. If your edition supports in-region processing, confirm that “Process data in the region selected for data at rest” is enabled.
- Open Advanced settings. Go to Data regions → Advanced settings, then select the relevant service and organizational unit or group.
- Review the cross-region processing option. The option to enable or disable features that may process data across multiple regions is enabled by default. Decide whether to apply the stricter setting.
- Apply to a test OU first. Before a broad rollout, apply the stricter option to a small test organizational unit and run every important automation to verify behavior.
- Expand the policy. Once validated, expand to larger OUs or groups.
Apps Script follows the administrator-assigned policy automatically. Users do not configure anything themselves, and project creation and execution adhere to the assigned policy without end-user intervention.
Admin Best Practices Before You Change Anything
Changing data region settings can break existing automations if scripts depend on services that are not regionalized. Use this checklist before applying stricter settings:
- Inventory all scripts and triggers. Identify every Apps Script project, including container-bound scripts, standalone scripts, and installed triggers.
- Identify non-regionalized service usage. Check whether any script uses advanced services, external APIs, or classes that rely on cross-region processing.
- Test with a small organizational unit. Apply the stricter option to a test group first, not the entire domain.
- Run every critical automation. Execute all important scripts and observe whether any fail due to regional restrictions.
- Review Google’s covered data documentation. Do not assume that storage residency equals complete data sovereignty. Google limits the promise to explicitly listed covered data and services.
- Document your policy decisions. Record which OUs or groups have which data region policies for audit purposes.
Frequently Asked Questions
Data regions are administrative policies that control the geographic location where covered Apps Script data is stored and processed. Admins can choose the United States, Europe, or no preference for organizational units and groups.
Enterprise Plus and Frontline Plus support both in-region storage and in-region processing. Education Standard and Education Plus support in-region storage only.
No. Apps Script follows the administrator-assigned data region policy automatically. There is no end-user setting, and users cannot change the geographic processing location.
For organizations that enable the Drive and Docs disablement toggle in data regions advanced settings, non-regionalized Apps Script services will be disabled starting September 2026. Scripts using affected services may fail.
No. Google’s coverage documentation limits the promise to listed covered data and services. External APIs, connected third-party systems, and some logs may not be regionalized. Review the official covered data list for your specific services.
Yes. Data region policies can be assigned at the organizational unit or group level, allowing different geographic requirements for different parts of your organization.
Key Takeaways
- Data regions for Apps Script are now generally available as of September 16, 2026.
- Apps Script project files, code, manifests, trigger metadata, Properties Service data, and Cache Service data are stored in the designated region.
- In-region processing is available for Enterprise Plus and Frontline Plus; Education editions get storage only.
- September 2026 is a hard deadline for non-regionalized services if the Drive and Docs disablement toggle is enabled.
- Admins must inventory scripts, identify non-regionalized dependencies, and test with a small OU before broad rollout.
- In-region storage does not automatically mean every connected system or external API is regionalized.
Final Thoughts
Google Apps Script data regions close a long-standing compliance gap for organizations that need geographic control over their automation layer. The feature is available now, and for many admins, the real work is not turning it on—it is understanding what might break when stricter settings are applied.
Start with an inventory. Test with a small group. Review the official covered data documentation. And treat the September 2026 deadline for non-regionalized services as a firm date, not a suggestion.
If your organization depends on Apps Script for critical workflows, the time to prepare is now.
0 Comments
Optional