Analytics and IoT dbac

Azure Databricks Access Connector naming convention

The CAF abbreviation for Azure Databricks Access Connector is dbac. Names can be 3 to 64 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

Naming rules

CAF abbreviation	dbac
Length	3 to 64 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens, underscores
Scope of uniqueness	Unique within the resource group
CAF pattern	dbac-{workload}-{environment}-{region}-{instance}

Rules follow Microsoft's resource naming rules and CAF abbreviations. Some resource types have extra start/end character restrictions, so verify against the official docs before locking in a convention.

Example names

Generated by the same engine as the name generator, so length and character rules are already applied.

Scenario	Generated name	Length
Payments API, production	`dbac-payments-prod-eus-001`	26/64
Web app, development	`dbac-webapp-dev-weu-002`	23/64
Analytics with company prefix	`dbac-contoso-analytics-stage-uks-001`	36/64

Naming in Terraform and Bicep

Build the name from variables so one module produces the right name in every environment.

Terraform

locals {
  databricks_access_connector_name = "dbac-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var databricksAccessConnectorName = 'dbac-${workload}-${environment}-${region}-001'

Generate Azure Databricks Access Connector names for your workload

Free, no login. Validation and Terraform, Bicep, or CSV export included.

Open in the generator →

Related Analytics and IoT resources

as Azure Analysis Services server dbw Azure Databricks workspace dec Azure Data Explorer cluster dedb Azure Data Explorer cluster database adf Azure Data Factory dt Azure Digital Twin instance asa Azure Stream Analytics synplh Synapse Analytics private link hub

See the full list of Azure resource naming rules or read the complete CAF naming guide.