Anonymous

My feedback

  1. 1,185 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
    Anonymous commented  · 

    any update on this? I need this feature... the 'documented' workarounds suck.. option 1: use sync, option 2: use vpn.. wow.. those are really great workarounds!

    Anonymous supported this idea  · 
  2. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Active Directory » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base