This post is #3 in the series to automatically build a Microsoft BI machine using PowerShell – see the start of series.
In this series so far:
In our last post we looked a one way of working with the install files required for automating the installation of a BI machine, using disks. This post will focus on sharing the install files using Azure File Service. The Azure File Service exposes file shares using the standard SMB 2.1 protocol. It is in some ways an addition to storage accounts. See http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx for more information. This service is in beta at the moment, so you will need to subscribe to the beta using the Azure Preview portal: http://azure.microsoft.com/en-us/services/preview/. Look for ‘Azure Files’ in the list and click on ‘Try it’ to get your account activated for the preview.
The Azure File Service is not exposed in any portal, probably since it is in preview. Also, keep in mind that while the service is in preview existing storage accounts will not have access to the File Service, so we will need to create a new storage account as well. To do this login into the portal and click on ‘New’ and create a new storage account. After the storage account has been created, you will need to use PowerShell to create a file share. Make sure you have the latest version of Azure PowerShell installed and then run the following in Azure PowerShell or use ISE:
$storageAccountName = "YourStorageAccountName" $storageAccountKey = "YourStorageAccountKey" $ctx = New-AzureStorageContext $storageAccountName $storageAccountKey $s = New-AzureStorageShare YourShareName -Context $ctx
After this runs you should be able to access the file share in multiple ways, but the easiest way I found is mapping the share as a folder in a VM by running:
Net use e: \\YourStorageAccountName.file.core.windows.net\YourShareName /u:YourStorageAccountName YourStorageAccountKey
Now you can download and store files on the share just as you can with disks, as discussed in post #2 on using install files using Azure disks.
Next post will be our final step of the preparation: logging.