This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The connection script provided by Azure Files shows the following result; however, no Z drive is created.
Can someone please help?
The end user is logged into an Azure AD-joined PC.
Azure AD Kerberos is set as the authentication source on Azure Files.
Azure AD is synced with a domain controller using Azure AD Connect.
PS C:\Users\user\Desktop> .\connect-file-share.ps1
Name Used (GB) Free (GB) Provider Root CurrentLocation
---- --------- --------- -------- ---- ---------------
Z 0.14 102399.86 FileSystem \\storage.file.core.window...
What resolved this issue was adding a "-Scope Global" parameter to the New-PSDrive command.
The script must also run as an administrator.
New-PSDrive -Name Z -PSProvider FileSystem -Root "\\storage.file.core.windows.net\file-share" -Persist -Scope Global
@Ash Glad to hear that issue got fixed, and thank you for sharing the steps that helped you fix the issue. This would definitely benefit community members.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 57.99999999999999%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
@Ash Welcome to Microsoft Q&A, Thank you for posting your here!
No folder with a drive letter in "My Computer" or "This PC"
If you map an Azure file share as an administrator by using the net use command, the share appears to be missing.
Cause
By default, Windows File Explorer doesn't run as an administrator. If you run net use from an administrative command prompt, you map the network drive as an administrator. Because mapped drives are user-centric, the user account that is logged in doesn't display the drives if they're mounted under a different user account.
Solution
Mount the share from a non-administrator command line. Alternatively, you can follow this TechNet topic to configure the EnableLinkedConnections registry value.
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
---------------------------------------------------------------------------------------------------------------------------
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
I'm not using 'net use' to map an Azure file share. I am using the PowerShell script provided by Azure.
I ran the PS script as both the Azure AD user and the PC's local administrator - Z drive still won't map.
$connectTestResult = Test-NetConnection -ComputerName storage.file.core.windows.net -Port 445
if ($connectTestResult.TcpTestSucceeded) {
# Mount the drive
New-PSDrive -Name Z -PSProvider FileSystem -Root "\\storage.file.core.windows.net\file-share" -Persist
} else {
Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
}
Make sure your clients have had the registry key added: https://learn.microsoft.com/azure/storage/files/storage-files-identity-auth-azure-active-directory-enable?tabs=azure-powershell&WT.mc_id=AZ-MVP-5004796#configure-the-clients-to-retrieve-kerberos-tickets
Yep I have already added: reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters /v CloudKerberosTicketRetrievalEnabled /t REG_DWORD /d 1