Share via

Azure File Sync and Move 100% to the Cloud

rr-4098 2,271 Reputation points
2026-04-19T01:39:23.1433333+00:00

We are currently using Azure File Sync on our onprem file server to tier files that have not been accessed in x amount of days to Azure. we would like to retire our onprem file server. Is it possible to have Azure File Sync do "one file sync" then cut the shares over to Azure only?

Azure Files
Azure Files

An Azure service that offers file shares in the cloud.

Answer accepted by question author
  1. Venkatesan S 7,635 Reputation points Microsoft External Staff Moderator
    2026-04-20T02:34:19.8666667+00:00

    Hi rr-4098,

    Thanks for reaching out in Microsoft Q&A forum,

    Yes, you can absolutely do exactly that. Since you already have Azure File Sync running with cloud tiering enabled, your data is already syncing to Azure in the background. Here’s how to complete the migration and retire your on-premises server:

    Migration:

    1. Let the initial sync finish Your files are already syncing to Azure. With cloud tiering active, files not accessed in your specified number of days are already tiered to Azure, while hot files stay local.
    2. Do a final sync before cutover
      • Make your on-prem share read-only (or stop SMB sharing) to prevent new changes
      • Wait about 1 hour for any remaining changes to sync to Azure. Azure File Sync syncs changes in near-real-time (seconds to minutes), so this delay ensures everything is up to date.
    3. Remove the server endpoint
      • In the Azure portal, go to your Storage Sync Service > Sync groups > Server endpoints
      • Delete the server endpoint (this stops syncing but keeps all data in Azure)
      • Your files remain intact in the Azure file share
    4. Cut over to Azure Files
      • Redirect users directly to the Azure file share endpoint (\\<storageaccount>.file.core.windows.net\<sharename>)
      • Or use DFS Namespaces to keep the same UNC path (\\domain\<sharename>) so users don’t notice the change
    5. Unregister and decommission
      • After verifying everything works for 2–4 weeks, unregister the server from Azure File Sync
      • Then you can safely retire/decommission your on-premises file server

    Preserves NTFS permissions: ACLs are maintained during sync – no need for extra migration tools

    Minimal downtime: Only the final cutover requires downtime (usually < 1 hour)

    No extra tools needed: Azure File Sync handles everything; you don’t need Storage Migration Service or AZCopy

    Transparent to users: With DFS-N, users keep the same file paths and don’t need to change anything

    This is a recommended and supported migration pattern that Microsoft documents for replacing Windows file servers with Azure Files.

    Update:

    Do share permissoin on the Azure file share need to be updated at all before migrating

    No, share permissions on Azure Files usually don't need updating when migrating with Azure File Sync.

    Since File Sync is already running successfully, NTFS permissions (file/folder ACLs) get preserved automatically during sync. Users will have the same access after cutover.

    Share-level permissions should already work because users can access tiered ("cold") files in Azure right now.

    Quick check before cutover: Have someone test \\<storageaccount>.file.core.windows.net\<sharename>. If tiered files are accessible, you're set.

    Only update if needed: If access fails, add Storage File Data SMB Share Contributor role via Storage Account > IAM.

    After cutover, everything stays the same - especially with DFS Namespaces.

    Official Microsoft documentation

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

    Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-04-19T01:39:34.0666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Yes. Azure File Sync can be used as a migration path and then the environment can be switched to “cloud‑only” Azure file shares after a final sync.

    Conceptually, the steps are:

    1. Ensure all data is fully in Azure Files
      • If cloud tiering is enabled, first recall all tiered files so the server has a complete local copy before the final upload:
        • Turn off cloud tiering on the server endpoint.
        • Run Invoke-StorageSyncFileRecall (with -PerFileRetryCount) and repeat until the summary shows all files are fully recalled and local.
      • Let Azure File Sync complete upload so that the Azure file share has a full, current copy of the data.
    2. Move to a cloud‑only deployment
      • Azure Files supports a cloud-only deployment where the SMB Azure file share replaces the on‑premises file server entirely.
      • Once the Azure file share contains the complete dataset and is in sync, re‑point users and applications from the on‑premises SMB shares to the Azure file share (for example, via new UNC paths, Azure Files over SMB, or mapped drives).
      • At this point, Azure File Sync is no longer required if there is no on‑premises cache server.
    3. Retire the on‑premises file server
      • After verifying that users can access all data directly from the Azure file share and that no workloads depend on the on‑premises server, decommission the Azure File Sync server endpoint and then retire the server.

    If instead of going pure cloud you wanted to move to a different server (for example, a new on‑premises server or Azure VM) before retiring the current one, Azure File Sync also supports that pattern by creating a new sync group and server endpoint and using it as a migration mechanism.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.