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 101-125 of 231 flagged pages
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-local-web-ui-admin.md ...b/main/articles/databox/data-box-local-web-ui-admin.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (e.g., File Explorer) is used exclusively when describing file access, and references to Active Directory and Backup Operators are made without Linux equivalents. The SMB protocol is discussed without mention of Linux mounting tools or commands. There are no Linux-specific instructions, screenshots, or references to Linux tools (such as smbclient, mount.cifs, or NFS mounting commands), nor is there guidance for Linux users on accessing shares or manifests. All examples and UI references assume a Windows environment.
Recommendations
  • Add Linux-specific instructions and examples for accessing SMB/NFS shares (e.g., using smbclient, mount.cifs, or NFS mount commands).
  • Include references to Linux file managers (such as Nautilus, Dolphin) alongside File Explorer.
  • Provide guidance on handling credentials and manifests on Linux systems, including command-line and GUI options.
  • Mention Linux equivalents for Active Directory concepts, or clarify when features are Windows-only.
  • Ensure screenshots and terminology are inclusive of both Windows and Linux environments.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-export-ordered.md ...ain/articles/databox/data-box-deploy-export-ordered.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates Windows bias primarily through the exclusive mention of Windows tools (Robocopy, Powershell script) for tasks such as applying ACLs and generating XML files for export. There are no Linux equivalents or examples provided for these operations. The only tool recommended for ACL application is Robocopy, which is Windows-specific, and the sample script for XML generation is a Powershell script, also Windows-centric. No Linux command-line tools (e.g., rsync, cp, getfacl/setfacl, Bash scripts) are referenced, and no Linux usage patterns or examples are given for these key steps.
Recommendations
  • Provide Linux equivalents for all Windows-specific tools mentioned (e.g., suggest rsync or setfacl for ACL application, Bash or Python scripts for XML generation).
  • Include explicit Linux command-line examples alongside Windows examples for all major steps, especially for data copy and scripting.
  • Reference cross-platform or Linux-native tools in the prerequisites and guidance sections, not just Windows tools.
  • Clarify which steps are OS-agnostic and which require OS-specific tooling, and ensure Linux users are not left without guidance.
  • Add a section or tab for Linux users detailing the process and recommended tools for each major operation.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-deploy-copy-data-from-vhds.md ...s/databox/data-box-heavy-deploy-copy-data-from-vhds.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows/SMB connection instructions first, using Windows-specific tools and commands (e.g., 'net use', File Explorer, Windows + R), and providing more detailed step-by-step guidance for Windows users. Linux/NFS instructions are present but less detailed and appear after the Windows section. There is also an emphasis on Windows command-line patterns and graphical tools, with less parity for Linux equivalents.
Recommendations
  • Present SMB and NFS connection instructions in parallel or alternate the order to avoid always listing Windows first.
  • Provide Linux SMB connection instructions (e.g., using 'mount -t cifs' or 'smbclient') for parity with Windows SMB examples.
  • Include Linux graphical file manager instructions (e.g., Nautilus, Dolphin) for accessing SMB shares, similar to the Windows File Explorer example.
  • Offer PowerShell and Bash command examples side-by-side for common tasks.
  • Clarify that both Windows and Linux are equally supported and provide troubleshooting steps for both platforms.
  • Expand Linux/NFS instructions to include more details, screenshots, and common error handling, matching the depth of Windows guidance.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-file-acls-preservation.md ...in/articles/databox/data-box-file-acls-preservation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 prioritizing Windows terminology, tools, and patterns. Windows-specific ACLs (NT ACLs, DACLs, SACLs, SeBackupPrivilege) are described in detail, while Linux equivalents are either omitted or mentioned only in relation to Windows features (e.g., Linux clients only transfer Windows NT ACLs). There are no Linux-specific examples, tools, or guidance for preserving Linux ACLs, attributes, or timestamps. Default ACL transfer is only supported for Windows clients, with Linux support explicitly excluded.
Recommendations
  • Add Linux-specific examples and instructions for copying data with preservation of metadata (e.g., using smbclient, rsync, or cp with appropriate flags).
  • Explain the limitations and differences in ACL/attribute/timestamp preservation for Linux clients, including what Linux ACLs (POSIX ACLs) are supported or not.
  • Provide guidance on how Linux administrators can verify and troubleshoot metadata preservation, including any required permissions or configuration.
  • List Linux tools and commands alongside Windows tools, and avoid using Windows terminology exclusively (e.g., clarify what 'Windows NT ACLs' means for Linux users).
  • Include a comparison table summarizing metadata preservation capabilities for both Windows and Linux clients.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-troubleshoot-share-access.md ...articles/databox/data-box-troubleshoot-share-access.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and screenshots are based on Windows tools and interfaces (e.g., 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 procedures are used exclusively and presented as the default or only option.
Recommendations
  • Add Linux and macOS examples for connecting to SMB shares (e.g., using smbclient, mount.cifs, or Finder).
  • Include troubleshooting steps for Linux clients, such as checking syslog, dmesg, or Samba logs for authentication failures.
  • Describe how to adjust SMB authentication settings on Linux (e.g., via smb.conf options like client min protocol, client max protocol, or ntlm auth).
  • Provide parity in error messages and troubleshooting flows for non-Windows platforms.
  • Mention cross-platform considerations for SMB (e.g., differences in supported authentication mechanisms, file system permissions, and group policy equivalents).
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-limits.md ...ocs/blob/main/articles/databox/data-box-disk-limits.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd) and providing instructions only for enabling long paths on Windows clients. There are no equivalent examples, instructions, or tool references for Linux or macOS environments, nor is there guidance for handling long paths or data copy operations on non-Windows platforms.
Recommendations
  • Include Linux and macOS equivalents for data copy and validation tools, or clarify cross-platform support.
  • Provide instructions for handling long file paths on Linux and macOS clients, including relevant OS limits and configuration steps.
  • Add examples and troubleshooting guidance for data copy operations on Linux and macOS, ensuring parity with Windows instructions.
  • Explicitly mention supported operating systems for all referenced tools and features, and offer alternatives or workarounds for non-Windows users.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-how-to-set-data-tier.md ...main/articles/databox/data-box-how-to-set-data-tier.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing instructions and examples using Windows PowerShell, including explicit references to elevated Windows PowerShell sessions and Windows-specific output. There are no equivalent examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting tools. The documentation assumes a Windows environment and does not mention or prioritize Linux-compatible methods.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Provide Bash script examples for blob tiering operations, demonstrating how to use REST API or Azure CLI.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, and provide instructions for those platforms.
  • Remove or generalize references to 'elevated Windows PowerShell session' and Windows-specific paths/output.
  • Include a section comparing scripting options for both Windows and Linux environments, helping users choose the best tool for their platform.
  • Ensure that all steps and sample outputs are platform-neutral or provide alternatives for each major OS.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-overview.md ...e-docs/blob/main/articles/databox/data-box-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Data Box demonstrates a Windows bias by referencing Windows-centric migration scenarios (e.g., SQL Server, VM farm), mentioning Windows tools (SharePoint Migration Tool, Azure File Sync) before Linux equivalents, and omitting explicit Linux or cross-platform examples for device setup, data copy, and workflow steps. There is no mention of Linux-specific commands, tools, or guidance for mounting shares, copying data, or integrating with Linux-based environments, despite the prevalence of Linux in enterprise and cloud workloads.
Recommendations
  • Include explicit Linux examples for mounting SMB shares (e.g., using mount.cifs), copying data (e.g., rsync, cp), and network configuration.
  • Mention Linux-based migration scenarios (e.g., migrating data from Linux servers, NFS shares) alongside Windows scenarios.
  • List Linux-compatible tools and workflows (e.g., Azure CLI, third-party Linux backup solutions) in parallel with Windows tools.
  • Add guidance for troubleshooting and optimizing Data Box usage on Linux systems, including permissions, SMB version compatibility, and performance tuning.
  • Ensure that all workflow steps (setup, copy, return) provide both Windows and Linux instructions or references.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-export-logs.md ...ocs/blob/main/articles/databox/data-box-export-logs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several ways. It references Windows-specific account names (e.g., WIN-DATABOXADMIN), NT AUTHORITY, and logon processes typical of Windows environments. Audit log samples and explanations are tailored to Windows authentication and event log formats. There are no examples or instructions for Linux environments, nor are Linux tools, patterns, or log formats mentioned. The only code sample is XML output, but the context and explanations are Windows-centric. There is no mention of how to access, interpret, or use these logs on Linux systems, nor any parity in troubleshooting or operational steps for Linux users.
Recommendations
  • Include Linux-specific examples for accessing and interpreting logs, such as using Linux authentication logs or syslog.
  • Mention Linux account names and logon processes alongside Windows equivalents in audit log explanations.
  • Provide guidance for Linux users on how to mount, access, and copy data from Data Box devices, including relevant commands (e.g., mount, cp, rsync).
  • Add troubleshooting steps and log interpretation for Linux environments.
  • Ensure that references to tools and patterns (e.g., Azure portal, device credentials) are not exclusively Windows-centric, and clarify cross-platform applicability where relevant.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-logs.md ...azure-docs/blob/main/articles/databox/data-box-logs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Audit Log Windows Format
Summary
The documentation page demonstrates a moderate Windows bias. While most instructions are platform-neutral and focus on Azure portal, logs, and file formats, the audit log sample and log explanations use Windows-centric terminology (e.g., 'WIN-DATABOXADMIN', NT AUTHORITY, Windows event log fields). There is no mention of Linux-specific audit log formats or examples, nor are Linux-native tools referenced for log inspection or verification. The documentation does not provide parity for Linux users in terms of log analysis or troubleshooting, and the audit log format is presented in a way that assumes familiarity with Windows authentication and event logging.
Recommendations
  • Add Linux-specific audit log samples, showing how Data Box logs appear when accessed from Linux clients (e.g., NFS, SMB mounts, syslog entries).
  • Include instructions or examples for inspecting logs using Linux-native tools (such as grep, tail, less, or journalctl) alongside Azure portal guidance.
  • Clarify whether the log formats and authentication events are identical or different when Data Box is accessed from Linux, and document any differences.
  • Reference troubleshooting steps and verification tools that are available or recommended for Linux environments, not just Windows.
  • Explicitly mention Linux compatibility and provide parity in examples for both platforms where relevant, especially in sections about log analysis and device access.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-troubleshoot-data-upload.md .../articles/databox/data-box-troubleshoot-data-upload.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell in recovery steps, omitting Linux or cross-platform CLI examples, and generally assuming a Windows-centric workflow. No Linux-specific tools, commands, or troubleshooting patterns are provided, and PowerShell is mentioned as the default for key vault recovery. This may hinder Linux users or those using non-Windows environments from following troubleshooting steps effectively.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell-based instructions, especially for key vault recovery and management.
  • Explicitly mention that troubleshooting steps can be performed on Linux, macOS, or Windows, and clarify any platform-specific requirements.
  • Include examples using Bash or shell scripts where appropriate, alongside PowerShell.
  • Reference cross-platform tools and documentation (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add troubleshooting notes or links for common Linux issues encountered during Data Box uploads.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-deploy-copy-data.md ...ain/articles/databox/data-box-disk-deploy-copy-data.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All file copy examples use Windows-native tools (Robocopy, File Explorer), and the Data Box Disk Split Copy and Validation tools are only available for Windows. There are no Linux-specific examples or equivalent Linux tool recommendations for copying or validating data. Linux users are only briefly mentioned, with no guidance or parity in tooling or workflow.
Recommendations
  • Provide equivalent Linux command-line examples for copying data, such as using cp, rsync, or smbclient.
  • Document how to mount Data Box Disks on Linux, including any required SMB/CIFS options.
  • Recommend and provide examples of Linux-compatible checksum/validation tools (e.g., sha256sum, md5sum) and describe how to use them for data integrity verification.
  • Clarify any limitations or differences for Linux users, and offer troubleshooting steps specific to Linux environments.
  • Where Windows-only tools are referenced, suggest open-source or cross-platform alternatives where possible.
  • Ensure that screenshots and walkthroughs include Linux desktop or CLI environments where appropriate.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-system-requirements.md .../articles/databox/data-box-disk-system-requirements.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by listing Windows operating systems and tools before Linux equivalents, providing a detailed list of required Windows software (including PowerShell, .NET Framework, and BitLocker) while only briefly mentioning Linux requirements. Windows-specific tools and patterns (e.g., PowerShell, BitLocker) are highlighted, and there is no parity in the depth of explanation or tool listing for Linux environments.
Recommendations
  • List Linux operating systems and requirements before or alongside Windows, not after.
  • Provide equal detail for Linux client requirements, including versions and installation instructions for required tools.
  • Include Linux command-line examples or references where Windows tools (like PowerShell) are mentioned.
  • Mention Linux-native disk encryption and management tools with the same prominence as BitLocker.
  • Ensure parity in troubleshooting and validation steps for both Windows and Linux clients.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-limits.md ...ure-docs/blob/main/articles/databox/data-box-limits.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Windows-specific features and limitations (such as ReFS metadata and SMB protocol), describing the Data Box as a Windows-based device, and omitting Linux-specific guidance or examples. There are no Linux or cross-platform instructions or caveats, and Windows terminology is used exclusively when discussing file system and protocol compatibility.
Recommendations
  • Include explicit information about Linux compatibility, such as supported file systems (e.g., ext4, XFS) and any caveats when using Data Box with Linux clients.
  • Provide examples and limitations for both Windows and Linux environments, especially regarding file naming, protocol support (e.g., NFS vs SMB), and case sensitivity.
  • Clarify whether features like ReFS metadata space consumption are relevant only to Windows or if there are analogous considerations for Linux file systems.
  • Add a section or table comparing Windows and Linux behaviors and limitations when using Data Box.
  • Mention Linux tools/utilities (e.g., rsync, NFS mount commands) alongside Windows tools where relevant.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-export-copy-data.md ...n/articles/databox/data-box-deploy-export-copy-data.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows connection instructions and tools (such as 'net use', File Explorer, and Robocopy) first and in detail, while Linux instructions are minimal and potentially inaccurate (using NFS instead of SMB). Linux copy tool examples are missing, and only Windows-specific tools are referenced for data copy operations.
Recommendations
  • Provide Linux connection instructions using the correct SMB mounting command (e.g., 'mount -t cifs ...') instead of NFS.
  • Include Linux copy tool examples (such as 'cp', 'rsync', or 'smbclient') alongside Robocopy.
  • Present Windows and Linux instructions in parallel sections or give equal prominence to both.
  • Reference cross-platform or Linux-native tools for file copying, not just Windows tools.
  • Ensure all screenshots and UI instructions have Linux equivalents or clarify OS-specific steps.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-limits.md ...ocs/blob/main/articles/databox/data-box-disk-limits.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd) and providing instructions only for enabling long paths on Windows clients, without mentioning Linux or macOS equivalents. There are no examples or guidance for Linux users regarding path length issues, validation, or copy tools, and no mention of cross-platform alternatives.
Recommendations
  • Include equivalent instructions for handling long file paths on Linux and macOS clients, or clarify if such limitations do not apply.
  • Mention or provide cross-platform data copy and validation tools, or explicitly state if the provided tools are Windows-only.
  • Add Linux/macOS-specific caveats or best practices for copying data to Data Box Disk, especially regarding file system compatibility and naming conventions.
  • If the Data Box Disk workflow is only supported on Windows, state this clearly at the beginning of the documentation. Otherwise, ensure parity in examples and tool references for all supported platforms.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-how-to-set-data-tier.md ...main/articles/databox/data-box-how-to-set-data-tier.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing instructions and examples using Windows PowerShell, including explicit references to 'elevated Windows PowerShell session' and Windows-specific output. No Linux or cross-platform CLI examples (such as Azure CLI, Bash, or Python) are provided, and the workflow assumes the user is on a Windows system with PowerShell 5.0 or higher.
Recommendations
  • Add equivalent examples using Azure CLI (az storage blob update) that work on Linux, macOS, and Windows.
  • Provide Bash and/or Python script examples for blob tiering to support non-Windows environments.
  • Avoid language such as 'Open an elevated Windows PowerShell session'; instead, use neutral phrasing or provide parallel instructions for Linux/macOS terminals.
  • Include a section or callout for Linux/macOS users, clarifying how to perform the same operations using cross-platform tools.
  • Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-copy-data.md ...lob/main/articles/databox/data-box-deploy-copy-data.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows (and Windows-specific tools like Robocopy) first and in greater detail, providing comprehensive step-by-step instructions and command output for Windows users, while Linux instructions are minimal and lack equivalent detail or examples. Linux users are only given a basic mount command, with no guidance on file copy tools, performance tuning, or sample output, and no mention of Linux-native alternatives to Robocopy.
Recommendations
  • Provide Linux examples for copying data, such as using rsync or cp, including sample commands and recommended flags for performance and metadata preservation.
  • Include sample output for Linux copy operations, similar to the Robocopy output shown for Windows.
  • Offer performance tuning advice for Linux file copy tools (e.g., rsync options for parallelism, preserving ACLs, etc.), and compare them to the Robocopy recommendations.
  • Present Windows and Linux instructions in parallel sections or tables, rather than always listing Windows first and in more detail.
  • Mention and link to Linux-specific documentation or community resources for troubleshooting SMB mounts and file copy issues.
  • Clarify which features (such as metadata preservation) are supported or unsupported on Linux, and provide workarounds or references where possible.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-copy-data-via-copy-service.md .../databox/data-box-deploy-copy-data-via-copy-service.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric patterns and tools. Examples include only providing SMB paths in Windows UNC format (\\Server\Share), specifying username formats in Windows domain style, and referencing Windows UI actions (right-click, Properties, Security tab) for permissions. There are no Linux/NFS examples or guidance, and compatibility with non-Windows NAS devices is explicitly stated as not officially supported.
Recommendations
  • Provide explicit examples for Linux environments, such as NFS mount paths and Linux-compatible username formats.
  • Include instructions for setting permissions and accessing shares from Linux systems (e.g., using chmod/chown, setfacl, or Linux SMB/NFS clients).
  • Clarify the extent of support for non-Windows NAS devices and, if possible, provide troubleshooting or best-practices for Linux users.
  • When referencing file paths or commands, offer both Windows and Linux syntax where applicable.
  • If the service is truly Windows-only, state this clearly at the beginning to set user expectations.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-quickstart-portal.md ...ob/main/articles/databox/data-box-quickstart-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows a Windows bias in the data copy section, where Windows tools (Robocopy) are mentioned first and in more detail, with a direct link to Robocopy documentation. Linux/Unix equivalents (cp, rsync) are mentioned only as alternatives for NFS hosts, with no further explanation or links. There are no explicit Linux command-line examples, and the documentation assumes familiarity with Windows SMB paths and tools. No Linux-specific troubleshooting or mounting instructions are provided.
Recommendations
  • Provide Linux/Unix command-line examples for copying data (e.g., mounting SMB shares with mount.cifs, using rsync/cp for both SMB and NFS).
  • Include links to Linux/Unix documentation for relevant tools (e.g., rsync, mount.cifs, NFS client setup).
  • Mention Linux/Unix tools and workflows before or alongside Windows tools to avoid 'windows_first' ordering.
  • Add troubleshooting tips for Linux/Unix environments (e.g., handling SMB credentials, SELinux, firewall issues).
  • Clarify that both Windows and Linux hosts are supported, and provide parity in detail and guidance for both platforms.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-file-acls-preservation.md ...ticles/databox/data-box-disk-file-acls-preservation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 tools (robocopy) and detailed usage instructions first, with extensive examples and option explanations. In contrast, Linux instructions are minimal, lacking detailed examples for copying metadata (ACLs, attributes, timestamps) and omitting step-by-step guidance for Linux-specific tools (e.g., smbcacls, cifsacl). The Linux section does not provide equivalent depth or clarity, making it harder for Linux users to achieve parity in functionality.
Recommendations
  • Provide Linux examples with the same level of detail as the Windows section, including step-by-step commands for copying both data and metadata (ACLs, attributes, timestamps).
  • Include explanations of relevant Linux tools (e.g., smbcacls, cifsacl, getfacl/setfacl) and their options, similar to the robocopy option table.
  • Present Linux and Windows instructions in parallel sections or side-by-side, rather than Windows-first, to avoid the perception of prioritizing one platform.
  • Clarify any limitations or differences in metadata preservation between Windows and Linux up front, and offer workarounds or best practices for Linux users.
  • Add links to Linux-specific documentation or tutorials for copying ACLs and metadata to Azure Files.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-troubleshoot-rest.md ...ob/main/articles/databox/data-box-troubleshoot-rest.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by listing Windows-specific tools and paths before Linux equivalents, providing more detailed troubleshooting steps for Windows (e.g., AzCopy for Windows has its own section before Linux), and referencing Windows infrastructure (e.g., time.windows.com) without mentioning Linux alternatives. Some sections lack parity in Linux-specific troubleshooting details or examples.
Recommendations
  • Ensure that Linux and Windows troubleshooting sections are presented with equal prominence and detail, possibly by combining them or alternating their order.
  • When referencing file paths (such as hosts file), always present both Windows and Linux paths together, or alternate their order to avoid Windows-first bias.
  • For system-level operations (like certificate import), provide explicit Linux commands and steps, not just generic instructions.
  • When referencing time synchronization (e.g., time.windows.com), mention Linux NTP pools (such as pool.ntp.org) as alternatives.
  • Include PowerShell and Bash (or shell) command examples side by side where applicable.
  • Review all sections to ensure Linux users are not left with less actionable or less detailed guidance compared to Windows users.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-logs.md ...azure-docs/blob/main/articles/databox/data-box-logs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools, logs, and patterns (e.g., Windows account names, domains, and log formats in audit logs), and by omitting explicit Linux or cross-platform command-line examples for log inspection or troubleshooting. The documentation assumes familiarity with Windows conventions and does not provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Include explicit Linux examples for accessing and interpreting logs (e.g., using Linux commands to view error.xml, BOM, or audit logs).
  • Provide sample audit log entries from Linux/NFS access, not just Windows event logs.
  • Clarify that Data Box supports both SMB (Windows) and NFS (Linux/Unix) protocols, and offer troubleshooting/logging examples for both.
  • When referencing file paths or log formats, show both Windows-style (\path\file) and Linux-style (/path/file) examples.
  • Add guidance for Linux users on how to download and inspect logs, including recommended tools (e.g., cat, less, grep) and any differences in log content or access.
  • Ensure that any scripts or tools referenced (e.g., CRC checksum tool) are cross-platform or provide Linux-specific alternatives/instructions.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-customer-managed-encryption-key-portal.md ...box/data-box-customer-managed-encryption-key-portal.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell-specific commands (e.g., Get-AzKeyVault), linking to PowerShell-based recovery instructions, and omitting Linux or cross-platform CLI alternatives in troubleshooting and recovery steps. The only command-line tool mentioned is PowerShell, and there are no Bash, Azure CLI, or Linux-native instructions or examples. This may hinder Linux or cross-platform users from following the documentation effectively.
Recommendations
  • For every PowerShell example or reference, provide an equivalent Azure CLI (az) command, which is cross-platform and works on Linux, macOS, and Windows.
  • In troubleshooting sections, link to both PowerShell and Azure CLI documentation for tasks like key vault recovery and URI retrieval.
  • Avoid referencing only Windows tools (e.g., Get-AzKeyVault) in command-line contexts; always include or prefer cross-platform alternatives.
  • Explicitly state that the Azure portal and Azure CLI are supported on all major operating systems, and provide links to installation guides for Linux/macOS users.
  • Where screenshots or UI steps are shown, clarify that the Azure portal experience is the same across platforms, and mention any OS-specific caveats if they exist.
GitHub Create Pull Request
Databox https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-copy-data-from-vhds.md ...rticles/databox/data-box-deploy-copy-data-from-vhds.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 🔧 Windows Tools
Summary
The documentation presents a clear Windows-first bias: the SMB/Windows workflow is described first and in greater detail, with explicit step-by-step instructions, screenshots, and use of Windows-specific tools (e.g., 'net use', File Explorer, Windows + R). The Linux/NFS section is shorter, less detailed, and lacks parity in terms of troubleshooting, verification, and user experience guidance. There is also a reliance on Windows command-line tools and GUI patterns, with Linux equivalents either missing or less emphasized.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them in parallel tabs to avoid always putting Windows first.
  • Provide equally detailed, step-by-step instructions for Linux/NFS workflows, including screenshots of typical Linux file managers (e.g., Nautilus, Dolphin) and terminal outputs.
  • Include Linux command-line equivalents for all Windows commands (e.g., show how to use 'mount', 'df', 'ls', etc., to verify connection and file transfer).
  • Add troubleshooting and verification steps specific to Linux, such as checking mount status, permissions, and log files.
  • Avoid referencing Windows GUI patterns (e.g., 'Windows + R', File Explorer) without Linux equivalents; instead, show how to access shares via Linux file managers or command line.
  • Ensure that all error scenarios and their resolutions are covered for both platforms, not just Windows.
GitHub Create Pull Request
← Previous Page 5 of 10 Next →