Microsoft Azure StorageImportExport
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageObject Storageoauth210 EndpointsREST
For Agents
Create and track Azure Import/Export jobs that move terabytes of data between physical disks and Azure Storage.
Use for: I want to create an Azure import job to ship 50 TB of archive data into blob storage, List all active import/export jobs in my subscription, Retrieve the BitLocker keys for a job whose disks were just shipped, Find which Azure regions accept Import/Export disk shipments
Not supported: Does not perform online data transfer, manage storage accounts, or arrange physical shipping — use for Azure Import/Export job lifecycle and BitLocker key retrieval only.
Jentic publishes the only available OpenAPI specification for StorageImportExport, keeping it validated and agent-ready. The Azure Import/Export Resource Provider API drives bulk transfer of data into and out of Azure Blob and File storage by physically shipping disks to and from Azure datacentres. It manages import or export jobs, lists the locations that accept shipments, and returns the BitLocker keys needed to encrypt and decrypt the disks on transit. Use it for terabyte-scale data migrations where network transfer is impractical.
Install Jentic One Beta
Connect the StorageImportExport to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the StorageImportExport, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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 StorageImportExport API.
Create an import job that loads data from shipped disks into Azure Storage
Create an export job that writes blobs onto disks for return shipping
List every import/export job under a subscription or resource group
Retrieve the BitLocker keys needed to encrypt or decrypt a job's disks
Discover the Azure datacentre locations that accept Import/Export shipments
Update job status when the disks are received or returned
List the management operations supported by the Microsoft.ImportExport provider
Use Cases
Patterns agents use StorageImportExport API for, with concrete tasks.
★ Bulk Cloud Migration of Cold Archives
Organisations moving multi-terabyte archives — backup tapes, video libraries, scientific datasets — into Azure cannot rely on internet transfer that would take weeks. StorageImportExport lets a customer create an import job, ship encrypted disks to a designated Azure datacentre, and have the data ingested directly into a target storage account. The API exposes job creation, status polling, and BitLocker key retrieval so an operator can track shipments programmatically end to end.
Create an Azure Import job named 'archive-2026-q1' in resource group 'migration-rg' targeting storage account 'archivecold001' and return the shipping address and BitLocker keys.
Bulk Data Egress for Compliance
Compliance and forensic workflows sometimes require exporting full storage account contents onto physical media for offline review. StorageImportExport supports export jobs that copy specified blob prefixes onto disks shipped back to the customer. Each disk is encrypted with BitLocker; the keys are retrievable through /listBitLockerKeys once the job completes.
Create an export job 'legal-export-2026' in resource group 'compliance-rg' that targets blob prefix 'cases/2025/' and returns BitLocker keys after job completion.
Operations Dashboard for Migration Programmes
Migration teams running parallel Import/Export shipments across many subscriptions need a single dashboard view of in-flight jobs. The list endpoints scoped at subscription and resource group level return every job's state, progress percentage, and target storage account. A nightly aggregator pulls those listings and surfaces blocked or stalled shipments.
List every import/export job in subscription 'migration-platform' and group results by status (Creating, Shipping, Transferring, Completed).
Agent-Initiated Cold Data Transfer via Jentic
An AI agent embedded in a data engineering workflow can spin up Import jobs without learning the ARM JSON contract. Through Jentic, the agent searches for the right StorageImportExport operation, loads its input schema, and submits the create request with disk metadata. Tokens stay in the Jentic vault.
Use Jentic to load the StorageImportExport create-job operation, then create an import job for 12 disks targeting storage account 'genomicsbulk'.
Key Endpoints
10 endpoints — jentic publishes the only available openapi specification for storageimportexport, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/providers/Microsoft.ImportExport/locations
List Azure datacentre locations that accept shipments
GET
/providers/Microsoft.ImportExport/locations/{locationName}
Get a specific Import/Export location
GET
/providers/Microsoft.ImportExport/operations
List operations exposed by the resource provider
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ImportExport/jobs
List jobs in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs
List jobs in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs/{jobName}
Create or update an Import/Export job
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs/{jobName}/listBitLockerKeys
Retrieve BitLocker keys for the job's disks
GET
/providers/Microsoft.ImportExport/locations
List Azure datacentre locations that accept shipments
GET
/providers/Microsoft.ImportExport/locations/{locationName}
Get a specific Import/Export location
GET
/providers/Microsoft.ImportExport/operations
List operations exposed by the resource provider
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ImportExport/jobs
List jobs in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs
List jobs in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs/{jobName}
Create or update an Import/Export job
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs/{jobName}/listBitLockerKeys
Retrieve BitLocker keys for the job's disks
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Agents calling StorageImportExport receive scoped, short-lived bearer tokens at execution time — refresh tokens and tenant secrets never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'create an azure import export job') and Jentic returns the matching StorageImportExport operation with its full input schema, so the agent can submit jobs without reading ARM docs.
Time to first call
Direct integration with Azure Resource Manager — service principal setup, MSAL token handling, drive metadata structures — typically takes 1-2 days. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using StorageImportExport API through Jentic.
Why is there no official OpenAPI spec for StorageImportExport?
Microsoft Azure publishes Swagger fragments for the Microsoft.ImportExport resource provider but does not publish a consolidated, validated OpenAPI 3 spec. Jentic generates and maintains this spec so that AI agents and developers can call StorageImportExport via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the StorageImportExport API use?
All endpoints require Azure Active Directory OAuth 2.0, declared as the azure_auth security scheme with the user_impersonation scope against https://login.microsoftonline.com. Through Jentic, Azure tokens are held in the vault and injected at call time so the agent never sees the raw bearer token.
Can I retrieve the BitLocker keys for shipped disks via this API?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ImportExport/jobs/{jobName}/listBitLockerKeys returns the BitLocker keys for the disks attached to the named job, scoped to your subscription and resource group.
What are the rate limits for the StorageImportExport API?
Calls go through Azure Resource Manager, which throttles writes per subscription (typically 1,200 writes per hour) and reads more generously. Job state transitions are eventually consistent — poll the job GET endpoint rather than retrying create requests.
How do I create an Azure import job through Jentic?
Run pip install jentic, search Jentic for 'create an azure import export job', load the StorageImportExport create-or-update job operation, and execute it with subscriptionId, resourceGroupName, jobName, and the body containing the storage account id, list of drive metadata, and return shipping address. Jentic handles the Azure AD token exchange.
Does this API ship the disks for me?
No. The API only manages the Azure-side job metadata, drive registration, and BitLocker keys. Physical shipping is arranged by you against the Azure datacentre address returned by the location endpoints.
GET STARTED