Stay organized with collections
Save and categorize content based on your preferences.
This page lists the locations where Google Agentspace
(Google Agentspace and NotebookLM Enterprise)
is available.
Agentspace supports data residency at-rest when using
multi-region APIs as described below.
If you don't have compliance or regulatory reasons to locate your data in the
US or EU multi-region, Google recommends that you choose the global location. This
is because the global location provides better end-user response times and the
full feature set. See Limitations for multi-regions.
Multi-regions
The following table lists the multi-regions where
Agentspace is available.
Multi-region description
Multi-region name
API availability in the European Union
eu
API availability in the United States
us
Specify a multi-region for your data store
To confine your at-rest data to the us or eu multi-region, follow
these steps:
If you create the data store through the Google Cloud console, then choose us
(multiple regions in the United States) or eu (multiple regions in the
European Union) when you pick your app location.
For NotebookLM Enterprise, make sure that the user is licensed
for and is using a notebook in the us or eu multi-region.
Review the limitations associated with using a specific
multi-region.
Limitations for multi-regions
The following features of Agentspace are supported globally but
are not supported for the us and eu multi-regions:
Autocomplete: Although autocomplete is available in the us and eu
multi-regions, the tail match suggestions and the advanced document data
mode features cannot be used in multi-regions. For general information about
autocomplete, see Configure
autocomplete.
Dynamic facets: Even if a field is set to Dynamic Facetable,
Agentspace does not use that field as a dynamic facet.
Analytics: Search analytics are available in Public preview in us and
eu multi-regions. Viewing media recommendations analytics is global only.
For general information about analytics, see View
analytics.
Idea generation: The Idea Generation agent is available only in the
global region.
Using multi-region APIs might not produce identical results to the global
API.
[[["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\u003eGoogle Agentspace, including Agentspace Enterprise and NotebookLM Enterprise, is available in the \u003ccode\u003eeu\u003c/code\u003e and \u003ccode\u003eus\u003c/code\u003e multi-regions, as well as the \u003ccode\u003eglobal\u003c/code\u003e location.\u003c/p\u003e\n"],["\u003cp\u003eData residency at-rest is supported in the \u003ccode\u003eus\u003c/code\u003e and \u003ccode\u003eeu\u003c/code\u003e multi-regions by using the corresponding multi-region APIs, ensuring that machine learning processes occur within the chosen region.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a data store, users can choose the \u003ccode\u003eus\u003c/code\u003e or \u003ccode\u003eeu\u003c/code\u003e multi-region through the Google Cloud console or by specifying \u003ccode\u003eeu-discoveryengine\u003c/code\u003e or \u003ccode\u003eus-discoveryengine\u003c/code\u003e in API calls instead of the \u003ccode\u003eglobal\u003c/code\u003e location.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eglobal\u003c/code\u003e location is recommended by Google when there are no compliance or regulatory reasons to limit data to \u003ccode\u003eus\u003c/code\u003e or \u003ccode\u003eeu\u003c/code\u003e multi-regions, due to better end-user response times and full feature set availability.\u003c/p\u003e\n"],["\u003cp\u003eCertain Agentspace features like autocomplete's advanced functionalities, feedback buttons on the widget, dynamic facets, and some analytics are limited or unavailable in the \u003ccode\u003eus\u003c/code\u003e and \u003ccode\u003eeu\u003c/code\u003e multi-regions, compared to the \u003ccode\u003eglobal\u003c/code\u003e location.\u003c/p\u003e\n"]]],[],null,["# Agentspace locations\n\nThis page lists the locations where Google Agentspace\n(Google Agentspace and NotebookLM Enterprise)\nis available.\n\nAgentspace supports data residency at-rest when using\nmulti-region APIs as described below.\n\nIf you don't have compliance or regulatory reasons to locate your data in the\nUS or EU multi-region, Google recommends that you choose the `global` location. This\nis because the global location provides better end-user response times and the\nfull feature set. See [Limitations for multi-regions](#limitations).\n\nMulti-regions\n-------------\n\nThe following table lists the multi-regions where\nAgentspace is available.\n\n| **Important:** All machine learning (ML) processes, such as training, prediction, and tuning a model, occur within the US when requests are made to regionally-available APIs in the US, or within the EU when requests are made to regionally-available APIs in Europe.\n\nSpecify a multi-region for your data store\n------------------------------------------\n\nTo confine your at-rest data to the `us` or `eu` multi-region, follow\nthese steps:\n\n1. If you create the data store through the Google Cloud console, then choose **us\n (multiple regions in the United States)** or **eu (multiple regions in the\n European Union)** when you pick your app location.\n\n For more information, see [Create an\n app](/agentspace/docs/create-app).\n2. For API calls, replace `discoveryengine` with `eu-discoveryengine` or\n `us-discoveryengine` and replace `global` with `eu` or `us`.\n\n For example, the path for the calls is: \n\n ```\n https://eu-discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/eu/…\n ```\n\n or \n\n ```\n https://us-discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/us/…\n ```\n\n instead of \n\n ```\n https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/…\n ```\n3. For NotebookLM Enterprise, make sure that the user is licensed\n for and is using a notebook in the `us` or `eu` multi-region.\n\n4. Review the [limitations](#limitations) associated with using a specific\n multi-region.\n\nLimitations for multi-regions\n-----------------------------\n\nThe following features of Agentspace are supported globally but\nare not supported for the `us` and `eu` multi-regions:\n\n- **Autocomplete** : Although autocomplete is available in the `us` and `eu`\n multi-regions, the tail match suggestions and the advanced document data\n mode features cannot be used in multi-regions. For general information about\n autocomplete, see [Configure\n autocomplete](/agentspace/docs/configure-autocomplete).\n\n- **Dynamic facets** : Even if a field is set to **Dynamic Facetable**,\n Agentspace does not use that field as a dynamic facet.\n\n- **Analytics** : Search analytics are available in Public preview in `us` and\n `eu` multi-regions. Viewing media recommendations analytics is global only.\n For general information about analytics, see [View\n analytics](/agentspace/docs/view-analytics).\n\n- **Idea generation** : The Idea Generation agent is available only in the\n `global` region.\n\n- Using multi-region APIs might not produce identical results to the global\n API."]]
