Import Export

14
Total Pages
2
Linux-Friendly Pages
12
Pages with Bias
85.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

97 issues found
Showing 26-50 of 97 flagged pages
Import Export Using Azure Import/Export to transfer data to and from Azure Storage | Microsoft Docs ...rticles/import-export/storage-import-export-service.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Import/Export demonstrates a strong Windows bias. The only supported tool for preparing and encrypting disk drives (WAImportExport) is explicitly stated to be compatible only with 64-bit Windows operating systems, with no Linux or macOS alternatives or examples provided. All instructions and workflows assume access to Windows and Windows-specific technologies (BitLocker). There is no mention of cross-platform or Linux-compatible tooling, nor are there examples or guidance for users on non-Windows systems.
Recommendations
  • Develop and document a cross-platform (Linux/macOS) alternative to the WAImportExport tool, or provide guidance for Linux users on how to prepare and encrypt drives for Azure Import/Export.
  • Include explicit examples and workflows for Linux users, such as using Linux-native disk encryption tools (e.g., LUKS) and how to ensure compatibility with Azure Import/Export requirements.
  • Clarify any limitations or workarounds for non-Windows users in the requirements section, and provide links to relevant resources or community solutions.
  • Consider supporting BitLocker unlocking and drive preparation on Linux via open-source tools (e.g., dislocker) and document these steps.
  • Ensure parity in documentation by presenting Linux/macOS options alongside Windows instructions, rather than only after or not at all.
GitHub Create Pull Request
Import Export Repairing an Azure Import/Export export job - v1 | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-export-job-v1.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the 'Microsoft Azure Import/Export Tool' as a Windows executable (WAImportExport.exe), with all command-line examples using Windows-style paths (e.g., C:\, G:\) and no mention of Linux-compatible tools, commands, or usage patterns. The copy log and manifest file examples use Windows file paths and terminology ('Windows Azure Import/Export service'), and there are no Linux or cross-platform alternatives or instructions provided.
Recommendations
  • Provide explicit information about platform compatibility for the Import/Export Tool (e.g., is there a Linux version or alternative?).
  • Include Linux command-line examples, using Linux path conventions (e.g., /mnt/exportdrive/).
  • Mention any cross-platform or open-source alternatives if the official tool is Windows-only.
  • Clarify whether the log and manifest files can be processed or validated using Linux tools (e.g., Python scripts, Azure CLI, or REST API).
  • Add a section addressing Linux users, including troubleshooting steps and any required dependencies or workarounds.
GitHub Create Pull Request
Import Export Repairing an Azure Import/Export import job - v1 | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-import-job-v1.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exclusively references the Windows Azure Import/Export Tool (WAImportExport.exe), provides only Windows-style command-line examples (with Windows paths and drive letters), and does not mention or provide any Linux equivalents, alternatives, or examples. All file paths and usage scenarios assume a Windows environment, and there is no guidance for users on Linux or other platforms.
Recommendations
  • Explicitly state platform support for the Import/Export Tool, including whether Linux or macOS are supported.
  • If Linux is supported, provide equivalent Linux command-line examples using Linux path syntax (e.g., /home/bob/Pictures) and usage patterns.
  • Mention any Linux-compatible tools or alternatives, or clarify if the tool is Windows-only.
  • Add a section addressing cross-platform usage, including any prerequisites or limitations for non-Windows users.
  • If the tool is Windows-only, suggest workarounds for Linux users (e.g., using a Windows VM, Docker container, or Azure Portal alternatives).
GitHub Create Pull Request
Import Export Repairing an Azure Import/Export export job - v1 | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-export-job-v1.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the 'Microsoft Azure Import/Export Tool' as a Windows executable (WAImportExport.exe), with all command-line examples using Windows paths and conventions (e.g., C:\, G:\). There are no Linux or cross-platform usage instructions, nor any mention of Linux-compatible alternatives or usage patterns. The documentation refers to the service as 'Windows Azure Import/Export' in several places, reinforcing a Windows-centric approach.
Recommendations
  • Clarify whether the Import/Export Tool is available for Linux or provide information about Linux alternatives if available.
  • Include Linux command-line examples (e.g., using /mnt/exportdrive, forward slashes, and Linux shell syntax) if the tool is cross-platform.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If the tool is Windows-only, suggest workarounds for Linux users (such as using a Windows VM or container) and provide links to relevant resources.
  • Avoid using 'Windows Azure' as a service name unless historically necessary; use 'Microsoft Azure' for consistency.
GitHub Create Pull Request
Import Export Setting Up the Azure Import/Export Tool v1 | Microsoft Docs ...s/import-export/storage-import-export-tool-setup-v1.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric: all prerequisites, examples, and tool requirements are specific to Windows environments (Windows OS, BitLocker, .NET Framework). There are no mentions of Linux support, alternatives, or examples, and all usage scenarios assume Windows tools and conventions.
Recommendations
  • Explicitly state whether the tool is Windows-only or provide information about Linux compatibility.
  • If Linux is supported, add installation and usage instructions for Linux, including equivalent commands and prerequisites.
  • Mention Linux alternatives for drive encryption (e.g., LUKS) and clarify if BitLocker is mandatory or if other encryption methods are supported.
  • Provide example commands using Linux paths and conventions.
  • If the tool is not supported on Linux, suggest alternative workflows or tools for Linux users.
GitHub Create Pull Request
Import Export Tutorial to export data from Azure Blob storage with Azure Import/Export | Microsoft Docs ...import-export/storage-import-export-data-from-blobs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias in several ways: it relies heavily on Windows-specific tools (e.g., WAImportExport.exe for unlocking BitLocker-encrypted drives), provides detailed PowerShell examples, and omits Linux-specific instructions or alternatives for critical steps such as unlocking disks. The use of BitLocker and WAImportExport.exe assumes a Windows environment, and there is no mention of Linux-compatible methods or cross-platform alternatives. Additionally, Windows tools and patterns are introduced before any consideration of Linux workflows.
Recommendations
  • Provide Linux-compatible instructions for unlocking BitLocker-encrypted drives, such as using dislocker or other open-source tools.
  • Include examples using bash scripts or Linux command-line utilities where applicable, especially for tasks like drive unlocking and log verification.
  • Explicitly mention cross-platform alternatives to WAImportExport.exe and clarify any platform limitations.
  • Ensure parity in CLI examples by showing how Azure CLI commands can be run on Linux and MacOS, not just Windows.
  • Add a section addressing common issues or differences when performing these tasks on Linux systems.
GitHub Create Pull Request
Import Export Tutorial to transfer data to Azure Files with Azure Import/Export | Microsoft Docs ...s/import-export/storage-import-export-data-to-files.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a strong Windows bias. All prerequisites and examples for preparing drives and running the WAImportExport tool require a Windows system and Windows-specific tools (NTFS, BitLocker, WAImportExport.exe). There are no instructions or examples for performing these steps on Linux or macOS, nor is there mention of Linux-compatible tooling or file systems. The documentation assumes the user has access to and is familiar with Windows environments, leaving Linux users without guidance.
Recommendations
  • Provide explicit guidance for Linux users, including supported scenarios and limitations.
  • If the WAImportExport tool is Windows-only, state this clearly and offer alternative approaches for Linux users (e.g., using Azure CLI, PowerShell Core, or other cross-platform tools where possible).
  • Include Linux-specific prerequisites and examples, such as preparing disks with ext4 or other Linux file systems, and handling encryption with Linux-native tools.
  • If BitLocker or NTFS is required, explain how Linux users can prepare disks (e.g., using third-party utilities or mounting NTFS volumes).
  • Clarify whether the import/export process can be initiated or managed from Linux using Azure CLI or REST APIs, and provide sample commands.
  • Add a section comparing Windows and Linux workflows, highlighting any differences or limitations.
GitHub Create Pull Request
Import Export Use the Azure portal to configure customer-managed keys for Import/Export service ...-export/storage-import-export-encryption-key-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell for key vault recovery before mentioning Azure CLI, and by providing links and troubleshooting steps that prioritize or exclusively mention PowerShell commands. There are no explicit Linux or cross-platform command examples, and the guidance assumes use of the Azure portal, which is platform-agnostic but does not address parity for Linux users who may prefer CLI or automation. Troubleshooting steps reference PowerShell modules and commands without equivalent Bash/CLI examples.
Recommendations
  • Provide equivalent Azure CLI (bash) commands alongside PowerShell examples for all key vault management and recovery operations.
  • Ensure that troubleshooting steps include both PowerShell and Azure CLI solutions, with clear instructions for Linux/macOS users.
  • Avoid listing Windows/PowerShell tools or instructions before their cross-platform alternatives; present both together or alternate order.
  • Include explicit notes or sections for Linux users, highlighting any differences or additional steps required when using CLI or automation.
  • Review all linked articles to ensure Linux parity and add references to CLI documentation where only PowerShell is currently mentioned.
GitHub Create Pull Request
Import Export Requirements for Azure Import/Export service | Microsoft Docs ...es/import-export/storage-import-export-requirements.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure Import/Export service demonstrates a strong Windows bias. All operating system requirements and examples are Windows-only, with explicit references to Windows versions and Windows Server. The required software section only mentions .NET Framework and BitLocker, both Windows technologies. Disk preparation instructions exclusively use PowerShell commands, with no Linux alternatives or mention of Linux-compatible tools. There is no guidance for users on Linux or macOS, nor any mention of cross-platform support for the WAImportExport tool.
Recommendations
  • Add explicit information about Linux and macOS support or limitations for the WAImportExport tool.
  • If Linux is unsupported, state this clearly and suggest alternatives (e.g., AzCopy) for Linux users.
  • Provide Linux equivalents for disk sector size checks (e.g., using 'lsblk', 'fdisk -l', or 'blockdev --getss').
  • Mention cross-platform tools and workflows where possible, and clarify which steps are Windows-specific.
  • Include a table or section comparing Windows and Linux/macOS requirements and procedures for Azure Import/Export.
GitHub Create Pull Request
Import Export Tutorial to import data to Azure Blob Storage with Azure Import/Export service | Microsoft Docs ...s/import-export/storage-import-export-data-to-blobs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits significant Windows bias. All prerequisites and drive preparation steps require a Windows system, BitLocker (Windows-only), and the WAImportExport tool (Windows executable). All examples for preparing disks, unlocking drives, and running the import/export tool are Windows-centric, with no mention of Linux or cross-platform alternatives. Command-line examples are exclusively for Windows CMD/PowerShell, and there is no guidance for Linux users on how to participate in the import/export workflow.
Recommendations
  • Explicitly state platform limitations in the prerequisites section, clarifying that the Import/Export tool and workflow are currently Windows-only.
  • If possible, provide or reference Linux-compatible tooling or workflows for disk preparation, encryption, and data copying (e.g., using LUKS for encryption, NTFS support on Linux, and alternative copy tools).
  • Offer guidance for Linux users on how to prepare disks for import, including any supported cross-platform methods or workarounds.
  • Add a note about future plans for Linux support or alternative workflows, if available.
  • Where PowerShell or CMD commands are given, provide equivalent bash or shell commands if feasible, or explain why they are not possible.
  • Highlight any Azure CLI steps that can be performed from Linux, and clarify which steps require Windows.
GitHub Create Pull Request
Import Export Check number of drives needed for an export with Azure Import/Export | Microsoft Docs ...t/storage-import-export-determine-drives-for-export.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively targets Windows users, requiring the Azure Import/Export tool to be run on Windows, and all examples use Windows paths and PowerShell/command prompt syntax. There is no mention of Linux support, alternatives, or equivalent commands, and the prerequisite explicitly states a Windows system is required.
Recommendations
  • Clarify whether the Import/Export tool is available or supported on Linux or macOS. If not, state this limitation explicitly.
  • If possible, provide or develop a cross-platform version of the Import/Export tool, or document alternative workflows for Linux users.
  • Include Linux-specific instructions and examples, such as using bash or Linux file paths, if the tool becomes available for Linux.
  • Mention any Linux-compatible tools or scripts that can help estimate drive requirements, or provide guidance for Linux users on how to prepare blob lists and interact with the REST API.
  • Consider reordering content so platform requirements are stated up front and alternatives (if any) are discussed.
GitHub Create Pull Request
Import Export Using Azure Import/Export to transfer data to and from Azure Storage | Microsoft Docs ...rticles/import-export/storage-import-export-service.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Azure Import/Export service demonstrates a Windows bias by exclusively referencing the WAImportExport tool, which is only compatible with 64-bit Windows operating systems. There are no examples, instructions, or alternative tools provided for Linux or macOS users. The documentation also prioritizes Windows compatibility information and BitLocker (a Windows-centric encryption technology) without mentioning cross-platform alternatives or parity.
Recommendations
  • Provide Linux and macOS alternatives for the WAImportExport tool, or document equivalent workflows for these platforms.
  • Include explicit instructions or examples for performing import/export operations from Linux systems, such as using open-source disk imaging and encryption tools.
  • Mention cross-platform encryption options (e.g., VeraCrypt, LUKS) and how they could be used in place of BitLocker for non-Windows environments.
  • Clarify any limitations for non-Windows users and suggest supported workarounds or third-party tools.
  • Ensure that OS compatibility information is presented in a neutral, cross-platform manner, rather than focusing on Windows first.
GitHub Create Pull Request
Import Export Repairing an Azure Import/Export import job - v1 | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-import-job-v1.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (WAImportExport.exe), using Windows-style paths (C:\...), and providing only Windows command-line examples. There is no mention of Linux equivalents, cross-platform usage, or PowerShell alternatives, nor are Linux file paths or shell commands shown.
Recommendations
  • Add explicit information about Linux support or limitations for the Azure Import/Export Tool.
  • Provide Linux command-line examples (e.g., using mono or dotnet if the tool is cross-platform, or note if it is Windows-only).
  • Include Linux-style file paths (e.g., /home/bob/Pictures) in examples alongside Windows paths.
  • Clarify whether the tool can be run on Linux, and if not, suggest alternative workflows for Linux users.
  • Mention any prerequisites or compatibility notes for non-Windows environments.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-import-job-v1.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-import-job-v1.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses Windows-centric tools (WAImportExport.exe), Windows-style file paths (e.g., C:\Users\bob\Pictures), and does not mention or provide examples for Linux or cross-platform usage. There are no Linux file path examples, no mention of running the tool on Linux, and no alternative instructions for non-Windows environments.
Recommendations
  • Clarify whether the Azure Import/Export Tool is available for Linux or only for Windows. If it is Windows-only, explicitly state this early in the documentation.
  • If a Linux version or alternative exists (e.g., via .NET Core, Mono, or a cross-platform CLI), provide equivalent Linux command-line examples using Linux-style paths (e.g., /home/bob/Pictures).
  • If the tool can be run under Wine or in a Windows VM/container on Linux, provide guidance for Linux users.
  • Where possible, use neutral or dual-path examples (Windows and Linux) to illustrate usage.
  • Mention any platform-specific prerequisites or limitations, so Linux users are aware of their options.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-data-from-blobs.md ...import-export/storage-import-export-data-from-blobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The disk unlocking step exclusively references the WAImportExport.exe tool and provides only Windows command-line examples for unlocking BitLocker-encrypted drives, with no mention of Linux alternatives. The PowerShell section is detailed and presented alongside Azure CLI, but there are no Linux-specific instructions for handling BitLocker disks or for using the WAImportExport tool. The documentation assumes the use of Windows tools and patterns for critical steps, such as disk unlocking and log verification, and does not provide parity for Linux users.
Recommendations
  • Add instructions and examples for unlocking BitLocker-encrypted drives on Linux, such as using dislocker or cryptsetup.
  • Mention and provide download links for cross-platform tools where available, or alternatives for Linux/Mac users.
  • Clarify whether the WAImportExport tool is Windows-only and suggest Linux-compatible workflows for verifying data and logs.
  • Ensure that CLI examples are not Windows-centric (e.g., avoid drive letters, provide Linux path formats where relevant).
  • Explicitly state OS requirements and limitations for each step, and provide guidance for Linux users throughout the process.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-data-to-files.md ...s/import-export/storage-import-export-data-to-files.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows. All prerequisites, setup steps, and examples for preparing drives and running the WAImportExport tool require a Windows system. Only Windows-specific tools (WAImportExport.exe) and patterns (NTFS, BitLocker, drive letters) are described. There are no Linux equivalents or examples, and Linux is not mentioned as a supported platform for the import/export workflow.
Recommendations
  • Explicitly state platform limitations and clarify if Linux is unsupported, or provide guidance for Linux users if possible.
  • If feasible, offer a Linux-compatible version of the WAImportExport tool, or document alternative workflows for Linux environments.
  • Include Linux-specific instructions for disk preparation (e.g., using ext4, mounting disks, encrypting with LUKS), and provide command-line examples for Linux.
  • Mention cross-platform file system compatibility issues and how to address them when preparing disks on Linux.
  • Add a section comparing Windows and Linux workflows, or at least acknowledge the lack of Linux support and suggest workarounds.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-data-to-blobs.md ...s/import-export/storage-import-export-data-to-blobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All prerequisites, drive preparation steps, and tooling (BitLocker, WAImportExport tool) are Windows-only, with no mention of Linux or macOS support. Command-line examples for drive preparation use Windows tools and PowerShell, and there is no guidance for performing these steps on Linux. Even file system requirements (NTFS, BitLocker) are Windows-centric, and enabling long paths is discussed only for Windows clients.
Recommendations
  • Clearly state if the Azure Import/Export tool and process are Windows-only, or provide guidance for Linux/macOS users if supported.
  • If Linux is supported, add equivalent instructions for preparing disks (e.g., using LUKS for encryption, ext4/xfs file systems, mounting and copying data) and provide Linux command-line examples.
  • Mention alternative disk encryption and file system options for non-Windows platforms, or clarify limitations.
  • Include troubleshooting and best practices for Linux users, such as handling long file paths and drive unlocking.
  • If the WAImportExport tool is not available for Linux, suggest alternative workflows or explicitly state the lack of support.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-determine-drives-for-export.md ...t/storage-import-export-determine-drives-for-export.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively describes usage of the Azure Import/Export tool on Windows, requiring a Windows system and providing only Windows/Powershell command-line examples. There is no mention of Linux support, alternatives, or equivalent instructions for Linux users. The tool appears to be Windows-only, and all paths and commands use Windows conventions.
Recommendations
  • Clarify whether the Azure Import/Export tool is available for Linux or if there are alternative methods for Linux users.
  • If a Linux version or equivalent exists, provide installation and usage instructions for Linux, including example commands using bash or other common Linux shells.
  • If the tool is Windows-only, explicitly state this limitation and suggest workarounds for Linux users, such as using a Windows VM or container.
  • Include file path examples using Linux conventions (e.g., /home/user/waimportexportv1) alongside Windows examples.
  • Mention any cross-platform compatibility considerations, and provide guidance for users working in mixed-OS environments.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-requirements.md ...es/import-export/storage-import-export-requirements.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Import/Export service is heavily Windows-centric. All OS requirements, software prerequisites, and disk preparation instructions reference Windows versions and tools (BitLocker, .NET Framework, PowerShell). There are no Linux or macOS equivalents mentioned, nor are there examples or instructions for preparing disks on non-Windows platforms. The WAImportExport tool and BitLocker are both Windows-only, and disk sector size checks are shown only with PowerShell commands.
Recommendations
  • Clarify whether the WAImportExport tool is available or supported on Linux/macOS, and if not, state this explicitly.
  • Provide instructions or alternative tooling for preparing disks on Linux (e.g., using cryptsetup for encryption, fdisk/lsblk for sector size checks).
  • Include Linux/macOS examples for checking disk sector size and formatting disks.
  • Mention cross-platform alternatives for disk encryption and preparation if available.
  • Add a section on limitations for non-Windows users and suggest workarounds or supported scenarios.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-setup-v1.md ...s/import-export/storage-import-export-tool-setup-v1.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric. All prerequisites, instructions, and examples assume a Windows environment (Windows OS, BitLocker, .NET Framework, drive letters, WAImportExport.exe). There are no references to Linux or cross-platform usage, nor are Linux equivalents or alternatives mentioned. The tool appears to be Windows-only, and the documentation does not acknowledge or guide Linux users.
Recommendations
  • Explicitly state platform support and limitations at the beginning of the documentation.
  • If the tool is Windows-only, recommend or link to alternative workflows or tools for Linux users (e.g., Azure CLI, REST API, or third-party utilities).
  • Provide guidance for Linux users on how to prepare drives for Azure Import/Export, including any supported cross-platform methods.
  • If possible, develop and document a cross-platform version of the tool or provide containerized solutions.
  • Mention BitLocker alternatives for Linux (such as LUKS) and clarify compatibility with Azure Import/Export.
  • Add a FAQ or troubleshooting section for non-Windows environments.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-encryption-key-portal.md ...-export/storage-import-export-encryption-key-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a Windows bias by referencing PowerShell and Windows-centric tools first or exclusively, especially in the prerequisites and troubleshooting sections. For example, enabling soft-delete and undoing key removal are described with PowerShell links, while Linux/CLI alternatives are mentioned second or not at all. There are no explicit Linux command examples, and the troubleshooting steps reference PowerShell modules without Bash or CLI equivalents.
Recommendations
  • Provide Azure CLI and Bash examples alongside or before PowerShell instructions for all key management and recovery steps.
  • Reference Linux-compatible tools and workflows explicitly, ensuring parity in troubleshooting and configuration guidance.
  • Where PowerShell modules are mentioned (e.g., Undo Key vault key removal), include equivalent Azure CLI commands or REST API instructions.
  • Review all linked articles to ensure Linux users are not directed to Windows-only documentation.
  • Add explicit notes or sections for Linux/macOS users to clarify cross-platform support and steps.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-service.md ...rticles/import-export/storage-import-export-service.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Azure Import/Export service demonstrates a clear Windows bias. The only supported tool for preparing and encrypting drives (WAImportExport) is explicitly limited to 64-bit Windows operating systems, with no mention of Linux or macOS alternatives. All instructions and workflows assume use of Windows-specific technologies (BitLocker, WAImportExport), and there are no examples or guidance for Linux users. This creates a barrier for users on non-Windows platforms and prioritizes Windows tooling and patterns throughout.
Recommendations
  • Provide a cross-platform alternative to the WAImportExport tool, or document how Linux/macOS users can prepare drives for import/export jobs.
  • Include examples and workflows for Linux users, such as using open-source encryption tools (e.g., VeraCrypt, LUKS) and drive preparation steps.
  • Clearly state platform limitations at the beginning of the documentation and offer guidance or workarounds for non-Windows environments.
  • If BitLocker is required, document how Linux users can interact with BitLocker-encrypted drives (e.g., using dislocker or similar tools).
  • Consider developing and supporting a native Linux/macOS version of the WAImportExport tool to ensure parity.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-export-job-v1.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-repairing-an-export-job-v1.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exclusively references the 'Microsoft Azure Import/Export Tool' as a Windows executable (WAImportExport.exe), provides only Windows-style command-line examples (e.g., C:\ paths, .exe usage), and refers to 'Windows Azure Import/Export service' throughout. There are no Linux or cross-platform tool alternatives, nor are there Linux-specific usage examples or instructions.
Recommendations
  • Clarify whether the Azure Import/Export Tool is available for Linux or provide alternative cross-platform tools if available.
  • Include Linux command-line examples (e.g., using /mnt/G or ~/WAImportExport/ paths) if the tool is supported on Linux, or document equivalent Linux workflows.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If only Windows is supported, suggest workarounds for Linux users (such as using a Windows VM or container).
  • Consider providing PowerShell and Bash script examples side by side for parity.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-data-from-blobs.md ...import-export/storage-import-export-data-from-blobs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools (WAImportExport.exe) for unlocking disks, providing detailed PowerShell instructions, and omitting Linux-native methods for drive unlocking and verification. The only tool for unlocking BitLocker-encrypted disks is a Windows executable, with no mention of Linux alternatives (e.g., dislocker). All command-line examples for job creation and management use Azure CLI and PowerShell, but the critical post-export step (unlocking disks) is Windows-only. There are no Linux shell or tool examples for handling exported drives, and the documentation does not address Linux users' needs for BitLocker decryption or log verification.
Recommendations
  • Add instructions for unlocking BitLocker-encrypted drives on Linux using tools such as dislocker, including example commands.
  • Provide parity in post-export steps by including Linux shell commands for verifying data integrity and reviewing logs.
  • Explicitly mention cross-platform compatibility for all steps, or note any limitations for non-Windows users.
  • If WAImportExport.exe is required, clarify its platform limitations and offer alternatives or workarounds for Linux/macOS.
  • Consider reordering or balancing examples so that Linux methods are presented alongside or before Windows-specific ones where possible.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-encryption-key-portal.md ...-export/storage-import-export-encryption-key-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and Windows-centric tools first or exclusively, especially in enabling soft-delete and key recovery scenarios. There is a lack of parity in Linux-focused examples, such as Bash/CLI commands, and no mention of Linux-specific workflows or troubleshooting steps. The troubleshooting section references PowerShell cmdlets for key recovery, but does not provide equivalent Azure CLI or REST API instructions, which are more platform-neutral.
Recommendations
  • Provide Azure CLI and REST API examples alongside PowerShell for all key management and recovery operations.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
  • Add troubleshooting instructions using Azure CLI and/or REST API for key and vault recovery, not just PowerShell.
  • Ensure that links to enabling soft-delete and purge protection include both PowerShell and CLI sections, and reference them equally.
  • Include sample commands for Linux/macOS users where command-line interaction is described.
  • Review screenshots and UI instructions to ensure they do not assume Windows-only environments.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →