Stay organized with collections
Save and categorize content based on your preferences.
Agent Assist provides
data residency
to keep your data-at-rest
physically within a specified geographical region or location. When you specify
a region, your data-at-rest is not stored outside that region. Pricing is the
same for all regions.
Specifying a region is particularly helpful in the following use cases:
Your system has regulatory or policy requirements that govern where your data
must reside.
Your network latencies might be improved when the data is in the same region
as your customers. For example, if Belgium customers use europe-west1, they
can expect better latency.
Available regions
Country grouping
Geographical location
Region ID
Data store region ID
Americas
Iowa
us-central1
us (multi-region)
Americas
South Carolina
us-east1
Americas
Oregon
us-west1
Americas
Montreal
northamerica-northeast1
global (multi-region)
Americas
United States multi-region
us *
us (multi-region) *
Europe
Belgium
europe-west1
eu (multi-region)
Europe
London
europe-west2
Europe
Frankfurt
europe-west3
Europe
Eemshaven
europe-west4
eu (multi-region)
Europe
Zurich
europe-west6
eu (multi-region)
Asia Pacific
Singapore
asia-southeast1
Asia Pacific
Jakarta
asia-southeast2
global (multi-region)
Asia Pacific
Tokyo
asia-northeast1
Asia Pacific
Mumbai
asia-south1
Asia Pacific
Sydney
australia-southeast1
Global
Global multi-region (global serving, data-at-rest in United States)
global (preferred) or no region (default) ¶
global (multi-region) ¶
Symbol
Description
*
Vertex AI does not support the 'us' multi-region location. As a result, using Agent Assist's Generative AI features in 'us' multi-region will rely on the respective existing US single region endpoints.
¶
Calls to the global region might have higher latency when called from outside of the US. Prefer a more specific region that is closer to your services and users, if possible.
Available features for regional serving
Region ID
Summarization with custom sections v4.0
Summarization with custom sections v3.1/3.0
Sentiment Analysis
(Proactive) Generative Knowledge Assist
Build Your Own Assist (Preview)
us-central1
✓
✓
✓
✓
✓
us-east1
✓
✓
✓
✓
✓
us-west1
✓
✓
✓
✓
✓
us
✓
✓
✓
✓
✓
northamerica-northeast1
✓
✓
✓
✓
europe-west1
✓
✓
✓
✓
✓
europe-west2
✓
✓
✓
✓
europe-west3
✓
✓
✓
✓
europe-west4
✓
✓
✓
europe-west6
✓
✓
✓
asia-southeast1
✓
✓
✓
✓
asia-southeast2
✓
✓
✓
asia-northeast1
✓
✓
✓
✓
asia-south1
✓
✓
✓
✓
australia-southeast1
✓
✓
✓
✓
✓
global
✓
✓
✓
✓
✓
Data-at-rest
All Agent Assist developer user and end-user data is included in data-at-rest.
For example:
CCAI Transcription only
supports multi-region data in use and data at rest (if not using the Speech
Adaptation feature) in EU, US, North America (Canada).
Only the following regions are supported for data stores, used by (Proactive) Generative Knowledge Assist feature: global, us multi-region, and eu multi-region.
Specify a region using the API
To use regionalization you must specify a region for every API request.
Required fields:
Provide the region ID for the location URL path parameter.
For the global region, use dialogflow.googleapis.com for the
hostname. For all other regions, use [region-id]-dialogflow.googleapis.com
for the hostname.
We recommend that you use the GOOGLE_APPLICATION_CREDENTIALS
environment variable to provide your client libraries with credentials.
See the Dialogflow setup instructions
for more information about setting this variable.
If you instead need to provide manual credentials in your code, one additional
step is required before you can call a regionalized endpoint. You must set
the scope to https://www.googleapis.com/auth/cloud-platform when you generate
your authentication credentials. The following example demonstrates how to do
this in Java when creating a GoogleCredentials object:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eAgent Assist offers data residency, ensuring your data-at-rest is stored within a specified geographical region you select.\u003c/p\u003e\n"],["\u003cp\u003eSpecifying a region can be crucial for systems with regulatory data location requirements or for improving network latency for customers in a specific area.\u003c/p\u003e\n"],["\u003cp\u003eData residency only applies to data-at-rest; it does not cover data-in-use or data-in-transit, so these will not be covered by this regionality.\u003c/p\u003e\n"],["\u003cp\u003eTo implement regionalization, you must specify a region ID in every API request and adjust the hostname accordingly, such as using \u003ccode\u003e[region-id]-dialogflow.googleapis.com\u003c/code\u003e instead of \u003ccode\u003edialogflow.googleapis.com\u003c/code\u003e for the global region.\u003c/p\u003e\n"],["\u003cp\u003eThe Agent Assist Console and Model training do not support regionalization, so it can only be done by calling the API directly, and model training may send data outside of the region.\u003c/p\u003e\n"]]],[],null,["# Regionalization and data residency\n\nAgent Assist provides\n[data residency](https://cloud.google.com/blog/products/identity-security/meet-data-residency-requirements-with-google-cloud)\nto keep your [data-at-rest](https://en.wikipedia.org/wiki/Data_at_rest)\nphysically within a specified geographical region or location. When you specify\na region, your data-at-rest is not stored outside that region. Pricing is the\nsame for all regions.\n\nSpecifying a region is particularly helpful in the following use cases:\n\n- Your system has regulatory or policy requirements that govern where your data must reside.\n- Your network latencies might be improved when the data is in the same region as your customers. For example, if Belgium customers use `europe-west1`, they can expect better latency.\n\n| **Important:** The [AI/ML data location](/terms/data-residency) (data residency for ML processing, or DRZ) commitment is only supported in locations in the US and EU. When requests are made to multi-region APIs, ML processing for generative models may occur in any of those regions. For non-AI/ML data (in use or transit) or data outside US and EU multi-regions, the DRZ commitment doesn't apply. For details, see the [Vertex AI documentation](/vertex-ai/generative-ai/docs/learn/locations).\n\nAvailable regions\n-----------------\n\nAvailable features for regional serving\n---------------------------------------\n\nData-at-rest\n------------\n\nAll Agent Assist developer user and end-user data is included in data-at-rest.\nFor example:\n\n- [Knowledge bases](/agent-assist/docs/knowledge-base) and [knowledge documents](/agent-assist/docs/knowledge-documents).\n- [Conversation profiles](/agent-assist/docs/basics#conversation_profiles).\n- [Conversation](/agent-assist/docs/basics#conversations) and message histories.\n- [Conversion participants](/agent-assist/docs/basics#participants).\n- Suggestions returned by Agent Assist.\n- [Feedbacks](/agent-assist/docs/feedback).\n\nLimitations\n-----------\n\nThe following limitations apply:\n\n- The **Agent Assist console** doesn't support regionalization. You can only implement regionalization by calling the API directly.\n- [Model training](/agent-assist/docs/model-training) does not support regionalization. Your data may get routed outside the region during this process.\n- [API Explorer](https://developers.google.com/explorer-help/), found on many\n [REST reference documents](/dialogflow/es/docs/reference/rest), only supports\n the `global` region for API calls.\n\n- [CCAI Transcription](/agent-assist/docs/transcription) only\n supports multi-region data in use and data at rest (if not using the Speech\n Adaptation feature) in EU, US, North America (Canada).\n\n- Only the following regions are supported for data stores, used by (Proactive) Generative Knowledge Assist feature: `global`, `us` multi-region, and `eu` multi-region.\n\nSpecify a region using the API\n------------------------------\n\nTo use regionalization you must specify a region for every API request.\n\nRequired fields:\n\n- Provide the region ID for the `location` URL path parameter.\n\n- For the `global` region, use `dialogflow.googleapis.com` for the\n hostname. For all other regions, use `[region-id]-dialogflow.googleapis.com`\n for the hostname.\n\nFor example:\n\n- `dialogflow.googleapis.com/v2/projects/project_id/locations/global/knowledgeBases/knowledge_base_id`\n\n- `us-central1-dialogflow.googleapis.com/v2/projects/project_id/locations/us-central1/knowledgeBases/knowledge_base_id`\n\nTo use [client libraries](/agent-assist/docs/reference-index), the following\nsteps are required:\n\n- Set the service endpoint to: `REGION_ID-dialogflow.googleapis.com`.\n- Set the resource name with the correct location, for example:\n\n projects/project_id/locations/region_id/knowledgeBases/knowledge_base_id\n\nCredentials\n-----------\n\nWe recommend that you use the \u003cvar translate=\"no\"\u003eGOOGLE_APPLICATION_CREDENTIALS\u003c/var\u003e\nenvironment variable to provide your client libraries with credentials.\nSee the [Dialogflow setup instructions](/dialogflow/es/docs/quick/setup#auth-env)\nfor more information about setting this variable.\n\nIf you instead need to provide manual credentials in your code, one additional\nstep is required before you can call a regionalized endpoint. You must set\nthe scope to https://www.googleapis.com/auth/cloud-platform when you generate\nyour authentication credentials. The following example demonstrates how to do\nthis in Java when creating a `GoogleCredentials` object: \n\n GoogleCredentials.fromStream(new FileInputStream(\"credential_file\"))\n .createScoped(\"https://www.googleapis.com/auth/cloud-platform\")\n\nCloud Logging\n-------------\n\nSee the [Cloud Logging documentation](/dialogflow/es/docs/logging) to control\nthe region where your logs are stored."]]
