Map Azure Storage as Network Drive

Occasional Visitor

Helping a client migrate completely off on-prem to Azure.  Need to map Azure storage directory as a network drive due to SQL and MS Access coding points to a mapped drive on-prem.  Few of the employees use Comcast at home, and port 445 is blocked so unable to map.  Setup Azure Point to Site VPN, installed on employee's home computer, no issue connecting on VPN client, but still getting "network path not found" when attempting to map the drive.  Anyone run into this type of issue and how did you fix / bypass?

All end points are Windows 10.  

Thanks in advance.

1 Reply
Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open; connections will fail if port 445 is blocked. You can check if your firewall is blocking port 445 with the Test-NetConnection cmdlet. To learn about ways to work around a blocked 445 port, see the Cause 1: Port 445 is blocked section of our Windows troubleshooting guide.

To use an Azure file share with Windows, you must either mount it, which means assigning it a drive letter or mount point path, or access it via its UNC path.

This article uses the storage account key to access the file share. A storage account key is an administrator key for a storage account, including administrator permissions to all files and folders within the file share you're accessing, and for all file shares and other storage resources (blobs, queues, tables, etc.) contained within your storage account. If this is not sufficient for your workload, Azure File Sync may be used, or you may use identity-based authentication over SMB.

A common pattern for lifting and shifting line-of-business (LOB) applications that expect an SMB file share to Azure is to use an Azure file share as an alternative for running a dedicated Windows file server in an Azure VM. One important consideration for successfully migrating a line-of-business application to use an Azure file share is that many line-of-business applications run under the context of a dedicated service account with limited system permissions rather than the VM's administrative account. Therefore, you must ensure that you mount/save the credentials for the Azure file share from the context of the service account rather than your administrative account.