Helge Rutz

My feedback

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

    Helge Rutz commented  · 

    We found that port 445 is generally blocked by many firewalls, ISPs and so on, cause SMB is considered a "private" protocol, which would cause a security vulnerability in the internet.
    Actually nobody is able or willing to determine if the used protocol is SMB3 with encryption, which would be safe. So Port 445 is a no go! No change in sight!
    But we wanted to use azure files to allow mobile workers to share files and interact with services hosted in azure without the need of a vpn connection to the company network.
    So Azure File Sync is not the right workaround. An the vpn solution in azure is also only a workaround, limited in connections and bandwith, or quite expensive, just to access azure files.
    So the simplest, and best solution for us would just be to change the used TCP Port.
    And we really can't understand, why after 2 years this is still under investigation.
    This make's us really sad as an azure customer.

    Helge Rutz supported this idea  · 
    Helge Rutz commented  · 

    HI, I just want to clarify, that Azure File Sync is not the answer for everything. We have a lot of home office users or mobile workers, which accessed lokal servers via VPN. Now with O365 and azure files, there should be no need to tunnel the traffic through the company network anymore. But the blocking of port 445 would force this. With azure file sync there would be no reduction of local servers or network bandwith.

  2. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Logic Apps » Workflow runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Helge Rutz shared this idea  · 
  3. 5,127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    205 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback! We are interested in collecting feedback on this request – please vote for it if this is something you like to see.

    We’re also interested in learning more what people want to use the SFTP/FTPS for and which protocol they prefer. Please feel free to leave us a comment letting us know more detail!

    Thanks,

    Will Gries
    Program Manager, Azure Files

    Helge Rutz supported this idea  · 

Feedback and Knowledge Base