Troubleshooting Cloudbreak
Also available as:

Cloudbreak deployment errors on Azure

The following section lists common issues related to launching Cloudbreak on Azure and steps to resolve them.

Resource was not found

Example error message: Resource /subscriptions/…/resourceGroups//providers/Microsoft.Network/virtualNetworks/cbdeployerVnet/ subnets/cbdeployerSubnet referenced by resource /subscriptions/…/resourceGroups/Manulife-ADLS/providers/ Microsoft.Network/networkInterfaces/cbdeployerNic was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.

Symptom: The most common reason for this error is that you did not provide the Vnet RG Name (last parameter in the template).

Solution: To solve this, when launching Cloudbreak, under “Vnet RG Name” provide the name of the resource group in which the selected VNet is located. If using a new VNet, enter the same resource group name as in “Resource group”.