Databox

79
Total Pages
30
Linux-Friendly Pages
49
Pages with Bias
62.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

231 issues found
Showing 176-200 of 231 flagged pages
Databox Review copy errors in uploads from Azure Data Box, Data Box Next-Gen, and Azure Data Box Heavy devices .../articles/databox/data-box-troubleshoot-data-upload.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or troubleshooting steps. However, in the few places where command-line or scripting is referenced (such as Azure PowerShell for Key Vault recovery), only Windows-centric tools are mentioned, and there are no Linux/macOS equivalents or CLI alternatives shown. This creates a subtle bias by omission, as Linux/macOS users may need to adapt instructions or search for their own solutions.
Recommendations
  • Where PowerShell is referenced (e.g., Key Vault recovery), include equivalent Azure CLI commands and links to CLI documentation.
  • Explicitly state that troubleshooting steps can be performed from any supported OS, and provide parity in examples for Linux/macOS users.
  • If screenshots or UI instructions are OS-agnostic, clarify this, or add notes for any platform-specific differences.
  • Review linked articles (e.g., key vault recovery) to ensure Linux/macOS instructions are present and referenced.
GitHub Create Pull Request
Databox Tutorial to export data from Azure Data Box | Microsoft Docs ...ain/articles/databox/data-box-deploy-export-ordered.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Robocopy as a recommended tool for applying ACLs to exported Azure Files, without referencing any Linux/macOS alternatives. Additionally, the only script provided for generating XML files is a PowerShell (.ps1) script, with no mention of Bash, Python, or other cross-platform options. No Linux/macOS-specific tools or examples are provided for these critical steps.
Recommendations
  • Mention and provide examples of Linux/macOS tools for applying ACLs to exported files, such as 'setfacl', 'getfacl', or 'rsync'.
  • Offer a Bash or Python script alternative for generating XML files for export, or clarify how Linux/macOS users can perform this step.
  • Explicitly state cross-platform compatibility for all steps, and ensure parity in tool recommendations and examples.
  • Add a note or section for Linux/macOS users outlining any differences or additional steps required.
GitHub Create Pull Request
Databox Azure Data Box Disk limits | Microsoft Docs ...ocs/blob/main/articles/databox/data-box-disk-limits.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation references Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd) and provides instructions for enabling long paths only on Windows clients. There are no Linux/macOS equivalents or instructions, nor any mention of how Linux users should handle long paths or validate/copy data. Windows tools and patterns are mentioned exclusively, creating friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalents for DataBoxDiskSplitCopy and DataBoxDiskValidation tools, or document alternative workflows for those platforms.
  • Include instructions for handling long file paths on Linux/macOS clients, such as relevant filesystem settings or limitations.
  • Explicitly state platform support and limitations for all tools and workflows.
  • Add Linux/macOS-specific examples and troubleshooting steps where relevant.
GitHub Create Pull Request
Databox Preserving file ACLs, attributes, and timestamps with Azure Data Box ...in/articles/databox/data-box-file-acls-preservation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-specific concepts (NT ACLs, SeBackupPrivilege, Administrator/SYSTEM accounts), providing more detail for Windows scenarios, and omitting concrete Linux copy tool examples. Linux users are told only Windows NT ACLs are transferred, but no guidance is given on how to use Linux tools or what limitations exist. Windows terminology and privileges are explained, while Linux equivalents are not discussed.
Recommendations
  • Add explicit Linux copy tool examples (e.g., smbclient, rsync, cp) and clarify their behavior regarding ACLs, attributes, and timestamps.
  • Discuss Linux-specific ACL types (POSIX ACLs) and clarify their mapping (or lack thereof) to Azure Files.
  • Provide guidance for Linux users on how to maximize metadata preservation, including any required mount options or tool flags.
  • Balance explanations of Windows and Linux privilege requirements, including what Linux users need to ensure for successful metadata transfer.
  • Clearly state limitations for Linux users and offer workarounds or alternatives where possible.
GitHub Create Pull Request
Databox Microsoft Azure Data Box Disk system requirements| Microsoft Docs .../articles/databox/data-box-disk-system-requirements.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows operating systems and tools are consistently listed first, and the 'Other required software for Windows clients' section details specific Windows tools (PowerShell, .NET Framework, BitLocker) without equivalent detail or usage examples for Linux. There are no command-line or usage examples for Linux tools, and the Windows requirements are more thoroughly enumerated. This could create friction for Linux users, who may need to research tool installation and usage independently.
Recommendations
  • List Linux and Windows operating systems and tools in parallel order, or alternate which is listed first.
  • Provide equivalent detail for Linux tools as is given for Windows (e.g., installation commands, usage notes, minimum versions).
  • Include example commands for both Windows (PowerShell) and Linux (bash/terminal) for common tasks such as unlocking disks or copying data.
  • Clarify any differences in workflow or limitations between Windows and Linux clients.
  • Ensure that Linux-specific caveats (such as required packages or kernel modules) are as visible as Windows prerequisites.
GitHub Create Pull Request
Databox Tutorial to order Azure Data Box | Microsoft Docs .../blob/main/articles/databox/data-box-deploy-ordered.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias, especially in its command-line examples and instructions. Azure CLI usage is repeatedly demonstrated in Windows PowerShell terminals, with explicit references to 'PS C:\Windows>' and instructions to open Windows PowerShell. Installation instructions for Azure CLI and PowerShell modules prioritize Windows-specific methods (MSI installer, Windows PowerShell). There is little to no mention of Linux/macOS terminals, shells, or installation patterns, and no CLI examples are shown in Bash or native Linux/macOS environments. The documentation assumes a Windows context throughout, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI examples using Bash or native Linux/macOS terminals (e.g., $ az login) alongside PowerShell examples.
  • Include installation instructions for Azure CLI and PowerShell modules for Linux and macOS (e.g., apt, yum, Homebrew).
  • Avoid using Windows-specific prompts (PS C:\Windows>) as the default; show generic or platform-appropriate prompts.
  • Explicitly state that Azure CLI and PowerShell modules are cross-platform, and link to platform-specific installation guides.
  • Balance example output and screenshots to include Linux/macOS environments where appropriate.
GitHub Create Pull Request
Databox Tutorial: Copy data to Azure Data Box Blob storage via REST APIs ...es/databox/data-box-heavy-deploy-copy-data-via-rest.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias. Certificate import instructions are detailed for Windows (PowerShell and UI) before Linux, with screenshots and step-by-step guidance, while Linux instructions are more generic and less visual. Windows tools and patterns (PowerShell, Windows Server UI) are described in depth, and Windows examples are often presented first. However, Linux equivalents are present for key tasks, and AzCopy commands are shown for both platforms.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux certificate import, including screenshots for popular distributions (e.g., Ubuntu, RHEL).
  • List Linux examples before or alongside Windows examples to avoid Windows-first ordering.
  • Expand troubleshooting and partner software configuration sections to include Linux-specific guidance.
  • Reference macOS where applicable, or clarify if unsupported.
  • Ensure parity in visual aids (screenshots, UI walkthroughs) for Linux environments.
GitHub Create Pull Request
Databox Tutorial to copy data via SMB on Azure Data Box Heavy | Microsoft Docs ...in/articles/databox/data-box-heavy-deploy-copy-data.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: Windows examples and instructions are presented first and in greater detail, with extensive use of Windows-specific tools (e.g., Robocopy, net use, File Explorer). Linux instructions are minimal, lacking equivalent detail and examples (e.g., no rsync or cp command samples, no troubleshooting or performance tuning guidance for Linux). The copy section focuses almost exclusively on Robocopy, with no Linux copy tool alternatives or optimization advice.
Recommendations
  • Provide Linux/macOS examples for mounting SMB shares (e.g., using mount.cifs, smbclient) and copying data (e.g., rsync, cp, smbclient).
  • Include performance tuning guidance for Linux copy tools (e.g., rsync options, parallelization).
  • Offer troubleshooting steps and error log viewing instructions for Linux users.
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than Windows-first.
  • Reference cross-platform tools (e.g., AzCopy) where appropriate, and clarify their usage on Linux/macOS.
  • Add sample output for Linux copy commands, similar to the Robocopy output shown for Windows.
GitHub Create Pull Request
Databox Use your own certificates with Azure Data Box/Azure Data Box Heavy devices ...ticles/databox/data-box-bring-your-own-certificates.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for importing certificates on Windows clients only, with no mention of how to perform equivalent steps on Linux or macOS. The certificate import workflow is described exclusively using Windows tools and UI, creating friction for non-Windows users.
Recommendations
  • Add instructions for importing certificates on Linux (e.g., using 'update-ca-certificates', 'certutil', or manual placement in /usr/local/share/ca-certificates).
  • Include steps for macOS users (e.g., using Keychain Access or 'security' CLI tool).
  • Provide cross-platform guidance or links to official documentation for certificate management on Linux/macOS.
  • Clearly indicate platform-specific steps and offer parity for all major client OSes.
GitHub Create Pull Request
Databox Use the Azure portal to manage customer-managed keys for Azure Data Box ...box/data-box-customer-managed-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 Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps and command-line references frequently cite PowerShell and Windows-specific tools (e.g., Get-AzKeyVault), with no equivalent Azure CLI or Linux/macOS instructions. In error resolution tables, PowerShell is referenced for retrieving Key Vault URIs, and recovery steps link to PowerShell tabs by default. Azure CLI is mentioned only once, and Linux/macOS workflows are not described or illustrated. All screenshots and UI references are for the Azure portal, which is cross-platform, but command-line parity is lacking.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line instructions, especially for retrieving Key Vault URIs and setting policies.
  • Where PowerShell is referenced, provide equivalent bash/Azure CLI commands for Linux/macOS users.
  • Ensure troubleshooting links default to CLI or offer both PowerShell and CLI tabs.
  • Explicitly state that all portal instructions apply equally to Windows, Linux, and macOS.
  • Include a section or note on how Linux/macOS users can perform all relevant tasks using CLI or other cross-platform tools.
GitHub Create Pull Request
Databox Tutorial: Copy from VHDs to managed disks ...rticles/databox/data-box-deploy-copy-data-from-vhds.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 moderate Windows bias. The SMB connection section provides detailed, step-by-step instructions and screenshots for Windows users, including use of Windows-specific tools (net use, File Explorer, Windows + R). In contrast, the NFS (Linux) section is less detailed, lacks screenshots, and omits common Linux workflows (e.g., using file managers or persistent mounts via /etc/fstab). The overall structure presents Windows/SMB instructions first, reinforcing a Windows-centric approach.
Recommendations
  • Provide Linux SMB connection instructions (e.g., using smbclient, mount -t cifs, or GNOME/KDE file managers).
  • Include Linux/macOS screenshots for mounting shares and accessing Data Box folders.
  • Offer parity in step-by-step guidance for Linux users, including troubleshooting tips and persistent mount configuration (/etc/fstab).
  • Alternate the order of SMB (Windows) and NFS (Linux) sections or clarify that both are equally supported.
  • Mention macOS compatibility and provide relevant examples if supported.
GitHub Create Pull Request
Databox Tutorial: Use data copy service to copy to your device .../databox/data-box-deploy-copy-data-via-copy-service.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows terminology and patterns (such as UNC paths, Windows-style usernames, and references to right-clicking for security settings), and by not providing Linux/macOS equivalents or guidance. There is also a note that non-Windows NAS devices are not officially supported, which further marginalizes Linux users. No Linux-specific instructions, examples, or troubleshooting are provided.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as how to specify SMB paths and credentials from those systems.
  • Clarify whether Linux-based NAS devices are supported in practice, and if so, provide guidance for common configurations.
  • Include screenshots or command-line examples relevant to Linux/macOS environments.
  • Avoid Windows-centric language (e.g., 'Right-click the folder, select Properties, then Security') or provide equivalent steps for Linux/macOS.
  • If non-Windows NAS devices are unsupported, clearly state the limitations and suggest alternatives for Linux users.
GitHub Create Pull Request
Databox Tutorial: Copy to Blob storage via REST APIs ...articles/databox/data-box-deploy-copy-data-via-rest.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 moderate Windows bias. Certificate import instructions are detailed for Windows (PowerShell and GUI), with Linux steps given in less detail and requiring users to consult external documentation. Windows examples and screenshots are shown first and more prominently. AzCopy usage is covered for both platforms, but Windows command syntax is presented before Linux in some sections. Partner software configuration and verification steps lack Linux-specific guidance or examples.
Recommendations
  • Provide equally detailed, step-by-step instructions for importing certificates on popular Linux distributions, including specific commands and screenshots where possible.
  • Include Linux-specific examples and troubleshooting tips for configuring partner software and verifying connections.
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Expand guidance for macOS users where relevant.
  • Ensure that all critical procedures (e.g., certificate import, AzCopy usage) have complete, tested Linux/macOS instructions.
GitHub Create Pull Request
Databox Tutorial to copy data via SMB from your Azure Data Box | Microsoft Docs ...n/articles/databox/data-box-deploy-export-copy-data.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 page demonstrates a Windows bias by presenting Windows connection and copy instructions first and in greater detail, including screenshots and step-by-step guidance. Windows-specific tools like 'net use' and Robocopy are highlighted, with no Linux equivalents (e.g., rsync, cp) mentioned. The Linux section is brief, only showing a mount command (which incorrectly uses NFS instead of SMB/cifs), and lacks detailed copy instructions or tool recommendations for Linux users.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence.
  • Correct the Linux mount command to use SMB/CIFS (e.g., 'sudo mount -t cifs ...') instead of NFS.
  • Include Linux file copy tool examples (e.g., 'cp', 'rsync', 'smbclient') and usage instructions.
  • Add screenshots or terminal output examples for Linux workflows.
  • Mention macOS compatibility and provide relevant instructions if supported.
GitHub Create Pull Request
Databox Tutorial to copy data via SMB on Azure Data Box | Microsoft Docs ...lob/main/articles/databox/data-box-deploy-copy-data.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 notable Windows bias. Windows-specific tools (Robocopy, net use) are explained in detail with step-by-step instructions, screenshots, and command output. Linux instructions are minimal, limited to a single mount command for SMB, with no examples for copying files (e.g., rsync, cp) or error handling. The primary file copy tool discussed is Robocopy, which is Windows-only, and all detailed examples and performance tuning are focused on Robocopy. Linux users are left to infer their own copy procedures and best practices.
Recommendations
  • Provide equivalent Linux/macOS file copy examples (e.g., rsync, cp, smbclient) alongside Robocopy, including command syntax and sample output.
  • Include Linux/macOS-specific guidance for optimizing performance (e.g., rsync options, parallelization, mount options for performance).
  • Add troubleshooting steps and screenshots for Linux/macOS environments, similar to the Windows section.
  • Present Windows and Linux/macOS instructions in parallel or in clearly separated sections, rather than focusing on Windows first.
  • Reference Linux/macOS documentation for SMB/NFS mounting and copying, and link to relevant tools.
GitHub Create Pull Request
Databox Microsoft Azure Data Box Disk security features | Microsoft Docs in data ...s/blob/main/articles/databox/data-box-disk-security.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references BitLocker and a proprietary 'Data Box Disk unlock tool' as core security mechanisms, both of which are Windows-centric. There is no mention of Linux-compatible disk unlocking methods or alternatives to BitLocker, nor are Linux/macOS workflows or tools discussed. This creates ambiguity for users on non-Windows platforms regarding how to access encrypted disks.
Recommendations
  • Explicitly state whether the Data Box Disk unlock tool is available for Linux/macOS, and provide download links or instructions if so.
  • If the unlock tool is Windows-only, provide Linux/macOS alternatives or document supported workflows for those platforms.
  • Mention whether BitLocker-encrypted disks can be mounted and accessed on Linux/macOS, and provide guidance or references for doing so.
  • Add examples or sections for Linux/macOS users, including any required dependencies or troubleshooting tips.
GitHub Create Pull Request
Databox Azure Data Box Disk troubleshooting | Microsoft Docs ...ob/main/articles/databox/data-box-disk-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-style drive letters (e.g., D:\, E:\) and Windows file paths in examples, without providing Linux or macOS equivalents. There are no Linux/macOS-specific instructions or examples for locating logs or validating data, which may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS examples for file paths (e.g., /mnt/DataBoxDiskImport/logs) alongside Windows examples.
  • Clarify whether the validation tool and disk structure are supported on Linux/macOS, and provide platform-specific instructions if so.
  • Explicitly mention any OS requirements or limitations for the validation tool.
  • Add troubleshooting steps or notes relevant to Linux/macOS environments, such as permissions or mount points.
GitHub Create Pull Request
Databox Tutorial to unpack, connect to, unlock Azure Data Box Disk| Microsoft Docs ...b/main/articles/databox/data-box-disk-deploy-set-up.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 provides both Windows and Linux instructions for unlocking Azure Data Box Disk, but Windows examples and tool references are often presented first and in greater detail. Windows-specific tools (DataBoxDiskUnlock.exe) and PowerShell/Command Prompt usage are emphasized, with Linux instructions sometimes appearing as secondary or requiring third-party utilities. Some sections, especially in the 'Unlock disks' area, give Windows steps before Linux, and troubleshooting guidance is more Windows-centric. Linux instructions are present and fairly detailed, but parity in example ordering and tool explanation is lacking.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which OS is shown first in each section.
  • Provide equal detail and troubleshooting guidance for Linux users, including common error scenarios.
  • Ensure all tool download links and usage examples are equally prominent for both platforms.
  • Avoid Windows-centric terminology (e.g., PowerShell, drive letters) in general explanations; use platform-neutral language.
  • Add explicit Linux CLI examples where only Windows/PowerShell commands are shown.
  • Highlight any platform-specific limitations or requirements at the start of each relevant section.
GitHub Create Pull Request
Databox Track and log Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events for export order| Microsoft Docs ...ocs/blob/main/articles/databox/data-box-export-logs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific concepts (such as NT AUTHORITY, WIN-DATABOXADMIN, and MICROSOFT_AUTHENTICATION_PACKAGE_V1_0) in audit log samples, and the log output is clearly from a Windows environment. There are no explicit Linux/macOS examples, nor are Linux-specific tools or log formats mentioned. The only code block is labeled as 'powershell', and the authentication and logon event descriptions are Windows-centric. There is no guidance for Linux users on how to interpret logs, access credentials, or perform equivalent auditing steps.
Recommendations
  • Include Linux/macOS-specific examples for log formats and audit events, especially for NFS or SMB access.
  • Document how Linux users can access device credentials and logs, and how audit events would appear on Linux systems.
  • Clarify whether the Data Box supports Linux authentication and logging, and if so, provide parity in instructions.
  • Add notes or sections for Linux/macOS users, including troubleshooting steps and expected log outputs.
  • Avoid labeling generic XML output as 'powershell' unless it is truly a PowerShell command or output.
GitHub Create Pull Request
Databox Tutorial: Copy from VHDs to managed disks ...s/databox/data-box-heavy-deploy-copy-data-from-vhds.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Windows/SMB connection instructions first, with detailed steps using Windows-specific tools (net use, File Explorer, Windows + R). Linux/NFS instructions are provided, but appear after the Windows section and are less detailed regarding troubleshooting and GUI usage. There is a notable emphasis on Windows tools and patterns, with Windows terminology and screenshots dominating the connection workflow.
Recommendations
  • Present Linux/NFS connection instructions alongside or before Windows/SMB instructions to avoid ordering bias.
  • Expand Linux instructions to include troubleshooting steps, GUI alternatives (e.g., using Nautilus or Dolphin for mounting NFS shares), and screenshots where appropriate.
  • Include parity in credential acquisition steps for Linux users (e.g., how to use credentials in Linux environments).
  • Reference cross-platform tools (e.g., smbclient for Linux) and provide examples for both CLI and GUI workflows.
  • Explicitly mention macOS compatibility and provide macOS-specific mounting instructions if supported.
GitHub Create Pull Request
Databox Send data to Hot, Cool, and Archive blob tier via Azure Data Box, Data Box Next-Gen, and Azure Data Box Heavy ...main/articles/databox/data-box-how-to-set-data-tier.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples and instructions, specifically referencing 'Windows PowerShell' and requiring an 'elevated Windows PowerShell session'. There are no CLI, Bash, or cross-platform scripting examples, nor any mention of Linux/macOS-compatible tools or workflows. The sample output and instructions are tailored to Windows environments, which may hinder Linux/macOS users from following the guide directly.
Recommendations
  • Add equivalent Azure CLI examples for blob tiering, which are cross-platform and work on Linux/macOS.
  • Provide Bash or shell script samples for common operations, or reference SDKs usable on Linux/macOS.
  • Clarify that PowerShell Core (pwsh) is available on Linux/macOS and provide instructions for those platforms.
  • Rephrase instructions to avoid assuming a Windows environment (e.g., do not require 'elevated Windows PowerShell session').
  • Include notes or links to platform-specific guidance for Linux/macOS users.
GitHub Create Pull Request
Databox Microsoft Azure Data Box Disk security features | Microsoft Docs in data ...s/blob/main/articles/databox/data-box-disk-security.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing BitLocker (a Windows disk encryption tool) as the software encryption method for Data Box Disk, without mentioning Linux-compatible alternatives or providing guidance for Linux users. There are no examples or instructions for unlocking or using the disks on Linux systems, nor is there mention of Linux-native tools or workflows.
Recommendations
  • Include information on how Data Box Disk can be used with Linux systems, including supported unlock tools or procedures for Linux.
  • Mention Linux-compatible disk encryption and management tools, or clarify cross-platform compatibility of the Data Box Disk unlock tool.
  • Provide Linux-specific examples and instructions alongside Windows/BitLocker references.
  • Explicitly state any platform limitations or requirements for disk access and management.
GitHub Create Pull Request
Databox Use your own certificates with Azure Data Box/Azure Data Box Heavy devices ...ticles/databox/data-box-bring-your-own-certificates.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and screenshots for importing certificates on Windows clients only. There are no examples, instructions, or mentions of how to perform equivalent certificate import steps on Linux or macOS clients. The Windows workflow is presented as the default and only supported method, which may exclude or confuse users on other platforms.
Recommendations
  • Add step-by-step instructions for importing certificates on Linux clients, such as using 'openssl', 'certutil', or updating the system's trusted CA store.
  • Include macOS instructions for importing certificates via Keychain Access.
  • Provide cross-platform command-line examples (e.g., using 'openssl' or 'certutil') for certificate management.
  • Clearly state that the process applies to all major operating systems and link to platform-specific guidance where appropriate.
  • Add a table or section comparing certificate import steps across Windows, Linux, and macOS.
GitHub Create Pull Request
Databox Azure Data Box Disk troubleshooting | Microsoft Docs ...ob/main/articles/databox/data-box-disk-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-style drive letters (e.g., D:\, E:\) and Windows folder paths, and by using a PowerShell script (.ps1) as an example file. There are no Linux or cross-platform examples, nor is there mention of Linux tools, file paths, or validation workflows. This may make it harder for Linux users to relate to the troubleshooting steps or understand how to apply them in their environment.
Recommendations
  • Include Linux-style path examples (e.g., /mnt/databoxdiskimport/logs) alongside Windows paths.
  • Provide sample error logs referencing Linux files (e.g., shell scripts, .sh files) as well as PowerShell scripts.
  • Clarify whether the validation tool and troubleshooting steps are supported on Linux, and if so, provide instructions for Linux users.
  • Mention any Linux-specific considerations, such as file permissions or mounting disks, in troubleshooting steps.
  • Ensure that all examples and screenshots are platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
Databox Microsoft Azure Data Box security overview | Microsoft Docs in data ...e-docs/blob/main/articles/databox/data-box-security.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page does not provide explicit examples or instructions for either Windows or Linux platforms, but it does mention SMB 3.0 (commonly associated with Windows environments) as the recommended protocol for encrypted data transfer. Additionally, the secure erase tools listed (ARCCONF, MSECLI) are typically Windows-centric or at least not clarified for Linux usage. There are no references to Linux-specific protocols (such as NFS with Kerberos, SSH/SCP, rsync, etc.), nor are Linux command-line examples or tools mentioned anywhere. This results in a subtle bias toward Windows environments and tools, with Linux parity lacking in protocol recommendations and tool documentation.
Recommendations
  • Explicitly mention and provide examples for both Windows and Linux environments when discussing data transfer protocols (e.g., include NFS with Kerberos, rsync over SSH, SCP, etc.).
  • Clarify whether secure erase tools (ARCCONF, MSECLI) are available and supported on Linux, and provide Linux usage instructions if applicable.
  • Provide Linux command-line examples for connecting to the Data Box device, mounting shares, and transferring data.
  • List Linux-compatible protocols and best practices for secure data transfer to/from Data Box.
  • Ensure parity in documentation by referencing both Windows and Linux administrative patterns and tools wherever relevant.
GitHub Create Pull Request
← Previous Page 8 of 10 Next →