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 151-175 of 231 flagged pages
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through its exclusive use of Windows-centric terminology, log formats, and user account references (e.g., 'WIN-DATABOXADMIN', 'NT AUTHORITY', 'Workgroup'). There are no explicit PowerShell commands or Windows command-line examples, but the audit log samples and explanations are clearly based on Windows event logs and authentication models. There are no Linux-specific examples, log samples, or instructions, and the documentation does not mention or demonstrate parity for Linux users or administrators.
Recommendations
- Include Linux-specific log samples, such as syslog or auditd entries, to illustrate how Data Box events appear on Linux systems.
- Add instructions or examples for tracking and auditing Data Box events on Linux, including relevant tools (e.g., journalctl, grep, auditctl).
- Clarify whether the Data Box device supports Linux authentication and logging mechanisms, and if so, provide guidance for Linux administrators.
- When presenting sample logs or user accounts, provide both Windows and Linux variants (e.g., show a sample with a Linux user and group, or NFS authentication).
- Explicitly mention any differences in experience or available features between Windows and Linux environments, if applicable.
- Ensure that troubleshooting and verification steps (such as checksum validation) include Linux command-line examples (e.g., using sha256sum or cksum).
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools (Robocopy) are mentioned by name and linked, while Linux equivalents (cp, rsync) are referenced generically without links or examples. Windows hosts and SMB are described first, with NFS/Linux as a secondary note. There are no explicit Linux command examples or screenshots, and no mention of Linux-specific troubleshooting or nuances. The documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Provide explicit Linux command-line examples for data copy (e.g., sample rsync and cp commands with flags).
- Include links to Linux documentation for cp and rsync, similar to the Robocopy link.
- Add screenshots or step-by-step instructions for Linux/NFS hosts, not just Windows/SMB.
- Mention Linux/NFS options before or alongside Windows/SMB, not after.
- Include troubleshooting tips or common issues for Linux/NFS environments.
- Clarify that both Windows and Linux hosts are fully supported, and provide parity in documentation depth.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-quickstart-export.md
...ob/main/articles/databox/data-box-quickstart-export.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Copy data' section by mentioning Windows/SMB/Robocopy first and providing a link to Robocopy documentation, while Linux/NFS commands are only briefly referenced without examples or links. There are no detailed Linux copy command examples or parity in tool guidance. The rest of the documentation is largely OS-neutral, but the copy step lacks Linux parity.
Recommendations
- Provide explicit Linux/NFS copy examples, such as sample cp and rsync commands, alongside the Windows/Robocopy example.
- Include links to official documentation for Linux tools (e.g., GNU cp, rsync) similar to the Robocopy link.
- Present Windows and Linux instructions in parallel, or in separate clearly-labeled sections, to ensure equal visibility.
- Avoid listing Windows tools or instructions before Linux equivalents; consider alphabetical or scenario-based ordering.
- Clarify any OS-specific requirements or differences in supported protocols (SMB/NFS) and provide troubleshooting tips for both platforms.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a Windows-first bias by listing Windows-specific tools, paths, and troubleshooting steps before their Linux equivalents. Sections such as 'Errors seen in AzCopy for Windows' precede 'AzCopy for Linux', and Windows paths (e.g., C:\Windows\System32\drivers\etc\hosts) are mentioned first. Some recommendations reference Windows-specific services (e.g., time.windows.com) without Linux alternatives. There is also a lack of parity in example commands and troubleshooting steps for Linux, especially in sections not explicitly labeled for Linux.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel tables to ensure equal visibility.
- When referencing file paths or system actions (e.g., editing hosts file), always provide both Windows and Linux examples together.
- Avoid using Windows-specific services (e.g., time.windows.com) as the only example; mention Linux-appropriate NTP servers or general best practices for both OSes.
- Include explicit Linux troubleshooting steps and example commands wherever Windows examples are given (e.g., importing certificates into the system store).
- Where possible, use cross-platform tools and terminology, or clarify when a tool or step is OS-specific.
- Review section ordering to avoid always listing Windows before Linux; consider alternating or grouping by task rather than OS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All troubleshooting steps, error messages, and examples reference Windows tools (e.g., net use, Event Viewer, Local Security Policy, Registry Editor) and Windows-specific concepts (Group Policy, Active Directory OUs, GPOs). There are no Linux or macOS equivalents provided for connecting to SMB shares, diagnosing issues, or adjusting authentication settings. The documentation assumes the user is on Windows and does not address cross-platform scenarios.
Recommendations
- Add Linux and macOS examples for connecting to SMB shares (e.g., using smbclient or mount.cifs).
- Include troubleshooting steps for common Linux SMB errors and how to view relevant logs (e.g., dmesg, journalctl, /var/log/syslog, or /var/log/samba).
- Document how to adjust SMB authentication settings on Linux (e.g., editing /etc/samba/smb.conf or mount options for NTLMv2).
- Mention Linux equivalents for Windows tools (e.g., Event Viewer → journalctl/log files, net use → smbclient/mount.cifs).
- Reorganize sections to present both Windows and Linux solutions in parallel, or clearly indicate which steps are OS-specific.
- Clarify that the documentation is currently Windows-centric and provide links to cross-platform SMB troubleshooting resources if available.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-audit-logs.md
...docs/blob/main/articles/databox/data-box-audit-logs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: it repeatedly emphasizes that Data Box is a Windows-based device, all log event providers are Windows-specific (e.g., Microsoft-Windows-Kernel-General, BitLocker, PowerShell), and there are no references to Linux tools, patterns, or equivalents. No Linux or cross-platform log event examples or access methods are provided.
Recommendations
- Clarify early in the documentation that Data Box is a Windows-based appliance, but explicitly state whether Linux users can interact with the device or logs in any way.
- If Data Box supports any Linux-compatible protocols (e.g., SMB, NFS, REST APIs), provide examples or references for Linux users.
- If log access or troubleshooting can be performed from Linux systems (e.g., via SMB mounts, SCP, or REST API), add Linux command-line examples alongside any PowerShell or Windows instructions.
- If the device is strictly Windows-only, add a note to set expectations for Linux users and suggest alternative workflows or tools where possible.
- Review all event provider and tool references to see if there are cross-platform equivalents or abstractions that could be mentioned (e.g., general log formats, open standards).
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for importing certificates on Windows clients only, using Windows-specific tools (File Explorer, Certificate Import Wizard). There are no equivalent instructions or examples for Linux or macOS clients, nor are cross-platform certificate import methods discussed. This creates friction for non-Windows users who need to access the Data Box device securely.
Recommendations
- Add instructions for importing certificates on Linux (e.g., using 'openssl' and 'update-ca-certificates' or manual trust store updates) and macOS (e.g., using Keychain Access or 'security' CLI).
- Include cross-platform notes or links to official guidance for certificate management on Linux and macOS.
- Present platform-specific instructions in parallel sections, not Windows-first.
- Mention any platform-specific limitations or requirements for Data Box access.
Databox
Tutorial to order Azure Data Box | Microsoft Docs
.../blob/main/articles/databox/data-box-deploy-ordered.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a notable Windows bias, especially in the Azure CLI and PowerShell sections. Windows PowerShell is referenced as the default shell for CLI usage, and all CLI and PowerShell code samples use Windows-style prompts and paths (e.g., PS C:\Windows>). Installation instructions and examples for Azure CLI and PowerShell modules are Windows-centric, with explicit references to MSI installers and Windows PowerShell versions. There is no mention of Linux/macOS equivalents, nor are Bash or non-Windows terminal examples provided, despite Azure CLI and Cloud Shell supporting Bash. This may create friction for Linux/macOS users, who must adapt instructions and commands for their environments.
Recommendations
- Provide explicit instructions and examples for Linux/macOS users, including Bash terminal usage and installation steps (e.g., apt, yum, Homebrew).
- Show CLI examples using generic shell prompts ($) or Bash, not just Windows PowerShell (PS C:\Windows>).
- Mention and demonstrate the use of Azure CLI in Bash (locally and in Cloud Shell), including sample commands and outputs.
- Clarify that Azure CLI and PowerShell modules are cross-platform, and link to platform-specific installation guides.
- Avoid language that implies Windows is the default or preferred platform for CLI usage.
Databox
Azure Data Box Disk limits | Microsoft Docs
...ocs/blob/main/articles/databox/data-box-disk-limits.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation references Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd) and provides guidance only for enabling long paths on Windows clients. There are no equivalent instructions, examples, or tool references for Linux or macOS users, nor any mention of how to handle long paths or validation on those platforms. Windows is prioritized in troubleshooting and operational guidance.
Recommendations
- Document Linux/macOS equivalents for data validation and split copy operations, or clarify if the provided tools are cross-platform.
- Provide instructions for handling long paths on Linux/macOS, including relevant OS settings or workarounds.
- Include examples and troubleshooting steps for Linux/macOS environments where applicable.
- Explicitly state platform support for all referenced tools and features.
Databox
Tutorial to export data from Azure Data Box | Microsoft Docs
...ain/articles/databox/data-box-deploy-export-ordered.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (Robocopy) for handling ACLs and providing a PowerShell script for XML generation, without mentioning or providing Linux/macOS equivalents or alternatives. No Linux/macOS-specific tools, commands, or examples are given for key tasks such as ACL management or XML file creation.
Recommendations
- Include Linux/macOS equivalents for ACL management, such as using 'rsync', 'setfacl', or 'getfacl' for file permissions.
- Provide a Bash or Python script example for XML file generation alongside the PowerShell script.
- Explicitly mention cross-platform options for all steps involving file transfer, scripting, and permissions.
- Add guidance for Linux/macOS users on how to perform each major step, especially those currently referencing Windows-only tools.
Databox
Tutorial: Copy from VHDs to managed disks
...rticles/databox/data-box-deploy-copy-data-from-vhds.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. The SMB (Windows) connection instructions are presented first and in greater detail, including screenshots and explicit use of Windows tools (net use, File Explorer, Windows + R). The Linux/NFS section is present and functional, but less detailed and lacks parity in visual aids and troubleshooting. There are no explicit Linux copy command examples (e.g., rsync, cp), and the overall flow assumes familiarity with Windows environments.
Recommendations
- Alternate the order of SMB (Windows) and NFS (Linux) instructions, or present them in parallel to avoid privileging Windows.
- Provide equivalent screenshots and step-by-step instructions for Linux/NFS workflows, including mounting via GUI (e.g., GNOME Files) if possible.
- Include Linux-specific copy command examples (e.g., cp, rsync) for copying VHDs after mounting.
- Mention macOS compatibility and steps if supported.
- Ensure troubleshooting and error screenshots/examples are provided for both Windows and Linux.
- Use neutral language and avoid assuming the user is on Windows.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on the Azure portal (GUI), which is platform-agnostic, but command-line troubleshooting and references are almost exclusively Windows/PowerShell-centric. For example, error resolutions reference PowerShell cmdlets (Get-AzKeyVault) and provide links to PowerShell-based recovery guides before mentioning CLI alternatives. There is minimal mention of Azure CLI, and no Linux/macOS-specific instructions or examples are provided. This creates friction for users on Linux/macOS who prefer or require command-line solutions.
Recommendations
- Include Azure CLI examples alongside PowerShell for all command-line instructions, especially in troubleshooting sections.
- Reference Linux/macOS command-line tools and workflows where applicable.
- Ensure links to recovery or management guides include both PowerShell and Azure CLI tabs, and mention this in the documentation.
- Add a note clarifying that all portal instructions are cross-platform, but command-line alternatives exist for Linux/macOS users.
- Provide parity in error resolution steps by listing Azure CLI commands before or alongside PowerShell commands.
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 →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing on SMB protocol paths and username formats that are Windows-centric, referencing Windows UI patterns (such as right-clicking folders and using the Security tab), and including a note that copy service compatibility with non-Windows NAS devices is not officially supported. There are no Linux/macOS-specific instructions or examples, and the documentation assumes familiarity with Windows conventions.
Recommendations
- Provide explicit instructions or examples for Linux/macOS users, such as how to specify SMB paths and credentials from those platforms.
- Clarify the level of support and any known workarounds for non-Windows NAS devices or hosts.
- Include Linux/macOS equivalents for UI actions (e.g., how to set SMB permissions on a Linux NAS).
- If the service is truly Windows-only, state this clearly in the prerequisites and offer alternative guidance for Linux users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows tools (e.g., Robocopy, net use) are featured prominently and exclusively in step-by-step examples, with detailed command-line and File Explorer instructions. Linux instructions are minimal, limited to a single mount example, with no Linux-native file copy tool (e.g., rsync, cp, smbclient) usage shown. Robocopy is presented as the primary and only detailed copy tool, with no Linux equivalents or performance guidance for Linux users.
Recommendations
- Provide Linux/macOS equivalents for all Windows command-line examples, including mounting SMB shares and copying data (e.g., using rsync, cp, or smbclient).
- Include sample commands and output for Linux tools, similar to the Robocopy examples for Windows.
- Offer performance tuning guidance for Linux copy tools (e.g., rsync options, parallelization strategies) as is done for Robocopy.
- Mention Linux/macOS tools and workflows alongside Windows tools, not only after or as an afterthought.
- Consider a parity table or side-by-side examples for Windows and Linux/macOS users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows connection instructions and examples first, using Windows-specific tools (net use, File Explorer, Robocopy), and providing detailed command and screenshot walkthroughs for Windows users. Linux instructions are minimal, with only a single mount command (which incorrectly uses NFS instead of SMB/cifs), and no Linux file copy tool examples or screenshots. There is no guidance for macOS users.
Recommendations
- Present Linux/macOS instructions and examples alongside or before Windows instructions.
- Correct the Linux mount command to use SMB/cifs (e.g., mount -t cifs) instead of NFS.
- Provide examples of Linux file copy tools (e.g., cp, rsync, smbclient) and usage.
- Include screenshots or step-by-step instructions for Linux and macOS users.
- Mention macOS compatibility and provide relevant connection and copy instructions.
- Avoid recommending Windows-only tools (like Robocopy) without Linux/macOS equivalents.
Databox
Microsoft Azure Data Box Disk system requirements| Microsoft Docs
.../articles/databox/data-box-disk-system-requirements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias: Windows operating systems and tools are consistently listed first, and there is a dedicated section for required Windows software (including PowerShell, .NET Framework, and BitLocker), while the Linux section is less detailed and lacks parity in explanation. Windows-specific tools are mentioned by name, and the documentation assumes familiarity with Windows environments.
Recommendations
- List Linux and Windows operating systems and tools in parallel or alternate order to avoid always putting Windows first.
- Provide equal detail for Linux required software, including installation instructions or references, as is done for Windows.
- Include Linux-specific troubleshooting tips or common issues, similar to what might be provided for Windows.
- Where Windows tools (e.g., PowerShell, BitLocker) are mentioned, provide Linux equivalents or clarify when they are not needed.
- Ensure that any steps or requirements unique to Linux are as clearly documented as those for Windows.
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 →
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, with more detailed step-by-step guidance and screenshots. Windows-specific tools (DataBoxDiskUnlock.exe) and PowerShell/Command Prompt usage are emphasized, while Linux instructions, though present, sometimes rely on external utilities (SEDUtil, dislocker) and require more manual setup. In some sections, Windows instructions precede Linux, and troubleshooting guidance is more Windows-centric. Linux instructions are comprehensive but may require more technical familiarity and external dependencies.
Recommendations
- Present Windows and Linux instructions in parallel or alternate order to avoid Windows-first bias.
- Ensure Linux examples are as detailed and illustrated as Windows examples, including screenshots and troubleshooting steps.
- Highlight Linux-specific tools and workflows at the same level of prominence as Windows tools.
- Provide direct links to Linux troubleshooting and support resources.
- Clarify parity between Windows and Linux toolsets, and note any limitations or differences explicitly.
- Where external Linux utilities are required, offer guidance on installation and usage for multiple distributions, not just CentOS/Ubuntu.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references BitLocker encryption and a disk unlock tool, both of which are Windows-centric technologies. There is no mention of Linux or macOS equivalents, nor are there instructions or examples for non-Windows platforms regarding disk unlocking or encryption management.
Recommendations
- Clarify whether the Data Box Disk unlock tool is available for Linux/macOS, or provide alternative instructions for those platforms.
- If BitLocker is required, explain how Linux/macOS users can interact with BitLocker-encrypted disks (e.g., using open-source tools like Dislocker).
- Add explicit examples or guidance for Linux/macOS users in relevant sections, especially for disk unlocking and data access.
- Mention any platform limitations up front so users can plan accordingly.
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 →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and patterns (e.g., Windows event log formats, NT AUTHORITY accounts, and references to 'WIN-DATABOXADMIN') are used in log samples and explanations. The verbose log sample is formatted as XML but is presented within a PowerShell code block, and the audit log sample is clearly based on Windows event logs. There are no explicit Linux/macOS command examples, nor is there guidance for interpreting logs or accessing Data Box from non-Windows systems. The documentation assumes familiarity with Windows authentication and logging conventions, which may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS examples for accessing Data Box logs and credentials, such as using SSH, NFS, or SMB from Linux.
- Include sample audit logs generated from Linux-based access, highlighting differences in authentication and log formats.
- Clarify whether all features (e.g., chain of custody logs, device credential access) are available and accessible from Linux/macOS, and document any platform-specific limitations.
- Avoid presenting Windows-specific log formats and account names as the only example; add parity for Linux/macOS environments.
- If PowerShell is not required, use neutral code blocks for XML or log samples.
Databox
Preserving file ACLs, attributes, and timestamps with Azure Data Box
...in/articles/databox/data-box-file-acls-preservation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows terminology, tools, and behaviors. Windows ACLs and privileges (such as SeBackupPrivilege) are discussed in detail, with references to Windows accounts and error messages. Linux is mentioned only in passing, with limited details and no concrete Linux copy tool examples. The documentation lacks Linux-specific guidance and does not provide parity in instructions or troubleshooting for Linux users.
Recommendations
- Add explicit Linux copy tool examples (e.g., smbclient, rsync with SMB, or mount.cifs) and instructions for preserving ACLs, attributes, and timestamps.
- Clarify what 'Windows NT ACLs' means for Linux users and how Linux ACLs map to Azure Files.
- Provide troubleshooting steps and error messages relevant to Linux clients.
- Discuss Linux-specific limitations and workarounds in detail, not just as a footnote.
- Present Windows and Linux instructions side-by-side or in parallel sections for equal visibility.
Databox
Azure Data Box Disk troubleshooting | Microsoft Docs
...ob/main/articles/databox/data-box-disk-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., D:\, E:\) and examples, and references a PowerShell script (.ps1) in the error log sample. There are no Linux/macOS-specific examples, paths, or troubleshooting notes. The documentation implicitly assumes a Windows environment for disk access and validation, which may create friction for Linux/macOS users.
Recommendations
- Add Linux/macOS equivalent examples, including sample paths (e.g., /mnt/DataBoxDiskImport/logs) and file system conventions.
- Clarify whether the validation tool and disk access are supported on Linux/macOS, and provide instructions for those platforms if available.
- Include troubleshooting notes for common Linux/macOS issues (e.g., mount permissions, file system compatibility).
- Avoid referencing Windows-specific file types (e.g., .ps1) in generic error samples, or provide cross-platform alternatives.
Databox
Tutorial: Copy from VHDs to managed disks
...s/databox/data-box-heavy-deploy-copy-data-from-vhds.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows/SMB connection instructions are presented first and in greater detail, including screenshots and step-by-step guidance using Windows tools (net use, File Explorer, Windows + R). Linux/NFS instructions are provided but are less detailed, lack troubleshooting steps, and do not include equivalent graphical examples or error handling guidance. There are no Linux-specific copy command examples (e.g., cp, rsync), nor parity in troubleshooting or verification steps for Linux users.
Recommendations
- Alternate the order of SMB/Windows and NFS/Linux instructions, or present them in parallel.
- Provide Linux-specific copy command examples (e.g., cp, rsync) for copying VHDs after mounting.
- Include screenshots and step-by-step guidance for Linux file managers (e.g., Nautilus, Dolphin) similar to File Explorer instructions for Windows.
- Add troubleshooting steps and error handling guidance for Linux users, including common NFS mount issues and log verification.
- Clarify that both Windows and Linux users can perform all critical steps, and highlight any OS-specific limitations.
- Ensure parity in detail and clarity between Windows and Linux sections.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows instructions and tooling (such as Robocopy and File Explorer) are presented first and in much greater detail, including step-by-step walkthroughs, screenshots, and command output. Linux instructions are minimal, with only a basic mount command provided and no equivalent file copy tool recommendations or examples. The primary file copy workflow is centered around Robocopy, a Windows-only tool, with no mention of Linux alternatives like rsync or cp in the main tutorial section. This creates friction for Linux/macOS users, who must infer or research their own workflows.
Recommendations
- Provide Linux/macOS examples for mounting SMB shares using smbclient or mount.cifs, not just NFS.
- Include detailed Linux file copy instructions using standard tools (e.g., rsync, cp) with sample commands and output.
- Add parity in screenshots and step-by-step guides for Linux workflows, similar to the Windows section.
- Mention and explain Linux/macOS compatible SMB copy tools (e.g., smbclient, rsync over SMB, mount.cifs).
- Present Windows and Linux/macOS instructions side-by-side or in parallel sections, rather than Windows-first.
- Clarify which steps/tools are cross-platform and which are OS-specific.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples, explicitly referencing 'Windows PowerShell', and showing command outputs from a Windows environment. There are no Linux/macOS CLI or scripting examples, nor any mention of cross-platform alternatives such as Azure CLI, Bash, or Python SDK. This may create friction for Linux/macOS users who cannot easily follow the instructions as written.
Recommendations
- Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
- Provide Bash or Python SDK sample scripts for blob tiering operations.
- Clarify that Azure PowerShell can be used on Linux/macOS (with PowerShell Core), and update instructions to be OS-agnostic.
- Show command outputs from non-Windows environments, or remove OS-specific prompts.
- Reorder or parallelize examples so that Linux/macOS instructions are presented alongside Windows instructions.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Certificate import instructions are presented in detail for Windows (PowerShell and UI), with Linux guidance given in a more generic, less step-by-step manner. Windows examples and screenshots appear first in several sections. The use of AzCopy is cross-platform, but Windows command syntax is shown before Linux in some cases. The tutorial references Windows-specific tools and UI elements more thoroughly than Linux equivalents.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux certificate import, including common distributions (e.g., Ubuntu, RHEL, CentOS, Fedora) with actual command lines and expected output.
- Include Linux screenshots or terminal output where Windows UI screenshots are shown.
- Present Linux and Windows examples side-by-side, or alternate which platform is shown first in command examples.
- Reference macOS where applicable, especially for certificate import and AzCopy usage.
- List cross-platform tools and procedures before platform-specific ones to avoid implicit prioritization.