# AzCopy

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/azcopy

## Quick definition

AzCopy is a tool you run from a command prompt or script to move files and folders into or out of Azure cloud storage. It can copy data between different storage locations, like from your computer to Azure, between two Azure storage containers, or from one storage account to another. It helps you manage large amounts of data quickly and reliably, and you can automate tasks with scripts.

## Simple meaning

Think of AzCopy as a high-powered, remote-control moving truck for your digital files. Imagine you have a huge collection of family photos and important documents on your home computer, and you want to safely store a backup in a giant, secure warehouse in the cloud. The normal way would be to drag and drop files one by one, which is slow and tiring, especially if you have thousands of files. AzCopy is like hiring a professional moving crew with a fleet of trucks that can load up entire rooms of your digital stuff and transport it to the warehouse in one go. It can even organise the items into different rooms (containers) inside the warehouse. If you need to rearrange things inside the warehouse later, AzCopy can quickly shift boxes from one room to another without you having to download and re-upload them. It is designed for speed and reliability, so even if a power cut happens halfway through, it can pick up where it left off, just like a moving crew keeping an inventory. For IT professionals, this means they can move terabytes of data between storage locations using simple text commands, schedule these moves to happen overnight, and include them in automated scripts without any manual clicking.

## Technical definition

AzCopy is a command-line utility provided by Microsoft for high-performance, scriptable data transfer to and from Azure Blob Storage, Azure Files, and Azure Table Storage. It uses the Azure Storage REST API under the hood, which means it communicates directly with the storage services over HTTPS, ensuring secure and efficient data movement. AzCopy supports copying data between a local file system and an Azure storage account, between two storage accounts, and even between two containers within the same account. It can handle large files and high-volume transfers by using parallel operations, automatically splitting large files into smaller chunks for faster transfer, and using multiple concurrent connections to maximise network throughput. The tool supports both authentication methods: Azure Active Directory (Azure AD) for more secure, role-based access, and Shared Access Signature (SAS) tokens for fine-grained, time-limited permissions. AzCopy also provides data integrity verification by calculating and comparing MD5 hashes of files after transfer, ensuring that no data corruption occurs. In terms of standards, AzCopy works with block blobs, append blobs, and page blobs, and uses the standard HTTP/HTTPS protocols. It can preserve file attributes like last modified time and metadata during transfers, which is critical for maintaining backup integrity. For exam objectives related to AZ-104, AzCopy is a key tool for implementing storage migrations, setting up disaster recovery replication, and performing bulk data uploads from on-premises environments. It can be integrated into Azure DevOps pipelines or PowerShell scripts to automate data management workflows. The utility is cross-platform, available for Windows, macOS, and Linux, and can be installed via Microsoft package managers or direct download. Its ability to synchronise directories, making the destination match the source by adding, updating, or deleting files, makes it invaluable for maintaining consistent cloud storage in dynamic environments.

## Real-life example

Imagine you are moving into a new apartment on the other side of the city. You have a bookshelf filled with hundreds of books, each with its own place. In your old apartment, you also have a storage closet with boxes of seasonal decorations. The normal way to move would be to take each book off the shelf, carry it down the stairs, put it in your car, drive to the new place, carry it up, and place it on the new shelf. Then you would repeat that for every book and every decoration box. That would take days and you would be exhausted. Now, imagine you hire a professional moving company that shows up with a large truck, several movers, and a detailed inventory system. The movers can lift the entire bookshelf onto the truck at once, including the books. They can also take the storage closet boxes and load them separately. In the new apartment, they place the bookshelf exactly where you want it, and they put the decoration boxes in the right closet. If you later decide you want the seasonal decorations to sit on top of the bookshelf, the movers can adjust that without bringing everything back to the old apartment. In the world of IT, your old apartment is a local server or a different cloud storage, the new apartment is Azure Blob Storage, the books and boxes are your data files, and the moving company is AzCopy. The truck represents the high-speed network connection and parallel data channels. The inventory system is AzCopy’s ability to keep track of which files have been transferred and verify their integrity. So, just like the movers save you time and effort by handling the whole move efficiently, AzCopy saves IT professionals from manually dragging files or writing complex scripts to move large datasets to the cloud.

## Why it matters

In practical IT environments, data is constantly being created, modified, and moved. Businesses rely on cloud storage for backups, disaster recovery, analytics, and collaboration. AzCopy matters because it provides a reliable, fast, and scriptable way to transfer large volumes of data to and from Azure without relying on graphical tools that cannot be automated. For example, a company running an on-premises file server might need to migrate 10 terabytes of user data to Azure Files. Using the Azure portal to upload that much data over a web browser would be impractical and take weeks. With AzCopy, the administrator can write a single command to sync the entire folder structure overnight, and the tool will handle retries, verify data integrity, and log the results. This saves time, reduces human error, and allows the migration to be repeated or scheduled. AzCopy is essential for hybrid cloud setups where data must flow between on-premises systems and Azure. It supports incremental sync, meaning only changed files are transferred after the initial copy, which minimises bandwidth usage and costs. For IT professionals managing Azure storage, AzCopy is a fundamental tool for day-to-day operations, data movement for testing, and replication for availability. Understanding it is not just about passing an exam; it is about being able to perform real-world tasks efficiently.

## Why it matters in exams

For the Microsoft Azure Administrator exam (AZ-104), AzCopy is a primary tool covered under the 'Manage Azure storage' domain, specifically within objectives related to 'implement storage accounts' and 'manage data in Azure storage'. Exam questions often ask candidates to choose the appropriate tool for a given scenario. For instance, a question might present a situation where a company needs to upload 100 GB of backup data from an on-premises server to Azure Blob Storage every night. The correct answer would be AzCopy because it is designed for high-speed, automated, and scheduled transfers. Another common question type involves comparing AzCopy with other tools like Azure Storage Explorer, Azure Data Box, or Azure File Sync. Candidates must know that AzCopy is command-line based and suitable for scripting, while Storage Explorer is a graphical tool for smaller, manual operations. Questions may also test knowledge of AzCopy commands, such as how to authenticate with a SAS token versus Azure AD, or how to use the 'sync' command to mirror directories. The AZ-104 exam question patterns include multiple-choice, case studies, and 'drag and drop' arrangements where candidates must order the steps to migrate data using AzCopy. Since AzCopy can handle both uploads and downloads, as well as cross-account transfers, exam questions often require the candidate to select the correct syntax for transferring between different storage locations. Mastery of AzCopy’s parameters, such as '--recursive', '--include-pattern', and '--exclude-pattern', is also tested. Therefore, understanding AzCopy deeply is not optional but essential for achieving a high score on the storage management sections.

## How it appears in exam questions

AzCopy questions in the AZ-104 exam typically fall into three patterns: scenario-based selection, command syntax, and troubleshooting. In scenario-based questions, you are given a business requirement, such as 'A company has 50 TB of historical data on a local NAS that must be moved to Azure Blob Storage for archival. The network bandwidth is limited, but the migration must be automated and resume if interrupted.' You will be asked to choose the best approach, and AzCopy is often the correct answer due to its resume capability and parallel transfer. Another pattern presents a specific command with placeholders and asks you to identify a missing parameter. For example, 'Which of the following completes the AzCopy command to copy all .txt files from a local folder to a container?' The options might include '--include-pattern *.txt', '--include *.txt', or '--pattern txt'. The correct answer is '--include-pattern *.txt'. Troubleshooting-style questions might describe an error during a sync operation, such as 'Access denied' or 'SAS token expired', and ask you to diagnose the cause. In these questions, you must know that SAS tokens are time-limited and that authentication with Azure AD requires the correct role assignment on the storage account. Case study questions may integrate AzCopy into a larger migration plan, where you must sequence steps: first install AzCopy, then generate a SAS token with the appropriate permissions, then run the copy command, then verify with the '--list-of-files' flag. Some questions test the cost and performance implications, asking why AzCopy might be preferred over the Azure portal for large transfers, requiring you to understand network efficiency and automation benefits. Knowing these patterns helps you focus your study on practical command usage and common pitfalls.

## Example scenario

Your company, FinData Corp, has a Windows server in its New York office containing 500 GB of quarterly financial reports stored in a folder called 'QReports'. The company wants to move these files to an Azure Blob Storage container called 'financial-backup' for long-term archiving. The IT manager asks you to perform this transfer securely and with minimal manual effort. You decide to use AzCopy because it can handle large data sets, supports resuming if the transfer is interrupted, and can be scripted to run after business hours. First, you install AzCopy on the Windows server by downloading the latest version from the Microsoft website. Next, you obtain a SAS token for the 'financial-backup' container from the Azure portal, which provides time-limited access with write permissions. You then open a command prompt and run the command: 'azcopy copy "C:\QReports" "https://fincatastorage.blob.core.windows.net/financial-backup?sv=2022-11-02&ss=b&srt=sco&sp=rwdl&se=2025-12-31T23:59:59Z&st=2025-01-01T00:00:00Z&spr=https&sig=..." --recursive'. This command tells AzCopy to copy the entire QReports folder and all its subfolders to the specified container. During the transfer, the network drops out for a few minutes. AzCopy automatically retries the operation and continues from where it left off, ensuring no files are lost. After the transfer completes, you run a verification command: 'azcopy list "https://fincatastorage.blob.core.windows.net/financial-backup?..."' to confirm all 500 GB of files are present. The entire process takes less than two hours, much faster than uploading through the web portal, and you have a log file to share with your manager.

## Common mistakes

- **Mistake:** Using AzCopy without specifying the --recursive flag when copying folders.
  - Why it is wrong: Without --recursive, AzCopy will only copy the top-level files and ignore all subfolders and their contents. The destination will be missing critical data.
  - Fix: Always include --recursive when you want to copy an entire folder tree. If you only need the immediate files, omit the flag intentionally.
- **Mistake:** Copying data with an expired or insufficiently permissioned SAS token.
  - Why it is wrong: The SAS token has a time limit and a set of permissions. If it expires during a long transfer or lacks write permission, the copy will fail partway through, and you may get an authorization error.
  - Fix: Generate a SAS token with a long expiry window for large transfers and ensure it includes at least 'write' and 'list' permissions for the destination container. Use Azure AD as an alternative for longer-lived access.
- **Mistake:** Forgetting to include the destination URL in quotes when the SAS token contains special characters.
  - Why it is wrong: SAS tokens often contain ampersands and other special characters that the command shell interprets incorrectly, leading to a malformed command or authentication failure.
  - Fix: Always enclose the full destination URL (including the SAS token) in double quotes to prevent the shell from misinterpreting characters.
- **Mistake:** Assuming AzCopy can overwrite files by default without using the --overwrite flag.
  - Why it is wrong: By default, AzCopy will skip existing files at the destination that have the same name, unless you explicitly tell it to overwrite. This can lead to outdated or incomplete data at the destination.
  - Fix: Use the --overwrite flag with values like 'true' (to always overwrite) or 'ifSourceNewer' (to overwrite only if the source file is newer) to control the behavior correctly.

## Exam trap

{"trap":"Choosing Azure Storage Explorer over AzCopy for a large-scale automated scheduled migration task.","why_learners_choose_it":"Learners see Storage Explorer as a user-friendly graphical tool and assume it can handle large migrations easily, or they may not fully understand the automation limitations of GUI-based tools.","how_to_avoid_it":"Read the scenario carefully for keywords like 'automated', 'scheduled', 'script', or 'large volume' (over a few GB). These almost always point to AzCopy. Storage Explorer is better suited for ad-hoc manual operations or small data transfers. On the exam, if the question mentions scriptability or resilience to network interruptions, AzCopy is the correct answer."}

## Commonly confused with

- **AzCopy vs Azure Storage Explorer:** Azure Storage Explorer is a graphical desktop tool that allows you to browse and manage storage accounts interactively. It is easier to use for one-off tasks and exploring data, but it cannot be easily automated or scripted for repeated operations. AzCopy, on the other hand, is purely command-line and designed for automation, large-scale transfers, and integration into CI/CD pipelines. (Example: If you need to quickly look at a few blobs in a container, use Storage Explorer. If you need to copy 50 GB of logs from a server to Azure every night, use AzCopy in a scheduled task.)
- **AzCopy vs Azure Data Box:** Azure Data Box is a physical device that Microsoft ships to you for offline data transfer. It is used when transferring very large amounts of data (often tens of terabytes) over a slow network would take weeks. AzCopy transfers data over the network and is suitable when the network bandwidth is practical for the data size. They are complementary: you might use AzCopy to load data onto a Data Box, or to move data once it reaches Azure. (Example: To migrate 100 TB of historical archives from a remote location with limited internet, use Data Box. To sync a few terabytes of daily logs from your datacenter to Azure over a high-speed connection, use AzCopy.)
- **AzCopy vs Azure File Sync:** Azure File Sync is a service that syncs an on-premises Windows file server with Azure Files, enabling multi-site sync and cloud tiering. It is a continuous process that keeps files in sync automatically. AzCopy is a one-time or scheduled copy tool, not a continuous sync service. Azure File Sync is more appropriate for ongoing file server synchronization, while AzCopy is for bulk migrations or ad-hoc copies. (Example: If you have two branch offices that need to share the same set of files in real-time, use Azure File Sync. If you just need to move a year's worth of data to the cloud once, use AzCopy.)

## Step-by-step breakdown

1. **Download and Install AzCopy** — Visit the official Microsoft website to download the latest AzCopy installer for your operating system (Windows, macOS, or Linux). Installation is straightforward, and once completed, the 'azcopy' command becomes available in your terminal or command prompt.
2. **Prepare Authentication** — You need to authenticate with the Azure storage service. The two main methods are: using Azure Active Directory (recommended for long-term scripts) or generating a Shared Access Signature (SAS) token from the Azure portal for specific containers with time-limited permissions. For a script, you might store the SAS token securely as an environment variable.
3. **Identify Source and Destination** — Decide what you want to copy (the source) and where to copy it (the destination). The source can be a local file path (like C:\Data) or a URL to an Azure blob container. The destination can be another local path or an Azure URL with its own SAS token. AzCopy can also copy between two Azure URLs.
4. **Construct the Command** — Use the base syntax: azcopy copy [source] [destination] [options]. Include flags like --recursive for folders, --include-pattern to filter specific file types, and --overwrite ifSourceNewer to avoid overwriting newer files. Always enclose URLs with SAS tokens in double quotes.
5. **Run the Command and Monitor** — Execute the command in the terminal. AzCopy will display progress, including the number of files transferred, transfer rate, and any errors. You can cancel and resume the operation later; AzCopy keeps a job plan file in the local job folder allowing resumption.
6. **Verify the Transfer** — After completion, optionally run the 'azcopy list' command on the destination container to confirm files are present. You can also compare the total file counts or sizes between source and destination using AzCopy's '--list-of-files' flag for validation.

## Practical mini-lesson

AzCopy is more than just a simple copy tool; it is a data orchestration utility that professionals rely on for cloud migration, backup, and disaster recovery. To use it effectively in a real-world environment, you need to understand how it handles performance, authentication, and error recovery. Performance tuning is critical when moving large data sets. AzCopy automatically uses multiple concurrent connections to speed up transfers, but you can control this with the '--concurrency' flag. For example, on a high-bandwidth network, increasing concurrency from the default of 8 to 32 might improve throughput. However, if you are on a limited connection, lowering concurrency can prevent network saturation for other users. Professionals also use AzCopy in scripted workflows. For instance, you might write a PowerShell script that exports a list of all storage accounts in your subscription, then loops through each account and uses AzCopy to copy daily logs into a central archival container. This script can be scheduled with Windows Task Scheduler or a Linux cron job. One common challenge is permission management. When using Azure AD authentication, the user or service principal running AzCopy must have the appropriate RBAC role on the storage account, such as 'Storage Blob Data Contributor'. Without this, the command will fail with an authorization error. Another practical reality is handling large files (multiple GB). AzCopy splits large files into chunks and transfers them in parallel, reducing the impact of a single file failure. If a chunk fails, only that chunk is retried, not the entire file. This makes AzCopy robust for large backups. Professionals also need to be aware of the 'sync' command, which compares the source and destination and makes the destination match. This is useful for incremental backups: after an initial full copy, subsequent runs only transfer changed or new files, saving time and bandwidth. For compliance and auditing, AzCopy offers a '--log-level' option to record all activity to a file. This way, you can prove what was transferred and when. Effective use of AzCopy requires understanding its flag options, authentication nuances, and how to integrate it into automated workflows, all of which are skills directly tested in the AZ-104 exam and essential for daily Azure administration.

## Memory tip

Think 'AzCopy = Automatic Zero-touch Copy'. The 'A' is for Azure and Automatic, and it copies data with integrity checks (that's the 'Copy' part).

## FAQ

**Can AzCopy be used to copy data between two different Azure subscriptions?**

Yes, AzCopy can copy data between storage accounts in different Azure subscriptions. You just need to provide the appropriate source and destination URLs with their respective SAS tokens or use Azure AD authentication with proper permissions on both accounts.

**Does AzCopy support copying from Azure to on-premises?**

Yes. AzCopy can download files from Azure Blob Storage or Azure Files to a local file system. The command syntax is similar, just swap the source and destination positions in the command.

**How does AzCopy handle network interruptions?**

AzCopy automatically retries failed transfers. It also saves a job plan file so that if the command is stopped and restarted, it can resume the transfer from where it left off rather than starting over.

**Do I need to install anything to use AzCopy?**

Yes, you must download and install AzCopy on the machine from which you are running the command. It is a standalone executable available for Windows, macOS, and Linux.

**Can AzCopy copy files with their metadata?**

Yes, AzCopy can preserve file metadata such as last modified time, and it can also copy custom metadata associated with blobs. This is important for maintaining file properties during migrations.

**Is AzCopy free to use?**

Yes, AzCopy is a free utility provided by Microsoft. You only pay for the underlying Azure storage and data transfer costs according to your Azure subscription pricing.

## Summary

AzCopy is an essential command-line utility for any IT professional working with Microsoft Azure. It enables fast, scriptable, and reliable data transfers between local systems and Azure storage, as well as between different Azure storage accounts. Its ability to handle large files through chunked, parallel transfers and to resume interrupted operations makes it far superior to manual uploads through the Azure portal for bulk data movement. For Azure administrators pursuing the AZ-104 certification, mastering AzCopy is critical because it appears directly in exam objectives related to storage management and data migration. You must understand its command syntax, authentication with both SAS tokens and Azure AD, and the use of flags like '--recursive', '--include-pattern', and '--overwrite'. The exam will test your ability to choose AzCopy over similar tools like Storage Explorer or Data Box based on scenario requirements such as automation, scale, and schedule. In real-world IT, AzCopy is a daily tool for migrating data to the cloud, creating backups, synchronising directories, and automating workflows. By learning it thoroughly, you not only prepare for exam success but also gain a practical skill that simplifies cloud storage management.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/azcopy