Azure FIles with FIle Sync

RL 0

when using file sync and a local server endpoint do clients connect to a local server endpoint name (mapped drive)?

If we have multiple locations with local server endpoints do users in each location need to connect to their local endpoint?

If so how do you handle roaming users between locations?

1 answer

Deepanshukatara-6769 10,765 Reputation points

2024-11-21T06:50:20.6766667+00:00
Hello , Welcome to MS Q&A

Clients connect to a local server endpoint when using Azure File Sync by accessing the Azure file share through an on-premises server that has the Azure File Sync agent installed. The agent synchronizes files between the Azure file share and the local server, allowing clients to access the cached data using their preferred protocols (such as SMB, NFS, or FTPS).

For roaming users, handling their connectivity between different locations can be managed by ensuring that the DNS configuration on the on-premises servers resolves the Azure resources to the appropriate private IP addresses. This can be achieved by creating DNS zones for the relevant Azure resources, allowing users to access the local cache seamlessly as they move between locations.

References:

Networking considerations for Azure File Sync

Connecting Windows File Server to Azure with Azure File Sync

Kindly check and let us know

Please accept answer .

Thanks

Deepanshu
Please sign in to rate this answer.
RL 0 Reputation points

2024-11-21T06:56:41.2133333+00:00

Thanks for this, so once the file sync has been configured on local server endpoint what does that local client actually connect to? Does the folder as part of the share need to be shared out or is there a specific namespace automatically created that users connect to such as \server\share?

Deepanshukatara-6769 10,765 Reputation points

2024-11-21T07:00:31.56+00:00

After Azure File Sync is configured on a local server endpoint, clients connect to the local server endpoint using the standard file-sharing protocols available on Windows Server, such as SMB (Server Message Block). The folder that is part of the Azure file share needs to be shared out on the local server. Users will connect to this shared folder using a path like \server\share.

For example, if the local server is named Server1 and the shared folder is named Share1, users would connect to \Server1\Share1.

References:

What is Azure File Sync?

Migrate from Network Attached Storage (NAS) to a hybrid cloud deployment with Azure File Sync

Networking considerations for Azure File Sync

RL 0 Reputation points

2024-11-21T07:05:44.08+00:00

Excellent, could you elaborate a bit on the roaming users please? "DNS configuration on the on-premises servers resolves the Azure resources to the appropriate private IP addresses"

Deepanshukatara-6769 10,765 Reputation points

2024-11-21T07:23:02.88+00:00

Set up your on-premises DNS servers to forward requests for the core.windows.net and afs.azure.net zones to your Azure private DNS zone. This allows roaming users to resolve Azure resources correctly regardless of their location to the appropriate private IP addresses

RL 0 Reputation points

2024-11-21T08:10:43.2566667+00:00

Ho would the dns forwarding of local server name e.g. server1 relate to the azure resources?

Deepanshukatara-6769 10,765 Reputation points

2024-11-21T10:49:40.84+00:00

DNS forwarding of a local server name, such as server1, to Azure resources involves configuring your on-premises DNS servers to forward specific DNS queries to Azure's DNS servers. This setup ensures that DNS queries for local server names are resolved correctly, whether the queries originate from on-premises or Azure environments.

Here's how it works:

DNS Forwarding Configuration: You configure your on-premises DNS servers to forward DNS requests for specific zones (e.g., core.windows.net and afs.azure.net) to Azure's private DNS zones. This allows DNS queries for Azure resources to be resolved to their private IP addresses.

Name Resolution: When a DNS query for server1 is made, the on-premises DNS server checks its local records. If it doesn't find a match, it forwards the query to the configured Azure DNS server. The Azure DNS server then resolves the query based on its records.

Seamless Integration: This setup allows roaming users and applications to resolve Azure resources correctly, regardless of their location. It ensures that DNS queries for both on-premises and Azure resources are handled seamlessly, providing a unified name resolution experience.

Private IP Address Resolution: By forwarding DNS requests to Azure's private DNS zones, you ensure that the resolved IP addresses are private, enhancing security and connectivity for your Azure resources.

In summary, DNS forwarding of local server names to Azure resources enables integrated and seamless name resolution across on-premises and Azure environments, ensuring that DNS queries are resolved correctly and efficiently.

Hope it answers your query now ?Thanks

RL 0 Reputation points

2024-11-21T11:26:20.73+00:00

ok, got it however what I really would like to achieve a single namespace across all server endpoints so that a drive mapping in one location will be the same in the other location - similar to DFS. Not sure if this can be achieved
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure FIles with FIle Sync

1 answer

Your answer