Azure Databricks is timing out creating in WUS2.

John Conway (XBOX) 0 Microsoft Employee

Why is azure databricks creation failing.. I've done this ~3 times and it keeps timing out.

{

"code": "ResourceDeploymentFailure",

"target": "/subscriptions/XXX/providers/Microsoft.Databricks/workspaces/XX",

"message": "The resource provision operation did not complete within the allowed timeout period."

}

why? logs don't show anything other then timeout failure waiting for appliance to be created.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Naveena Patlolla 9,390 Reputation points Microsoft External Staff Moderator

2026-03-15T03:45:21.43+00:00
Hey John Conway (XBOX), it looks like your Azure Databricks workspace deployment in West US 2 is hitting an ARM timeout (“ResourceDeploymentFailure … did not complete within the allowed timeout period”). This typically points to one of these root causes:

• Temporary capacity constraints or backend resource unavailability in the region

• Subscription-level quota limits (workspaces, NICs, public IPs, etc.)

• Networking/DNS misconfiguration when using VNet injection

• IP-egress limits or IP-quota exhaustion on your virtual network

Here’s what you can try:

Check Regional Health & Retry – Visit the Azure Status page (https://azure.status.microsoft/en-us/status) or Service Health in the portal to see if West US 2 is experiencing issues. – Wait 10–15 minutes and retry the deployment. Transient capacity shortages often auto-heal.

Verify Subscription & Regional Quotas – In the portal, go to your Subscription → “Usage + quotas” and confirm you haven’t hit limits on: • Databricks workspaces • Network interfaces or public IP addresses • Total vCPUs in West US 2 – If you’re near your IP-quota limit, follow these steps to request an increase: https://docs.microsoft.com/azure/azure-portal/supportability/networking-quota-requests

Simplify Networking (if using VNet injection) – If you’re deploying into a custom VNet, try a public deployment first to rule out VNet issues. – Ensure your VNet DNS can resolve Azure endpoints: • Add Azure recursive DNS (168.63.129.16) to your DNS servers • Verify NSGs/UDRs allow the “AzureDatabricks” service tag to Internet • Allow service endpoints for Microsoft.Storage and Microsoft.Sql on your subnets – For more details, see: https://learn.microsoft.com/azure/databricks/administration-guide/cloud-configurations/azure/udr

Try an Alternate Region or Zone – Deploy the same workspace configuration in a nearby region (e.g., East US, West US 3) or into a different availability zone of West US 2 to see if capacity constraints are zone-specific.

Gather More Deployment Diagnostics – In the Azure portal, open your resource group → Activity log → filter on the failed deployment. – Use the Azure CLI to list the deployment operations and error details: az deployment group operation list --resource-group <rg> --name <deploymentName>

If none of the above helps, please let us know:

Are you using a public workspace deployment or VNet-injected?

Do you see any quota alerts under Usage + quotas (workspaces, NICs, IPs, vCPUs)?

Can you successfully create other resources in West US 2?

Are you using custom DNS, NSGs or UDRs in your VNet?

Have you tried a different region or zone for the same template?

Hope this points you in the right direction!

Reference list:

Troubleshoot transient cluster provisioning timeouts (Synapse Spark example) https://learn.microsoft.com/azure/synapse-analytics/known-issues

DNS & networking best practices for VNet-injected Databricks https://learn.microsoft.com/azure/databricks/administration-guide/cloud-configurations/azure/udr

Request IP-quota increase https://docs.microsoft.com/azure/azure-portal/supportability/networking-quota-requests

Azure status & Service Health https://azure.status.microsoft/en-us/status

Your answer