Create Azure Databricks workspace

I noticed that the Provisioning State was "Running" and Status as "Created". After 4 hours, it marked as "RequestTimeOut". After logging out and logging back in, I can see the workspace created successfully.

Azure Databricks workspace deployments normally complete in a few minutes, not hours. If the portal shows “Deployment is in progress” for several hours, the deployment is effectively stuck.

For Azure Databricks workspaces, when a deployment fails or hangs, the workspace resource is still created but left in a failed state. The documented guidance is to delete that workspace and redeploy a new one that addresses any underlying issue.

Recommended steps:

1. In the Azure portal, go to the Databricks Workspaces page and check the workspace status:
   • Provisioning = in progress
   • Running = successful
   • Failed = failed deployment
2. If it is still not Running after this long, delete the workspace resource (this also deletes the managed resource group and any successfully deployed resources) and create a new workspace:
   • Either via Create a resource → Analytics → Azure Databricks in the portal, or
   • Using PowerShell/ARM/Bicep if preferred.
3. After redeployment, verify the status is Running on the Workspaces page.

If repeated deployments hang or fail, switch region or adjust configuration and redeploy, as region-specific issues can cause long-running or failing deployments.

References:

• Deploy a workspace using the Azure Portal
• Deploy a workspace with PowerShell
• Sign up for Azure Databricks for free
• Deploy a workspace with an ARM template
• Deploy a workspace with Bicep
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A