This chapter covers Azure Data Box, a physical, offline data-transfer service. AZ-900 tests this under objective 2.4, as an alternative to network-based transfer tools like AzCopy for very large datasets.
Jump to a section
A simple way to picture Azure Data Box
Emailing a small file is instant, but shipping an entire archive of files on a physical hard drive is sometimes faster and more practical than waiting for a massive upload over a home internet connection. Azure Data Box applies that same idea at a larger scale: Microsoft ships a secure physical storage device to an organization, which loads it with data and ships it back, rather than transferring an enormous dataset over the network.
What Azure Data Box is
Azure Data Box is a service that provides a secure physical storage device, shipped by Microsoft to an organization's location. The organization loads their data onto the device locally, then ships it back to Microsoft, who uploads the data into Azure storage.
Why use physical shipping instead of network transfer
For very large datasets, transferring data over a network connection can take an impractically long time, depending on available bandwidth. Physically shipping a device carrying the data can be faster and more predictable than a lengthy network transfer, especially where network bandwidth is limited.
When it's a good fit
Data Box is most relevant for large-scale, one-time data migrations (like an initial bulk migration to Azure) or for locations with limited network connectivity — not for ongoing, everyday data transfer, which is better served by network-based options like AzCopy.
Relationship to other transfer tools
Data Box complements, rather than replaces, network-based tools. Organizations often use AzCopy or Storage Explorer for smaller, ongoing transfers, and reserve Data Box specifically for large, one-time bulk transfers where physical shipping is genuinely faster than the network alternative.
Assess whether physical transfer makes sense
For very large datasets or limited network bandwidth, compare the time a network transfer would take against physical shipping.
Request a Data Box device
Microsoft ships a secure physical storage device to the organization.
Load data locally
The organization copies its data onto the device using their local network, avoiding the internet transfer bottleneck.
Ship the device back
The device is shipped back to Microsoft, who uploads the data into the organization's Azure storage.
A company with a massive on-premises archive and limited internet bandwidth uses Azure Data Box for its initial bulk migration to Azure, since shipping a physical device is faster and more predictable than attempting to upload the entire archive over their available network connection.
Objective 2.4 expects recognition of Azure Data Box as a physical, offline data-transfer option, distinct from network-based tools like AzCopy.
A common wrong answer is assuming all Azure data transfer happens over the network — Data Box specifically exists for scenarios where physical shipping is a better fit than network transfer.
Stable terms: Azure Data Box. Memory trick: Data Box = physical device shipped to you, loaded locally, shipped back — for large, one-time transfers where network transfer would be impractically slow.
Azure Data Box provides a secure physical storage device for large-scale, offline data transfer into Azure.
It's most relevant for large, one-time migrations or locations with limited network bandwidth.
It complements network-based tools like AzCopy, rather than replacing them for everyday transfers.
Mistake
All Azure data transfer must happen over a network connection.
Correct
Azure Data Box offers a physical, offline alternative for large-scale data transfer, useful when network transfer would be impractically slow or bandwidth is limited.
It's a service providing a secure physical storage device, shipped by Microsoft to an organization, loaded locally with data, and shipped back for upload into Azure storage — an offline alternative to network-based data transfer for large datasets.
Data Box fits large-scale, one-time transfers where network transfer would take impractically long, or where bandwidth is limited. AzCopy suits smaller, ongoing, or scripted transfers over the network.
You've just covered Azure Data Box — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?