You have an on-premises Windows Server named Server1 and an Azure file share named share1 in a storage account named storage1. You plan to deploy Azure File Sync. All synchronization traffic must travel over a private network connection, and public network access to both storage1 and the Storage Sync Service must be disabled. Which sequence of steps should you perform to configure Azure File Sync under these security constraints? Arrange the steps in the correct chronological order from first to last.
- 1Register the Microsoft.StorageSync resource provider in the Azure subscription.
- 2Create the Storage Sync Service and configure private endpoints for the Storage Sync Service and the storage account.
- 3Install the Azure File Sync agent on the on-premises Windows Server.
- 4Register the Windows Server with the Storage Sync Service.
- 5Create a Sync Group, add a Cloud Endpoint, and then add a Server Endpoint.
Cevap
Register the Microsoft.StorageSync resource provider first, then create the Storage Sync Service and configure private endpoints for both the service and the storage account. Next, install the Azure File Sync agent on the on-premises server, register the server, and finally create a Sync Group, add a Cloud Endpoint, and then add a Server Endpoint.
The correct order ensures all prerequisites are met: the resource provider must be registered to create the service; the service and private endpoints must exist to allow private registration; the agent must be installed to perform the registration; and the server must be registered and the sync group/cloud endpoint created before a server endpoint can be linked.
Adım Adım Çözüm
Anahtar Kavram
Deploying Azure File Sync in a secure, private-only network topology requires registering the resource provider, deploying the Storage Sync Service and its private endpoints, installing the local agent, registering the server over the private network, and then configuring the sync group, cloud endpoint, and server endpoint in sequence.