Azure File Sync Endpoint Deletion

Question

Azure File Sync Endpoint Deletion

Richard Fisk 20

Hello All,

After reading the documentation, I would really like to get human verification regarding a plan for migrating servers using Azure File Sync.

The docs I am referencing are:

Manage registered servers with Azure File Sync

https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-server-registration#unregister-the-server

De-provision or delete your Azure File Sync server endpoint (Scenario 1)

https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-server-endpoint-delete

Replace an Azure File Sync server

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

We have an on-prem file server (Server 1) currently configured with Azure File Sync. This is a 1:1 file sync, we are not doing any cloud tiering with Server 1. Server 1 has 7 sync groups.

We would like to de-commission Server 1 and setup Server 2 in its place. We have registered and created 7 sync groups for Server 2 and are doing cloud tiering. Both servers are on and running. Data is syncing to Server 2.

What we want to confirm is this: After proceeding with the steps in Scenario 1 in the De-provisioning article, does deleting the Server 1 endpoints have any effect on the data in the Azure File Share?

We think no, the data has been syncing 1:1. We should be able to delete the Server 1 endpoints and start using Server 2. The Azure File Share has become the source of truth, our data should not be effected by deleting the endpoints for Server 1.

I plan to test this by creating a test file share and sync group, but also wanted to ask here in case we are missing something.

Richard Fisk 20 Reputation points

2026-02-18T14:38:58+00:00

Thank you, Venkatesan. This was the confirmation I needed.

I can also confirm it's working as stated after creating a test share on Server 1, populating it with files, syncing it to Server 2, and then deleting the Server 1 sync group.

Thank you for your help.

Answer accepted by question author

0 additional answers

Your answer

Richard Fisk 20 Reputation points

2026-02-18T14:38:58+00:00

Thank you, Venkatesan. This was the confirmation I needed.

I can also confirm it's working as stated after creating a test share on Server 1, populating it with files, syncing it to Server 2, and then deleting the Server 1 sync group.

Thank you for your help.

Answer 1

Hi Richard Fisk,

Thanks for reaching out in Microsoft Q&A forum,

What we want to confirm is this: After proceeding with the steps in Scenario 1 in the De-provisioning article, does deleting the Server 1 endpoints have any effect on the data in the Azure File Share?

Deleting Server 1's endpoints will not affect data in the Azure File Share, provided sync is fully up to date beforehand. The Azure Files share acts as the source of truth in Azure File Sync, retaining all data independently of server endpoints.

Your approach completing Scenario 1 steps from the deprovisioning documentation, verifying final upload sync (Event 9102 in Event Viewer), then removing endpoints ensures a safe transition to Server 2 with its sync groups and cloud tiering intact.

Verify before deletion:

Block user access to Server 1 synced paths to prevent changes.
Trigger the VSS Sync Scheduled Task for final upload.
Confirm success: Event 9102 shows HResult=0 and PerItemErrorCount=0.
Resolve any errors using FileSyncErrorsReport.ps1 if needed.

Once confirmed, delete endpoints via Azure portal or PowerShell; data stays in the share and continues syncing with Server 2.

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

Please “Accept the Answer” wherever the information provided helps you, this can be beneficial to other community members.

Share via

Azure File Sync Endpoint Deletion

0 additional answers

Your answer