DMAC

My feedback

  1. 1,179 votes
    Vote
    Sign in
    (thinking…)
    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: 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
    DMAC commented  · 

    I first commented on this issue back in April 2018. Just took a look at the most voted on Storage requests (https://feedback.azure.com/forums/217298-storage) and this problem with port 445 being blocked isn't too far from the top. Many requests above it have a fix "planned" or MS is undergoing a fix and has already "started" development. Perhaps we're closer than we realize to MS creating a proper alternative to blocked port 445. Keeping the faith.

Feedback and Knowledge Base