Unable to connect azure file share in local Machine, Using Active Directory or Microsoft Entra(URL)

Question

Hi, I need help.

On my local machine, I log in with my company ***@Domain.com user ID. This ID is configured in Azure MS Entra ID. I created a file share and assigned the Storage File Data SMB Share Elevated Contributor role to this ID. However, I am unable to access the file share from my local machine, even though I can access it from a Virtual Machine where I assigned the same access. It works fine on the VM but not on my local machine.

Note: My local machine's name is visible in Azure Entra ID under Users -> My UserID -> Devices.

Answer 1

Hello Renjeesh R,

Greetings! Welcome to Microsoft Q&A Platform.

Hope you have followed the perquisites ? and below mentioned setup. You can enable the feature on a new or existing on-premises AD DS environment. Identities used for access must be synced to Azure AD or use a default share-level permission. The Azure AD tenant and the file share that you are accessing must be associated with the same subscription. There is video which explain how connect azure file share using Azure Active Directory Service

Hope you have provided the Share level access (Access control (I AM)to the storage account and File share!

Are you getting any error message? If, so can you please share the screenshot of the error?

Cause 1: Port 445 is blocked: Refer to the suggestion mentioned in this article

Check if your firewall or ISP is blocking port 445, use the AzFileDiagnostics tool or Test-NetConnection cmdlet.

Azure Files only allows connections using SMB 3.0 (with encryption support) from outside the region or datacenter. SMB 3.0 protocol has introduced many security features including channel encryption which is very secure to use over internet. However, it's possible that port 445 has been blocked due to historical reasons of vulnerabilities found in lower SMB versions. In ideal case, the port should be blocked for only for SMB 1.0 traffic and SMB 1.0 should be turned off on all clients.

If you have ever been blocked using Azure Files due to your ISP's port 445, you can setup a Point to Site VPN to your Azure Files. Refer to the suggestions mentioned in the GitHub article

You can mount the file share on your local machine by using the SMB 3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage client libraries, REST APIs, PowerShell, or Azure CLI to access your files in the Azure file share.

Please refer to the suggestion mentioned in the SO thread and let me know the status.

This article lists common problems that are related to Microsoft Azure Files when you connect from Windows clients. It also provides possible causes and resolutions for these problems. In addition to the troubleshooting steps in this article, https://learn.microsoft.com/en-us/azure/storage/files/storage-troubleshoot-windows-file-connection-problems

Overview - on-premises Active Directory Domain Services authentication over SMB for Azure file shares

Similar reference docs- https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/security/files-troubleshoot-smb-authentication?tabs=azure-portal, https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity?tabs=windows, https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-hybrid-identities-enable?tabs=azure-portal, https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-domain-services-enable?tabs=azure-portal.

Hope the above information helps! Please let us know if you have any further queries. I’m happy to assist you further.

---

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.