You don't get charged simply for creating a new workspace in Azure Databricks. Workspaces act as organizational containers for your teams and projects, so they don't carry any base licensing or provisioning fees.

Where you will see costs is strictly on the consumption side. Databricks bills based on Databricks Units (DBUs), and you only pay for the compute resources, jobs, model serving or SQL warehouses that you actively run within that workspace.

Keep in mind that on the Azure side, the underlying infrastructure costs will depend on your deployment type. If you spin up a classic/hybrid workspace, Azure provisions resources like a VNet, NAT Gateway, and storage in your subscription. You will see those cloud infrastructure charges show up directly on the Azure bill separate from your Databricks DBU usage.

If you are using serverless workspaces, that compute infrastructure is managed entirely by Databricks. You generally won't see Azure infrastructure charges for VMs on your bill, though standard networking and storage access charges will still apply. Because of this model, you can safely create multiple workspaces to isolate your dev, test, and prod environments without worrying about a flat workspace fee multiplying across your account.