---
title: "Databricks (Service Principal) connector for agents — authorization and setup — AgentSky"
description: "Databricks is the lakehouse company, helping data teams solve the world’s toughest problems. Connect Databricks (Service Principal) to AgentSky with managed OAuth."
url: https://agentsky.dev/connectors/databricks_oauth
---

# Databricks (Service Principal)

Databricks is the lakehouse company, helping data teams solve the world’s toughest problems. Connect your account through managed OAuth to use the available operations in an agent task.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fconnectors%2Fdatabricks_oauth%3Fresume%3D1)

Connect Databricks (Service Principal) using the Connectors control before sending. Authorization opens separately and your draft stays here.

Setup

## Connect Databricks (Service Principal) with an explicit scope.

You need an AgentSky account and authority to connect the application account. Start with a read-only task before allowing changes.

01

### Find the application

Open connector settings and search for Databricks (Service Principal). If the catalog is unavailable, retry its load; an unavailable list is not proof the app is unsupported.

02

### Review authorization

Review the Databricks (Service Principal) account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

### Verify a bounded task

Name one Databricks (Service Principal) resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission.

Verify access and results

## A connected account is the start of the workflow.

Open the same resource in Databricks (Service Principal) and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

- Access troubleshooting If Databricks (Service Principal) access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
- Available actions The runtime discovers the connector's current operations and input requirements. Do not assume every feature in the application's website is available as an agent action.
- Authorize changes explicitly For writes, specify the target and the allowed change. An instruction to draft or analyze is not permission to publish, send or delete.

## Databricks (Service Principal) connector questions

## Related resources

[Claude Code + Databricks (Service Principal)Use Databricks (Service Principal) with Claude Code in the shared Composer.](https://agentsky.dev/agents/claude-code/connectors/databricks_oauth) [Codex + Databricks (Service Principal)Use Databricks (Service Principal) with Codex in the shared Composer.](https://agentsky.dev/agents/codex/connectors/databricks_oauth) [OpenClaw + Databricks (Service Principal)Use Databricks (Service Principal) with OpenClaw in the shared Composer.](https://agentsky.dev/agents/openclaw/connectors/databricks_oauth) [OpenCode + Databricks (Service Principal)Use Databricks (Service Principal) with OpenCode in the shared Composer.](https://agentsky.dev/agents/opencode/connectors/databricks_oauth) [Hermes + Databricks (Service Principal)Use Databricks (Service Principal) with Hermes in the shared Composer.](https://agentsky.dev/agents/hermes/connectors/databricks_oauth) [Kimi Code + Databricks (Service Principal)Use Databricks (Service Principal) with Kimi Code in the shared Composer.](https://agentsky.dev/agents/kimi-code/connectors/databricks_oauth) [DeepSeek Harness + Databricks (Service Principal)Use Databricks (Service Principal) with DeepSeek Harness in the shared Composer.](https://agentsky.dev/agents/dsh/connectors/databricks_oauth) [pi + Databricks (Service Principal)Use Databricks (Service Principal) with pi in the shared Composer.](https://agentsky.dev/agents/pi/connectors/databricks_oauth) [All connectorsUnderstand managed application access.](https://agentsky.dev/connectors) [ChannelsChoose where the agent conversation happens.](https://agentsky.dev/channels) [PricingReview charges before running work.](https://agentsky.dev/pricing)

## Connect the right Databricks (Service Principal) account.

[Open connector settings](https://agentsky.dev/connectors)

## Frequently asked questions

### How do I connect Databricks (Service Principal) to AgentSky?

Sign in to AgentSky, open Connectors in the Composer and search for Databricks (Service Principal). Choose Connect, complete the provider's authorization flow, and return to your draft. Check that the intended account appears as connected before sending.

### Do I need a Databricks (Service Principal) API key?

This listing uses managed OAuth. Authorize the account in the provider's flow; do not paste a password or API key into the Composer. Any account, plan or administrator requirements are determined by Databricks (Service Principal).

### What can my agent do in Databricks (Service Principal)?

The runtime discovers current operations and their required inputs. A catalog listing does not promise every feature of Databricks (Service Principal). Start by asking which operation supports your task, and specify the resources and changes you authorize.

### Does connecting Databricks (Service Principal) make agent tasks free?

No. Account authorization and task usage are separate. AgentSky bills compute and model usage according to its pricing. Any Databricks (Service Principal) subscription, API quota or provider charge remains separate; review those limits before running a task.

---

Markdown copy of https://agentsky.dev/connectors/databricks_oauth. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
