Josh Nesbit

My feedback

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

    Please don’t hesitate to reach out if you have any additional questions!


    Will Gries
    Program Manager, Azure Files

    Josh Nesbit supported this idea  · 
    An error occurred while saving the comment
    Josh Nesbit commented  · 

    Allowing an alternate port should be a simple process to allow. The unpredictability of which ISPs are going to work or not makes this service unusable. Performance and familiarity would make this a fantastic solution, but you must allow it to work from any and all ISPs. Allow a custom port and I could onboard 30-50 companies to utilizing this system. Please Fix this

Feedback and Knowledge Base