configuring azure file sync with on-premise server which has express route

David Kim 66 Reputation points

When configuring azure file storage sync with an on-premise server, do I need to configure private links?,... we would be using a express route peering to connect on-premise to azure. The configurations for private link request a VNET subnet but the onpremise server registered to the file storage sync is not on a VNET in azure.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,186 questions
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,004 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Carlos Solís Salazar 17,021 Reputation points MVP

    Thank you for asking this question on the Microsoft Q&A Platform.

    Azure Files and Azure File Sync provide two main types of endpoints for accessing Azure file shares:

    • Public endpoints, which have a public IP address and can be accessed from anywhere in the world.
    • Private endpoints, which exist within a virtual network and have a private IP address from within the address space of that virtual network.

    If you are required to use the service via an internal network, you must be Configuring Azure File Sync network endpoints

    Hope this helps!

    Accept Answer and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.

    NOTE: To answer you as quickly as possible, please mention me in your reply.

  2. Sumarigo-MSFT 44,081 Reputation points Microsoft Employee

    @David Kim Welcome to Microsoft Q&A Forum! Adding more information to the above answer.

    You can connect to an Azure file share in two ways:

    • Accessing the share directly via the SMB or FileREST protocols. This access pattern is primarily employed to eliminate as many on-premises servers as possible.
    • Creating a cache of the Azure file share on an on-premises server (or Azure VM) with Azure File Sync, and accessing the file share's data from the on-premises server with your protocol of choice (SMB, NFS, FTPS, etc.) for your use case. This access pattern is handy because it combines the best of both on-premises performance and cloud scale and serverless attachable services, such as Azure Backup.

    This article focuses on how to configure networking when your use case calls for using Azure File Sync to cache files on-premises rather than directly mounting the Azure file share over SMB. For more information about networking considerations for an Azure Files deployment, see Azure Files networking considerations.

    Networking configuration for Azure File Sync spans two different Azure objects: a Storage Sync Service and an Azure storage account. A storage account is a management construct that represents a shared pool of storage in which you can deploy multiple file shares, as well as other storage resources, such as blob containers or queues. A Storage Sync Service is a management construct that represents registered servers, which are Windows file servers with an established trust relationship with Azure File Sync, and sync groups, which define the topology of the sync relationship.

    Important: Azure File Sync doesn't support internet routing. The default network routing option, Microsoft routing, is supported by Azure File Sync.

    Azure File Sync networking considerations

    Tunneling traffic over a virtual private network or ExpressRoute

    Please let us know if you have any further queries. I’m happy to assist you further.   

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments