Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Rodrigo Castro

My feedback

  1. 1,503 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    100 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Hi folks,

    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!

    Thanks,

    Will Gries
    Program Manager, Azure Files

    Rodrigo Castro supported this idea  · 
    An error occurred while saving the comment
    Rodrigo Castro commented  · 

    You should create a middleware like OneDrive to route SMB3 from 445 to 443 and vice-versa... 99.99% of home users will be blocked on 445. ISPs are very difficult to discuss... most of them will never open the ports and there will be no discussion. COVID-19 has shown how its important to have a solution, mainly for small business. It adds cost to use the VPN and in the end the total cost makes it prohibitive.

Feedback and Knowledge Base