The issue came up if our data source on another Azure storage, but not attached to HDI Cluster ? as not in core-site.xml file. HDI Client lib does support to attach new storage once the Cluster provisioned.
Suggestion I received as TAP program member is that HDI cluster is in “transient” cluster pattern. My interpretation is prevision HDI on demand. Note HDI prevision takes about 10 mins, here is one breakdown by my observation.
Accepted: 2 mins
Windows Azure VM Configuration: 4 mins
HDInsight Configuration: 3 mins
Operational: 1 mins
Good part is its default WASB can be reused, and no need moving data around. So if you need attach new storage, just delete existing one, attache storage during HDI prevision.