Azure Databricks

Manage Azure Databricks compute, workspace and Unity Catalog resources from Bicep.

Community Maintained

Version	v0.2.0
Artifact	br:acrdbtextension.azurecr.io/extension/databricks:v0.2.0
Source	github.com/Gijsreyn/bicep-ext-databricks
Publisher	Gijsreyn
Licence	MIT
Category	Data

Installation

Register the extension in bicepconfig.json:

{
  "experimentalFeaturesEnabled": {
    "localDeploy": true,
    "ociEnabled": true
  },
  "implicitExtensions": [],
  "extensions": {
    "DatabricksExtension": "br:acrdbtextension.azurecr.io/extension/databricks:v0.2.0"
  }
}

Then reference it from your Bicep file:

extension DatabricksExtension

Configuration

Configuration is supplied using extension DatabricksExtension with { ... }.

Property	Type	Attributes	Description
workspaceUrl	string	Required	The Azure Databricks workspace URL.

Authentication

The extension first uses DATABRICKS_ACCESS_TOKEN when that environment variable is set. Otherwise, it uses DefaultAzureCredential to request an Azure Databricks token, allowing credentials such as Azure CLI or managed identity to be used.

Extension declaration

Pass the URL of the target Azure Databricks workspace when declaring the extension:

targetScope = 'local'

param workspaceUrl string

extension databricksExtension with {
  workspaceUrl: workspaceUrl
}

The extension supports compute resources, workspace objects such as directories, Git credentials, repositories and secrets, and Unity Catalog resources.

Notes

• The workspace URL must identify an existing Azure Databricks workspace.
• The identity or access token used by the extension needs permissions for each Databricks resource managed by the template.

Resource types

This extension exposes 12 resource types, documented under Reference.

Reference generated from acrdbtextension.azurecr.io/extension/databricks:v0.2.0 on 2026-08-24.