Document Details

Storage Import Export Data To Files
Home / Scan #2 / Storage Import Export Data To Files
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily biased toward Windows environments. All prerequisites, setup, and tooling (WAImportExport.exe) are Windows-only. Instructions for preparing drives, running the import tool, and even enabling long paths are specific to Windows. No Linux or macOS equivalents, tools, or examples are provided. The only cross-platform sections are the Azure CLI and PowerShell examples for creating jobs, but the core data preparation workflow is Windows-exclusive.
Recommendations
  • Clearly state at the beginning that the Import/Export tool and workflow are only supported on Windows, if that is the case. If Linux/macOS support is planned, provide a roadmap or alternatives.
  • If partial Linux support exists (e.g., for job creation via CLI), clarify which steps can be done from Linux and which require Windows.
  • If possible, develop and document a Linux-compatible version of the WAImportExport tool, or provide guidance for Linux users (e.g., using a Windows VM, Docker container, or Azure-hosted VM for the preparation steps).
  • Add explicit notes or callouts for Linux/macOS users about the lack of support and any available workarounds.
  • Where possible, provide Linux shell command equivalents for Azure CLI and job management steps, even if the core data preparation remains Windows-only.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-14 00:00 #250 in_progress Biased Biased
2026-01-13 00:00 #246 completed Biased Biased
2026-01-11 00:00 #240 completed Biased Biased
2026-01-10 00:00 #237 completed Biased Biased
2026-01-09 00:34 #234 completed Biased Biased
2026-01-08 00:53 #231 completed Biased Biased
2026-01-06 18:15 #225 cancelled Clean Clean
2025-08-17 00:01 #83 cancelled Clean Clean
2025-07-13 21:37 #48 completed Clean Clean
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-09 13:09 #3 cancelled Clean Clean
2025-07-08 04:23 #2 cancelled Biased Biased

Flagged Code Snippets

1. To get a list of the locations to which you can ship disks, use the [Get-AzImportExportLocation](/powershell/module/az.importexport/get-azimportexportlocation) cmdlet:

   
1. To update your job or cancel your job, run the [Update-AzImportExport](/powershell/module/az.importexport/update-azimportexport) cmdlet:

   
           BasePath,DstItemPathOrPrefix,ItemType
           "F:\MyFolder1\MyFile1.txt","MyAzureFileshare1/MyFile1.txt",file
       
           "F:\MyFolder2\","MyAzureFileshare1/",file
       
           "F:\MyFolder1\MyFile1.txt","MyAzureFileshare1/MyFile1.txt",file
           "F:\MyFolder2\","MyAzureFileshare1/",file
       
       DriveLetter,FormatOption,SilentOrPromptOnFormat,Encryption,ExistingBitLockerKey
       H,Format,SilentMode,Encrypt,
       
       DriveLetter,FormatOption,SilentOrPromptOnFormat,Encryption,ExistingBitLockerKey
       G,AlreadyFormatted,SilentMode,AlreadyEncrypted,060456-014509-132033-080300-252615-584177-672089-411631
       
    .\WAImportExport.exe PrepImport /j:<JournalFile> /id:<SessionId> [/logdir:<LogDirectory>] [/silentmode] [/InitialDriveSet:<driveset.csv>]/DataSet:<dataset.csv>
    
    .\WAImportExport.exe PrepImport /j:JournalTest.jrn /id:session#1 /InitialDriveSet:driveset.csv /DataSet:dataset.csv /logdir:C:\logs
    
    az import-export create \
        --resource-group myierg \
        --name MyIEjob1 \
        --location "West US" \
        --backup-drive-manifest true \
        --diagnostics-path waimportexport \
        --drive-list bit-locker-key=439675-460165-128202-905124-487224-524332-851649-442187 \
            drive-header-hash= drive-id=AZ31BGB1 manifest-file=\\DriveManifest.xml \
            manifest-hash=69512026C1E8D4401816A2E5B8D7420D \
        --type Import \
        --log-level Verbose \
        --shipping-information recipient-name="Microsoft Azure Import/Export Service" \
            street-address1="3020 Coronado" city="Santa Clara" state-or-province=CA postal-code=98054 \
            country-or-region=USA phone=4083527600 \
        --return-address recipient-name="Gus Poland" street-address1="1020 Enterprise way" \
            city=Sunnyvale country-or-region=USA state-or-province=CA postal-code=94089 \
            email=gus@contoso.com phone=4085555555" \
        --return-shipping carrier-name=FedEx carrier-account-number=123456789 \
        --storage-account myssdocsstorage
    
### Create a job

1. You can use an existing resource group or create one. To create a resource group, run the [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup) cmdlet:

   
1. You can use an existing storage account or create one. To create a storage account, run the [New-AzStorageAccount](/powershell/module/az.storage/new-azstorageaccount) cmdlet:

   
1. Use the `Get-AzImportExportLocation` cmdlet with the `Name` parameter to get locations for your region:

   
1. Run the following [New-AzImportExport](/powershell/module/az.importexport/new-azimportexport) example to create an import job:

   
   > [!TIP]
   > Instead of specifying an email address for a single user, provide a group email to ensure that you receive notifications even if an admin leaves.

1. Use the [Get-AzImportExport](/powershell/module/az.importexport/get-azimportexport) cmdlet to see all the jobs for the myierg resource group: