Marc

My feedback

  1. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Marc supported this idea  · 
  2. 1,193 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
    Marc commented  · 

    I think it would be more helpful in this article if it was more clearly explained how to open port 445. the most confusing part is that it does not even explain where the port needs to be opened at, Azure portal or client computer/facility firewall. Lack of detail makes this very confusing.

    Marc supported this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Marc shared this idea  · 

Feedback and Knowledge Base