Model Armor Adds Option to Disable Data Residency Enforcement
Google Cloud's Model Armor now allows users to disable data residency enforcement for data that is in use and in transit. This enables cross-jurisdictional routing, unlocking Model Armor features previously unavailable in regions with limited support. While enforcement can be lifted for active data, data at rest will continue to adhere to established data residency requirements. This enhancement benefits users who need broader feature access while maintaining compliance for stored data.
Features (1) ›
- Model Armor
You can disable data residency enforcement for in-use and in-transit data in Model Armor templates. Disabling data residency enforcement allows cross-jurisdictional routing to enable Model Armor features that are otherwise unavailable in limited-support regions . Data at rest remains compliant with data residency requirements. For more information, see Set data residency compliance and Data residency and endpoints .
https://docs.cloud.google.com/release-notes#August_27_2026
Related releases
- Apigee X SemanticCacheLookup Policy Adds Vector Search Distance Measures Google Cloud release notes ·
- GCP Model Armor Enhances AI Prompt and Response Screening with Larger Token Support Google Cloud release notes ·
- Google Cloud Contact Center as a Service Patches Numerous Issues Google Cloud release notes ·
- Model Armor Feature Clarification for Melbourne and Seoul Regions Google Cloud release notes ·
- GCP Model Armor Feature Filter v3 Stable Promotion and v1/v2 Retirement Google Cloud release notes ·
- Looker Mobile (Legacy) App Deprecation Postponed Google Cloud release notes ·