Share via


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 Geographies 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.

The following tables list support for features that are only available on a subset of Azure 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.

Note

The Azure Government regions usgovaz and usgovva do not support any of the following features. Additionally, these regions do not support Databricks SQL or Unity Catalog.

System tables availability

The following table shows supported regions for system tables.

Region Location System tables
australiacentral AustraliaCentral
australiacentral2 AustraliaCentral2
australiaeast AustraliaEast
australiasoutheast AustraliaSoutheast
brazilsouth BrazilSouth
canadacentral CanadaCentral
canadaeast CanadaEast
centralindia CentralIndia
centralus CentralUS
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3
eastasia EastAsia
eastus EastUS
eastus2 EastUS2
francecentral FranceCentral
germanywestcentral GermanyWestCentral
japaneast JapanEast
japanwest JapanWest
koreacentral KoreaCentral
mexicocentral MexicoCentral
northcentralus NorthCentralUS
northeurope NorthEurope
norwayeast NorwayEast
qatarcentral QatarCentral
southafricanorth SouthAfricaNorth
southcentralus SouthCentralUS
southeastasia SoutheastAsia
southindia SouthIndia
swedencentral SwedenCentral
switzerlandnorth SwitzerlandNorth
switzerlandwest SwitzerlandWest
uaenorth UAENorth
uksouth UKSouth
ukwest UKWest
westcentralus WestCentralUS
westeurope WestEurope
westindia WestIndia
westus WestUS
westus2 WestUS2
westus3 WestUS3

Serverless availability

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

Region Location Serverless compute for notebooks, jobs, pipelines, and SQL warehouses Serverless workspaces Default storage Private connectivity Managed connectors in Lakeflow Connect Databricks Apps Mosaic AI Model Training - forecasting
australiacentral AustraliaCentral
australiacentral2 AustraliaCentral2
australiaeast AustraliaEast
australiasoutheast AustraliaSoutheast
brazilsouth BrazilSouth
canadacentral CanadaCentral
canadaeast CanadaEast
centralindia CentralIndia
centralus CentralUS
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3
eastasia EastAsia
eastus EastUS
eastus2 EastUS2
francecentral FranceCentral
germanywestcentral GermanyWestCentral
japaneast JapanEast
japanwest JapanWest
koreacentral KoreaCentral
mexicocentral MexicoCentral
northcentralus NorthCentralUS
northeurope NorthEurope
norwayeast NorwayEast
qatarcentral QatarCentral
southafricanorth SouthAfricaNorth
southcentralus SouthCentralUS
southeastasia SoutheastAsia
southindia SouthIndia
swedencentral SwedenCentral
switzerlandnorth SwitzerlandNorth
switzerlandwest SwitzerlandWest
uaenorth UAENorth
uksouth UKSouth
ukwest UKWest
westcentralus WestCentralUS
westeurope WestEurope
westindia WestIndia
westus WestUS
westus2 WestUS2
westus3 WestUS3

AI and machine learning features availability

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

Region Location Vector Search Predictive Optimization Mosaic AI Framework and Evaluation Foundation Model Fine-tuning AI Functions optimized for batch inference Lakehouse monitoring
australiacentral AustraliaCentral
australiacentral2 AustraliaCentral2
australiaeast AustraliaEast   ✓†
australiasoutheast AustraliaSoutheast
brazilsouth BrazilSouth   ✓†
canadacentral CanadaCentral   ✓†
canadaeast CanadaEast
centralindia CentralIndia   ✓†
centralus CentralUS
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3
eastasia EastAsia     ✓†
eastus EastUS
eastus2 EastUS2
francecentral FranceCentral
germanywestcentral GermanyWestCentral
japaneast JapanEast ✓†
japanwest JapanWest
koreacentral KoreaCentral     ✓†
mexicocentral MexicoCentral
northcentralus NorthCentralUS
northeurope NorthEurope
norwayeast NorwayEast
qatarcentral QatarCentral
southafricanorth SouthAfricaNorth
southcentralus SouthCentralUS
southeastasia SoutheastAsia   ✓†
southindia SouthIndia
swedencentral SwedenCentral
switzerlandnorth SwitzerlandNorth
switzerlandwest SwitzerlandWest
uaenorth UAENorth   ✓†
uksouth UKSouth ✓†
ukwest UKWest
westcentralus WestCentralUS
westeurope WestEurope
westindia WestIndia
westus WestUS
westus2 WestUS2
westus3 WestUS3

† 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.

Model serving features availability

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

Important

For Foundation Model APIs pay-per-token:

  • Databricks-hosted models are only available in certain regions. For some models, the model provider determines the region availability that Databricks must follow. See Foundation models hosted on Databricks for which models are supported in each region.

  • If your workspace is in a Model Serving region, but not in a US or EU region, you might be able to enable cross region data processing. See Enable cross-Geo processing. See Databricks Designated Services for which geographies process pay-per-token workloads.

For Foundation Model APIs provisioned throughput, Meta Llama 3.1 and 3.2 models can be downloaded from HuggingFace and served using provisioned throughput endpoints. See Foundation models hosted on Databricks for supported regions and model variants.

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)
australiacentral AustraliaCentral
australiacentral2 AustraliaCentral2
australiaeast AustraliaEast ✓†
australiasoutheast AustraliaSoutheast
brazilsouth BrazilSouth ✓†
canadacentral CanadaCentral ✓†
canadaeast CanadaEast
centralindia CentralIndia ✓†
centralus CentralUS
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3
eastasia EastAsia ✓† ✓†
eastus EastUS
eastus2 EastUS2
francecentral FranceCentral
germanywestcentral GermanyWestCentral
japaneast JapanEast ✓† ✓†
japanwest JapanWest
koreacentral KoreaCentral ✓† ✓†
mexicocentral MexicoCentral
northcentralus NorthCentralUS
northeurope NorthEurope
norwayeast NorwayEast
qatarcentral QatarCentral
southafricanorth SouthAfricaNorth
southcentralus SouthCentralUS
southeastasia SoutheastAsia ✓† ✓†
southindia SouthIndia
swedencentral SwedenCentral
switzerlandnorth SwitzerlandNorth
switzerlandwest SwitzerlandWest
uaenorth UAENorth ✓† ✓†
uksouth UKSouth ✓† ✓†
ukwest UKWest
westcentralus WestCentralUS
westeurope WestEurope
westindia WestIndia
westus WestUS
westus2 WestUS2
westus3 WestUS3

** 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.