Features with limited regional availability

This article lists features with availability differences by region.

note

Some features are not included in the tables below. These features, known as Designated Services, use Databricks Geos to manage data residency when processing customer content. A Geo is a group of data center regions that Databricks uses to provide predictability and transparency regarding where your data is processed. See Databricks Designated Services and Databricks Geos: Data residency.

The following tables list support for features that are only available on a subset of Databricks on Google Cloud regions. The tables indicate whether or not a region supports each of these features. If a feature is supported in all regions, it is not included.

All Databricks on Google Cloud features are supported in these regions. However, some regions do not support GPU instance types. For a list of regions and zones that support GPU instance types, see the Google Cloud Platform documentation.

Serverless availability

The following table shows supported regions for these serverless compute features that have limited availability:

• Serverless compute: Notebooks, jobs, pipelines, and SQL warehouses
• Databricks Apps
• Serverless workspaces
• Default storage

Region	Location	Serverless compute for notebooks, jobs, pipelines, and SQL warehouses	Databricks Apps	Serverless workspaces	Default storage
asia-northeast1	Tokyo, Japan	✓		✓	✓
asia-south1	Mumbai, India	✓	✓	✓	✓
asia-southeast1	Singapore	✓	✓	✓	✓
australia-southeast1	Sydney, Australia	✓		✓	✓
europe-west1	Belgium, Europe	✓	✓	✓	✓
europe-west2	England, Europe	✓	✓	✓	✓
europe-west3	Frankfurt, Germany	✓	✓	✓	✓
me-central2	Dammam, Saudi Arabia	✓
northamerica-northeast1	Montréal, Canada	✓		✓	✓
southamerica-east1	São Paulo, Brazil	✓		✓	✓
us-central1	Iowa, US	✓	✓	✓	✓
us-east1	South Carolina, US	✓	✓	✓	✓
us-east4	Virginia, US	✓	✓	✓	✓
us-west1	Oregon, US	✓	✓	✓	✓
us-west4	Nevada, US	✓

Ingestion availability

The following table shows supported regions for these ingestion features that have limited availability:

• Managed connectors in Lakeflow Connect
• Zerobus Ingest

Region	Location	Managed connectors in Lakeflow Connect	Zerobus Ingest
asia-northeast1	Tokyo, Japan	✓
asia-south1	Mumbai, India	✓
asia-southeast1	Singapore	✓
australia-southeast1	Sydney, Australia	✓
europe-west1	Belgium, Europe	✓
europe-west2	England, Europe	✓
europe-west3	Frankfurt, Germany	✓
me-central2	Dammam, Saudi Arabia
northamerica-northeast1	Montréal, Canada	✓
southamerica-east1	São Paulo, Brazil
us-central1	Iowa, US	✓
us-east1	South Carolina, US	✓	✓
us-east4	Virginia, US	✓
us-west1	Oregon, US	✓
us-west4	Nevada, US	✓

Compliance standards with serverless and standard compute availability

For a table of supported regions for compliance standards by compute type, see Classic and serverless compute support by region.

AI and machine learning features availability

The following table shows supported regions for these AI and machine learning features that have limited availability:

• Predictive optimization
• Vector Search
• Databricks Data Quality Monitoring

Region	Location	Vector Search	Data Quality Monitoring	Predictive Optimization
asia-northeast1	Tokyo, Japan			✓
asia-south1	Mumbai, India	✓	✓	✓
asia-southeast1	Singapore	✓	✓	✓
australia-southeast1	Sydney, Australia			✓
europe-west1	Belgium, Europe			✓
europe-west2	England, Europe	✓	✓	✓
europe-west3	Frankfurt, Germany	✓		✓
me-central2	Dammam, Saudi Arabia
northamerica-northeast1	Montréal, Canada			✓
southamerica-east1	São Paulo, Brazil
us-central1	Iowa, US	✓	✓	✓
us-east1	South Carolina, US	✓	✓	✓
us-east4	Virginia, US	✓	✓	✓
us-west1	Oregon, US	✓	✓	✓
us-west4	Nevada, US		✓	✓

AI agent features availability

The following table shows supported regions for these agent features that have limited availability:

• Agent Framework and Agent Evaluation
• Knowledge Assistant and Supervisor Agent

Region	Location	Agent Framework & Evaluation	Knowledge Assistant	Supervisor Agent
asia-northeast1	Tokyo, Japan
asia-south1	Mumbai, India	✓
asia-southeast1	Singapore	✓	✓⥂	✓⥂
australia-southeast1	Sydney, Australia
europe-west1	Belgium, Europe
europe-west2	England, Europe	✓
europe-west3	Frankfurt, Germany	✓	✓⥂	✓⥂
me-central2	Dammam, Saudi Arabia
northamerica-northeast1	Montréal, Canada
southamerica-east1	São Paulo, Brazil
us-central1	Iowa, US	✓	✓	✓
us-east1	South Carolina, US	✓	✓	✓
us-east4	Virginia, US	✓	✓	✓
us-west1	Oregon, US	✓	✓	✓
us-west4	Nevada, US

⥂ Region supported only when cross geography routing is enabled. Foundation Model API workloads that rely on GPU compute availability, such as workloads that use models from the Meta Llama family, require cross geography routing.

AI function availability

The following table shows supported regions for these AI functions that have limited availability:

• ai_query (batch inference)
• ai_parse_document v2
• ai_forecast
• ai_extract and ai_classify v2
• Other AI functions (ai_classify, ai_extract, ai_summarize, ai_gen, and others)

Region	Location	ai_query (batch inference)	ai_parse_document v2	ai_forecast	ai_extract and ai_classify v2	Other AI functions
asia-northeast1	Tokyo, Japan			✓
asia-south1	Mumbai, India	✓⥂	✓⥂	✓	✓⥂	✓⥂
asia-southeast1	Singapore	✓⥂	✓⥂	✓	✓⥂	✓⥂
australia-southeast1	Sydney, Australia			✓
europe-west1	Belgium, Europe			✓
europe-west2	England, Europe	✓⥂	✓⥂	✓	✓⥂	✓⥂
europe-west3	Frankfurt, Germany	✓⥂	✓⥂	✓	✓⥂	✓⥂
me-central2	Dammam, Saudi Arabia			✓
northamerica-northeast1	Montréal, Canada			✓
southamerica-east1	São Paulo, Brazil			✓
us-central1	Iowa, US	✓	✓	✓	✓	✓
us-east1	South Carolina, US	✓	✓	✓	✓	✓
us-east4	Virginia, US	✓	✓	✓	✓	✓
us-west1	Oregon, US	✓	✓	✓	✓	✓
us-west4	Nevada, US			✓

⥂ Region supported only when cross geography routing is enabled.

Model serving features availability

The following table shows supported regions for these Model Serving capabilities and features that have limited availability:

• Core Model Serving
• Foundation Model API pay-per-token
• Foundation Model API provisioned throughput
• External models
• AI Gateway (Beta)

Region	Location	Core Model Serving capability (CPU serving)	Core Model Serving capability (GPU serving)	External models	Foundation Model APIs (provisioned throughput)**	Foundation Model APIs (pay-per-token)	AI Gateway (Beta)
asia-northeast1	Tokyo, Japan
asia-south1	Mumbai, India	✓	✓	✓	✓⥂	✓⥂	✓
asia-southeast1	Singapore	✓	✓	✓	✓⥂	✓⥂	✓
australia-southeast1	Sydney, Australia
europe-west1	Belgium, Europe
europe-west2	England, Europe	✓	✓	✓	✓⥂	✓⥂	✓
europe-west3	Frankfurt, Germany	✓	✓	✓	✓⥂	✓⥂	✓
me-central2	Dammam, Saudi Arabia
northamerica-northeast1	Montréal, Canada
southamerica-east1	São Paulo, Brazil
us-central1	Iowa, US	✓	✓	✓	✓	✓	✓
us-east1	South Carolina, US	✓	✓	✓	✓	✓	✓
us-east4	Virginia, US	✓	✓	✓	✓	✓	✓
us-west1	Oregon, US	✓	✓	✓	✓	✓	✓
us-west4	Nevada, US

** Includes GPU support

⥂ Region supported only when cross geography routing is enabled. Foundation Model API workloads that rely on GPU compute availability, such as workloads that use models from the Meta Llama family, require cross geography routing.