Creating an import job for the Azure Import/Export service
Creating an import job for the Microsoft Azure Import/Export service using the REST API involves the following steps:
Preparing drives with the Azure Import/Export Tool.
Obtaining the location to which to ship the drive.
Creating the import job.
Shipping the drives to Microsoft via a supported carrier service.
Updating the import job with the shipping details.
See Using the Microsoft Azure Import/Export service to Transfer Data to Blob Storage for an overview of the Import/Export service and a tutorial that demonstrates how to use the Azure portal to create and manage import and export jobs.
Preparing drives with the Azure Import/Export Tool
The steps to prepare drives for an import job are the same whether you create the job via the portal or via the REST API.
Preparing your drive involves:
Identifying the data to be imported.
Identifying the destination blobs in Windows Azure Storage.
Using the Azure Import/Export Tool to copy your data to one or more hard drives.
The Azure Import/Export Tool will also generate a manifest file for each of the drives as it is prepared. A manifest file contains:
An enumeration of all the files intended for upload and the mappings from these files to blobs.
Checksums of the segments of each file.
Information about the metadata and properties to associate with each blob.
A listing of the action to take if a blob that is being uploaded has the same name as an existing blob in the container. Possible options are: a) overwrite the blob with the file, b) keep the existing blob and skip uploading the file, c) append a suffix to the name so that it does not conflict with other files.
Obtaining your shipping location
Before creating an import job, you need to obtain a shipping location name and address by calling the List Locations operation.
List Locations will return a list of locations and their mailing addresses. You can select a location from the returned list and ship your hard drives to that address. You can also use the
Get Location operation to obtain the shipping address for a specific location directly.
Follow the steps below to obtain the shipping location:
Identify the name of the location of your storage account. This value can be found under the Location field on the storage account's Dashboard in the Azure portal or queried for by using the service management API operation Get Storage Account Properties.
Retrieve the location that is available to process this storage account by calling the
AlternateLocationsproperty of the location contains the location itself, then it is okay to use this location. Otherwise, call the
Get Locationoperation again with one of the alternate locations. The original location might be temporarily closed for maintenance.
Creating the import job
To create the import job, call the Put Job operation. You will need to provide the following information:
A name for the job.
The storage account name.
The shipping location name, obtained from the previous step.
A job type (Import).
The return address where the drives should be sent after the import job has completed.
The list of drives in the job. For each drive, you must include the following information that was obtained during the drive preparation step:
The drive Id
The BitLocker key
The manifest file relative path on the hard drive
The Base16 encoded manifest file MD5 hash
Shipping your drives
You must ship your drives to the address that you obtained from the previous step, and you must provide the Import/Export service with the tracking number of the package.
You must ship your drives via a supported carrier service, which will provide a tracking number for your package.
Updating the import job with your shipping information
After you have your tracking number, call the Update Job Properties operation to update the shipping carrier name, the tracking number for the job, and the carrier account number for return shipping. You can optionally specify the number of drives and the shipping date as well.
Deleting personal information
This article provides steps for how to delete personal data from the device or service and can be used to support your obligations under the GDPR. If you’re looking for general info about GDPR, see the GDPR section of the Service Trust portal.
Personal information is relevant to the import/export service (via the portal and API) during import and export operations. Data used during these processes include:
- Contact name
- Phone number
- Street address
- Zip/postal code
- Drive ID
- Carrier account number
- Shipping tracking number
When an import/export job is created, users provide contact information and a shipping address. Personal information is stored in up to two different locations: in the job and optionally in the portal settings. Personal information is only stored in portal settings if you check the checkbox labeled, Save carrier and return address as default during the Return shipping info section of the export process.
Personal contact information may be deleted in the following ways:
Data saved with the job is deleted with the job. Users can delete jobs manually and completed jobs are automatically deleted after 90 days. You can manually delete the jobs via the REST API or the Azure portal. To delete the job in the Azure portal, go to your import/export job, and click Delete from the command bar. For details on how to delete an import/export job via REST API, refer to Delete an import/export job.
Contact information saved in the portal settings may be removed by deleting the portal settings. You can delete portal settings by following these steps:
- Sign in to the Azure portal.
- Click on the Settings icon
- Click Export all settings (to save your current settings to a
- Click Delete all settings and private dashboards to delete all settings including saved contact information.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.