Can a Databricks Workspace be renamed after creation ?

[apjeskeaa]

A Databricks workspace has already been created with all configurations completed. The customer has now requested to change the workspace name. Is it possible to rename an existing Databricks workspace after creation?

[nayan_wylde]

No, it is not currently possible to rename an existing Databricks workspace after it has been created—whether on Azure or AWS. Workspace names are immutable once provisioned through the Databricks account console or cloud provider portal.

Workaround Options:

If renaming is essential, here are your alternatives:

• Create a new workspace with the desired name.
• Migrate resources (notebooks, clusters, jobs, users, etc.) from the old workspace to the new one.
• Decommission the old workspace once migration is complete.

[jeffreyaven · Accepted solution]

Yes you can update workspace names, what you can't change is the deployment name (part of the workspace URL, eg the dbc-4c2df2f4-018b in this https://dbc-4c2df2f4-018b.cloud.databricks.com/ - this may be what Nayan was referring to), the workspace name is largely cosmetic, it can be changed in the account console or the workspace console (you would need to be an account admin or workspace admin of course), see the attached screen shots for the UI approach to doing this, it is exposed in the backend API as well https://docs.databricks.com/api/account/workspaces/update

[apjeskeaa]

Workspace name is tightly coupled with several backend configuration right; Is that fine to rename the existing workspace it wont create any issues ? Please confirm. Thanks

[jeffreyaven · Accepted solution]

Yes, you can safely rename it. The workspace name is largely cosmetic - it won't affect the actual workspace functionality, API endpoints, or integrations since those all rely on the deployment name/URL (which doesn't change).

That said, just a heads up: you may want to check if your organization references the workspace name in any documentation, monitoring dashboards, or cost tracking systems - those would need updating to reflect the new name. But from a technical/operational standpoint, the workspace itself will continue functioning normally.