Features with limited regional availability

This article lists features where there is regional differentiation in feature availability.

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.

The following tables list the Azure regions supported by Databricks. Some features are supported only in a subset of regions, and the table indicates whether or not a region supports each of these features. If a feature is supported in all regions, it is not included in the table.

System tables availability

Region Location System tables
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3

Serverless availability

Region Location Serverless SQL warehouses Serverless compute for notebooks and jobs Mosaic AI Model Training - forecasting Serverless DLT pipelines Private connectivity Databricks Apps
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3

AI and machine learning

Region Location Vector Search Predictive Optimization Mosaic AI Framework and Evaluation Foundation Model Fine-tuning AI Functions using Foundation Model APIs
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3

Model serving regional availability

Region Location Core Model Serving capability * Foundation Model APIs (provisioned throughput) ** Foundation Model APIs (pay-per-token) External models
chinaeast2 ChinaEast2
chinaeast3 ChinaEast3
chinanorth2 ChinaNorth2
chinanorth3 ChinaNorth3
  • CPU compute only

** Includes GPU support

† Region supported when cross geography routing is enabled.