Failed to create Bonsai workspace

Occasional Contributor

Hi Team,


When I tried to create a Bonsai workspace, I got an error during the deployment state. The status is "conflict", and the operation details is "The resource operation completed with terminal provisioning state 'Failed'".


The status message is:

"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'."
Do you know the reason of this issue, or have any thoughts about it?
8 Replies
Can you send the full ARM log of the failure?

@davidcoe Please check the attached zip file, including two json files.

Thank you for the additional details. It appears Bonsai attempts to create a storage account in the managed resource group but is forbidden by a policy that is enabled on your subscription. I will look into this on the Bonsai side.

Thanks @davidcoe ! Do you have any idea about this forbidden rules of the subscription? For example, what kind of rules it could be?

Hey David, thanks for taking a look at this with us. I work with Jingshu and have also been trying to figure out what's going on here. There are two potential policies that may be relevant, depending on what Bonsai does by default.


  1. Public blob access disabled this policy in our subscription prevents creation of storage accounts with public blob access. For example, when creating an Azure ML instance, the AML creation wizard by default enables public blob access when creating storage. To get around this default behavior, we create a storage account **prior** to initiating the Azure ML creation, then we specify that storage account as the one.  
  2. Minimum TLS Version 1.2 I saw this once before, maybe this is relevant here. The minimum is 1.2 on created storage accounts, but our policy might need 1.0 or 1.1. Do you know what Bonsai defaults to?

If these might be the culprits, let us know what you think a remedy might be. I don't see an option for a pre-existing storage account when creating, is there a way to do this or change the properties?


Thanks again for your help! -Michael


@JingshuChen @davidcoe 

@mkirch Apologies for the delay. The policy is the minimum TLS 1.2. We are working to implement a fix and should have it up by the end of the week. I will let you know when it lands.

best response confirmed by JingshuChen (Occasional Contributor)
We have deployed the update to enforce TLS 1.2. Let me know if you continue to have problems and I can investigate further.

@davidcoe Thank you for the help and getting it updated so quickly! It works on my end and I can create the workspace now. I will let you know if we have any other issues or questions. Thank you!