Databricks / Service profile
Foundation Model APIs
Configuration dependentThe Australian workspace Geo includes Australia and New Zealand; cross-Geo settings and model hosting determine the actual boundary.
The important distinction:Australia and New Zealand share a Databricks Geo. Cross-Geo processing is enabled by default on many non-US/EU workspaces.
Source review: 09 Nov 2026 · Exact model configuration not yet verified
Model coverage
Sydney options include databricks-gpt-oss-20b and databricks-gemma-3-12b
API access
Databricks workspace; entitlement review required
Billing
Pay-per-token option
Capacity commitment
Not yet verified.
Storage
Workspace location alone is insufficient; service and model terms require review.
Retention and training
Model and workspace-level retention needs review. External-model APIs forward requests to their named provider.
Ownership and control
Databricks plus applicable infrastructure or external model provider.
What to check before using it
- Distinguish pay-per-token from provisioned and external-model endpoints.
- Check the processing geography for the exact model and workspace.
- Review workspace costs and model-provider exceptions.
Still to verify
- Australian processing for a named model
- Workspace fees and minimum requirements
- Retention and external model routing
Sources and supported claims
Foundation Model APIs compliance and security ↗
Processing depends on workspace and model and may occur outside the originating region or cloud.
Checked 2026-11-09 · Scope: this service profile