@Peter Teunissen What do you mean exactly by switching subscriptions? You can check the source of the tool, it works with the given subscription id, except the following case: The tool itself logs in with azure cli as a first step, you should see the output of the login similar to below: If the subscription here is different than you expected, that might be because the username and password that you provided belongs to multiple subscriptions, and the default is selected. If this is the case, the role assignment phase will most certainly fail. As a workaround you can run download official azure cli and run these steps by hand after changing the default subscription. azure account set new-default-subscription I will file an issue to set the default subscription automatically in the tool to the one provided by the parameter. Hope this helps! ... View more

@Alex Woolford The suggested way of creating these prerequisites is by using our cli tool. cbd azure configure-arm --app_name myapp --app_password password123 --subscription_id 1234-abcd-efgh-1234 This should create all the needed resources. For your particular case, the role assignment seems to be missing. azure role assignment create --objectId $OBJECT_ID -o Owner -c /subscriptions/$APP_SUBSCRIPTION_ID &> $APP_NAME-assign.log The new version of Cloudbreak coming soon will contain enhancements to automate this error-prone process from the UI. Hope this helped! ... View more

@Suzanne Dimant Hortonworks Sandbox for HDP 2.5 comes with Ambari version 2.4.0.0. ... View more

@Alex Gauthier You could use DASH but it is just a workaround to overcome the limitations (eg. IOPS) of WASB. Have you checked Azure Data Lake Storage as an option? It does not have such limits, and HDP supports it. The only prerequisite is the creation of a Data Lake storage account. As a side note, if you would like to automate cluster mgmt. on Azure, Cloudbreak supports WASB (with DASH as well) and now ADLS as well. It automates both the provisioning and configuration steps. ... View more

Hi @Prasanna G! You have the following options: 1. You can use "docker cp" if you have only one file. Here is the documentation with examples. 2. The most flexible solution is mounting local drives to the sandbox with the -v option of "docker run". This is preferred because all the content in the folder is accessible inside the container. docker run -v /Users/<path>:/<container path> ... You can find an example how to configure this for Sandbox here. ... View more