Moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync
Slide deck explaining tools for moving and managing files with Azure Storage: AzCopy for bulk transfers, Storage Explorer for interactive management, and Azure File Sync for ongoing synchronization.
Moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync
Introduction to tools for moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync.
Moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync
Introduction to tools for moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync.
Three jobs hiding behind 'move files to Azure'
Pick the tool by naming the job: transfer, manage, or sync. Transfer: copy data from A to B (often one-time). Interactive management: browse plus admin tasks. Synchronization: keep two endpoints aligned over time.
Transfer vs Manage vs Sync (quick checklist)
These workflows overlap, but they feel very different day-to-day. Transfer: bulk copy, throughput, repeatable runs. Manage: browse, inspect, small uploads/downloads. Sync: ongoing alignment, hybrid endpoints, long-lived setup.
AzCopy = bulk transfer + automation (CLI)
Use AzCopy when you want fast, repeatable transfers you can script. Command-Line Interface (CLI) tool for Azure Storage transfers. Great for many files / large datasets (throughput). Ideal for scripts, scheduled jobs, pipelines. Not designed for visual browsing.
Auth options (high level): Microsoft Entra ID or SAS
You need identity plus permissions before tools can read or write data. Microsoft Entra ID (formerly Azure Active Directory (Azure AD)) equals identity-based access. Shared Access Signature (SAS) equals scoped, time-limited access token. Both require correct permissions for the target data.
Storage Explorer = browse + manage (GUI)
Use Storage Explorer when you want visual access for day-to-day tasks. Graphical User Interface (GUI) desktop app. Browse containers, file shares, folders visually. Best for ad-hoc uploads/downloads and troubleshooting. Not ideal for repeatable bulk migrations.
Two permission layers: management-plane vs data-plane
Seeing a resource isn't the same as having access to the data inside it. Management-plane access: discover and view resources. Data-plane access: read/write blobs and files. Common symptom: 'I can see it, but can't open data'. Fix mindset: verify identity plus roles plus permissions scope.
Azure File Sync = ongoing Windows Server ↔ Azure Files sync
Use Azure File Sync for long-term synchronization in hybrid file server setups. Designed for hybrid: Windows Server plus Azure Files. Azure Files equals cloud 'source of truth'. Windows Servers equals local endpoints (often with caching/tiering). Goal: keep endpoints aligned over time.
Sync vs Backup (don't mix them)
Sync keeps endpoints matching; backup helps you recover the past. Sync equals endpoints aligned (changes replicate). Backup equals point-in-time restore after loss/corruption. Sync can replicate deletions/overwrites. Use backups/snapshots when recovery matters.
Quick rule: match the job to the tool
One sentence per tool is enough to choose correctly most of the time. AzCopy → transfer plus automation plus throughput (CLI). Storage Explorer → interactive browsing plus admin tasks (GUI). Azure File Sync → continuous Windows Server ↔ Azure Files sync.
Scenario: 5 TB overnight (repeatable transfer)
High-volume plus scheduled runs → use AzCopy. Job type: Transfer plus automation. Primary tool: AzCopy (Command-Line Interface (CLI)). Why: throughput plus scripting plus predictable runs. Avoid: manual GUI steps for repeatable migrations.
Scenario: browse now (interactive management)
When you need visibility and ad-hoc actions, use Storage Explorer. Job type: Interactive management. Primary tool: Azure Storage Explorer (Graphical User Interface (GUI)). Best for: browsing plus troubleshooting plus small transfers. Note: overlaps with AzCopy, but workflow is different.
Scenario: hybrid sync (and the 'toolbox' reality)
Continuous Windows Server ↔ Azure Files sync → Azure File Sync; mix tools when jobs differ. Job type: Synchronization over time. Primary tool: Azure File Sync. Don't confuse sync with backup (recovery is separate). Real projects often use multiple tools for different jobs.
Common pitfalls (and quick fixes)
Most problems come from mixing jobs, mixing tools, or missing permissions. AzCopy does not equal Storage Explorer (automation vs interactive). Azure File Sync does not equal backup (alignment vs recovery). Name the job first: transfer / manage / sync. Check identity plus permissions (management-plane vs data-plane).