Databox

158
Total Pages
130
Linux-Friendly Pages
28
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

55 issues found
Showing 1-25 of 55 flagged pages
Databox Tutorial to copy data to Azure Data Box Disk | Microsoft Docs ...ain/articles/databox/data-box-disk-deploy-copy-data.md
High Priority View Details →
Scanned: 2026-01-12 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 shows a strong Windows bias. All tool-based instructions (Split Copy, Validation) are Windows-only, with explicit statements that these tools are unavailable for Linux. The primary file copy example uses Robocopy, a Windows-native tool, and the only command-line examples and screenshots are for Windows environments. No Linux/macOS-specific copy or validation workflows, commands, or screenshots are provided, and Linux users are left with generic advice to 'validate' data without concrete steps or parity tooling.
Recommendations
  • Provide Linux/macOS equivalents for file copy, such as examples using rsync, cp, or smbclient, including recommended parameters for performance and integrity.
  • Offer checksum validation instructions for Linux/macOS, e.g., using sha256sum or md5sum, with sample scripts or commands.
  • Clarify which steps/tools are cross-platform and which are Windows-only, and offer alternative workflows for Linux/macOS users.
  • Include screenshots or terminal output examples from Linux environments.
  • If possible, develop and document parity tools for Linux/macOS, or recommend open-source alternatives.
GitHub Create Pull Request
Databox Azure Data Box Disk troubleshooting disk unlocking issues | Microsoft Docs .../articles/databox/data-box-disk-troubleshoot-unlock.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page focuses exclusively on troubleshooting Azure Data Box Disk unlock issues using Windows tools and workflows. All examples, error messages, and troubleshooting steps reference Windows-specific components such as .NET Framework, BitLocker, and Windows PowerShell. There are no instructions, examples, or troubleshooting guidance for Linux or macOS users, nor is there any mention of cross-platform compatibility for the unlock tool.
Recommendations
  • Add explicit guidance for Linux and macOS users, including supported unlock workflows and troubleshooting steps.
  • Clarify whether the Data Box Disk Unlock tool is available for Linux/macOS, and if not, provide alternatives or workarounds.
  • Include Linux/macOS-specific error messages and resolutions, if applicable.
  • Present examples for both Windows and Linux/macOS platforms, or clearly state platform limitations at the beginning of the document.
  • If the tool is Windows-only, make this limitation clear and suggest supported alternatives for non-Windows environments.
GitHub Create Pull Request
Databox Troubleshoot share connection failure during data copy to Azure Data Box | Microsoft Docs ...articles/databox/data-box-troubleshoot-share-access.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily Windows-centric, with all troubleshooting steps, error messages, and example commands shown using Windows tools (net use, Event Viewer, Local Security Policy, Registry Editor). There are no Linux or macOS equivalents provided for connecting to SMB shares, checking logs, or adjusting authentication settings. Windows terminology and tools are used exclusively and presented first, leaving Linux/macOS users without guidance.
Recommendations
  • Add Linux/macOS-specific troubleshooting steps for SMB share connection issues, including example commands (e.g., smbclient, mount.cifs) and error messages.
  • Include instructions for checking relevant logs on Linux (e.g., syslog, journalctl, dmesg, Samba logs) when diagnosing authentication failures.
  • Provide guidance for adjusting SMB/CIFS client settings on Linux/macOS, such as modifying mount options or smb.conf parameters to match required authentication levels.
  • Present cross-platform examples side-by-side or in separate sections to ensure parity.
  • Reference Linux/macOS documentation for group policy equivalents or clarify when steps are Windows-only.
GitHub Create Pull Request
Databox Tutorial to copy data to Azure Data Box Disk | Microsoft Docs ...ain/articles/databox/data-box-disk-deploy-copy-data.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All detailed examples and screenshots use Windows tools (Robocopy, File Explorer, DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd), and instructions are written for Windows environments. Linux is mentioned only in passing, with no equivalent examples, recommended tools, or step-by-step guidance for Linux/macOS users. Critical validation and split-copy tools are Windows-only, leaving Linux users without supported alternatives or parity in workflow.
Recommendations
  • Provide equivalent Linux/macOS instructions and examples for copying data (e.g., using rsync, cp, or smbclient).
  • List and demonstrate Linux-compatible tools for checksum validation (e.g., sha256sum, md5sum) and explain how to verify data integrity on Linux.
  • Offer guidance for splitting and copying data across disks on Linux, or clarify limitations and suggest manual alternatives.
  • Include screenshots and command-line examples from Linux environments.
  • Clearly indicate which steps/tools are Windows-only and provide Linux/macOS workarounds or alternatives wherever possible.
GitHub Create Pull Request
Databox Azure Data Box Disk troubleshooting disk unlocking issues | Microsoft Docs .../articles/databox/data-box-disk-troubleshoot-unlock.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on Windows environments, with all troubleshooting examples, error messages, and resolutions referencing Windows-specific tools (such as PowerShell and BitLocker). There are no instructions, examples, or troubleshooting steps for Linux or macOS users, nor any mention of equivalent unlock workflows or requirements for non-Windows platforms.
Recommendations
  • Add troubleshooting steps and examples for Linux and macOS clients, including how to unlock Data Box Disks on those platforms.
  • Document any required dependencies or tools for disk unlocking on Linux/macOS (e.g., compatible .NET versions, command-line utilities).
  • Provide parity in error messages and resolutions for Linux/macOS users, including common issues and their fixes.
  • Clarify if the Data Box Disk Unlock tool is Windows-only, and if so, explicitly state this limitation and suggest alternatives or workarounds for non-Windows users.
GitHub Create Pull Request
Databox Troubleshoot share connection failure during data copy to Azure Data Box | Microsoft Docs ...articles/databox/data-box-troubleshoot-share-access.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, providing only Windows command-line examples (net use), troubleshooting steps, and screenshots. All instructions for checking logs, changing authentication levels, and registry edits are specific to Windows tools (Event Viewer, Local Security Policy, Registry Editor), with no mention of equivalent Linux/macOS procedures or tools. There are no Linux or macOS SMB client examples, nor guidance for troubleshooting on non-Windows platforms.
Recommendations
  • Add SMB connection examples for Linux (e.g., using smbclient or mount.cifs) and macOS.
  • Include troubleshooting steps for Linux/macOS, such as checking syslog, dmesg, or Samba logs.
  • Provide guidance for adjusting SMB authentication settings on Linux/macOS clients (e.g., editing smb.conf).
  • Mention cross-platform differences in error messages and lockout behavior.
  • Add screenshots or CLI output from Linux/macOS tools where appropriate.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The SMB connection instructions are presented first and are heavily focused on Windows tools and workflows, such as using 'net use' in the command prompt and File Explorer. The Linux/NFS section is provided, but is less detailed and appears after the Windows/SMB instructions. No Linux SMB example is given, and Windows-specific terminology and screenshots dominate the SMB section.
Recommendations
  • Provide SMB connection instructions for Linux/macOS hosts, including example commands (e.g., using 'mount -t cifs' or 'smbclient').
  • Alternate the order of SMB and NFS instructions or present them side-by-side to avoid Windows-first bias.
  • Include screenshots or terminal output for Linux/macOS workflows where appropriate.
  • Clarify that SMB can be used from non-Windows systems and link to relevant documentation.
  • Avoid assuming File Explorer or Windows GUI tools are the only way to interact with shares.
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-12 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 focusing on SMB protocol (primarily associated with Windows environments), providing examples and instructions using Windows-style paths and user formats, referencing Windows security dialogs (e.g., right-click folder > Properties > Security), and explicitly noting that non-Windows NAS devices are not officially supported. There are no Linux/macOS-specific instructions, examples, or troubleshooting guidance, and Windows patterns/tools are mentioned exclusively.
Recommendations
  • Add explicit instructions and examples for Linux/macOS environments, including SMB mounting and path formats.
  • Clarify support status and provide troubleshooting steps for non-Windows NAS devices, or document alternative workflows for Linux/macOS users.
  • Include Linux/macOS equivalents for user permissions and file access (e.g., using chmod, chown, or setfacl instead of Windows Security tab).
  • If POSIX regular expressions are supported, provide examples using Linux tools and syntax.
  • Avoid language that implies Windows is the default or only supported platform; present cross-platform guidance where possible.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references BitLocker as the disk encryption method, which is a Windows-specific technology. There is no mention of Linux-compatible disk unlocking or encryption tools, nor are there instructions or examples for Linux or macOS users on how to interact with Data Box Disk. The unlock tool is referenced only as available in the Data Box Disk service portal, but no cross-platform details are provided.
Recommendations
  • Explicitly state whether Data Box Disk can be unlocked and accessed on Linux/macOS, and provide instructions or supported tools for those platforms.
  • If BitLocker is required, document how Linux/macOS users can access BitLocker-encrypted disks (e.g., using dislocker or similar tools), including step-by-step guidance.
  • Include examples and screenshots for Linux and macOS workflows where relevant, not just Windows.
  • Clarify any limitations or requirements for non-Windows users in the 'requirements' or 'quickstart' documentation.
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-12 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 Windows bias by referencing Windows-style drive letters (e.g., D:\, E:\), Windows folder paths, and providing examples that use Windows conventions exclusively. There are no Linux or macOS-specific examples, paths, or troubleshooting notes. The error log samples and instructions assume a Windows environment, and there is no mention of Linux equivalents or how to access logs or validate data on non-Windows systems.
Recommendations
  • Add Linux/macOS-specific examples, including typical mount points (e.g., /mnt/DataBoxDiskImport/logs) and file paths.
  • Clarify whether the validation tool and error logs are accessible and usable on Linux/macOS, and provide instructions for those platforms if supported.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, case sensitivity).
  • Explicitly state platform requirements and parity, or provide links to Linux/macOS documentation if available.
GitHub Create Pull Request
Databox Audit logs for Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events | Microsoft Docs ...docs/blob/main/articles/databox/data-box-audit-logs.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. It repeatedly emphasizes that Data Box is a Windows-based device, exclusively references Windows event providers (e.g., Microsoft-Windows-Kernel-General, BitLocker, PowerShell), and lists only Windows event IDs and audit sources. There are no mentions of Linux/macOS equivalents, nor any examples or guidance for users familiar with non-Windows environments. The audit log collection and event descriptions are all framed in Windows terminology and tooling.
Recommendations
  • Clarify whether Data Box devices support any Linux/macOS features or access patterns, and explicitly state if they are Windows-only.
  • If Linux/macOS access is possible (e.g., via SMB/NFS), provide audit log event mappings or relevant guidance for those platforms.
  • Include a section addressing Linux/macOS users, outlining any limitations or alternative approaches for audit log access and interpretation.
  • If audit logs can be consumed or parsed on non-Windows systems, provide example commands or tools (e.g., using Linux log viewers, parsing event logs with Python, etc.).
  • Explicitly mention the lack of Linux/macOS support if the device is strictly Windows-based, to set expectations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions and screenshots for importing certificates on Windows clients only, using Windows-specific tools (File Explorer, Certificate Import Wizard). There are no instructions or examples for Linux or macOS clients, nor are cross-platform certificate import methods discussed. This creates friction for non-Windows users attempting to complete the task.
Recommendations
  • Add instructions for importing certificates on Linux (e.g., using 'update-ca-certificates', 'certutil', or manual placement in /etc/ssl/certs).
  • Include macOS steps (e.g., using Keychain Access to import certificates).
  • Provide cross-platform CLI examples (such as OpenSSL commands) for certificate handling.
  • Clearly indicate that the process applies to all major OSes, and structure instructions so that Windows, Linux, and macOS guidance are presented in parallel or in separate sections.
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-12 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 moderate Windows bias. Certificate import instructions are detailed for Windows (PowerShell and UI) before Linux, with more step-by-step guidance and screenshots for Windows. Linux instructions are brief, lack screenshots, and defer to external documentation. AzCopy usage examples are provided for both Windows and Linux, but Windows commands and options are shown first in each section. GUI-based tools (Storage Explorer) are described with Windows-centric screenshots and terminology. Troubleshooting and partner software configuration sections do not offer Linux-specific guidance.
Recommendations
  • Provide Linux certificate import instructions with equal detail, including step-by-step commands and screenshots for major distributions (e.g., Ubuntu, RHEL, CentOS).
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Include troubleshooting steps and partner software configuration guidance specific to Linux environments.
  • Add explicit macOS instructions where relevant, especially for certificate import and AzCopy usage.
  • Clarify that Storage Explorer is cross-platform and provide screenshots or notes for Linux/macOS usage.
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-12 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 notable Windows bias. Connection instructions and examples are presented for Windows first, with detailed steps using Windows tools (net use, File Explorer, Robocopy). The Linux section is brief, only showing a mount command (with a possible error, as it uses NFS instead of SMB), and lacks parity in copy tool examples or troubleshooting. Robocopy is recommended as the primary copy tool, with no Linux alternatives mentioned.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first.
  • Correct the Linux mount command to use the SMB protocol (e.g., 'mount -t cifs').
  • Provide Linux copy tool examples (e.g., 'cp', 'rsync', 'smbclient') and usage instructions.
  • Mention macOS compatibility and provide relevant examples if supported.
  • Include troubleshooting tips and supported SMB versions for Linux/macOS clients.
  • Reference Linux documentation or community resources for SMB mounting and copying.
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-12 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-specific instructions, tools (Robocopy), and examples are presented first and in greater detail, while Linux guidance is minimal and lacks parity. Windows commands and screenshots dominate, with only a single Linux mount example and no Linux file copy tool recommendations or examples. The use of Robocopy (Windows-only) is emphasized for performance and error handling, with no mention of Linux equivalents like rsync or cp for SMB. This creates friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
  • Provide Linux/macOS SMB file copy examples using rsync, cp, or smbclient, including recommended flags for performance and metadata preservation.
  • Include Linux/macOS screenshots or terminal output for mounting and copying to SMB shares.
  • Add a table or section comparing Windows and Linux/macOS tools for SMB file transfer, with pros/cons and usage notes.
  • List Linux/macOS commands for error handling, logging, and performance optimization when copying data.
  • Ensure that Linux/macOS instructions are presented with equal prominence and detail as Windows instructions.
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-12 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 primarily through its recommendation of Robocopy for ACL management and by referencing a PowerShell script (generateXMLFilesForExport.ps1) for XML file generation, without mentioning or providing Linux/macOS equivalents. No Linux tools or cross-platform alternatives are suggested for these tasks, and there are no examples or guidance for Linux users regarding ACL handling or XML generation.
Recommendations
  • Provide Linux/macOS alternatives for ACL management, such as referencing setfacl, getfacl, or rsync with ACL support.
  • Offer a cross-platform or Linux shell script (e.g., Bash, Python) for XML file generation, or mention how Linux users can generate XML files.
  • Explicitly state which steps and tools are platform-agnostic and which require platform-specific actions.
  • Add examples or notes for Linux/macOS users wherever Windows-specific tools (Robocopy, PowerShell scripts) are mentioned.
  • Consider listing platform-neutral options first, or in parallel, to avoid implicit prioritization of Windows.
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-12 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 equivalent Linux/macOS tools or instructions mentioned, nor are Linux/macOS-specific caveats or examples provided. Windows is prioritized in error handling and path length guidance.
Recommendations
  • Document equivalent Linux/macOS workflows for data copy and validation, including any official or recommended tools for those platforms.
  • Provide guidance on handling long file paths on Linux/macOS, including relevant filesystem or OS settings.
  • List Linux/macOS-specific caveats and troubleshooting steps, especially for path length and file naming issues.
  • If Windows-only tools are required, clarify their platform limitations and suggest alternatives or workarounds for Linux/macOS users.
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-12 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 exhibits a notable Windows bias. PowerShell is referenced heavily throughout, with explicit instructions and examples using 'Windows PowerShell' and paths like 'PS C:\Windows'. Installation instructions and sample outputs are Windows-centric, and there is frequent mention of Windows-specific tools and terminology. While Azure CLI is cross-platform, its usage is often demonstrated from a Windows PowerShell prompt, and there is little to no mention of Linux/macOS terminal environments or examples. There are no explicit Linux/macOS shell examples, nor are there instructions tailored for those platforms.
Recommendations
  • Provide explicit Linux/macOS shell examples for Azure CLI commands (e.g., using bash/zsh syntax, showing output from a Linux terminal).
  • Clarify that Azure CLI can be installed and used on Linux/macOS, and provide platform-specific installation instructions and links.
  • Avoid using Windows PowerShell as the default context for CLI examples; alternate or parallel examples for bash should be included.
  • Mention and demonstrate usage of Azure CLI in Linux/macOS environments, including sample outputs and screenshots where relevant.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS and provide instructions for installing PowerShell Core on those platforms, if relevant.
  • Use neutral file paths and prompts (e.g., $ or user@host:~$) in CLI examples, or provide both Windows and Linux/macOS variants.
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-12 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 toolsets are frequently presented first, with more detailed step-by-step guidance and screenshots for Windows users. Windows-specific tools (DataBoxDiskUnlock.exe) and PowerShell/Command Prompt usage are emphasized, while Linux instructions are sometimes less detailed or require external utilities (e.g., SEDUtil, dislocker) with less Microsoft-managed support. In several sections, Windows unlock steps precede Linux, and troubleshooting guidance is more robust for Windows. Linux instructions are present but sometimes rely on community tools or require more manual setup.
Recommendations
  • Present Windows and Linux instructions side-by-side or in parallel tabs to avoid Windows-first ordering.
  • Provide equally detailed step-by-step guidance, screenshots, and troubleshooting for Linux users.
  • Ensure all required Linux tools are clearly documented, with direct links and installation instructions.
  • Offer parity in Microsoft-supported utilities for Linux, reducing reliance on third-party tools.
  • Include Linux-specific troubleshooting sections and examples where only Windows troubleshooting is referenced.
  • Avoid referencing Windows tools or patterns (e.g., PowerShell) before Linux equivalents in general instructions.
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-12 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 notable Windows bias. Windows terminology (NT ACLs, SeBackupPrivilege, Administrator/SYSTEM accounts) is used throughout, with Windows-specific behaviors and privileges described in detail. Linux is mentioned only to note limitations (e.g., only Windows NT ACLs are transferred, default ACLs not transferred), and there are no Linux-specific examples or guidance. Windows tools and patterns are referenced, while Linux equivalents are absent.
Recommendations
  • Add explicit Linux copy tool examples (e.g., smbclient, rsync with SMB mounts) and instructions for preserving metadata/ACLs.
  • Clarify what 'Windows NT ACLs' means for Linux users and how Linux ACLs map (or do not map) to Azure Files.
  • Provide parity in troubleshooting and privilege requirements for Linux (e.g., what Linux user/group permissions are needed).
  • Include a table comparing Windows and Linux behaviors for ACL/metadata transfer.
  • List any Linux-specific limitations or workarounds for preserving metadata.
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-12 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 steps first, with detailed instructions and screenshots for Windows tools (File Explorer, net use), while Linux/NFS instructions are provided after and in less detail. Windows-specific tools and UI patterns are emphasized, and there is no parity in example depth or troubleshooting guidance for Linux/macOS users.
Recommendations
  • Present SMB (Windows) and NFS (Linux) connection instructions in parallel or alternate order to avoid Windows-first bias.
  • Provide equivalent screenshots and step-by-step guidance for Linux/macOS workflows (e.g., using Nautilus or Finder for browsing NFS shares).
  • Include troubleshooting steps and error examples for Linux/macOS users, similar to those shown for Windows.
  • Mention macOS compatibility and provide examples for mounting NFS shares on macOS.
  • Avoid exclusive use of Windows-specific tools (e.g., File Explorer, net use) without Linux/macOS alternatives.
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-12 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 moderate Windows bias. Windows-specific instructions (PowerShell, Server UI) are presented first and in greater detail for certificate import, with Linux guidance given in a more generic, less step-by-step manner. GUI-based tools (Storage Explorer) are described without clarifying cross-platform availability. AzCopy examples are provided for both Windows and Linux, but Windows commands are shown first. Some troubleshooting and partner software configuration steps are referenced via includes, which may or may not be platform-neutral, but the main text leans toward Windows-centric workflows.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal detail and prominence to both.
  • Provide explicit step-by-step Linux examples for certificate import, including common distributions (Ubuntu, RHEL, etc.), rather than referring users to external documentation.
  • Clarify the cross-platform availability of GUI tools like Storage Explorer and provide Linux/macOS installation instructions if applicable.
  • Alternate the order of Windows and Linux examples, or group them together under platform-specific headings.
  • Ensure all referenced 'includes' have Linux/macOS parity, or summarize their platform coverage in the main document.
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-12 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 significant Windows bias by exclusively providing instructions and examples using Windows PowerShell, including explicit references to opening an 'elevated Windows PowerShell session' and showing sample output from a Windows environment. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform PowerShell Core. This may hinder Linux/macOS users from following the steps or completing the task efficiently.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using Azure CLI, Bash scripts, or PowerShell Core.
  • Clarify that PowerShell Core is available cross-platform and provide sample commands for non-Windows environments.
  • Show both Windows and Linux/macOS sample outputs, or use generic output where possible.
  • Avoid language that assumes a Windows environment (e.g., 'Open an elevated Windows PowerShell session'); instead, use 'Open a terminal or PowerShell session'.
  • Provide guidance on installing required tools on Linux/macOS (e.g., Azure CLI, PowerShell Core).
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-12 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 Windows bias primarily through its use of Windows-centric terminology, log samples, and account names (e.g., WIN-DATABOXADMIN, NT AUTHORITY), and by referencing authentication mechanisms and event log formats that are specific to Windows. There are no explicit Linux/macOS examples, tools, or instructions for accessing or interpreting logs, nor is there mention of Linux-specific patterns for device access or log analysis. The only code sample is marked as 'powershell', and the audit log format is clearly derived from Windows event logs.
Recommendations
  • Add explicit instructions and examples for accessing and interpreting Data Box logs from Linux/macOS systems, including command-line tools (e.g., grep, awk, tail) and authentication mechanisms.
  • Include sample log entries or audit events from Linux-based access, such as NFS or SMB mounts from Linux clients, and clarify any differences in log format or location.
  • Provide parity in code samples, e.g., show how to parse verbose logs using Bash, Python, or other cross-platform tools.
  • Mention Linux/macOS equivalents for device credential access and clarify if any features are Windows-only.
  • Review and update terminology to be OS-neutral where possible, or explicitly call out OS-specific behaviors.
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-12 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 instructions and examples (including screenshots and detailed steps) are presented first and in greater detail, with explicit use of Windows-specific tools like Robocopy and File Explorer. Linux instructions are minimal, lacking equivalent detail, examples, and recommended tools for file copying. The only Linux copy example is a mount command, with no guidance on optimal copy tools or performance tuning. There is no parity in troubleshooting, error log viewing, or performance optimization for Linux users.
Recommendations
  • Provide detailed Linux copy instructions, including recommended tools (e.g., rsync, cp, smbclient) and example commands for copying data after mounting SMB shares.
  • Include performance optimization guidance for Linux (e.g., parallel rsync, tuning mount options, recommended thread counts).
  • Add troubleshooting steps and error log viewing instructions for Linux users.
  • Present Windows and Linux instructions in parallel sections, or alternate which platform is shown first.
  • Include screenshots or terminal output examples for Linux workflows.
  • Mention cross-platform tools (e.g., AzCopy) where applicable, and provide usage examples for both Windows and Linux.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →