@Error_401 Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
A registered server can support multiple server endpoints, however a sync group can only have One server endpoint per registered server at any given time. Other server endpoints within the sync group must be on different registered servers.
A registered server can support multiple server endpoints, however, a sync group can only have one server endpoint per registered server at any given time. Other server endpoints within the sync group must be on different registered servers.
Multiple server endpoints can exist on the same volume if their namespaces are not overlapping (for example, F:\sync1 and F:\sync2) and each endpoint is syncing to a unique sync group.
This article helps you understand the options and decisions needed to create a new server endpoint and start sync. For this to work, you need to have finished planning for your Azure File Sync deployment and also have deployed resources needed in prior steps to creating a server endpoint.
Azure File Sync does not support more than one server endpoint from the same server in the same sync group. That's why you don’t see the server listed in the drop-down when you create a new server endpoint in the same sync group. We don’t allow multiple server endpoints from the same server in the sync group because the content in those directories would be the same once sync merged the data.
To add a new server endpoint from the same server, you need to create another sync group and that server endpoint will sync to a different Azure file share.
The Azure File Sync agent talks to both the Azure file share directly and to the Azure File Sync service. Data goes directly to the Azure file share.
A server endpoint must be a path on a registered server (rather than a mounted share). Network attached storage (NAS) is not supported.
Although the server endpoint can be on the system volume, server endpoints on the system volume may not use cloud tiering.
Changing the path or drive letter after you established a server endpoint on a volume is not supported. Make sure you are using a final path on your registered server.
A sync group defines the sync topology for a set of files. Endpoints within a sync group are kept in sync with each other. A sync group must contain one cloud endpoint, which represents an Azure file share and one or more server endpoints. A server endpoint represents a path on a registered server. A server can have server endpoints in multiple sync groups. You can create as many sync groups as you need to appropriately describe your desired sync topology.
A cloud endpoint is a pointer to an Azure file share. All server endpoints will sync with a cloud endpoint, making the cloud endpoint the hub. The storage account for the Azure file share must be located in the same region as the Storage Sync Service. The entirety of the Azure file share will be synced, with one exception: A special folder, comparable to the hidden "System Volume Information" folder on an NTFS volume, will be provisioned. This directory is called ".SystemShareInformation". It contains important sync metadata that will not sync to other endpoints. Do not use or delete it!
Please let us know if you have any further queries. I’m happy to assist you further.
----------
Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.