Databricks
Databricks support is experimental. Not all features may work correctly.
Posit Assistant can discover and use models served by a Databricks workspace. Every authentication method requires the workspace URL, such as https://dbc-example.cloud.databricks.com.
Choose an authentication method
| Method | Best for | Availability |
|---|---|---|
| User OAuth (U2M) | A person using a local desktop application | Not currently enabled; Databricks client and scope approval is pending |
| Service-principal OAuth (M2M) | Servers, terminals, automation, and unattended renewal | All Node-backed platforms |
| Personal access token (PAT) | Existing token-based setups | All platforms |
In the provider configuration dialog, select Databricks and choose service-principal OAuth or a personal access token. Service-principal OAuth asks for a client ID and secret; access tokens are obtained and renewed only when needed. Switching methods replaces the active credential source and removes inactive stored secrets.
The local PKCE implementation remains disabled while Posit confirms the supported OAuth client, redirect URI, and minimum operation scopes with Databricks. It will not appear in the configuration dialog until those prerequisites are recorded.
Use service-principal OAuth or a PAT in Standalone, Desktop, the TUI, RStudio, Workbench, and other deployments while user OAuth remains release-gated.
Environment configuration
For a PAT:
export DATABRICKS_HOST="https://dbc-example.cloud.databricks.com"
export DATABRICKS_TOKEN="your-token"
For service-principal OAuth:
export DATABRICKS_HOST="https://dbc-example.cloud.databricks.com"
export DATABRICKS_CLIENT_ID="your-client-id"
export DATABRICKS_CLIENT_SECRET="your-client-secret"
Saved credentials take precedence over environment credentials. If both environment methods are present, DATABRICKS_TOKEN wins unless you set DATABRICKS_AUTH_TYPE=oauth-m2m. Environment client secrets and derived OAuth access tokens are not persisted.
Model availability
Posit Assistant currently lists classic serving endpoints and supported Unity AI Gateway foundation models. Route-optimized endpoints are excluded because they require endpoint-scoped OAuth authorization details that provider-wide PAT, U2M, and M2M credentials do not supply.