Study guide

12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

Key Takeaways Explain This Topic AI

Estimate transfer time (data size divided by effective bandwidth) before choosing a tool; Microsoft treats roughly 40 TB as the tipping point favoring Data Box over network transfer

AzCopy is the default online tool for Blob Storage/Azure Files, with resume-on-failure, one-way sync mode, and tunable parallelism

Data Box Heavy is retired; current offline options are Data Box Disk (35 TB), Data Box classic (80 TB, being phased out), and Data Box Next Gen (120 TB or 525 TB)

Storage Migration Service uniquely preserves full file-server identity -- SMB shares, NTFS ACLs, DFS Namespace references, and server name -- via its cutover step

Azure File Sync is an ongoing hybrid-tiering pattern, not a one-time migration tool -- don't substitute it for Storage Migration Service or Data Box

Last updated: July 2026

Why This Topic Matters

The final Migrations bullet is "Recommend a solution for migrating unstructured data." Unstructured data — file shares, media archives, backup sets, blobs — is often the largest single dataset in a migration, and the deciding factor is rarely a feature gap; it's math : how long would this actually take to move over your available network, and can the business tolerate that?

The Core Calculation

Approximate transfer time with:

Transfer time ≈ Data size ÷ (available bandwidth × real-world efficiency)

A rough rule of thumb Microsoft itself uses in Data Box guidance: Azure Data Box is "ideally suited to transfer data sizes larger than 40 TB in scenarios with no to limited network connectivity." Below that threshold, or with strong bandwidth, an online tool is usually simpler and cheaper.

AzCopy: The Default Online Tool

AzCopy is a command-line utility for high-throughput copying to and from Azure Blob Storage and Azure Files . Key capabilities:

Resume on failure — interrupted transfers pick up where they left off instead of restarting.

Sync mode — one-way mirroring of a source to a destination, useful for incremental transfers after an initial bulk seed.

Tunable parallelism and SAS-token authentication for scripted, automatable transfers.

AzCopy is the right call whenever the dataset is small enough (well under the ~40 TB Data Box threshold, or larger but with ample dedicated bandwidth) to move over the network within the business's acceptable window.

Azure Data Box Family: Offline Transfer

When available bandwidth makes an online transfer impractical or unacceptably slow, ship a physical appliance instead:

  • Device Usable Capacity Status (2026) Best For
  • Data Box Disk Up to 35 TB (up to 5 disks) Current Small-to-medium one-time transfers, branch offices

Data Box (classic) 80 TB Being phased out region-by-region as Next Gen rolls out Mid-size single-appliance transfers where Next Gen isn't yet available

  • Data Box Next Gen (SKU 1) 120 TB Current Mid-to-large transfers, faster NVMe-based copy
  • Data Box Next Gen (SKU 2) 525 TB Current Very large single-appliance transfers
  • Data Box Heavy ~770 TB Retired — no longer orderable N/A (superseded by Data Box Next Gen)

Exam trap: older material still names Data Box Heavy as the answer for petabyte-scale migrations. As of 2026, Data Box Heavy is retired; the equivalent (and larger) scale is now covered by the Data Box Next Gen 525 TB SKU , or multiple Data Box units shipped in parallel for even bigger estates.

Storage Migration Service: Full File-Server Migration

Storage Migration Service (a Windows Server feature, managed through Windows Admin Center) is purpose-built for migrating an entire Windows file server — not just the files, but the SMB share configuration, NTFS permissions/ACLs, DFS Namespace references, and even the server's identity . Its distinguishing capability is the cutover step : after data transfer, the new server (an Azure VM, or a server registered with Azure File Sync) can assume the old server's name, so client machines and applications keep using the same \\server\share paths with zero reconfiguration. Plain copy tools like AzCopy or robocopy move file content and can preserve many ACLs, but they do not perform this identity cutover — that gap is exactly why Storage Migration Service exists as a distinct recommendation from AzCopy.

Azure File Sync is a related but different service worth disambiguating here: it is an ongoing hybrid caching/tiering pattern (on-premises servers keep a locally-cached namespace of an Azure file share, with cold data tiered to the cloud), not a one-time migration tool. A scenario asking for continuous hybrid access after migration may layer Azure File Sync on top of a completed Storage Migration Service or Data Box move — but by itself it does not answer a "how do we migrate" question.

Exam Scenarios

A media company must move 600 TB of video archives to Azure Blob Storage (Archive tier) but has only a 100 Mbps dedicated line. At that bandwidth, transferring 600 TB would take many weeks even at full utilization — the correct recommendation is Azure Data Box Next Gen (525 TB SKU) , potentially with a second unit run in parallel, not AzCopy.

A company is decommissioning two Windows Server 2012 R2 file servers holding 40 shares with complex NTFS ACLs, and end users must keep using the exact same share paths after the move. The correct tool is Storage Migration Service , because it performs the ACL-preserving transfer and the server-identity cutover that a manual file copy cannot replicate.

Key Takeaways

Estimate transfer time (data size ÷ effective bandwidth) before choosing a tool; Microsoft's own guidance treats ~40 TB as the point where Data Box beats network transfer.

AzCopy is the default online tool for Blob Storage/Azure Files with resume, sync mode, and scriptable parallelism.

Data Box Heavy is retired; current large-scale offline transfer options are Data Box Disk (35 TB), Data Box classic (80 TB, being phased out), and Data Box Next Gen (120 TB or 525 TB).

Storage Migration Service is the only tool here that preserves full file-server identity (SMB shares, ACLs, DFS-N, server name) via its cutover step — pick it whenever share paths must stay unchanged for end users.

Azure File Sync is an ongoing hybrid-tiering pattern, not a one-time migration tool; don't confuse it with Storage Migration Service.