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 126-150 of 231 flagged pages
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 →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows SMB paths, Windows-style username formats, and Windows file management patterns (e.g., right-clicking folders, using the Security tab). There is no mention of Linux or Unix equivalents, nor are there examples or instructions for Linux users. The note about non-Windows NAS devices not being officially supported further deprioritizes Linux environments.
Recommendations
- Include explicit instructions and examples for Linux environments, such as how to specify SMB paths and credentials from Linux systems.
- Provide guidance for managing file permissions and access on Linux (e.g., using chmod, setfacl, or other Linux tools) alongside Windows instructions.
- Clarify the level of support for Linux/Unix NAS devices and, if possible, offer troubleshooting steps or workarounds for Linux users.
- Avoid Windows-centric language (e.g., 'Right-click the folder, select Properties, then Security tab') or provide parallel Linux instructions (e.g., 'Use ls -l or getfacl to check permissions').
- If the service is truly Windows-only, state this clearly at the beginning to set expectations for Linux users.
Create Pull Request
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-deploy-set-up.md
...b/main/articles/databox/data-box-disk-deploy-set-up.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools are often presented first, with detailed PowerShell/Command Prompt examples and screenshots. The Windows toolset is referenced repeatedly and sometimes more prominently than Linux equivalents. While Linux instructions are present and fairly detailed, some sections (e.g., initial tool download, troubleshooting, and validation) default to Windows-first language or lack parity in example depth. There are also more references to Windows-specific requirements and tools, and some Linux steps require third-party utilities not managed by Microsoft, which may create a perception of less official support.
Recommendations
- Alternate the order of Windows and Linux instructions or use parallel tabbed layouts to present both platforms equally.
- Ensure that all examples, screenshots, and troubleshooting steps are provided for both Windows and Linux clients with equal detail.
- Where possible, provide official Microsoft-supported tools/utilities for Linux, or at least clarify support levels and provide direct links to trusted third-party resources.
- Avoid language that implies Windows is the default or primary platform (e.g., 'To unlock the disks, open Command Prompt...' before mentioning Linux).
- Add Linux-specific troubleshooting and validation sections to match the depth of Windows coverage.
- Where third-party Linux tools are required, provide clear installation and usage instructions, and consider contributing to or supporting these tools to improve user confidence.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-copy-data-via-rest.md
...articles/databox/data-box-deploy-copy-data-via-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the certificate import section, where Windows PowerShell and Windows Server UI instructions are presented first and in greater detail, including screenshots, before Linux instructions. The Linux section is less detailed and refers users to external documentation for specifics. Additionally, the use of Windows-specific tools and UI elements (e.g., Certificate Import Wizard) is emphasized, and Windows command-line options are highlighted alongside Linux, but Windows is often presented first.
Recommendations
- Present Linux and Windows instructions in parallel or alternate which comes first to avoid always prioritizing Windows.
- Provide equally detailed, step-by-step Linux instructions, including screenshots where possible, for tasks such as certificate import.
- Include examples for a wider range of Linux distributions (not just Ubuntu/Debian and RHEL/Fedora/CentOS), or at least link directly to official documentation for each.
- Where Windows-specific tools or UI are mentioned (e.g., Certificate Import Wizard), mention Linux GUI alternatives if available (such as GNOME Certificates or KDE's certificate manager).
- Ensure that all command-line examples (such as AzCopy) are equally detailed for both Linux and Windows, and clarify any differences in syntax or behavior.
- Avoid language that implies Windows is the default or primary platform (e.g., 'On a Windows system, you can...'), and instead use neutral phrasing like 'On Windows...' and 'On Linux...'.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows/SMB/Robocopy instructions and examples first and in greater detail, while Linux instructions are minimal and lack parity in depth and tooling. Windows-specific tools (Robocopy, net use, File Explorer) are emphasized, with only brief Linux mounting instructions and no Linux-native copy tool examples. There are no Linux equivalents for advanced copy scenarios, performance tuning, or error handling, and Robocopy is presented as the primary (and only detailed) copy tool.
Recommendations
- Provide Linux-native copy tool examples (e.g., rsync, cp, smbclient) for copying data after mounting the SMB share, including command-line syntax and sample output.
- Include Linux-specific performance tuning guidance (e.g., parallel rsync, mount options for performance, etc.) similar to the Robocopy session/thread recommendations for Windows.
- Offer parity in troubleshooting/error handling instructions for Linux users, such as how to interpret mount errors, log file locations, and common issues.
- Present Windows and Linux instructions in parallel sections or tables, rather than always listing Windows first and in more detail.
- Reference Linux documentation for SMB/CIFS (e.g., man mount.cifs, man smbclient) and provide links to relevant resources.
- If Robocopy is recommended for Windows, suggest and document equivalent robust tools for Linux (e.g., rsync with appropriate flags for preserving metadata, parallelization, logging, etc.).
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias. Windows instructions and screenshots are presented first and in greater detail, including explicit command-line and GUI (File Explorer) steps. The Linux section is brief, provides only a single mount command (which appears to use NFS syntax rather than SMB), and lacks further guidance or troubleshooting. The only file copy tool mentioned is Robocopy, a Windows utility, with no Linux alternatives or examples provided.
Recommendations
- Present Windows and Linux instructions in parallel sections, or alternate which OS is presented first.
- Provide accurate Linux SMB mount commands (e.g., using 'mount -t cifs' instead of NFS).
- Include Linux file copy tool examples (e.g., cp, rsync, smbclient) alongside Robocopy.
- Add Linux screenshots or terminal output where Windows screenshots are shown.
- Reference Linux troubleshooting steps and permissions considerations for SMB mounts.
- List both Windows and Linux tools/resources in the 'For more information' section.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. All file copy examples use Windows 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 tools mentioned for copying or validating data. Linux users are only briefly referenced, with no guidance or command-line examples provided for Linux environments.
Recommendations
- Provide equivalent Linux command-line examples for copying data to the Data Box Disk, such as using cp, rsync, or smbclient.
- List Linux-compatible tools for checksum validation (e.g., sha256sum, md5sum) and provide example commands for validating data integrity.
- Explicitly mention any limitations or differences for Linux users at the start of relevant sections, and offer alternative workflows where Windows-only tools are referenced.
- Include troubleshooting tips and best practices for Linux environments, such as handling long paths, file permissions, and mounting NTFS disks.
- Where screenshots or walkthroughs are provided, include at least one example from a Linux desktop or terminal.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-deploy-ordered.md
.../blob/main/articles/databox/data-box-deploy-ordered.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. PowerShell and Windows-specific instructions are given prominence, with command prompts and output examples consistently referencing Windows environments (e.g., 'PS C:\Windows>'). Installation steps and prerequisites focus on Windows PowerShell, and there is little to no mention of Linux or macOS equivalents for local CLI or PowerShell usage. Even when discussing Azure CLI, the examples and screenshots are Windows-centric, and there are no explicit Linux terminal examples or guidance for non-Windows users.
Recommendations
- Provide explicit Linux (and optionally macOS) examples for Azure CLI usage, including sample commands and expected output in a bash shell (e.g., '$ az login').
- When referencing installation steps for CLI or PowerShell, include links and instructions for Linux and macOS, not just Windows (e.g., 'Install Azure CLI on Linux').
- Avoid using Windows PowerShell as the default or only terminal in CLI examples; alternate or parallel examples in bash should be included.
- Where output paths or prompts are shown (e.g., 'PS C:\Windows>'), provide equivalent bash prompt examples (e.g., '$'), or use generic prompts.
- Clarify that Azure PowerShell can be used cross-platform (with PowerShell Core), and provide installation and usage instructions for Linux/macOS.
- Add a section or note explicitly addressing Linux/macOS users, outlining any differences or considerations for those platforms.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-deploy-ordered.md
.../main/articles/databox/data-box-disk-deploy-ordered.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific technologies (such as BitLocker) as the primary or default encryption method, mentioning Windows client requirements before Linux, and not providing Linux-specific instructions or examples for ordering or managing Data Box Disk. There are no CLI or portal instructions that address Linux-specific workflows or tools, and the only encryption technology explicitly named is BitLocker, which is a Windows technology.
Recommendations
- Provide explicit Linux client instructions and examples, especially for disk encryption and mounting, in parity with Windows.
- Mention Linux compatibility and workflows alongside Windows in all relevant sections, not just as an afterthought.
- Include references to Linux-native tools and commands (e.g., cryptsetup for disk encryption, mount commands) where appropriate.
- Clarify the process for using hardware-encrypted disks on Linux, including any required drivers or utilities.
- Ensure that any software prerequisites or required software sections include both Windows and Linux tools, with equal detail.
- Where BitLocker is mentioned, also describe the Linux alternatives or how Linux users can access BitLocker-encrypted disks.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows (robocopy) instructions and scenarios first and in much greater detail, including command breakdowns and multiple usage examples. Linux instructions are minimal, lacking detailed steps for preserving metadata (especially ACLs), and do not provide equivalent command breakdowns or advanced scenarios. The Linux section omits examples for copying ACLs and attributes, and does not mention or explain tools such as smbcacls or cifsacl beyond a brief mention.
Recommendations
- Provide Linux examples with the same level of detail as Windows, including command breakdowns and explanations for each parameter.
- Include step-by-step instructions for copying both data and metadata (ACLs, timestamps, attributes) on Linux, using tools like smbcacls or cifsacl.
- Present Linux and Windows sections in parallel or side-by-side, or clearly indicate both options at the start, to avoid the impression of Windows being the default.
- Add troubleshooting notes and advanced scenarios for Linux users, similar to the Windows/robocopy section.
- Reference Linux documentation for the mentioned tools, and provide links to official guides for rsync, smbcacls, and cifsacl.
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 →
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), providing troubleshooting steps only for Windows clients (enabling long paths), and omitting any mention of Linux equivalents or guidance for Linux users. There are no Linux or cross-platform examples or instructions, and the only client configuration advice is for Windows.
Recommendations
- Include equivalent instructions for Linux clients, such as how to handle long file paths and any relevant filesystem limitations.
- Mention or provide Linux-compatible tools or scripts for validating and splitting data, or clarify if the provided tools are Windows-only.
- Add examples or troubleshooting steps for common Linux scenarios, such as mounting disks, copying data, and handling file naming or path length issues.
- Use neutral, cross-platform language where possible, and avoid assuming the user is on Windows.
- If certain features or tools are only available on Windows, explicitly state this and suggest alternatives or workarounds for Linux users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by listing Windows operating systems and tools before Linux equivalents, providing detailed requirements for Windows (including PowerShell, .NET, BitLocker), and referencing Windows-specific tools without equivalent Linux usage examples or guidance. Linux requirements are mentioned, but with less detail and no example commands or workflows. There are no Linux command-line examples or step-by-step parity with Windows instructions.
Recommendations
- Present Linux and Windows operating systems and requirements in parallel, rather than listing Windows first.
- Provide example commands and workflows for both Windows (e.g., PowerShell) and Linux (e.g., bash, shell scripts) for common tasks such as disk unlocking and data copy.
- List required Linux tools with the same level of detail as Windows tools, and explain their installation and usage.
- Include troubleshooting and validation steps for Linux environments, not just Windows.
- Where Windows-specific tools (e.g., PowerShell, BitLocker) are mentioned, provide Linux equivalents (e.g., dislocker, cryptsetup) and usage notes.
- Ensure that all tables and sections have Linux and Windows content side-by-side to reinforce parity.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-troubleshoot-data-copy.md
...ticles/databox/data-box-disk-troubleshoot-data-copy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides detailed troubleshooting steps for Linux users in the first section, but in the Split Copy tool errors section, it references Windows-specific tools (e.g., 'diskmgmt.msc') without mentioning Linux equivalents or providing Linux-specific guidance. The error table assumes a Windows environment and does not offer parallel Linux instructions, which may leave Linux users without clear solutions for those scenarios.
Recommendations
- For each tool or command mentioned (such as 'diskmgmt.msc'), provide Linux equivalents (e.g., 'lsblk', 'fdisk', 'gnome-disks', or 'udisksctl') and instructions for bringing disks online in Linux.
- Ensure that error messages and troubleshooting steps are accompanied by both Windows and Linux solutions, or clearly indicate when a tool is Windows-only and suggest alternatives for Linux.
- Add Linux-specific examples and commands for all common operations, especially in sections currently focused on Windows tools or workflows.
- Review the error table to include Linux-relevant error messages and their resolutions, or clarify which errors are platform-specific.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-quickstart-portal.md
...in/articles/databox/data-box-disk-quickstart-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows terminology and tools, providing detailed instructions and validation scripts only for Windows, and lacking equivalent Linux-specific examples or guidance. The unlock and validation steps reference Windows tools (e.g., .cmd scripts, BitLocker dialogs) without offering Linux alternatives or parity.
Recommendations
- Provide explicit Linux command-line examples for unlocking disks, copying data, and validating files, alongside the Windows instructions.
- Document the availability and usage of the Data Box Disk unlock tool for Linux, including installation and execution steps.
- Offer Linux-compatible validation scripts or instructions, or clarify if the provided .cmd script is cross-platform or provide a shell script alternative.
- Mention Linux-specific considerations (e.g., mount commands, file system compatibility, safe removal procedures) where relevant.
- Ensure that any references to Windows tools (such as BitLocker dialogs) are matched with Linux equivalents or clear guidance for Linux users.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-disk-troubleshoot-unlock.md
.../articles/databox/data-box-disk-troubleshoot-unlock.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias: all troubleshooting workflows, error messages, and resolutions are written exclusively for Windows environments. Only Windows-specific tools (e.g., BitLocker, Windows PowerShell) are mentioned, and there are no examples, instructions, or troubleshooting steps for Linux or other operating systems. The unlock tool usage, error messages, and resolutions assume a Windows client, with no parity for Linux users.
Recommendations
- Add troubleshooting sections specifically for Linux clients, including common errors and their resolutions.
- Provide unlock tool usage examples for Linux, including command-line syntax and expected outputs.
- Mention Linux equivalents for tools (e.g., how to unlock encrypted drives using Linux utilities such as cryptsetup or dislocker if supported).
- Clarify OS compatibility for the Data Box Disk Unlock tool and provide download/installation instructions for Linux if available.
- Ensure that error messages and logs are explained for both Windows and Linux environments.
- If Linux is not supported, explicitly state this early in the documentation to set user expectations.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a Windows-first bias: Windows terminology, tools, and privileges (e.g., SeBackupPrivilege, Administrator/Backup Operators groups) are referenced in detail, while Linux equivalents are either omitted or only briefly mentioned. Linux-specific behaviors are described as exceptions or limitations (e.g., only Windows NT ACLs transferred, default ACLs not transferred on Linux), and there are no Linux command examples or tool recommendations. The documentation assumes familiarity with Windows security concepts and does not provide parity for Linux users.
Recommendations
- Provide explicit Linux tool examples (e.g., using smbclient, rsync, or cp with appropriate flags) for copying data and preserving metadata.
- Include Linux privilege requirements and equivalents to Windows concepts like SeBackupPrivilege (e.g., root or specific capabilities needed).
- Clarify what 'Windows NT ACLs' means in the context of Linux clients and how Linux users can verify or manage these ACLs.
- Add a section or table comparing Windows and Linux behaviors and limitations side-by-side for clarity.
- Ensure that Linux workflows are described with the same level of detail as Windows, including troubleshooting tips and error messages relevant to Linux environments.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by presenting Windows/SMB connection instructions and tools (e.g., 'net use', File Explorer) in greater detail and before Linux/NFS instructions. Windows-specific commands and UI steps are described with screenshots and explicit step-by-step guidance, while Linux/NFS instructions are more concise and lack comparable detail. There is also a reliance on Windows command-line tools and patterns (e.g., 'net use', File Explorer), with no mention of Linux equivalents for browsing shares or copying files.
Recommendations
- Provide Linux/NFS instructions with the same level of detail as Windows/SMB, including screenshots and step-by-step guidance for mounting and browsing shares.
- Include Linux command-line examples for copying files (e.g., using 'cp', 'rsync', or 'scp') and for browsing mounted shares (e.g., using 'ls', 'nautilus', or other file managers).
- Present Linux/NFS instructions before or alongside Windows/SMB instructions to avoid the appearance of prioritizing Windows.
- Mention and demonstrate Linux tools for verifying share access and copying data, not just Windows tools.
- Ensure parity in troubleshooting steps and error screenshots for both Windows and Linux scenarios.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific account names and log formats (e.g., 'WIN-DATABOXADMIN', 'NT AUTHORITY'), and by providing log samples and audit details that are clearly modeled after Windows Event Log output. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific audit or log formats discussed. The documentation assumes familiarity with Windows authentication and logging paradigms, and does not mention or illustrate Linux access, tools, or audit patterns.
Recommendations
- Include examples of accessing and interpreting Data Box logs from Linux systems, such as using Linux command-line tools (e.g., grep, less, tail) to view logs.
- Provide sample audit log entries or authentication events as they would appear when accessed from Linux clients (e.g., via NFS or SMB mounts from Linux).
- Clarify whether the Data Box supports Linux authentication mechanisms (e.g., mapping Linux users to SMB shares) and how such events are logged.
- Add instructions or screenshots for tracking and downloading logs using Linux tools or from a Linux environment.
- Ensure that any references to account names, domains, or logon types are explained in a cross-platform context, or provide Linux equivalents where possible.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-deploy-copy-data-via-copy-service.md
...ox/data-box-heavy-deploy-copy-data-via-copy-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing SMB paths in Windows UNC format (\\Server\Share), using Windows-style username formats, and describing file/folder permissions using Windows GUI actions (right-click, Properties, Security tab). There are no examples or instructions for Linux or Unix-based environments, such as how to specify SMB paths or credentials from a Linux NAS, nor are Linux command-line or permission management methods mentioned.
Recommendations
- Include examples for specifying SMB paths and credentials from Linux systems (e.g., using /mnt/server/share or smb:// syntax).
- Describe how to set permissions on source folders using Linux/Unix commands (e.g., chmod, chown) in addition to Windows GUI instructions.
- Clarify that the data copy service supports both Windows and Linux NAS sources, and provide guidance for both.
- Add troubleshooting steps and log file access instructions relevant to Linux environments.
- Ensure that regular expression and wildcard pattern examples are platform-agnostic or provide both Windows and Linux shell equivalents.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-deploy-copy-data.md
...in/articles/databox/data-box-heavy-deploy-copy-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: Windows instructions and examples (using net use, File Explorer, and Robocopy) are presented first and in much greater detail than Linux equivalents. The Linux section is brief, lacks detailed copy tool examples, and even contains a likely error (mount -t nfs instead of -t cifs for SMB). Only Windows-specific tools (Robocopy) are discussed in depth, with no Linux alternatives (like rsync or smbclient) shown for SMB copy. The copy performance tuning section only references Robocopy sessions/threads, not Linux tools. This results in a lack of parity and guidance for Linux users.
Recommendations
- Provide equally detailed Linux instructions for connecting to SMB shares, using the correct mount command (mount -t cifs) and showing how to specify credentials.
- Include Linux-native SMB copy tool examples (such as smbclient, rsync over SMB, or cp after mounting) with sample commands and output, similar to the Robocopy section.
- Add performance tuning guidance for Linux copy tools (e.g., rsync options, parallelization strategies) analogous to the Robocopy tuning table.
- Mention Linux tools and patterns alongside Windows tools, not only in separate sections but also in summary tables and recommendations.
- Correct any technical inaccuracies (e.g., using -t nfs for SMB is likely incorrect; should be -t cifs or -t smb3).
- Where Robocopy is referenced, also reference Linux equivalents and provide links to their documentation.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-deploy-copy-data-via-rest.md
...es/databox/data-box-heavy-deploy-copy-data-via-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In certificate import instructions, Windows PowerShell and Windows Server UI steps are provided in detail with screenshots, while Linux instructions are more generic and lack equivalent step-by-step detail or visuals. Windows tools and terminology (e.g., PowerShell, Windows Server UI) are mentioned first and more prominently. However, AzCopy usage is shown for both Linux and Windows, and Linux command-line examples are present, reducing the overall bias.
Recommendations
- Provide step-by-step, distribution-specific Linux certificate import instructions, including example commands for popular distributions (e.g., Ubuntu, RHEL) and screenshots where possible.
- Present Linux and Windows instructions in parallel or in separate, equally detailed sections, rather than listing Windows first and in more depth.
- Include troubleshooting tips and common issues for Linux users, similar to what is often provided for Windows.
- Ensure all tools and UI references (e.g., Storage Explorer) clarify cross-platform availability and usage.
- Where possible, use neutral language and ordering (e.g., 'On Linux or Windows, do X' instead of 'On Windows, do X. On Linux, ...').
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-migrate-spo.md
...ob/main/articles/databox/data-box-heavy-migrate-spo.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Windows-based instructions and examples, such as mounting Azure file shares using Windows-specific guides and creating Windows VMs. There are no Linux equivalents or alternative instructions for users on Linux systems. The SharePoint Migration Tool (SPMT), which is Windows-only, is recommended without mentioning alternatives or workarounds for Linux users.
Recommendations
- Include parallel instructions for Linux users, such as how to mount Azure file shares on Linux VMs using SMB or NFS.
- Provide guidance on creating both Windows and Linux VMs in Azure, with links to relevant documentation for each.
- Acknowledge that SPMT is Windows-only and suggest alternative migration strategies or tools for Linux environments, if available.
- Present steps for both operating systems side by side or clearly indicate OS-specific steps to ensure inclusivity.
- Add a section or note clarifying OS requirements and limitations for the SharePoint Migration Tool.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing only Windows PowerShell examples, referencing Windows-specific tools and environments (such as 'elevated Windows PowerShell session'), and omitting any Linux or cross-platform CLI examples. There is no mention of Azure CLI, Bash, or other Linux-compatible scripting approaches, and all sample outputs are from a Windows environment.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
- Provide Bash script examples for blob tiering operations, especially for users on Linux or macOS.
- Explicitly mention that Azure PowerShell can be used on Linux and macOS (via PowerShell Core), and provide any necessary adjustments for those platforms.
- Include sample outputs from non-Windows environments to demonstrate parity.
- Rephrase steps to avoid assuming a Windows environment (e.g., 'Open a terminal' instead of 'Open an elevated Windows PowerShell session').
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation repeatedly emphasizes Windows-specific behaviors and limitations, such as the device being Windows-based, lack of support for case-sensitive file names, and reliance on Windows protocols (SMB). There is no mention of Linux-specific usage patterns, tools, or caveats, nor are there examples or guidance for Linux users. The documentation assumes a Windows environment as the default and does not provide parity for Linux users.
Recommendations
- Include explicit guidance and examples for Linux users, such as how to connect to Data Box using NFS from Linux systems.
- Document any Linux-specific caveats or limitations, such as file system compatibility, case sensitivity, and supported protocols.
- Balance the mention of Windows and Linux tools and patterns, ensuring that Linux equivalents (e.g., NFS, rsync, Linux file system behaviors) are described alongside Windows/SMB.
- Add troubleshooting tips and best practices for both Windows and Linux environments.
- Where Windows limitations are described (e.g., case insensitivity), clarify the impact on Linux users and suggest workarounds if available.
Databox
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox/data-box-heavy-quickstart-portal.md
...n/articles/databox/data-box-heavy-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 the data copy section by listing Windows/SMB/Robocopy as the first and most detailed example, while Linux/NFS is mentioned only secondarily and with less detail. The use of Windows-specific tools (Robocopy) is highlighted, and there are no explicit Linux command-line examples (e.g., mounting SMB shares from Linux, or using Linux-native tools for SMB). There is also an implicit assumption of Windows environments in the share connection instructions (UNC paths), and no PowerShell or Linux shell parity is provided for all steps.
Recommendations
- Provide explicit Linux examples for copying data to SMB shares, such as using the 'mount -t cifs' command or 'smbclient', alongside the Windows/Robocopy example.
- List Linux/NFS and Windows/SMB options in parallel, not with Windows first.
- Include Linux command-line examples for connecting to SMB shares and copying data, not just referencing 'cp' or 'rsync' for NFS.
- Clarify that both Windows and Linux hosts are supported for all relevant steps, and provide parity in instructions and troubleshooting.
- Where UNC paths are shown (\\<IP>\ShareName), also show the equivalent Linux mount or access syntax.
- If PowerShell or Windows-specific tools are mentioned, provide equivalent Bash/Linux shell commands where possible.
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page for Azure Data Box demonstrates a Windows bias by referencing Windows-specific tools (e.g., SharePoint Migration Tool, Veeam for Hyper-V, SQL Server) and omitting explicit Linux usage examples or Linux-native tools. The workflow and setup instructions do not mention Linux hosts or provide Linux-specific guidance for mounting shares or copying data. The documentation also references Windows-centric scenarios (e.g., VM farm, SQL Server) before mentioning more cross-platform or Linux-relevant use cases (e.g., HDFS).
Recommendations
- Add explicit Linux usage examples for mounting SMB/NFS shares and copying data to/from Data Box devices, including relevant commands (e.g., mount, rsync, cp).
- Reference Linux-native tools and scenarios (e.g., using rsync, tar, or Linux backup solutions) alongside Windows tools.
- Include guidance for both Windows and Linux environments in workflow/setup steps, ensuring parity in instructions and troubleshooting.
- Mention Linux-based workloads (e.g., PostgreSQL, MySQL, Linux VMs) as migration examples, not just Windows-centric ones.
- Where third-party tools are referenced (e.g., Veeam, Commvault), clarify their Linux support or suggest Linux alternatives if available.