Databricks
Databricks support is in preview. 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 or https://adb-1234567890123456.7.azuredatabricks.net.
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 |
| Posit Workbench managed credentials | Workbench sessions where an administrator set up Databricks | Positron and RStudio on Posit Workbench |
In the provider configuration dialog (the AI Providers screen in Positron), select Connect next to Databricks, choose Service principal OAuth or Personal access token as the Authentication method, and enter the Workspace URL. Service-principal OAuth asks for a Client ID and Client 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.
If you signed in to Databricks through your browser in an earlier Positron version, connect again with a personal access token or a service principal.
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_AUTH_TYPE="oauth-m2m"
export DATABRICKS_HOST="https://dbc-example.cloud.databricks.com"
export DATABRICKS_CLIENT_ID="your-client-id"
export DATABRICKS_CLIENT_SECRET="your-client-secret"
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.
Posit Workbench managed credentials
In Positron and RStudio on Posit Workbench, when Workbench manages the Databricks profile, Posit Assistant uses it with nothing to set up. It reads the workbench profile from the Databricks configuration file Workbench sets in DATABRICKS_CONFIG_FILE. To use a different profile, set DATABRICKS_CONFIG_PROFILE. If the profile has a host, Posit Assistant saves it as the workspace URL in providers.json.
Credential priority
When more than one Databricks credential is available, Posit Assistant uses the first one it finds, in this order:
- Posit Workbench managed credentials
- Credentials you saved in the provider configuration dialog
- Environment variables
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.