A family of appliances and solutions for offline data transfer to Azure.
Hi Garrett-2476 & thx for join me at Q&A platform,
week without a shipping update is definitely worth investigating, especially if your previous Data Box orders were dispatched within 1–2 business days.
One important distinction here is that Azure Data Box shipping depends on order processing, device availability, and logistics, not just the time elapsed since the order was submitted.
The usual 1–2 business day turnaround shouldn't be treated as a guaranteed dispatch SLA. Delays can occur if the requested device SKU isn't immediately available, the order requires additional validation, or the fulfillment team encounters a regional shipping constraint.
I'd first check the exact order status under your Data Box resource in the Azure portal. There's a difference between an order that hasn't finished processing and one that's already been processed but is waiting for shipment.
If the order is still showing as Ordered or Processing, that may indicate a provisioning or validation issue. If it's already processed but hasn't moved to Dispatched, I'd be more suspicious of device inventory or logistics.
Also, the absence of a tracking number doesn't necessarily mean something went wrong. Tracking information normally becomes available once the device has actually been dispatched.
At this point, I'd recommend opening an Azure Data Box support request against the existing order, rather than placing another order or waiting indefinitely.
Ask the Data Box fulfillment team to confirm whether the order has passed validation, whether the requested SKU is available in the fulfillment region, and whether there's a shipping hold or an estimated dispatch date.
Include the Data Box order resource ID, Azure region, device SKU, destination country, order creation date, and current portal status. Those details should help the team investigate the fulfillment record directly.
One other thing worth clarifying: Azure Import/Export and Azure Data Box are different services. With Import/Export, customers generally prepare and ship their own disks, while Data Box involves Microsoft shipping a physical appliance. Based on your description, this sounds like a Data Box fulfillment issue rather than an Import/Export job problem.
There's no reliable way to determine the reason for this particular delay from the portal status alone. The fulfillment team needs to check the order internally.
I wouldn't assume the order has been lost or rejected, but after approximately a week without dispatch, requesting a specific status update and estimated shipping date is reasonable.
rgds,
Alex
p.s. if my answer is help - pls mark it as an answer