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 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. Some features are available only in a subset of regions. 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.
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 feature availability
Region |
Location |
Serverless compute for notebooks and workflows |
Serverless SQL warehouses |
---|---|---|---|
|
Tokyo |
||
|
Mumbai |
✓ |
✓ |
|
Singapore |
✓ |
✓ |
|
Sydney,Australia |
||
|
Belgium,Europe |
||
|
England,Europe |
✓ |
✓ |
|
Frankfurt,Germany |
||
|
Montréal,Canada |
||
|
Iowa,US |
✓ |
✓ |
|
SouthCarolina,US |
✓ |
✓ |
|
Virginia,US |
✓ |
✓ |
|
Oregon,US |
✓ |
✓ |
|
Nevada,US |
Model serving regional availability
The following table summarizes region availability for Mosaic AI Model Serving capabilities.
Region |
Location |
Core Model Serving capability * |
External models * |
---|---|---|---|
|
Tokyo |
||
|
Mumbai |
||
|
Singapore |
||
|
Sydney,Australia |
||
|
Belgium,Europe |
||
|
England,Europe |
||
|
Frankfurt,Germany |
||
|
Montréal,Canada |
||
|
Iowa,US |
✓ |
✓ |
|
SouthCarolina,US |
✓ |
✓ |
|
Virginia,US |
||
|
Oregon,US |
||
|
Nevada,US |
* CPU compute only