2 different servers have same folder structure and file sync wont create endpoint

Question

2 different servers have same folder structure and file sync wont create endpoint

BH 20

i have 2 file servers that are setup with same root folders. i need to enable file sync on both. the second endpoint creation fails because another not related server has the same folder path.

Venkatesan S 9,575 Reputation points Microsoft External Staff Moderator

2026-06-23T18:45:23.95+00:00
Hi @BH ,

Thanks for reaching out in Microsoft Q&A forums,

Azure File Sync supports using the same local folder path on different registered servers, so having identical root folder paths on two separate file servers should not, by itself, prevent creation of a server endpoint.

This issue is usually caused by one of the following conditions:

The path is already configured as a server endpoint on the same registered server.

The path overlaps with an existing server endpoint, such as a parent or child folder relationship.

The server shown in the error is actually a duplicate registration of the same machine.

Stale server endpoint metadata still exists in the Storage Sync Service.

To identify the root cause, please verify the following:

The exact error message returned in the Azure portal or during server endpoint creation.

Whether both servers are registered to the same Storage Sync Service.

Existing server endpoints for any overlapping or duplicate path configurations.

Azure File Sync agent logs located at %ProgramData%\Microsoft Azure\StorageSyncAgent\Logs.

If both file servers are intended to synchronize the same dataset, they should typically be added as server endpoints within the same sync group. If the second server is being added to a different sync group, ensure there is no conflicting endpoint association and consider using a different local folder path if necessary.

Official Microsoft documentation:

Deploy Azure File Sync

Create an Azure File Sync Server Endpoint

Troubleshoot Azure File Sync sync group management

Kindly let us know if the above helps or you need further assistance on this issue.

Please “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Venkatesan S 9,575 Reputation points Microsoft External Staff Moderator

2026-06-24T17:06:43.6866667+00:00

Hi @BH ,

We haven’t heard back from you regarding our last response and wanted to check if you had the opportunity to review our previous post.

Please “up-vote” if the information helped you. This will help us and others in the community as well.

1 answer

Your answer

Venkatesan S 9,575 Reputation points Microsoft External Staff Moderator

2026-06-23T18:45:23.95+00:00

Hi @BH ,

Thanks for reaching out in Microsoft Q&A forums,

Azure File Sync supports using the same local folder path on different registered servers, so having identical root folder paths on two separate file servers should not, by itself, prevent creation of a server endpoint.

This issue is usually caused by one of the following conditions:

The path is already configured as a server endpoint on the same registered server.

The path overlaps with an existing server endpoint, such as a parent or child folder relationship.

The server shown in the error is actually a duplicate registration of the same machine.

Stale server endpoint metadata still exists in the Storage Sync Service.

To identify the root cause, please verify the following:

The exact error message returned in the Azure portal or during server endpoint creation.

Whether both servers are registered to the same Storage Sync Service.

Existing server endpoints for any overlapping or duplicate path configurations.

Azure File Sync agent logs located at %ProgramData%\Microsoft Azure\StorageSyncAgent\Logs.

If both file servers are intended to synchronize the same dataset, they should typically be added as server endpoints within the same sync group. If the second server is being added to a different sync group, ensure there is no conflicting endpoint association and consider using a different local folder path if necessary.

Official Microsoft documentation:

Deploy Azure File Sync

Create an Azure File Sync Server Endpoint

Troubleshoot Azure File Sync sync group management

Kindly let us know if the above helps or you need further assistance on this issue.

Please “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Venkatesan S 9,575 Reputation points Microsoft External Staff Moderator

2026-06-24T17:06:43.6866667+00:00

Hi @BH ,

We haven’t heard back from you regarding our last response and wanted to check if you had the opportunity to review our previous post.

Please “up-vote” if the information helped you. This will help us and others in the community as well.

Answer 1

hi BH & thx for sharing urs issue here at Q&A portal,

That’s expected behavior in Azure File Sync. A server endpoint path can’t overlap with another server endpoint path in the same sync group, even if it’s on a totally different server.

Azure File Sync treats the server endpoint namespace as one sync topology. So if Server A already has D:\Data

as an endpoint, Server B can’t add the same path as another endpoint in that same sync group. It prevents two independent server copies from both acting like the source for the same root. Otherwise sync conflicts would get ugly fast.

If both servers need to sync the same data, create the endpoint on Server B using a different local path, for example

D:\Data-Replica It can still sync to the same Azure file share/cloud endpoint. The local folder names don’t need to match.

If Server B already has data in its existing D:\Data folder, don’t just point a new empty folder at it and copy stuff around blindly. Compare the data first and decide which server is the source of truth. Azure File Sync initial sync can create conflicts if both sides already contain different files.

Another option is separate sync groups/cloud endpoints if these are actually separate datasets and only happen to use the same folder name/path.

https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide

https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-planning

https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-troubleshoot

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal 
and at my blog https://ctrlaltdel.blog/