Creating a Mapped Drive to Azure File Storage
It is very simple from within an Azure VM, to access an Azure File Storage Service by means of a mapped network drive to the FileShare using SMB 3.0 protocol. Problems may occur from within a local client machine in connecting to the Azure domain — more to follow on that scenario.
Create the Azure File Service
Go to Azure StorageAccount > Files > Add File Share > Create Name (all lowercase and storage quota) > Create
To get UNC Address to the File Storage Account: File Service > Connect and the Connect blade will open:
Command line code is provided in the Connect blade, to connect to the specific file storage service. Note the comment that outbound TCP port 445 must be opened on the local network or within an Azure VM. This is done from Windows Firewall Advanced Settings on servers or from within an installed specific 3rd Party software on client machines.
Command Prompt and Net Use command:
Copy and paste the path provided in the Azure Connect blade into a text editor such as Notepad, and add the desired drive letter (or use * for next drive letter available) and access key (deleting the [ ] brackets).
In an elevated Command Prompt, paste in the completed command to create the mapped network drive:
‘ Windows Map Network Drive’ Use:
Copy and paste the UNC address and the access keys for this storage account into Notepad.
On Azure VM, or local client machine — Use the UNC address provided which is the Azure Storage Account name wthin the Azure domain and the specific File Service container.
When the ACL dialogue box pops up:
Login = Storage Account Name Password = StorageAccount Access Key
Now there is a mapped drive for direct access to the Azure File Storage service:
As mentioned, this works very quickly from within an Azure VM, or from a client machine where the ISP provider has not blocked Port 445 (and the Operating System supports SMB 3.0. For steps for determining why the mapped network drive has not connected, read our troubleshooting process for Error 80070043 — Network name cannot be found.
Originally published at https://arlanblogs.alvarnet.com on Oct 11, 2016.
