You have an on-premises server named Server 1 that runs Windows Server.

1. Create an Azure Storage account. 2. Create an Azure file share. 3. Create a sync group.

A server endpoint in Azure File Sync -- an on-premises path such as Server1\Share1 -- can only be added to a sync group that already exists and already has a cloud endpoint defined, because a server endpoint is created as a member of a specific sync group and syncs against that group ' s cloud endpoint. Before a sync group and its cloud endpoint can exist, the underlying Azure file share that will serve as the cloud endpoint must itself exist, and before an Azure file share can be created, the Azure Storage account that will host it must exist. This produces a strict prerequisite chain: first create (or select) an Azure Storage account; second, create an Azure file share within that storage account; third, create a sync group in the Storage Sync Service and specify that file share as its cloud endpoint. Only once the sync group and cloud endpoint exist can Share1 on the already-registered Server1 be added as a server endpoint within that sync group. The other listed actions -- deploying an Azure VPN gateway, creating a private endpoint, or deploying the Azure Connected Machine agent -- are unrelated to Azure File Sync ' s cloud-endpoint prerequisites: a VPN gateway and private endpoints concern network connectivity/exposure of Azure resources, and the Connected Machine agent is used for Azure Arc server onboarding, not Azure File Sync. Therefore, the required sequence is: Create an Azure Storage account, Create an Azure file share, Create a sync group.