balajij8
Esteemed Contributor II

@Aparajita_Nag 

Notebooks rely on either classic all purpose clusters or serverless compute in databricks. You can use serverless compute because your workspace already has serverless enabled. The error occurred as Azure is experiencing temporary capacity constraints for that specific VM SKU in the West India region during classic cluster provisioning. You can bypass the regional capacity bottleneck by selecting alternative VM families such as Standard_D4ds_v4, Standard_D8ds_v5 or Standard_E4ds_v5 if classic cluster is definitely required.
 
You can stay in the current notebook and run any code you need. The serverless compute will handle it. Instead of classic cluster select serverless. Everything you need to work with Unity Catalog tables via SQL is already available in the current environment. You can also use SQL editor and create sql queries if you plan to use SQL warehouses.