I'm trying to set up a Windows 11 Azure Virtual Desktop that can access an Azure file share as a mapped drive. I successfully created the File Share and can connect to it from my local Windows 11 workstation using commands like `net use S: \mystorageaccount.file.core.windows.netsharename` and `New-PSDrive`. However, when I attempt to mount the same path from any Azure VM, I get a System error 67. I verified connectivity with `nslookup` and `Test-Connection`. I also tried this on a Windows Server 2022 VM with the same results. I'm using the Storage Account Key for authentication, but I plan to switch to Entra ID authentication later. Both the File Share and VM are in the same region, and I haven't set up any Azure Firewalls or Network Security Groups. Is there something I might be missing, or do others have advice on getting this to work?
4 Answers
Check the command in the Azure portal; make sure you’re copying it as is. The command format should be similar. Remember to note if it mentions 'localhost' as the domain – might help with connectivity issues.
When using the Storage Account Key, make sure your command looks like this: `net use S: \storageaccountname.file.core.windows.netsharename /user:Azurestorageaccountname`. Just replace 'storageaccountname' and '' with your details and that should do the trick.
I tried the command exactly as you suggested, but it still doesn't work on the Azure VMs. Works perfectly from my workstation though.
Keep in mind that Entra ID authentication relies on the WebAccountManager service, which may not be available on all Windows 11 setups, especially with multi-session images. That might be why it isn't working for you. Just something to consider when configuring your environment.
I found that an Intune policy was blocking NTLM authentication on my setup. Once I adjusted the policies to allow NTLM for the Azure VM, it started working. You might want to check if there’s a similar policy affecting your VM. Here’s what I had to change in the settings: adjust the Network Security policies for NTLM to allow outgoing traffic.
Yeah, I noticed they suggest 'localhost' for the username, but when I try 'Azure' for the domain, I still run into issues on the VMs.