Academmia

Moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync

az-900•mixed•

Azure architecture and services

Moving and managing files with Azure Storage: AzCopy, Storage Explorer, and Azure File Sync

Short Summary

When I say “move files to Azure,” I’m usually doing one of three jobs: a one-time transfer, interactive management, or ongoing synchronization. This lesson compares three Microsoft tools that map cleanly to those jobs: AzCopy, Azure Storage Explorer, and Azure File Sync. The goal is to pick the simplest tool that matches the workflow I actually need.

Learning Objectives

By the end of this lesson, you will be able to:

  • Differentiate one-time transfer, interactive management, and ongoing synchronization scenarios.
  • Describe what AzCopy (a Command-Line Interface (CLI) tool) is best at and when it’s the wrong fit.
  • Explain what Azure Storage Explorer (a Graphical User Interface (GUI) tool) is best at for day-to-day storage tasks.
  • Identify what Azure File Sync is designed for in a hybrid Windows Server + Azure Files setup.
  • Choose an authentication approach at a high level (Microsoft Entra ID or Shared Access Signature (SAS)) and understand why permissions matter.

Core Concepts

The three jobs people mix together

When someone says “I need to move files to Azure,” I first ask which job they mean:

  1. Transfer: copy data from A to B (often once, sometimes repeated).
  2. Interactive management: browse storage, inspect content, upload/download a few items, run admin tasks.
  3. Synchronization: keep two endpoints aligned over time (hybrid or multi-location).

Each tool below is strongest in one of these jobs.

AzCopy: high-throughput, scriptable transfers (CLI)

AzCopy is a CLI utility for copying data to, from, or between Azure Storage accounts. I reach for it when:

  • I want automation (scripts, scheduled jobs, pipelines).
  • I need high-throughput transfer for many files or large datasets.
  • I want a repeatable process (same command, predictable behavior).

What it’s not: a “browse and click” tool. Also, while AzCopy has commands like copy and sync, I treat it primarily as a transfer engine. For “keep Windows file shares continuously synchronized,” Azure File Sync is the purpose-built option.

Authentication note (high level): AzCopy can authenticate using Microsoft Entra ID (formerly Azure Active Directory (Azure AD)) or using SAS, depending on what I’m copying and how I’m running the job.

Azure Storage Explorer: interactive browsing and management (GUI)

Azure Storage Explorer (often shortened to “Storage Explorer”) is a desktop GUI app for working with Azure Storage resources interactively. I use it when I want to:

  • Browse containers, file shares, and folders visually.
  • Upload/download a handful of items while troubleshooting.
  • Do ad-hoc tasks without writing scripts.

Permissions note: Storage Explorer commonly needs both:

  • Management-plane access (to discover resources), and
  • Data-plane access (to actually read/write the blobs/files).

That’s why “I can see the storage account but can’t open the data” is a common real-world issue.

Azure File Sync: continuous sync for hybrid file servers

Azure File Sync is a service for centralizing file shares in Azure Files while keeping the flexibility and performance of a Windows Server file server. It’s meant for a hybrid model where:

  • Azure Files is the cloud “source of truth” for the share, and
  • One or more Windows Servers act as local endpoints (often with caching/tiering behavior).

This is not “copy once.” It’s “keep both sides aligned over time,” without forcing users to change how they access files on the LAN.

A simple selection rule

  • AzCopy → transfer + automation + throughput
  • Storage Explorer → interactive browsing + admin tasks
  • Azure File Sync → continuous Windows Server ↔ Azure Files synchronization

Practical Understanding

Practical Situation 1: “I need to move terabytes overnight with a script”

I’m migrating a large dataset and I want it to run during off-hours as a scripted job. I care about throughput and repeatability.

How to think about it: This is transfer + automation. A CLI tool built for bulk movement is the right fit.

Common misunderstanding: “A GUI is simpler, so it must be best.” GUIs are great for ad-hoc work, but they’re not ideal for repeatable, high-volume transfers.

Practical Situation 2: “I need to browse storage and do quick admin tasks”

I want to inspect what’s in a storage account, upload a few files, and download some data for troubleshooting. I prefer a desktop app.

How to think about it: This is interactive management. A GUI tool is ideal because it’s built for browsing and one-off operations.

Common misunderstanding: “Because both tools can upload/download, they’re interchangeable.” The overlap is real, but the workflow is different: GUI for interactive work, CLI for automated/bulk work.

Practical Situation 3: “We keep Windows file servers, but centralize in Azure”

I want to keep on-premises Windows file servers, but I also want Azure to hold the central file share. I need ongoing synchronization so both sides stay aligned.

How to think about it: This is a continuous sync requirement between Windows Server and Azure Files, which points to Azure File Sync.

Common misunderstanding: “Sync is basically backup.” Sync keeps endpoints aligned; backup is about point-in-time recovery after deletion or corruption.

Practical Situation 4: “One-time migration for some data, sync for other shares”

Some shares move once and then live only in Azure. Other shares must remain on-premises while staying synchronized. The team also wants both automation and a visual admin tool.

How to think about it: I use a toolbox: AzCopy for bulk scripted transfers, Storage Explorer for interactive tasks, and Azure File Sync where continuous synchronization is required.

Common misunderstanding: “There must be one ‘best’ tool for everything.” In practice, the jobs are different, so I often use more than one tool.

Common Pitfalls

  • Mistake: Treating AzCopy and Azure Storage Explorer as interchangeable. Correction: Use AzCopy for automated/bulk transfers; use Storage Explorer for interactive browsing and management.

  • Mistake: Assuming Azure File Sync is a backup solution. Correction: Azure File Sync is for synchronization between Windows Server file shares and Azure Files; backup is a separate restore-focused capability.

  • Mistake: Picking a tool before naming the job (transfer vs management vs sync). Correction: Identify the job first, then choose the tool that matches that workflow.

  • Mistake: Forgetting that “can connect” is not the same as “can read/write data.” Correction: Plan authentication and permissions (for example, Microsoft Entra ID roles vs a SAS) before expecting tools to access data.

  • Mistake: Using a manual GUI process for repeatable migrations. Correction: When the job must be repeatable (and especially scheduled), favor a scriptable CLI approach.

  • Mistake: Thinking “sync” means “safe from deletion.” Correction: Sync can replicate deletions/overwrites; use backups or snapshots when you need point-in-time recovery.

Check Your Understanding

  1. Describe a situation where a GUI tool is the best fit, even if a CLI tool could technically do the same upload/download tasks.
  2. Explain the difference between “copy once” and “keep synchronized over time,” and name a real example where that difference matters.
  3. You have three tasks: (a) move 5 TB overnight, (b) inspect and download a few folders right now, (c) keep a Windows file server and the cloud share aligned long-term. Which tool fits each, and why?
  4. List two things you would check before running a transfer against a storage account (think: identity and permissions).
  5. In your own words, explain why Azure File Sync does not replace backups.

Further Reading