These are cloud provider related errors and we will not have much error details from the error message. Based on the error message and also, that you have enough CPU/VM quota available, I think the issue might be due to the storage creation stage in the cluster startup.

If the workspace is a VNET injected workspace, you can try adding Microsoft.Storage service endpoint for both the public and private subnets used for the workspace and check if you are still seeing the same behaviour.