DataBoxManagementClient

Name: DataBoxManagementClient API
Brand: Data Box Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject Storageoauth216 EndpointsREST

For Agents

Order and track Azure Data Box bulk data-transfer jobs through 16 operations on the Microsoft.DataBox resource provider, including SKU lookup, address validation, job status, and credentials.

Connect the DataBoxManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataBoxManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DataBoxManagementClient API.

List available Data Box SKUs in a region with their capacity and supported transfer types

Validate a shipping address before placing an order to avoid delivery failures

Validate the full input payload (including address and SKU) for a Data Box job

Query region-specific configuration such as supported countries and currency

GET STARTED

Start building with DataBoxManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DataBoxManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for DataBoxManagementClient, keeping it validated and agent-ready. The Azure Data Box management API exposes 16 operations across 13 paths to order, track, and manage Data Box jobs that physically ship petabyte-scale data into and out of Azure. Use it to validate shipping addresses and inputs, list available SKUs in a region, place an order, monitor the job through ordering, shipping, processing, and delivery, and download credentials when the device arrives on site.

Use Cases

Patterns agents use DataBoxManagementClient API for, with concrete tasks.

★ Bulk Data Migration to Azure

Move tens to hundreds of terabytes from on-premises storage into Azure by ordering a Data Box. The flow is: validate address, validate inputs, list SKUs to confirm capacity, place the order, track shipment, copy data on site once delivered, and ship the device back. The management API automates every step except the physical data copy. Total cycle is typically 7-21 days, dominated by transit and copy time.

Validate the shipping address for resource group 'rg-migrate', list SKUs available in westeurope, and place a Data Box order named 'migration-q3' for 80 TB

Multi-Site Migration Tracking

Run multiple Data Box jobs in parallel for branch offices or partner sites, and track them centrally. Listing jobs at the subscription level returns each job's current state and ETA, so an operations dashboard can show which devices are en route, on site, or back at the Azure datacentre. Cancellation is supported until the job ships.

List all Data Box jobs in subscription /subscriptions/{id}, group them by status, and return the count of jobs in each state

Validation Before Order Placement

Use the validation endpoints to catch problems early — bad postcodes, unsupported countries, SKUs out of stock, or insufficient capacity. Service_ValidateAddress confirms the address is reachable, Service_ValidateInputs confirms the full payload is acceptable, and Service_RegionConfiguration confirms the destination country and currency. Calling these first prevents failed orders that would otherwise need manual intervention.

Call Service_ValidateAddress for the proposed shipping address, then Service_ValidateInputs with the full Data Box order payload, and only place the order if both return Valid

AI Agent Migration Coordinator

An AI agent supporting an infrastructure team can orchestrate Data Box migrations through Jentic. The agent searches by intent ('order an azure data box'), Jentic returns the Jobs_Create operation with its schema, and the agent executes the call with managed Azure credentials. The same flow handles status tracking and cancellation, freeing engineers from portal-based order management.

Search Jentic for 'place an Azure Data Box order', load the Jobs_Create schema, validate the address and inputs first, then execute Jobs_Create with the user-supplied parameters

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for databoxmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/jobs

List all Data Box jobs in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/availableSkus

List available Data Box SKUs in a region

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/validateAddress

Validate a shipping address for a Data Box order

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/validateInputs

Validate the full input payload of a Data Box order

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBox/jobs/{jobName}

Delete (cancel) a Data Box job

GET

/providers/Microsoft.DataBox/operations

List Microsoft.DataBox provider operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/jobs

List all Data Box jobs in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/availableSkus

List available Data Box SKUs in a region

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/validateAddress

Validate a shipping address for a Data Box order

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataBox/locations/{location}/validateInputs

Validate the full input payload of a Data Box order

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBox/jobs/{jobName}

Delete (cancel) a Data Box job

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure service principal credentials are encrypted in the Jentic vault. Agents receive scoped ARM bearer tokens at execution time and never see the underlying client secret.

Intent-based discovery

Agents search by intent ('order an Azure Data Box' or 'list data box jobs') and Jentic returns the matching operation, avoiding the need to learn the 16 endpoints under Microsoft.DataBox.

Time to first call

Direct ARM integration: half a day for AAD app registration, MSAL token handling, and Data Box payload modelling. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Data Box Edge Management

Persistent edge compute device versus a one-time bulk transfer Data Box job.

Choose Data Box Edge for ongoing edge presence; choose Data Box for one-shot bulk migration.

Complementary

Storage Management

Provision the destination storage account that a Data Box copies data into.

Use Storage Management to set up the target Azure Storage account before placing a Data Box order.

Alternative

Storage Import Export

BYOD-disk import/export service for smaller transfers than a Data Box.

Choose Import/Export for terabyte-scale transfers using your own disks; choose Data Box for petabyte-scale managed devices.

FAQs

Specific to using DataBoxManagementClient API through Jentic.

Why is there no official OpenAPI spec for DataBoxManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataBoxManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Data Box management API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Contributor or a custom role with Microsoft.DataBox/* permissions on the resource group. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.

Can I cancel a Data Box order through this API?

Yes. Send DELETE to /subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DataBox/jobs/{jobName} while the order is still cancellable (typically before it ships). Once the device is in transit cancellation is no longer permitted by the service.

What are the rate limits for the Data Box management API?

Azure Resource Manager applies subscription-level read and write throttling (around 1,200 requests per hour). Long-running operations such as job creation return 202 Accepted with an Azure-AsyncOperation header that you poll for completion.

How do I order a Data Box through Jentic?

Run pip install jentic and search for 'place an azure data box order'. Jentic returns the Jobs_Create operation; load its schema and execute it after first validating the address with Service_ValidateAddress and the full payload with Service_ValidateInputs.

Does this API copy my data onto the device?

No. The API orchestrates ordering, status, and credentials only. The actual data copy happens on site after the device is delivered, typically using SMB or NFS to mount the device and standard file copy or robocopy.