Sample script to deploy K8S cluster won't work on Azure as they use temporary /mnt

Hi,
This is about
sql-server-samples/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/

Script relies on volumes created in /mnt
(namely create /mnt/local-storage/vol1.... /mnt/local-storage/vol25).
But /mnt in AzureVM is temporary storage, so it will work but everything will be gone after VM restart.

root@xxx:/mnt# pwd
/mnt
root@xxx:/mnt# ll
total 32
drwxr-xr-x  4 root root  4096 Aug 13 08:24 ./
drwxr-xr-x 23 root root  4096 Aug 13 08:23 ../
-r--r--r--  1 root root   639 Aug 13 08:23 DATALOSS_WARNING_README.txt
drwxr-xr-x  2 root root  4096 Aug 13 08:27 local-storage/
drwx------  2 root root 16384 Aug 13 08:23 lost+found/
root@xxx:/mnt# cat DATALOSS_WARNING_README.txt
WARNING: THIS IS A TEMPORARY DISK.

Any data stored on this drive is SUBJECT TO LOSS and THERE IS NO WAY TO
RECOVER IT.

Please do not use this disk for storing any personal or application data.

For additional details to please refer to the MSDN documentation at:
http://msdn.microsoft.com/en-us/library/windowsazure/jj672979.aspx

Start in sql-server-samples/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/ and inspect the sample script that creates /mnt/local-storage/vol1 through vol25. Determine how the deployment should use persistent storage on Azure instead of temporary /mnt storage, then verify that the volumes remain available after a VM restart.