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 76-97 of 97 flagged pages
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong 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, with no Linux or macOS alternatives or workarounds mentioned. All instructions and workflows assume access to Windows tools and environments, and there are no examples or guidance for users on Linux or other platforms.
Recommendations
  • Develop and document a cross-platform (Linux/macOS) version of the WAImportExport tool, or provide alternative workflows for non-Windows users.
  • If a cross-platform tool is not available, clearly state this limitation at the top of the documentation and suggest supported alternatives (such as using a Windows VM or container) for Linux/macOS users.
  • Include explicit Linux/macOS parity notes and, where possible, provide example commands or scripts for those platforms.
  • Consider supporting open-source or platform-agnostic encryption and drive preparation tools, and document how they can be used in the Import/Export workflow.
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-07-12 23:44
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 environments. All prerequisites, instructions, and examples assume the use of Windows operating systems and tools (e.g., BitLocker, .NET Framework, drive letters, WAImportExport.exe). There is no mention of Linux or cross-platform support, nor are there any examples or guidance for Linux users.
Recommendations
  • Clearly state whether the Azure Import/Export Tool is supported on Linux. If not, mention this limitation explicitly at the beginning.
  • If Linux support exists (or is planned), provide equivalent installation and usage instructions for Linux, including command-line examples and any required dependencies.
  • Offer alternatives or workarounds for Linux users, such as using a Windows VM or container, and document the process.
  • Where possible, use platform-agnostic language (e.g., 'mount point' instead of 'drive letter') and provide examples for both Windows and Linux.
  • Mention Linux-compatible encryption and file system tools if BitLocker is not available.
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use Windows-style paths (e.g., C:\Users\...), and only the Windows executable (WAImportExport.exe) is referenced. There are no Linux or cross-platform examples, nor is there mention of running the tool on Linux or using Linux paths. The documentation assumes a Windows environment throughout, both in tool usage and file path conventions.
Recommendations
  • Provide equivalent Linux command-line examples, using Linux-style paths (e.g., /home/bob/Pictures).
  • Clarify whether the WAImportExport tool is available and supported on Linux, or provide alternatives if not.
  • If the tool is Windows-only, explicitly state this limitation at the start of the documentation.
  • Include instructions or workarounds for Linux users, such as using Wine or a VM, if applicable.
  • Where possible, use platform-agnostic language and examples, or present both Windows and Linux variants side by side.
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-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias in several ways: it provides detailed PowerShell examples, references to the WAImportExport.exe tool (a Windows executable), and BitLocker (a Windows encryption technology) for unlocking disks. There are no Linux or cross-platform alternatives or examples for unlocking disks or handling BitLocker-encrypted drives. The unlock instructions and tooling are Windows-centric, and Linux users are not given guidance or parity in the workflow.
Recommendations
  • Provide Linux-compatible instructions and tooling for unlocking BitLocker-encrypted drives, such as using dislocker or cryptsetup with BitLocker support.
  • Include example commands for unlocking disks on Linux and macOS, not just Windows.
  • Mention cross-platform tools and workflows wherever possible, or clearly state platform limitations.
  • If the WAImportExport tool is Windows-only, explicitly state this and suggest alternatives or workarounds for Linux users.
  • Ensure parity in log verification steps by describing how to access and interpret logs on non-Windows systems.
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: 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 and preparation steps require a Windows system, and only Windows-specific tools (WAImportExport.exe) and file system formats (NTFS, BitLocker) are referenced. There are no instructions or examples for performing the import process from Linux or macOS systems. While Azure CLI and PowerShell are both covered for job creation, the actual data preparation and disk handling are exclusively Windows-based.
Recommendations
  • Clearly state at the beginning if the Import/Export tool and process are only supported on Windows, and explain why.
  • If possible, provide equivalent Linux/macOS tooling or workflows, or document any supported alternatives for non-Windows users.
  • Include explicit notes about the lack of Linux/macOS support and suggest workarounds, such as preparing disks on a Windows VM if required.
  • If future support for Linux is planned, mention this and provide a link for users to track progress or request features.
  • For parity, provide example commands for disk preparation, encryption, and file system formatting on Linux if/when supported.
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-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing detailed instructions and examples for Windows-centric tools such as PowerShell and the WAImportExport.exe utility, without offering equivalent Linux command-line examples or guidance. The unlock step for exported drives relies exclusively on a Windows executable, and there is no mention of Linux-compatible alternatives or workflows. Additionally, PowerShell examples are given equal or greater prominence compared to Azure CLI, and Windows tools are referenced without Linux parity.
Recommendations
  • Provide explicit instructions and examples for unlocking BitLocker-encrypted drives on Linux, such as using dislocker or cryptsetup, including command-line examples.
  • Mention and document any cross-platform or Linux-native tools that can be used in place of WAImportExport.exe, or clarify platform limitations if none exist.
  • Ensure that all steps involving command-line utilities (e.g., unlocking drives, reviewing logs) include both Windows and Linux workflows.
  • Where PowerShell is referenced, ensure Azure CLI (which is cross-platform) is given equal or greater prominence, and clarify when steps are Windows-only.
  • Add a section or callout summarizing platform support and any known limitations for Linux/Mac users.
  • If certain steps are only possible on Windows, clearly state this and provide recommended workarounds or alternatives for Linux users.
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-08 04:23
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 towards Windows environments. All prerequisites, setup steps, and tooling (BitLocker, NTFS, WAImportExport.exe, manage-bde, PowerShell examples) are Windows-specific. There are no instructions, examples, or tool alternatives for Linux or macOS users, nor is there any mention of cross-platform support or limitations. The documentation assumes the user has access to a Windows system and does not address Linux-based workflows.
Recommendations
  • Clearly state at the beginning if the Import/Export tool and process are Windows-only, and provide rationale.
  • If possible, provide Linux/macOS alternatives or clarify lack of support for non-Windows OSes.
  • If the WAImportExport tool is Windows-only, suggest workarounds for Linux users (e.g., using a Windows VM, or Azure VM, or third-party tools).
  • Mention disk preparation and encryption requirements for Linux (e.g., using LUKS or other encryption tools) if supported, or explicitly state that BitLocker/NTFS is required.
  • Add a section addressing frequently asked questions for Linux/macOS users.
  • If Azure CLI or REST API steps are cross-platform, clarify which steps require Windows and which can be done from any OS.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: all instructions, examples, and tooling are exclusively for Windows. The prerequisite explicitly requires a Windows system, all command-line examples use Windows paths and PowerShell, and the only tool provided (WAImportExport.exe) is a Windows executable. There is no mention of Linux or cross-platform alternatives, nor any guidance for non-Windows users.
Recommendations
  • Clarify early in the documentation whether the Azure Import/Export tool is available for Linux or if there are alternative workflows for Linux users.
  • If a Linux version of the tool exists, provide download and usage instructions, including Linux shell command examples.
  • If only Windows is supported, explicitly state this limitation and suggest workarounds (e.g., using a Windows VM or container).
  • Where possible, use platform-neutral language and file paths, or provide both Windows and Linux examples side by side.
  • Highlight any cross-platform REST API options that could be used from Linux, and provide sample scripts or commands for Linux 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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Windows-style paths (e.g., C:\Users\bob\Pictures), and the only tool referenced is WAImportExport.exe, which is a Windows executable. There are no Linux or cross-platform examples, nor is there any mention of Linux-compatible tools or usage patterns. The documentation refers to 'Windows Azure' and assumes a Windows file system and environment throughout.
Recommendations
  • Provide equivalent Linux command-line examples using Linux-style paths (e.g., /home/bob/Pictures).
  • Clarify whether the WAImportExport tool is available for Linux, or suggest alternative methods for Linux users if not.
  • Mention any prerequisites or compatibility notes for non-Windows users.
  • Use neutral terminology such as 'Azure Blob Storage' instead of 'Windows Azure Blob service'.
  • Include guidance for handling BitLocker-encrypted drives on Linux, or note if this is unsupported.
  • If the tool is Windows-only, explicitly state this early in the documentation and link to Linux alternatives or workarounds 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: 2025-07-08 04:23
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 and Windows-centric tools first or exclusively when discussing enabling soft-delete and key recovery. While the Azure portal is cross-platform, command-line examples and recovery instructions are primarily given for PowerShell, with CLI mentioned secondarily and no explicit Linux shell or cross-platform command examples provided. There are no Linux-specific instructions or parity in troubleshooting steps.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for enabling soft-delete and key recovery.
  • Include explicit Linux shell (bash) command examples where relevant, ensuring parity for Linux users.
  • When referencing documentation for enabling features or troubleshooting, link to both PowerShell and CLI (bash) guides equally, or use CLI as the default since it is cross-platform.
  • Add a section or notes clarifying that all steps can be performed from Linux/macOS using Azure CLI, and provide sample commands.
  • Avoid referencing Windows tools or patterns (such as PowerShell) exclusively or as the primary method.
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-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Import/Export service is heavily Windows-centric. Only Windows operating systems are listed as supported, and all examples (such as checking disk sector size) use PowerShell commands. There is no mention of Linux or macOS support, nor are there equivalent instructions or tools for non-Windows platforms. The requirements and tooling (e.g., BitLocker, .NET Framework, WAImportExport tool) are all specific to Windows environments.
Recommendations
  • Explicitly state whether Linux and macOS are supported or not for the WAImportExport tool and the Import/Export process.
  • If Linux/macOS are not supported, provide a clear rationale and suggest alternatives or workarounds for users on those platforms.
  • If partial support exists (e.g., for AzCopy or other steps), provide equivalent Linux/macOS instructions and examples.
  • Include Linux command-line examples (e.g., using lsblk, fdisk, or other tools) for checking disk sector size.
  • Mention cross-platform tools where possible, and avoid assuming only Windows users will use the service.
  • If BitLocker is required, clarify if there are alternative encryption options for non-Windows users.
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-08 04:23
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 cross-platform alternatives or instructions provided. The documentation does not mention any Linux-compatible tools or workflows, nor does it offer guidance for users on non-Windows platforms.
Recommendations
  • Clearly state the lack of Linux support early in the documentation and provide guidance for Linux users (e.g., using a Windows VM or container).
  • Develop and document a cross-platform or Linux-compatible tool for data preparation and import/export jobs.
  • If possible, provide PowerShell and Bash (or other Linux shell) command examples side by side.
  • Mention any workarounds or third-party solutions for Linux users, if available.
  • Ensure parity in documentation by including Linux-specific instructions, troubleshooting, and requirements.
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-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Windows Azure Import/Export Tool (WAImportExport.exe), provides only Windows-style command-line examples (e.g., C:\ paths, .exe extension), and uses Windows-centric terminology (e.g., BitLocker, drive letters). There are no Linux equivalents, examples, or mentions of cross-platform support, which may exclude or confuse users on Linux or macOS systems.
Recommendations
  • Explicitly state whether the Azure Import/Export Tool is available for Linux/macOS, and if not, provide guidance or alternatives for non-Windows users.
  • If a Linux version or cross-platform tool exists, provide equivalent Linux command-line examples (e.g., using /mnt or ~/ paths, and appropriate executable names).
  • Mention Linux-compatible encryption/decryption tools if BitLocker is referenced (e.g., dislocker or cryptsetup).
  • Avoid using only Windows drive letters and backslashes in file paths; provide POSIX-style examples as well.
  • Clarify any platform limitations early in the documentation, so users know if they need to use a Windows environment or VM.
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: 2025-07-08 04:23
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, 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
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-07-08 04:23
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, instructions, and examples assume a Windows environment, with explicit requirements for Windows OS, .NET Framework, BitLocker, and the use of Windows drive letters and paths. There are no references to Linux or cross-platform alternatives, nor are there any Linux-specific instructions or examples.
Recommendations
  • Clearly state if the tool is Windows-only, or provide information about Linux/macOS support if available.
  • If cross-platform support exists, add equivalent Linux (and macOS) installation and usage instructions, including command-line examples using Linux paths and conventions.
  • Mention Linux-compatible alternatives for prerequisites (e.g., disk encryption, file system preparation) if possible.
  • If the tool is not supported on Linux, suggest alternative workflows for Linux users or clarify the limitations up front.
  • Ensure that documentation structure and examples do not assume Windows as the default or only environment.
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-08 04:23
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-centric error codes (e.g., 'UploadErrorWin32', Win32 error codes like 267 and 123) and terminology. There are no explicit PowerShell or Windows-only command examples, but the error reporting and log samples reference Windows filesystem errors and Win32 error categories, with no mention of Linux equivalents or how errors would appear on non-Windows systems. This may leave Linux users uncertain about how to interpret or troubleshoot similar issues on their platforms.
Recommendations
  • Include examples or explanations of how errors manifest on Linux systems, such as typical error codes or messages encountered when using Linux filesystems.
  • Clarify whether 'UploadErrorWin32' and related error codes are also used for Linux-originated errors, or provide a mapping/reference for Linux error codes if different.
  • Add a section or note addressing cross-platform considerations, explicitly stating whether the logs and error categories apply equally to Linux and macOS environments.
  • If possible, provide sample logs or troubleshooting steps for Linux users, or link to relevant Linux documentation.
  • Avoid using Windows-specific terminology (e.g., 'Win32') without explanation, or supplement with Linux equivalents.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell for key vault recovery and soft-delete instructions before mentioning CLI alternatives, and by linking to PowerShell-specific troubleshooting steps. There are no explicit Linux/macOS command examples, and the workflow assumes use of the Azure portal, which is platform-agnostic but the supporting command-line instructions and troubleshooting are Windows-centric.
Recommendations
  • Provide equivalent Azure CLI and Bash examples alongside PowerShell instructions for key vault recovery and management.
  • Ensure troubleshooting steps reference both PowerShell and CLI/Bash solutions, with links to Linux/macOS documentation.
  • Where command-line instructions are given, present CLI (cross-platform) examples before PowerShell, or side-by-side.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences or additional steps required.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-troubleshooting-v1.md ...xport/storage-import-export-tool-troubleshooting-v1.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation does not provide any platform-specific troubleshooting steps, but it implicitly assumes the use of Windows tools and workflows. There are no examples or instructions for Linux users, nor are Linux-compatible tools or commands mentioned. The guidance around deleting journal files and rerunning commands presumes familiarity with the default (Windows-based) Import/Export tool, which is not natively available on Linux.
Recommendations
  • Include explicit instructions or notes for Linux users, such as how to manage journal files and run Import/Export operations using cross-platform tools or Azure CLI.
  • Mention whether the Import/Export tool is available for Linux, and if not, provide alternatives or workarounds.
  • Add troubleshooting examples or command-line snippets for both Windows (PowerShell/Command Prompt) and Linux (Bash/Azure CLI) environments.
  • Clarify any platform-specific limitations or requirements, such as file system compatibility or tool availability.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-troubleshooting-v1.md ...xport/storage-import-export-tool-troubleshooting-v1.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation does not provide any platform-specific troubleshooting steps, but it implicitly assumes the use of Windows tools and patterns (e.g., 'command-line parameters', 'journal file', 'copy session') without clarifying if or how these apply to Linux environments. There are no Linux-specific examples, commands, or references, and the documentation does not mention cross-platform compatibility or alternative tools for Linux users.
Recommendations
  • Explicitly state whether the troubleshooting steps and tools apply to both Windows and Linux, or clarify any platform limitations.
  • Provide Linux-specific examples and command-line instructions where relevant, such as using Linux shell commands for managing journal files or copy sessions.
  • Mention any cross-platform tools or alternatives available for Linux users, or provide links to Linux-focused documentation.
  • If the Azure Import/Export tool is Windows-only, clearly state this at the beginning of the documentation and suggest alternative workflows for Linux users.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell for key vault recovery and soft-delete instructions before mentioning CLI alternatives. The troubleshooting section provides a PowerShell-specific command for key recovery, and enabling soft-delete/purge protection links to PowerShell instructions first. There are no explicit Linux/macOS examples or CLI commands shown directly in the main flow, and the Azure portal UI is platform-agnostic but implicitly assumes a Windows-centric workflow due to PowerShell prominence.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands, especially in troubleshooting sections.
  • Explicitly mention that the Azure portal is accessible from any OS/browser.
  • Ensure that links to enabling soft-delete and purge protection reference CLI and REST API instructions equally, not just PowerShell.
  • Add a note or section for Linux/macOS users, highlighting parity and alternative tools where relevant.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-troubleshooting-v1.md ...xport/storage-import-export-tool-troubleshooting-v1.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific troubleshooting steps or examples, but it also does not mention or demonstrate any Linux tools, commands, or workflows. This omission may leave Linux users without clear guidance, especially if there are platform-specific considerations for Azure Import/Export operations.
Recommendations
  • Add explicit troubleshooting steps for both Windows and Linux environments, including relevant command-line examples for each.
  • Mention any differences in handling journal files, drive preparation, or error recovery on Linux systems.
  • Reference Linux-compatible tools (such as dd, lsblk, or fdisk) where appropriate, alongside any Windows tools.
  • Include links to platform-specific guides or documentation for both Windows and Linux users.
GitHub Create Pull Request
Import Export https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/import-export/storage-import-export-tool-troubleshooting-v1.md ...xport/storage-import-export-tool-troubleshooting-v1.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific troubleshooting steps or examples, but it also does not mention or demonstrate any Linux-specific tools, commands, or workflows. There is an implicit bias due to the absence of Linux guidance, which may leave Linux users without clear instructions for common troubleshooting scenarios.
Recommendations
  • Add explicit troubleshooting steps for both Windows and Linux environments, including relevant command-line examples for each.
  • Mention and provide examples for Linux-compatible tools (such as azcopy or relevant shell commands) alongside any Windows-specific tools.
  • Clarify whether the described procedures (e.g., deleting journal files, rerunning commands) are the same on Linux, and provide file path examples for both platforms.
  • Include a section or note addressing any platform-specific differences or considerations for Linux users.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →