Azure naming · Microsoft.Databricks/workspaces

dbw Databricks workspace

Azure Databricks workspace.

Naming constraints

CAF abbreviationdbw
Resource typeMicrosoft.Databricks/workspaces
Length3–64 characters
CaseMixed case
Allowed charactersAlphanumerics, underscores, and hyphens.
Uniqueness Resource group
SeparatorHyphen
Watch out: Databricks deploys VMs, disks, VNets, and storage with generated names into a managed resource group (databricks-rg-*). Naming and tagging deny policies there break cluster start-up.

Source: Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviation from the Cloud Adoption Framework.

Example & copy-ready

A worked name for workload app, env prod, region weu, instance 001.

Example name
dbw-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript) 
^[A-Za-z0-9_-]{3,64}$
Bicep naming expression 
var name = take('dbw-${workload}-${env}-${region}-${instance}', 64)
Terraform local 
locals {
  name = substr(join("-", compact(["dbw", var.workload, var.env, var.region, var.instance])), 0, 64)
}

Azure Policy can't evaluate regular expressions, so a policy can check the dbw prefix but not the full format. Run the regex in your pipeline, or audit existing names on a schedule.

« Data Explorer cluster Foundry account »

Uniqueness scope

Unique within the parent resource group. The same name can be reused in a different resource group.

Open in the name generator

More in AI & data

All resource types