We are evaluating what we can do to address this feedback and would very much appreciate your continued votes and suggestions on it.
One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning
Please don’t hesitate to reach out if you have any additional questions!
Program Manager, Azure FilesTina O' Shea supported this idea ·
An error occurred while saving the commentTina O' Shea commented
Hi There, as an IT person working for lots of small business clients around California, I have been so disappointed that we cannot use SMB to connect as a result of Comcast and AT&T policies regarding port 445. One of my clients has three offices all located within twenty miles of each other and all need access to the same files. I do understand the issue regarding the ransomware on this port, but if we use OneDrive to link cloud storage, then it must not be too far to connect Blob storage the same way.