Moe Kayali

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
    Moe Kayali commented  · 

    This is a deal-breaker for our use-case right now (SMB3 over WAN). I was able to make this work by using port-forwarding in Azure Firewall, but that costs ~1000 USD a month to enable, so we cannot use that option. Simply redirecting traffic to file storage servers on port 443 to port 445 would solve this issue for us. Thanks!

    Moe Kayali supported this idea  · 

Feedback and Knowledge Base