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 51-75 of 97 flagged pages
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Windows-based WAImportExport.exe tool, provides only Windows-style command-line examples (with Windows paths and drive letters), and does not mention or provide instructions for Linux or cross-platform usage. All file paths and usage patterns assume a Windows environment, with no Linux equivalents or parity.
Recommendations
  • Clarify whether the Azure Import/Export Tool is available for Linux or provide alternatives if it is not.
  • If a Linux version or cross-platform tool exists, include equivalent Linux command-line examples and file path formats.
  • Explicitly state OS requirements and provide guidance for Linux users (e.g., using Wine, or alternative workflows).
  • Ensure documentation does not assume Windows-only environments by using more neutral language (e.g., 'your system' instead of 'C:\Users\...').
  • If the tool is Windows-only, suggest workarounds or reference Azure CLI/PowerShell cross-platform commands where possible.
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-08 00:53
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), provides only Windows-style command-line examples (with Windows file paths and drive letters), and mentions 'Windows Azure Import/Export service' repeatedly. There are no Linux equivalents, cross-platform alternatives, or Linux-specific instructions/examples provided.
Recommendations
  • Clarify whether the Import/Export Tool is available for Linux or provide information about cross-platform alternatives.
  • If a Linux version or method exists, add Linux-specific command-line examples (using Linux paths, e.g., /mnt/exportdrive/).
  • Explicitly state OS requirements and limitations at the beginning of the documentation.
  • If only Windows is supported, suggest workarounds for Linux users (e.g., using a Windows VM or container).
  • Consider mentioning Azure CLI or REST API alternatives if relevant and available for Linux environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All instructions, examples, and tooling are exclusively for Windows, specifically referencing PowerShell and Windows command-line usage. There is no mention of Linux or macOS support, nor are alternative instructions or examples provided for non-Windows platforms. The Azure Import/Export tool is described as requiring a Windows system, and all paths and commands use Windows conventions.
Recommendations
  • Clarify whether the Azure Import/Export tool is available for Linux or macOS, and if so, provide installation and usage instructions for those platforms.
  • If the tool is Windows-only, explicitly state this limitation early in the documentation and suggest alternatives or workarounds for Linux users (e.g., using a Windows VM or container).
  • Provide equivalent command-line examples for Linux (bash) if possible, or note the lack of support.
  • Include information about file path conventions and administrative privilege requirements for non-Windows systems, if applicable.
  • Consider developing or documenting cross-platform tools or APIs for this workflow to improve accessibility.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, requiring Windows OS and BitLocker, referencing only Windows-specific tools and patterns, and providing examples exclusively in Windows context. There is no mention of Linux support, alternatives, or parity in prerequisites, installation, or usage examples.
Recommendations
  • Explicitly state OS support and limitations; if Linux is unsupported, clarify this early.
  • If Linux support is possible, provide equivalent Linux prerequisites, such as supported distributions, required packages, and disk encryption alternatives (e.g., LUKS).
  • Offer Linux command-line examples and usage patterns alongside Windows examples.
  • Reference cross-platform tools or provide guidance for Linux users on how to prepare drives for Azure Import/Export.
  • If the tool is Windows-only, suggest alternative workflows for Linux users, such as using Azure Storage REST APIs or other supported import/export mechanisms.
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-08 00:53
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 tooling instructions require a Windows system, specifically referencing NTFS volumes, BitLocker encryption, and the WAImportExport.exe tool, which is only available for Windows. There are no Linux or macOS equivalents or examples for preparing drives, running the import/export tool, or handling encryption. The documentation assumes the user has access to a Windows environment and does not mention cross-platform alternatives.
Recommendations
  • Provide explicit statements about platform support, including whether Linux/macOS are supported or not.
  • If possible, develop and document Linux/macOS versions of the WAImportExport tool, or provide alternative workflows for non-Windows users.
  • Include Linux-specific instructions for preparing disks (e.g., using ext4/xfs, LUKS encryption, mounting, and CSV file preparation).
  • Offer guidance for users who only have access to Linux or macOS, such as using a VM or cloud-hosted Windows environment, or alternative Azure data transfer services.
  • Clearly indicate any limitations or requirements for NTFS and BitLocker, and suggest cross-platform compatible options if available.
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-08 00:53
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 stated to be compatible only with 64-bit Windows operating systems. There are no Linux or macOS alternatives or examples provided, nor is there guidance for users on non-Windows platforms. Windows-specific technologies (BitLocker) are referenced without mention of cross-platform equivalents or workarounds. The documentation introduces Windows requirements before discussing any general process, reinforcing the Windows-first approach.
Recommendations
  • Provide guidance or alternatives for Linux and macOS users, such as recommending third-party tools or manual steps for drive preparation and encryption.
  • Document any possible workarounds for non-Windows environments, or clarify if the service is fundamentally Windows-only.
  • Include explicit examples or instructions for Linux users, even if limited (e.g., how to mount drives, encrypt with Linux-native tools, or prepare journal files).
  • If possible, develop and support a cross-platform version of the WAImportExport tool.
  • Clearly state platform limitations at the beginning of the documentation and suggest options for users who do not have access to Windows.
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-08 00:53
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 displays a strong Windows bias. All examples and requirements are focused exclusively on Windows operating systems and tools, such as BitLocker, .NET Framework, and PowerShell commands. There is no mention of Linux support, alternatives, or equivalent tooling, and all instructions and supported platforms are Windows-centric.
Recommendations
  • Explicitly state whether Linux is supported or not for the WAImportExport tool and disk preparation. If not supported, clarify this limitation.
  • If Linux support is possible, provide equivalent instructions for preparing disks on Linux, including recommended tools (e.g., cryptsetup for encryption, fdisk/lsblk for disk info).
  • Include Linux-compatible examples for checking disk sector size and formatting disks.
  • Mention Linux file system compatibility (e.g., NTFS support on Linux, or alternatives if possible).
  • If BitLocker is required and not available on Linux, suggest cross-platform alternatives or clarify the requirement.
  • Provide parity in documentation structure, listing Linux requirements and steps alongside Windows, not just after.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a strong Windows bias. All prerequisites and disk preparation steps require a Windows system, BitLocker (Windows-only), and the WAImportExport tool (Windows executable). There are no instructions or examples for Linux or macOS users, nor mention of cross-platform alternatives. Command-line examples for disk preparation use Windows tools (manage-bde, PowerShell), and the only supported workflow is via Windows. While Azure CLI and PowerShell examples are provided for job creation, the core data import workflow is Windows-centric.
Recommendations
  • Explicitly state Windows-only requirements at the start and clarify lack of Linux/macOS support.
  • If possible, provide or reference cross-platform alternatives for disk encryption and preparation (e.g., Linux-compatible tools, BitLocker alternatives, or WAImportExport support for Linux).
  • Offer guidance for Linux/macOS users, such as using a Windows VM or Azure Virtual Machine for disk preparation.
  • Add a FAQ or troubleshooting section for non-Windows users.
  • Monitor and document any future support for Linux/macOS in the Import/Export tooling.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All prerequisites, setup steps, and tooling (BitLocker, NTFS, WAImportExport tool) are Windows-specific. There are no instructions or examples for Linux or macOS users, and all command-line examples for disk preparation and encryption use Windows tools (manage-bde, BitLocker, PowerShell). The only cross-platform section is the Azure CLI, but it is only used for job creation, not for disk preparation or encryption.
Recommendations
  • Clearly state at the beginning if the Azure Import/Export tool and workflow are only supported on Windows, and if so, explain why.
  • If Linux or macOS support is possible, provide equivalent instructions for preparing disks, encrypting with open-source tools (e.g., LUKS/dm-crypt), and copying data.
  • Mention and document any cross-platform alternatives or limitations explicitly.
  • If only Windows is supported, suggest workarounds for Linux users (e.g., using a Windows VM or container for disk preparation).
  • Add a table or section comparing Windows and Linux/macOS support for each step, so users can quickly see platform requirements.
  • For Azure CLI and PowerShell sections, clarify which steps are platform-agnostic and which require Windows.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-reviewing-job-status-v1.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-reviewing-job-status-v1.md
High Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Error Codes Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-specific error codes (e.g., 'UploadErrorWin32', Win32 error codes 267 and 123) and terminology. There are no examples or references to Linux-specific errors, file system behaviors, or tools. The documentation does not provide Linux-oriented troubleshooting steps or mention how logs/errors might differ on Linux systems.
Recommendations
  • Include examples of errors and error codes that may be encountered on Linux systems, such as common Linux file system errors.
  • Clarify whether 'UploadErrorWin32' and related error codes are relevant only to Windows-formatted drives, and provide equivalent Linux error scenarios if applicable.
  • Add troubleshooting guidance for Linux users, including how to interpret logs and error messages on Linux.
  • Mention any differences in log formats or error handling between Windows and Linux environments.
  • If tools or commands are referenced (e.g., for viewing logs), provide both Windows (PowerShell, File Explorer) and Linux (bash, ls, cat) examples.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows. All prerequisites, tool requirements, and usage examples are specific to Windows environments (e.g., requiring Windows 7 or newer, .NET Framework, BitLocker, and drive letters). There are no mentions of Linux or cross-platform alternatives, and all command-line examples use Windows paths and conventions.
Recommendations
  • Clearly state in the introduction whether the tool is Windows-only, or provide Linux/macOS support if available.
  • If a Linux version or alternative exists, include equivalent installation and usage instructions for Linux.
  • Provide Linux-specific examples, including command-line syntax, file paths, and prerequisites (e.g., required packages, mounting drives).
  • Mention Linux-compatible encryption tools if BitLocker is not available, or provide guidance for preparing drives on Linux.
  • If the tool is not supported on Linux, suggest alternative workflows for Linux users or clarify the limitation explicitly.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a strong Windows bias by exclusively referencing the WAImportExport tool, which is only available for 64-bit Windows operating systems. There are no Linux or macOS alternatives or examples provided, and the documentation does not mention any cross-platform tools or workflows. The use of BitLocker (a Windows-centric encryption technology) is also emphasized without discussion of Linux-compatible options. This effectively excludes Linux users from using the Import/Export service directly.
Recommendations
  • Provide or reference a cross-platform (Linux/macOS) version of the WAImportExport tool, or document alternative workflows for non-Windows users.
  • Include explicit guidance or examples for Linux users, such as how to prepare drives, encrypt data, and interact with the Import/Export service from Linux systems.
  • Mention any third-party or open-source tools that can be used on Linux for similar purposes, if available.
  • If BitLocker is required, document how Linux users can interact with BitLocker-encrypted drives (e.g., using dislocker or similar tools), or provide alternative encryption options.
  • Clearly state the platform limitations at the beginning of the documentation and provide links to feature requests or feedback channels for non-Windows support.
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: 2025-08-17 00:01
Reviewed by: Unknown
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 before CLI in the prerequisites for enabling soft-delete and purge protection, and by linking to a PowerShell-specific recovery command in the troubleshooting section. There are no explicit Linux or cross-platform command-line examples, and the documentation assumes use of the Azure Portal UI, which is platform-agnostic but does not address command-line parity for Linux users.
Recommendations
  • When referencing enabling soft-delete and purge protection, list CLI instructions before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • In troubleshooting sections, provide both PowerShell and Azure CLI (or REST API) equivalents for recovery operations, such as undoing key removal.
  • Include explicit Azure CLI examples for all key management operations, ensuring Linux users have clear, first-class guidance.
  • Where possible, provide bash shell script snippets or note any OS-specific considerations for Linux users.
  • Review all linked articles to ensure Linux and cross-platform parity is maintained throughout the documentation journey.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Powershell Heavy Windows First
Summary
The documentation exhibits a Windows bias by exclusively referencing and providing examples for Windows-specific tools (e.g., WAImportExport.exe, BitLocker, PowerShell), omitting Linux equivalents or instructions. The disk unlocking and verification steps are Windows-centric, and there is no mention of how to perform these actions on Linux or macOS. PowerShell is given a dedicated section, and the only disk-unlock command provided is for a Windows executable, with no cross-platform alternatives.
Recommendations
  • Provide instructions and examples for unlocking BitLocker-encrypted drives on Linux (e.g., using dislocker or cryptsetup) and macOS.
  • Include Linux/macOS command-line examples for verifying data transfer and reading logs.
  • Mention and document any cross-platform tools or third-party utilities that can be used in place of WAImportExport.exe.
  • Clearly indicate platform-specific requirements and offer parity in guidance for non-Windows users.
  • Where PowerShell is referenced, also provide Bash or shell script equivalents for Linux/macOS environments.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references and provides examples for the Windows-based WAImportExport.exe tool, with all command-line examples using Windows file paths and syntax. There is no mention of Linux or cross-platform alternatives, nor are there any Linux-specific instructions or examples. The documentation refers to the tool as 'Microsoft Azure Import/Export Tool' but only demonstrates usage in a Windows context, and the tool's name and file paths reinforce this bias.
Recommendations
  • Explicitly state whether the Azure Import/Export Tool is available for Linux or provide alternatives if it is not.
  • If a Linux version or equivalent CLI exists, provide parallel Linux command-line examples using Linux file paths and syntax.
  • If the tool is Windows-only, clearly mention this limitation at the beginning of the documentation.
  • Consider referencing or linking to cross-platform tools or scripts (e.g., Azure CLI, PowerShell Core, or REST API usage) that can be used for similar repair/validation tasks on Linux.
  • Ensure documentation parity by including troubleshooting or workflow guidance for users on non-Windows platforms.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows: it requires the use of a Windows system, only provides Windows command-line and PowerShell examples, and references a Windows-only executable tool. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives.
Recommendations
  • Clearly state in the prerequisites if the tool is Windows-only, and if so, explain why.
  • If possible, provide or reference a cross-platform version of the Azure Import/Export tool, or suggest alternatives for Linux/macOS users.
  • Include Linux (bash) and macOS terminal examples if the tool or equivalent functionality is available.
  • If the tool is not available for Linux/macOS, suggest using a Windows VM or container as a workaround, and provide guidance for those platforms.
  • Consider advocating for or developing a cross-platform version of the tool to ensure parity.
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: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Import/Export service demonstrates a strong Windows bias. All operating system requirements, software prerequisites, and usage instructions are exclusively focused on Windows platforms. Only Windows and Windows Server are listed as supported OSes, with no mention of Linux or macOS. Required tools and commands (e.g., PowerShell, .NET Framework, BitLocker) are Windows-specific, and all example commands use PowerShell. There are no Linux equivalents or guidance for non-Windows users.
Recommendations
  • Explicitly state whether Linux and macOS are supported or unsupported for the WAImportExport tool and the Import/Export process.
  • If Linux/macOS are unsupported, provide a clear rationale and suggest alternative workflows for non-Windows users.
  • If partial support exists, document any available Linux-compatible tools or methods (e.g., using AzCopy, third-party BitLocker-compatible utilities, or mounting NTFS drives).
  • Include example commands for checking disk sector size and preparing disks on Linux (e.g., using lsblk, fdisk, or hdparm).
  • Mention cross-platform alternatives for required software (e.g., .NET Core, open-source disk encryption tools) where possible.
  • Ensure that documentation for related tools (like AzCopy) includes parity in examples and instructions for Linux and macOS.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a strong Windows bias by requiring the use of the WAImportExport tool, which is explicitly stated to be compatible only with 64-bit Windows operating systems. There are no Linux or cross-platform alternatives mentioned, nor are there any Linux-specific instructions or examples. The documentation also references BitLocker (a Windows-native encryption technology) as the only supported encryption method, further reinforcing the Windows-centric approach.
Recommendations
  • Provide or reference a cross-platform (Linux/macOS) version of the WAImportExport tool, or offer equivalent functionality via a platform-agnostic tool or script.
  • Include Linux-specific instructions and examples for preparing drives, copying data, and handling encryption/decryption.
  • If BitLocker is required, document supported methods for unlocking BitLocker-encrypted drives on Linux (e.g., using dislocker or similar tools), and provide step-by-step guidance.
  • Clearly state any limitations for non-Windows users and suggest workarounds or alternatives where possible.
  • Consider supporting open, cross-platform encryption standards in addition to BitLocker to improve accessibility for Linux users.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows tools (WAImportExport.exe), Windows-style paths (e.g., C:\Users\bob\Pictures), and does not provide any Linux or cross-platform examples. All command-line examples use Windows syntax, and there is no mention of Linux equivalents or usage on non-Windows systems.
Recommendations
  • Provide equivalent Linux command-line examples, using Linux-style paths (e.g., /home/bob/Pictures) and syntax.
  • Clarify whether the Azure Import/Export Tool is available for Linux, and if not, mention any alternatives or workarounds for Linux users.
  • If the tool is Windows-only, explicitly state this limitation early in the documentation.
  • Include guidance for accessing and manipulating log and path map files on Linux systems, if supported.
  • Ensure that any file path or environment variable references are shown in both Windows and Linux formats where applicable.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Windows-based 'WAImportExport.exe' tool, provides only Windows-style command-line examples (with Windows file paths and drive letters), and does not mention or provide instructions for Linux or cross-platform usage. There is no discussion of Linux equivalents, compatibility, or alternative tooling, and all examples and terminology are Windows-centric.
Recommendations
  • Explicitly state whether the Azure Import/Export Tool is available for Linux or cross-platform environments. If not, clarify this limitation early in the documentation.
  • If a Linux version or alternative exists (such as a .NET Core or Python-based tool), provide equivalent Linux command-line examples, using Linux-style paths and conventions.
  • If only Windows is supported, suggest workarounds for Linux users (e.g., using a Windows VM, Docker container, or Azure Cloud Shell).
  • Avoid using 'Windows Azure' in tool/service names unless it is the official name; prefer 'Azure' for neutrality.
  • Add a section addressing platform compatibility and any known issues or requirements for non-Windows users.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows. All instructions, examples, and tooling are exclusively for Windows, specifically referencing PowerShell, Windows command-line, and a Windows-only executable (WAImportExport.exe). There are no Linux or cross-platform instructions, nor any mention of Linux support or alternatives.
Recommendations
  • Clearly state if the Azure Import/Export tool is Windows-only, and if so, provide guidance for Linux users (e.g., using a Windows VM, Docker container, or alternative workflows).
  • If possible, provide a Linux-compatible version of the tool or a cross-platform alternative, and include equivalent Linux command-line examples.
  • Explicitly mention the lack of Linux support early in the prerequisites, to set expectations for non-Windows users.
  • If the tool can be run under Wine or similar compatibility layers, document and test this as an option for Linux users.
  • Where possible, use platform-agnostic language and examples, or provide parallel instructions for both Windows and Linux environments.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All prerequisites, tooling, and step-by-step instructions assume or require a Windows system. Only Windows tools (BitLocker, manage-bde, WAImportExport.exe) are mentioned, and all example commands are for Windows command line or PowerShell. There are no Linux or macOS equivalents, nor any mention of cross-platform alternatives. The documentation does not address how users on non-Windows systems can participate in the import/export process.
Recommendations
  • Explicitly state early in the documentation that the Azure Import/Export tool and workflow are Windows-only, if that is the case, and provide rationale.
  • If possible, provide or reference Linux/macOS-compatible tools or workflows, or clarify their absence and suggest alternatives (such as using a Windows VM or Azure VM for preparation).
  • Include a section addressing Linux/macOS users, outlining any supported approaches or workarounds.
  • If future cross-platform support is planned, mention this and provide a feedback channel for interested users.
  • Where possible, use neutral language (e.g., 'on your system' instead of 'on your Windows system') and avoid assuming the user is on Windows unless strictly necessary.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use Windows paths and the WAImportExport.exe tool, which is a Windows executable. There is no mention of Linux or cross-platform usage, no Linux shell or path examples, and no guidance for users on non-Windows systems. The documentation refers to 'Windows Azure Import/Export service' and uses Windows-centric terminology throughout.
Recommendations
  • Clarify whether the Azure Import/Export Tool is available for Linux or provide alternatives if it is not.
  • If a Linux version exists, include equivalent Linux shell command examples (e.g., using ./WAImportExport or mono).
  • Use cross-platform path examples or explicitly show both Windows (C:\path) and Linux (/home/user/path) formats.
  • Mention any prerequisites or limitations for Linux users, such as needing Wine or Mono to run the tool, or alternative tools/scripts.
  • Update terminology to refer to 'Azure Import/Export service' instead of 'Windows Azure Import/Export service' to avoid platform-specific branding.
  • Add a section or note for Linux/macOS users explaining their options for repairing export jobs.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Only Windows operating systems are listed as supported, and all software requirements (e.g., .NET Framework, BitLocker) are Windows-specific. Disk preparation instructions and examples exclusively use Windows PowerShell commands, with no mention of Linux or macOS alternatives. There is no guidance for users on non-Windows platforms, nor are cross-platform tools or workflows discussed.
Recommendations
  • Clearly state if the Import/Export tool is Windows-only, and if so, explain the rationale and any planned Linux/macOS support.
  • If possible, provide equivalent instructions and supported tools for Linux (e.g., using Linux-native disk preparation and encryption tools such as cryptsetup or LUKS).
  • Include Linux/macOS examples for checking disk sector size (e.g., using 'lsblk', 'fdisk -l', or 'blockdev --getss').
  • Mention cross-platform alternatives to BitLocker and .NET Framework, or clarify their necessity.
  • If Linux is not supported, add a prominent note at the top of the page to inform users and suggest workarounds or alternatives 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-reviewing-job-status-v1.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-reviewing-job-status-v1.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Error Codes Windows Terms
Summary
The documentation page exhibits subtle Windows bias, primarily through the use of Windows-specific error codes (e.g., Win32 errors), error categories (e.g., UploadErrorWin32), and terminology that references Windows file system behaviors. There are no explicit PowerShell commands or Windows-only instructions, but Linux equivalents for error codes, file system errors, or troubleshooting patterns are not mentioned. The documentation assumes familiarity with Windows error codes and does not provide Linux-specific guidance or examples.
Recommendations
  • When referencing error codes such as Win32 errors (e.g., Error 267, Error 123), provide context or mapping for Linux users, such as equivalent errno codes or typical Linux file system errors.
  • Include examples or notes on how to interpret and troubleshoot logs on Linux systems, especially for file system errors that may manifest differently.
  • Avoid using Windows-centric terms like 'Win32' exclusively; if the service can be used with Linux disks or environments, clarify how errors would appear or be resolved on those platforms.
  • Add troubleshooting steps or log review examples that are relevant to Linux users, such as using Linux tools to inspect drives or parse logs.
  • If certain errors or behaviors are unique to Windows-formatted drives, explicitly state this and provide Linux-specific caveats or instructions.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →