| title | description | services | author | ms.service | ms.subservice | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|
Microsoft Azure Data Box system requirements| Microsoft Docs |
Learn about important system requirements for your Azure Data Box and for clients that connect to the Data Box. |
databox |
alkohli |
databox |
pod |
article |
10/07/2021 |
alkohli |
This article describes important system requirements for your Microsoft Azure Data Box and for clients that connect to the Data Box. We recommend you review the information carefully before you deploy your Data Box and then refer to it when you need to during deployment and operation.
The system requirements include:
- Software requirements: For hosts that connect to the Data Box, describes supported operating systems, file transfer protocols, storage accounts, storage types, and browsers for the local web UI.
- Networking requirements: For the Data Box, describes requirements for network connections and ports for best operation of the Data Box.
The software requirements include supported operating systems, file transfer protocols, storage accounts, storage types, and browsers for the local web UI.
[!INCLUDE data-box-supported-os-clients]
[!INCLUDE data-box-supported-file-systems-clients]
Important
Connection to Data Box shares is not supported via REST for export orders.
[!INCLUDE data-box-supported-storage-accounts]
[!INCLUDE data-box-supported-storage-types]
[!INCLUDE data-box-supported-web-browsers]
Your datacenter needs to have high-speed network. We strongly recommend you have at least one 10-GbE connection. If a 10-GbE connection isn't available, you can use a 1-GbE data link to copy data, but the copy speeds are affected.
The following table lists the ports that need to be opened in your firewall to allow for SMB or NFS traffic. In this table, In (inbound) refers to the direction from which incoming client requests access to your device. Out (or outbound) refers to the direction in which your Data Box device sends data externally, beyond the deployment. For example, data might be outbound to the Internet.
[!INCLUDE data-box-port-requirements]