Databricks workspace in failed state

sumitkuma49 — Tue, 08 Jul 2025 06:27:33 GMT

Hi Community,

I had my Databricks workspace up and running and it was managed through terraform, and encryption was enabled through cmk, there were some updation in the code, so I put terraform plan, one of the key changes(replace) it showed me was

"azurerm_role_assignment.storage_identity_kv_access
module.workspace.azurerm_role_assignment.storage_identity_kv_access"

the terraform run was running for 30 min, and the workspace was in deployment for long time and then ultimately got failed. Again, as all the changes were not done, I reapplied, and I got this error

"Performing CreateOrUpdate: unexpected status 400 (400 Bad Request
) With error: InvalidEncryptionConfiguration: Configure encryption for workspace at creation is not allowed, configure encryption once workspace is created and key vault access policies are added"

Again, I applied and everything and terraform run succeeded but I can see in azure portal that workspace is in failed state, but if I go to Databricks account
I can see Databricks as running and if I go to workspace, I am able to start clusters and execute some queries.

I am not able to launch the workspace using azure portal, not sure there will be other issues due to this.

Could anyone help me to resolve this issue. Let me know if you need anything further to investigate the issue.

Re: Databricks workspace in failed state

SP_6721 — Tue, 22 Jul 2025 13:51:16 GMT

Hi @sumitkuma49 ,

Did you try what the error is suggesting? You could try re-creating the workspace. Once the workspace is created, set up the necessary Key Vault access policies or role assignments. After confirming the permissions are in place, update the existing workspace to enable CMK encryption.

Re: Databricks workspace in failed state

VivekBaira — Sun, 15 Mar 2026 23:58:44 GMT

topic Re: Databricks workspace in failed state in Get Started Discussions

Databricks workspace in failed state

Re: Databricks workspace in failed state

Re: Databricks workspace in failed state