Anonymous

My feedback

  1. 1,198 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    83 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

    An error occurred while saving the comment
    Anonymous commented  · 

    The ultimate problem is allowing client machines to map the Azure Files drives when they are away from the LAN where the server resides. Using Azure File Sync on every client device is obviously not an option. The port 445 issue is a big road block since people will be moving from network to network and need to access the file shares.

Feedback and Knowledge Base