Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 26-50 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-deploy-configure-network-compute-web-proxy.md
...-edge-pro-r-deploy-configure-network-compute-web-proxy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation primarily references PowerShell for command-line configuration (e.g., changing Kubernetes workload profiles) and does not provide equivalent Linux/bash/CLI examples. There is an implicit Windows-first approach, as PowerShell is mentioned as the default scripting interface, and no Linux tools or commands are referenced. The documentation assumes use of the local web UI or PowerShell, with no mention of Linux-based management or automation options.
Recommendations
- Provide equivalent Linux/bash command-line instructions for all PowerShell-based tasks, especially for changing Kubernetes workload profiles and network settings.
- Explicitly mention cross-platform CLI tools (such as Azure CLI) where possible, and provide examples for both Windows and Linux environments.
- Avoid assuming PowerShell as the default or only scripting interface; clarify when steps are platform-specific and offer alternatives.
- Include notes or links to Linux-compatible management tools or scripts for users who do not use Windows or PowerShell.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-deploy-set-up-device-update-time.md
...zure-stack-edge-pro-r-deploy-set-up-device-update-time.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools and defaults, such as Windows Server Update Services (WSUS), Microsoft Update server, and time.windows.com as the default NTP server. There are no mentions of Linux equivalents (e.g., Linux update mirrors, chrony/ntpd, or pool.ntp.org), nor are there examples or instructions for Linux environments. The focus on Windows tools and defaults, without Linux alternatives or parity, may hinder users managing Azure Stack Edge devices in Linux-centric environments.
Recommendations
- Include Linux-friendly update options, such as guidance for using Linux update mirrors or repositories if supported.
- Mention and provide examples for configuring NTP servers commonly used in Linux environments (e.g., pool.ntp.org, chrony, ntpd).
- Clarify whether WSUS and Microsoft Update are required, or if other update mechanisms (such as Linux package managers or custom update servers) are supported.
- Provide parity in examples and terminology, ensuring that both Windows and Linux administrators can follow the instructions.
- Explicitly state any platform limitations or requirements, so users know if only Windows-based infrastructure is supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-system-requirements.md
...x-online/azure-stack-edge-pro-r-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a bias towards Windows environments by referencing Azure PowerShell for data tiering and providing monitoring commands only via the PowerShell interface. There are no equivalent Linux CLI or Bash examples, and Linux-native tooling is not mentioned. This may make it less accessible for Linux users or administrators.
Recommendations
- Provide equivalent Linux/Bash/CLI examples alongside PowerShell instructions, especially for tasks like setting blob tiers and monitoring.
- Mention cross-platform tools (e.g., Azure CLI) where possible, and clarify if features are available on Linux.
- Include references to Linux-native management and monitoring approaches (e.g., SSH, Bash scripts, Linux command-line tools) for device interaction.
- Ensure that all code snippets and step-by-step guides are available for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-overview.md
...cles/databox-online/azure-stack-edge-pro-r-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, notably in the 'Double encryption' capability, where BitLocker (a Windows-specific tool) is mentioned as the method for local encryption, and the linked VPN configuration documentation references PowerShell. There are no Linux-specific tools or methods mentioned for encryption or VPN configuration, nor are there examples or references to Linux command-line usage. The documentation does not provide parity for Linux administrators, and Windows tools are mentioned exclusively and/or first.
Recommendations
- Include Linux-equivalent tools and instructions for local encryption (e.g., LUKS/dm-crypt) alongside BitLocker.
- Provide VPN configuration steps or references for both Windows (PowerShell) and Linux (e.g., strongSwan, OpenVPN) environments.
- When referencing command-line tools or scripts, offer both PowerShell (Windows) and Bash (Linux) examples.
- Explicitly state cross-platform compatibility and provide guidance for Linux-based workflows where relevant.
- Avoid assuming the use of Windows tools by default; mention alternatives or note platform-specific requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-profiles-azure-resource-manager-versions.md
...re-stack-edge-profiles-azure-resource-manager-versions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by featuring a 'Next steps' link that exclusively references managing Azure Stack Edge via Windows PowerShell, with no mention of Linux or cross-platform alternatives. Throughout the document, there are no examples or references to Linux tools, shells, or workflows, and Windows/PowerShell is the only environment highlighted for further action.
Recommendations
- Add equivalent Linux/bash/CLI examples or links alongside any PowerShell/Windows instructions.
- Include a 'Next steps' link for managing Azure Stack Edge from Linux or cross-platform tools (such as Azure CLI or REST API usage from bash).
- Explicitly mention cross-platform management options where applicable, ensuring parity in guidance for both Windows and Linux users.
- Review the documentation for any implicit assumptions about the user's operating system and clarify when instructions are OS-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-security.md
...cles/databox-online/azure-stack-edge-pro-r-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows Defender Application Control (WDAC), BitLocker encryption, and PowerShell for remote management. There are no Linux equivalents or examples provided for device management, security tooling, or remote access. The documentation assumes a Windows-centric environment both in terminology and in the tools described, with no mention of Linux-based workflows or cross-platform alternatives.
Recommendations
- Include Linux-based management options and examples, such as SSH or Linux CLI tools, for remote device access and administration.
- Mention Linux-compatible security solutions or clarify if the device is Windows-only, and if so, state this explicitly.
- Provide parity in documentation by describing how Linux clients can interact with the device, including authentication, encryption, and logging.
- If BitLocker and WDAC are required due to the device OS, explain this and suggest best practices for integrating with mixed-OS environments.
- Add examples or references for NFS and SMB access from both Windows and Linux clients, including command-line usage.
- Clarify support for Linux-based automation or scripting for device management, if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-security.md
...//articles/databox-online/azure-stack-edge-security.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows security tools (e.g., Windows Defender Device Guard, BitLocker), providing only PowerShell-based remote management instructions, and omitting any mention of Linux equivalents or cross-platform management options. There are no examples or guidance for Linux users, and Windows tools/patterns are presented as the default or only option.
Recommendations
- Include information on whether Linux-based management or remote access is supported, and provide equivalent instructions or note limitations.
- Mention Linux-compatible security features or clarify if the device is Windows-only.
- If PowerShell is the only supported remote interface, explicitly state this and provide rationale; otherwise, add SSH or Linux CLI examples.
- Reference cross-platform encryption and security tools where possible, or explain why only Windows tools are used.
- Ensure parity in documentation structure by presenting any Linux options alongside Windows ones, not after or omitted.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-return-device.md
...icles/databox-online/azure-stack-edge-return-device.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only command-line example for device reset, with no mention of Linux or cross-platform CLI alternatives. The instructions reference PowerShell and the local web UI, but do not provide equivalent steps for Linux users or mention Azure CLI/REST API options. This may hinder users operating from non-Windows environments.
Recommendations
- Add Linux-specific instructions for device reset, such as using Azure CLI or REST API, if available.
- Explicitly mention whether the PowerShell instructions can be run on PowerShell Core (cross-platform) or are Windows-only.
- Provide command-line examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) where applicable.
- Clarify if the local web UI is accessible from any OS/browser, and highlight this as a cross-platform option.
- Review all references to tools and ensure Linux equivalents are mentioned or linked where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-audit-logs.md
...ocs/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, only references Windows event providers and event IDs, and mentions Windows-specific tools and patterns (e.g., BitLocker, remote PowerShell). There are no examples or references to Linux tools, logs, or access patterns, nor any guidance for Linux users.
Recommendations
- Clarify early in the documentation that Data Box devices run Windows and explain any implications for users coming from Linux environments.
- If Data Box supports Linux-based access (e.g., via SMB/NFS, or log retrieval from Linux clients), provide explicit instructions and examples for Linux users.
- Include a section or FAQ addressing common Linux user concerns, such as how to interact with audit logs or device shares from Linux systems.
- Where possible, mention cross-platform tools or interfaces (e.g., REST APIs, Azure CLI) that can be used from both Windows and Linux to interact with Data Box or retrieve logs.
- If audit logs are only accessible via Microsoft support, clarify whether the logs are provided in a format readable on Linux systems, and offer guidance for Linux users on how to interpret or process these logs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-deploy-export-copy-data.md
...//articles/databox/data-box-deploy-export-copy-data.md
High Priority
View Details →
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 greater detail, while Linux instructions are brief, potentially incorrect (using NFS instead of SMB), and lack parity in copy tool examples. There is no mention of Linux file copy tools or GUI workflows, and the Linux mounting example may be inaccurate for SMB shares.
Recommendations
- Provide Linux connection instructions using the correct SMB mount syntax (e.g., 'mount -t cifs ...'), not NFS.
- Present Linux and Windows instructions in parallel sections or with equal prominence.
- Include Linux file copy tool examples (e.g., 'cp', 'rsync', 'smbclient') similar to the Robocopy example for Windows.
- Mention Linux GUI options for accessing SMB shares (e.g., using Nautilus or Dolphin file managers).
- Avoid assuming Windows as the default by not presenting Windows steps first or exclusively.
- Ensure all screenshots and command samples have Linux equivalents where applicable.
Azure Docs
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 and user formats (e.g., \\<ServerName>\<ShareName>, \\<DomainName><UserName>), and by providing instructions that align with Windows file system conventions (such as right-clicking folders and using the Security tab). There are no Linux or Unix-specific examples, nor is there guidance for non-Windows environments, despite a note that non-Windows NAS devices are not officially supported. The documentation does not mention Linux tools, commands, or file path formats, and does not provide parity for Linux administrators.
Recommendations
- Provide explicit Linux/Unix examples for SMB path formats (e.g., smb://server/share or mount -t cifs ...).
- Include instructions for managing permissions and user credentials on Linux systems (e.g., using chmod, setfacl, or mount options).
- Clarify the level of support for Linux and non-Windows NAS devices, and if unsupported, suggest workarounds or alternative approaches for Linux users.
- Add screenshots or CLI examples relevant to Linux environments, if possible.
- Avoid Windows-centric language (such as 'right-click', 'Properties', 'Security tab') or provide equivalent steps for Linux file managers or command-line tools.
Azure Docs
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. In the certificate import section, Windows methods (PowerShell and Server UI) are described in detail and presented before Linux instructions. The Linux section is less detailed and refers users to external documentation for specifics. Additionally, the use of Windows-specific tools (PowerShell, Windows Server UI) is emphasized, and screenshots are only provided for Windows workflows. However, parity is better in the AzCopy usage section, where both Linux and Windows examples are given.
Recommendations
- Present Linux and Windows instructions in parallel or in separate, equally detailed sections, rather than always listing Windows first.
- Provide step-by-step Linux certificate import instructions for at least one major distribution (e.g., Ubuntu, RHEL), including screenshots where possible, to match the detail level of Windows instructions.
- Include Linux-specific troubleshooting tips or references, not just generic 'see your OS documentation' notes.
- Where screenshots are used for Windows, consider adding equivalent Linux terminal or UI screenshots.
- When referencing tools, mention cross-platform or Linux-native alternatives where appropriate, and avoid assuming the user is on Windows by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-limits.md
...cs/blob/main//articles/databox/data-box-disk-limits.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing only Windows-specific tools (DataBoxDiskSplitCopy.exe, DataBoxDiskValidation.cmd), providing instructions solely for enabling long paths on Windows clients, and omitting any Linux or cross-platform examples or guidance for file path limitations or data copy operations.
Recommendations
- Include equivalent Linux tools or scripts for data validation and split copy operations, or clarify if such tools are unavailable.
- Provide instructions for handling long file paths on Linux clients, including any relevant OS or filesystem considerations.
- Add Linux-specific or cross-platform examples for common tasks such as copying data to the Data Box Disk, validating data, and troubleshooting errors.
- Explicitly state platform support and any differences in behavior or requirements between Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-overview.md
.../blob/main//articles/databox/data-box-disk-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing BitLocker (a Windows-specific encryption tool) as the default for software-encrypted disks, without mentioning Linux-compatible alternatives or providing Linux-specific instructions. While there is a note about hardware-encrypted disks being suitable for Linux, the main workflow and benefits sections do not address Linux usage or provide Linux-specific examples, tools, or guidance. The documentation assumes familiarity with Windows tools and patterns, and does not offer parity for Linux users.
Recommendations
- Explicitly mention and provide examples for both Windows and Linux workflows, including how to unlock and mount disks on Linux systems.
- Reference Linux-compatible encryption and unlocking tools (e.g., using cryptsetup for hardware-encrypted disks) alongside BitLocker.
- Add Linux-specific instructions or links for copying data to disks, including command-line examples (e.g., using cp, rsync, or dd).
- Ensure that all features and benefits are described in a cross-platform manner, avoiding Windows-first language.
- Include a section or callout specifically for Linux users, outlining any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-disk-quickstart-portal.md
...n//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 displays a Windows bias by prioritizing Windows terminology and tools, especially in the disk unlocking and validation steps. While Linux is mentioned as a supported OS, all detailed instructions and examples (such as the unlock tool and validation script) are Windows-centric, with no equivalent Linux commands or workflows provided. The use of Windows-specific tools (e.g., .cmd scripts) and references to Windows UI elements (e.g., drive letters) further reinforce this bias.
Recommendations
- Provide explicit Linux command-line examples for unlocking disks, including the use of the Data Box Disk unlock tool on Linux (with sample commands).
- Include Linux-specific validation instructions and scripts (e.g., a bash script or instructions for running validation on Linux).
- Mention Linux mount points and file system handling alongside Windows drive letters.
- Ensure that any references to tools (such as .cmd scripts) are accompanied by Linux equivalents (such as .sh scripts or cross-platform tools).
- Where UI steps or terminology differ between Windows and Linux, clarify both paths equally.
Azure Docs
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 detailed options first, with extensive explanation and scenarios. In contrast, Linux instructions are minimal, lacking detailed examples for copying metadata (ACLs, attributes, timestamps), and do not provide equivalent step-by-step guidance or command breakdowns. Linux tools for ACL preservation are only briefly mentioned, with no concrete usage examples.
Recommendations
- Provide Linux instructions and examples at parity with Windows, including step-by-step commands for copying both data and metadata (ACLs, attributes, timestamps).
- List Linux tools (e.g., rsync, getfacl/setfacl, smbcacls, cifsacl) and show how to use them to preserve metadata, with command breakdowns similar to the robocopy section.
- Present Windows and Linux sections in parallel, or alternate which platform is presented first, to avoid the impression of Windows being the primary or default environment.
- Include troubleshooting notes and caveats for Linux users, similar to those provided for Windows/robocopy.
- Link to official documentation for Linux tools, just as is done for robocopy.
Azure Docs
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 demonstrates a Windows-first bias by listing Windows operating systems and tools before Linux equivalents, providing detailed requirements for Windows (including PowerShell, .NET, BitLocker) while Linux requirements are less detailed and lack usage examples. Windows-specific tools and patterns are mentioned explicitly, but there are no command-line or usage examples for Linux tools, and Linux requirements are presented more generically.
Recommendations
- Present Linux and Windows operating systems in parallel or alternate order in tables and lists to avoid Windows-first ordering.
- Provide equivalent detail for Linux requirements, including explicit version numbers and required packages.
- Include example commands for both Windows (e.g., PowerShell) and Linux (e.g., bash/terminal) for common tasks such as unlocking disks, copying data, and validating data.
- List Linux tools (e.g., dislocker, ntfs-3g, sedutil-cli) with brief descriptions and installation instructions, similar to how Windows tools are listed.
- Avoid assuming Windows as the default environment; clarify when features or steps are platform-specific.
- Ensure parity in troubleshooting and operational guidance for both platforms.
Azure Docs
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
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting workflows, error messages, and tool usage instructions are oriented toward Windows environments. Only Windows-specific tools (e.g., BitLocker, Windows PowerShell) are mentioned, and there are no Linux or cross-platform examples or guidance. The unlock tool's usage is described with Windows command-line syntax and parameters, and troubleshooting steps reference Windows-only dependencies. There is no mention of Linux equivalents, nor any instructions for Linux users.
Recommendations
- Add a dedicated section for troubleshooting disk unlocking issues on Linux clients, including common errors and resolutions.
- Provide unlock tool usage examples for Linux, using appropriate command-line syntax and environment variables.
- List Linux prerequisites (e.g., required .NET Core/Mono versions, dependencies) alongside Windows requirements.
- Mention and explain any differences in tool behavior or error messages between Windows and Linux.
- Include troubleshooting steps for Linux-specific issues, such as permissions, mount options, or file system compatibility.
- Ensure parity in documentation structure and depth between Windows and Linux sections.
Azure Docs
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 demonstrates a Windows bias by referencing Windows-specific technologies (e.g., BitLocker) and tools before mentioning Linux equivalents. It provides details about required software for Windows clients but does not specify or link to equivalent Linux requirements or tools. There are no Linux-specific command-line examples or guidance, and the only encryption technology explicitly named is BitLocker (a Windows technology), with Linux support mentioned as a secondary consideration. No Linux-specific workflows or screenshots are provided.
Recommendations
- Include explicit Linux client prerequisites and required software, with links to relevant documentation.
- Provide Linux-specific examples and workflows, especially for disk mounting, encryption, and data copy operations.
- Mention Linux compatibility and tools (e.g., cryptsetup, mount commands) alongside or before Windows tools where applicable.
- Add screenshots or terminal output examples from Linux environments to match the parity of Windows portal screenshots.
- Clarify the process for both Windows and Linux users in all relevant sections, not just as footnotes or secondary notes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-export-logs.md
...cs/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 concepts (such as 'WIN-DATABOXADMIN', NT AUTHORITY, and NTLM authentication), using log samples and terminology that are Windows-centric, and omitting any Linux-specific instructions or examples. There are no examples or guidance for Linux users on accessing logs, interpreting authentication events, or interacting with the Data Box device, and no mention of Linux tools or command-line usage.
Recommendations
- Add Linux-specific examples for accessing and interpreting logs, including sample log entries that would be seen when accessing Data Box from a Linux system.
- Include instructions or references for using Linux tools (such as smbclient, NFS utilities, or Azure CLI on Linux) to interact with the Data Box device.
- Provide parity in authentication and access examples, showing both Windows (NTLM/SMB) and Linux (NFS, Kerberos, or SMB via Samba) scenarios.
- Clarify any differences in log formats or access patterns when using Linux clients, and provide troubleshooting steps relevant to Linux environments.
- Ensure screenshots and sample outputs are not exclusively from Windows environments; include Linux terminal examples where appropriate.
Azure Docs
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 when discussing Split Copy tool errors, it references only Windows tools (e.g., 'diskmgmt.msc') and does not provide Linux equivalents or guidance. There are no Linux-specific examples or instructions for handling these errors, and Windows tools are mentioned exclusively and first in the relevant troubleshooting table.
Recommendations
- For each error in the Split Copy tool section, provide equivalent Linux commands or tools (e.g., using 'lsblk', 'fdisk', or 'gnome-disks' for disk management instead of 'diskmgmt.msc').
- Include Linux-specific troubleshooting steps and examples for Split Copy tool errors, not just Windows.
- When referencing tools or commands, mention both Windows and Linux options together, or provide parallel instructions for each platform.
- Review the documentation for other areas where only Windows tools or patterns are mentioned, and add Linux alternatives to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/how-to-configure-custom-bgp-communities.md
...xpressroute/how-to-configure-custom-bgp-communities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell for all configuration steps, with no mention of Azure CLI, Bash, or cross-platform tools. All code samples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there are no Linux- or macOS-specific examples or guidance.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the steps can be performed from any OS using Azure CLI or PowerShell Core, and clarify any OS-specific requirements.
- Include Bash or shell script examples where appropriate, especially for resource creation and property retrieval.
- Add a section or note highlighting cross-platform compatibility and linking to relevant Azure CLI documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox/data-box-file-acls-preservation.md
...n//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 page demonstrates a Windows bias by focusing primarily on Windows concepts, tools, and privileges (such as SeBackupPrivilege, Administrator/SYSTEM accounts, and Windows NT ACLs) while providing little to no practical guidance or examples for Linux users. Linux is mostly mentioned in terms of limitations (e.g., only Windows NT ACLs are transferred, default ACLs not transferred on Linux), and there are no Linux-specific copy tool examples or instructions. The documentation assumes familiarity with Windows security constructs and does not offer Linux equivalents or parity in detail.
Recommendations
- Provide explicit Linux copy tool examples (e.g., using smbclient, rsync with SMB, or cifs-utils) for preserving metadata and ACLs.
- Explain the Linux-side limitations and what Linux users can expect in terms of ACL preservation, including any mapping or translation of ACLs.
- Include Linux-specific troubleshooting steps and error messages, not just Windows-centric ones.
- List Linux user/group equivalents for the Windows accounts mentioned (Administrator, SYSTEM) or clarify their absence.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than always discussing Windows first.
- Clarify what 'Windows NT ACLs' means for Linux users and how they can verify or manage these from Linux.
- If certain features are unsupported on Linux, suggest workarounds or alternative approaches for Linux environments.
Azure Docs
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 and credential formats in Windows style (e.g., \\<ServerName>\<ShareName>), using Windows-specific terminology (such as 'Right-click', 'Properties', 'Security tab'), and omitting any Linux/NFS examples or instructions. There are no examples or guidance for Linux users or alternative protocols, and all file path and credential examples are Windows-centric.
Recommendations
- Include Linux/NFS examples for connecting to NAS devices, such as mounting NFS shares and specifying Linux-style paths.
- Provide credential format examples for Linux environments (e.g., username@domain or /etc/fstab syntax).
- Add instructions for managing permissions and security from a Linux perspective (e.g., using chmod, chown, or setfacl).
- Clarify whether the data copy service supports only SMB or also NFS, and if so, provide parity in documentation.
- Avoid Windows-specific UI instructions (like 'Right-click') or supplement them with Linux/CLI equivalents.
- Add troubleshooting tips and logs location for Linux users.
Azure Docs
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 (such as 'net use' and File Explorer) before Linux/NFS equivalents. The Windows instructions are more detailed, with explicit command-line and GUI steps, while the Linux section is shorter and less illustrated. There is also a reliance on Windows-specific tools and patterns, such as the use of UNC paths and File Explorer, without offering Linux alternatives for similar tasks.
Recommendations
- Present Linux/NFS instructions alongside or before Windows/SMB instructions to avoid the perception of Windows primacy.
- Expand the Linux section to include equivalent details, such as how to browse NFS shares using common Linux file managers (e.g., Nautilus, Dolphin) and how to unmount shares.
- Provide Linux command-line examples for copying data (e.g., using cp, rsync, or dd) similar to the detailed Windows 'net use' and File Explorer steps.
- Include troubleshooting tips and screenshots for Linux users, matching the depth provided for Windows.
- Reference Linux tools and patterns (e.g., fstab for persistent mounts, systemd automount) where appropriate.