Databox Online
209
Total Pages
71
Linux-Friendly Pages
138
Pages with Bias
66.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
890 issues found
Showing 551-575 of 890 flagged pages
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2309-release-notes.md
...abox-online/azure-stack-edge-gpu-2309-release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias through the frequent use of PowerShell cmdlets and interfaces for management tasks, explicit references to Windows tools (e.g., robocopy, Explorer), and examples that assume a Windows environment (such as mounting NFS shares from Windows paths and using Windows command syntax). There is a lack of equivalent Linux command examples or guidance, and Linux tools or workflows are rarely mentioned, if at all. In some cases, Linux is only referenced as a workaround or alternative, not as a first-class platform.
Recommendations
- Provide Linux CLI/bash equivalents for all PowerShell and Windows command examples (e.g., show how to check VM status or restart VMs using SSH and virsh or similar tools).
- When referencing tools like robocopy or Explorer, also mention Linux alternatives such as rsync, cp, or scp.
- For NFS mount instructions, include Linux mount command examples alongside Windows ones.
- Where PowerShell is mentioned as an interface, clarify if SSH or other Linux-native management options are available and provide links or instructions.
- Review all troubleshooting and workaround steps to ensure Linux users are equally supported with relevant commands and procedures.
- Adopt a platform-neutral or parallel documentation style, presenting Windows and Linux options side by side.
Create Pull Request
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2312-release-notes.md
...abox-online/azure-stack-edge-gpu-2312-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, Windows VM Guest Agent), and provide command-line examples or instructions only for Windows environments. In some cases, Linux alternatives are missing or only mentioned secondarily. There are also multiple references to connecting via PowerShell and using Windows cmdlets, with no equivalent Linux/bash instructions provided.
Recommendations
- For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux alternatives (e.g., rsync, cp, bash commands).
- When giving command-line examples, include both Windows and Linux syntax side by side.
- Mention Linux tools and patterns before or alongside Windows ones to avoid 'Windows-first' ordering.
- For troubleshooting steps involving Windows VMs or PowerShell, add parallel instructions for Linux VMs or SSH-based management where applicable.
- Review all examples and ensure Linux users have clear, actionable guidance for all scenarios.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2403-release-notes.md
...abox-online/azure-stack-edge-gpu-2403-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several workarounds and instructions reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, RDP), and Windows command-line examples are provided without equivalent Linux commands. In some cases, Windows tools or patterns are mentioned first or exclusively, and Linux alternatives are missing or only referenced indirectly. While there are some Linux mentions (e.g., ssh, NFS, Linux VM for IoT Edge), parity in examples and instructions is lacking.
Recommendations
- Provide Linux command-line equivalents for all Windows examples (e.g., show both robocopy and rsync/cp for file copy operations).
- When referencing PowerShell or Windows-specific tools, also include Linux/Unix alternatives (e.g., bash, systemctl, journalctl).
- Avoid mentioning Windows tools or patterns first unless they are more common for the audience; instead, present both Windows and Linux options together.
- For troubleshooting steps that use Windows tools (e.g., RDP, PowerShell cmdlets), provide SSH and Linux-native command alternatives.
- Where possible, add explicit Linux examples for VM management, certificate handling, and network troubleshooting.
- Review all workaround and example sections to ensure Linux users are equally supported and not required to infer steps from Windows instructions.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2407-release-notes.md
...abox-online/azure-stack-edge-gpu-2407-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer, PowerShell cmdlets), provide Windows command syntax before or instead of Linux equivalents, and sometimes omit Linux-specific instructions. In some cases, only Windows remediation steps are detailed, and Linux alternatives are not mentioned or are less prominent.
Recommendations
- For every Windows-specific tool or command (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, bash commands) alongside.
- When showing mount commands or file copy examples, include both Windows and Linux syntax, and do not default to Windows paths or commands.
- If a workaround or remediation is described for Windows (e.g., using PowerShell to manage VMs), provide parallel steps for Linux environments (e.g., SSH and relevant Linux commands).
- Ensure that troubleshooting steps and examples are balanced, with Linux and Windows instructions given equal prominence and detail.
- Where third-party tools are referenced (e.g., SQL command utility), clarify cross-platform availability and usage, and provide installation/use instructions for both Windows and Linux.
- Review all examples and tables for implicit prioritization of Windows workflows, and adjust ordering or content to reflect cross-platform parity.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2501-release-notes.md
...abox-online/azure-stack-edge-gpu-2501-release-notes.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 in several areas: Windows tools and commands (such as PowerShell cmdlets, robocopy, and Windows-specific troubleshooting steps) are referenced without equivalent Linux examples or alternatives. In some cases, Windows paths and commands are shown first or exclusively, and Linux alternatives are missing or only briefly mentioned. This may hinder Linux users from effectively following the documentation.
Recommendations
- For every Windows-specific tool or command (e.g., robocopy, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, systemctl, ps).
- When giving examples of mounting NFS shares, include both Windows and Linux syntax side by side.
- For troubleshooting steps involving Windows VMs or services, add parallel instructions for Linux VMs where applicable.
- Avoid referencing Windows tools or patterns (such as Explorer, RDP, robocopy) exclusively; always mention or link to Linux alternatives.
- Where PowerShell is used to interact with the device, include Bash or SSH-based alternatives for Linux users.
- Review all examples and ensure Linux users are not left without clear, actionable steps.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-certificate-requirements.md
...nline/azure-stack-edge-gpu-certificate-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools and patterns (such as exporting PFX from Windows 10/Server 2016), recommending the Microsoft RSA/Schannel Cryptographic Provider (Windows-specific), and providing next steps only for Azure PowerShell and the Azure Stack Hub Readiness Checker tool (both Windows-centric). There are no Linux or cross-platform certificate management examples or guidance, and Linux-compatible tools or methods are not mentioned.
Recommendations
- Include equivalent Linux/OpenSSL commands and workflows for exporting and managing PFX certificates.
- Mention cross-platform cryptographic providers or clarify if non-Windows providers are supported.
- Provide next steps or links for certificate creation and export using Linux tools (e.g., OpenSSL) alongside PowerShell.
- Clarify whether the Azure Stack Hub Readiness Checker tool is available or has alternatives for Linux/macOS.
- Ensure that references to Windows-specific defaults (like 3DES encryption) are accompanied by Linux/OpenSSL equivalents or instructions.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-certificates-overview.md
...x-online/azure-stack-edge-gpu-certificates-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell and Windows-centric tools for certificate creation and management. Instructions and links for certificate generation use PowerShell or Windows-based tools, with no mention of Linux or cross-platform alternatives. Some verification steps (e.g., right-clicking a certificate and using the Details tab) assume a Windows GUI environment. There are no Linux command-line examples or references to Linux-native certificate management tools.
Recommendations
- Provide equivalent Linux-based instructions for certificate creation, such as using OpenSSL commands for generating and exporting certificates.
- Include examples and links for certificate management on Linux clients, not just Windows/PowerShell.
- When referencing tools (e.g., Readiness Checker, PowerShell), clarify if they are cross-platform or provide Linux alternatives.
- For certificate verification steps, include Linux methods (e.g., using openssl x509 -text -in cert.pem) alongside Windows GUI instructions.
- Review all linked articles to ensure Linux parity in step-by-step guides and tool recommendations.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-cluster-witness-overview.md
...nline/azure-stack-edge-gpu-cluster-witness-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows Server Failover Clustering concepts and terminology, with no mention of Linux-based clustering solutions or examples. All technical explanations, requirements, and setup instructions assume a Windows environment (e.g., SMB file shares, Windows Server clustering), and there are no Linux equivalents or cross-platform considerations provided.
Recommendations
- Include references to Linux-based clustering solutions (e.g., Pacemaker, Corosync) and how quorum/witness concepts apply in those environments.
- Provide Linux-specific examples for setting up a cluster witness, such as using NFS shares or other Linux-supported mechanisms.
- Clarify whether Azure Stack Edge supports only Windows-based clustering or if Linux-based clusters are also supported, and document accordingly.
- If the product is Windows-only, explicitly state this limitation early in the documentation to set expectations.
- If cross-platform support exists, provide parity in setup and configuration instructions for both Windows and Linux environments.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-clustering-overview.md
...box-online/azure-stack-edge-gpu-clustering-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Windows Server Failover Clustering as the clustering technology, repeatedly links to Windows Server documentation, and describes clustering concepts in Windows-centric terms. There are no Linux-based clustering options, tools, or examples mentioned, nor are any Linux command-line or management approaches referenced. Cluster management is described via PowerShell and the local UI, with no mention of Linux CLI or tools.
Recommendations
- Acknowledge in the introduction that clustering on Azure Stack Edge is based on Windows Server Failover Clustering, and clarify if Linux-based clustering is supported or not.
- If Linux-based clustering is not supported, explicitly state this to set expectations for Linux users.
- If Linux-based clustering or management is possible, provide equivalent Linux examples, tools, and references (e.g., Pacemaker, Corosync, Linux CLI commands).
- When describing management interfaces, mention whether Linux-based management (e.g., SSH, Linux CLI) is available or not.
- In sections referencing PowerShell or Windows tools, provide Linux alternatives or clarify their absence.
- Consider including a comparison table or FAQ addressing platform support and management options for both Windows and Linux users.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-manage-certificates.md
...box-online/azure-stack-edge-gpu-manage-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All certificate import instructions and screenshots are exclusively for Windows, with no mention of Linux or macOS workflows. PowerShell and Windows-specific tools (e.g., Chocolatey) are referenced for installing and using openssl, and all command-line examples are shown in PowerShell with Windows file paths. There are no Linux or cross-platform instructions for certificate management, despite openssl being a cross-platform tool.
Recommendations
- Add parallel instructions and screenshots for Linux (and optionally macOS) users, especially for importing certificates into system stores.
- Provide openssl installation steps for Linux (e.g., using apt, yum, or other package managers) alongside the Chocolatey/Windows instructions.
- Show command-line examples using bash or generic shell syntax, not just PowerShell, and use platform-neutral file paths where possible.
- Clarify in each section whether the steps apply to Windows only or if there are alternative steps for other operating systems.
- Reference Linux certificate stores (such as /etc/ssl/certs or update-ca-certificates) and provide guidance for importing certificates on Linux clients.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-collect-virtual-machine-guest-logs.md
...zure-stack-edge-gpu-collect-virtual-machine-guest-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions and commands for collecting VM guest logs, without offering equivalent Linux shell or cross-platform alternatives. The log collection process relies on PowerShell cmdlets, and there are no examples or guidance for users who may be managing the device from a Linux or macOS environment. While log file locations for both Linux and Windows VMs are mentioned, the actual collection workflow is Windows-centric.
Recommendations
- Provide equivalent Linux shell (bash) commands or scripts for collecting VM guest logs, or clarify if the process is only supported via PowerShell.
- Mention and document any cross-platform tools (such as Azure CLI or REST API) that can be used for log collection, if available.
- If PowerShell is required, specify whether PowerShell Core (which is cross-platform) can be used on Linux/macOS, and provide installation or usage instructions.
- Ensure that examples and instructions are presented for both Windows and Linux environments, or explicitly state platform limitations.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-configure-metallb-bgp-mode.md
...ine/azure-stack-edge-gpu-configure-metallb-bgp-mode.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Windows PowerShell cmdlets and tools for configuring MetalLB via BGP on Azure Stack Edge, with no mention or examples of Linux-based workflows or CLI equivalents. All configuration steps and example outputs are Windows/PowerShell-centric, and there is no guidance for users operating from a Linux environment.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using SSH, kubectl, or Linux networking tools) for configuring MetalLB and BGP.
- Include examples of how to connect to the device and perform necessary configuration steps from a Linux or cross-platform shell.
- Mention any platform-specific limitations or requirements up front, and clarify if configuration is only possible via Windows tools.
- If PowerShell is required, note the availability of cross-platform PowerShell Core and provide examples for both Windows and Linux environments.
- Add troubleshooting and verification steps that can be performed from Linux systems.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-connect-virtual-machine-console.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-connect-virtual-machine-console.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by centering the workflow around PowerShell (even for Linux/macOS clients), presenting Windows Remote Desktop instructions before Linux alternatives, and using Windows-centric tools and patterns throughout. Linux instructions are present but less detailed and positioned after Windows examples.
Recommendations
- Provide equal prominence and detail for Linux workflows, including step-by-step instructions for using FreeRDP and other Linux-compatible RDP clients.
- Include example commands and outputs for Linux/macOS terminals, not just PowerShell.
- Clarify any differences or prerequisites for Linux/macOS users (e.g., how to install and use PowerShell 7 on Linux, or alternative ways to connect if PowerShell is not preferred).
- Present Windows and Linux/macOS instructions in parallel sections or side-by-side, rather than always listing Windows first.
- Mention and link to alternative Linux-native tools where applicable, and provide troubleshooting tips specific to non-Windows environments.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-certificates-powershell.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-certificates-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows, providing only Windows PowerShell examples and instructions for certificate creation. There are no Linux or cross-platform alternatives mentioned, and all tooling and workflows assume a Windows environment. The use of Windows-specific tools (PowerShell, Cert:\ store) is exclusive, and Linux users are not given guidance or parity in the documentation.
Recommendations
- Add equivalent Linux examples using OpenSSL for certificate creation, including step-by-step commands.
- Mention cross-platform tools (e.g., Azure CLI, OpenSSL) and provide guidance for both Windows and Linux users.
- Clearly indicate which steps are Windows-specific and offer alternative instructions for Linux/macOS environments.
- Include a section or note at the start highlighting cross-platform options and linking to relevant Linux/macOS documentation.
- Avoid assuming the user is on Windows; use neutral language and provide parallel workflows where possible.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-connect-resource-manager.md
...nline/azure-stack-edge-gpu-connect-resource-manager.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 instructions, examples, and screenshots assume the use of Windows clients, Windows PowerShell (specifically version 5.1), and Windows-specific tools (e.g., Notepad, hosts file at C:\Windows\System32\Drivers\etc). There are no examples or guidance for Linux or macOS users, despite PowerShell Core being cross-platform. Steps for certificate management, environment setup, and connectivity verification are all Windows-centric, and there is no mention of equivalent Linux commands, file paths, or tools.
Recommendations
- Add parallel instructions and examples for Linux (and optionally macOS) clients, including PowerShell Core usage.
- Provide Linux-specific commands for editing the hosts file (e.g., using nano or vi to edit /etc/hosts) and verifying DNS resolution (e.g., using ping, dig, or host).
- Include guidance on importing certificates into Linux certificate stores (e.g., update-ca-certificates, certutil, or relevant distro-specific tools).
- Clarify which steps are Windows-only and which are cross-platform, and provide clear alternatives where possible.
- Update screenshots and file paths to include Linux equivalents.
- Explicitly state PowerShell Core support and provide installation/usage instructions for non-Windows platforms.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-certificates-tool.md
...nline/azure-stack-edge-gpu-create-certificates-tool.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows, requiring a Windows 10 or Windows Server client and providing only PowerShell-based instructions and examples. There are no Linux or cross-platform alternatives mentioned for any step, and all file paths and tooling references are Windows-specific. The Azure Stack Hub Readiness Checker tool is distributed via the PowerShell Gallery, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent instructions for Linux users, including supported distributions and prerequisites.
- If the Azure Stack Hub Readiness Checker tool is not available for Linux, clearly state this limitation and suggest alternative methods for Linux users (e.g., using OpenSSL for CSR generation).
- Include Bash or cross-platform CLI examples alongside PowerShell commands where possible.
- Use platform-agnostic language and file paths in documentation, or provide both Windows and Linux/Mac examples.
- Clarify whether the tool can be run via PowerShell Core on Linux/macOS, and provide installation steps if supported.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-sharing.md
...rticles/databox-online/azure-stack-edge-gpu-sharing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for device access and GPU monitoring (e.g., 'connect to the PowerShell interface', 'Get-HcsNvidiaSmi' command), without providing equivalent Linux shell or command-line examples. There is no mention of standard Linux tools or workflows for GPU management, and all operational instructions assume a Windows-centric environment.
Recommendations
- Provide equivalent Linux shell commands for GPU monitoring (e.g., using 'nvidia-smi' directly in bash).
- Include instructions for accessing the device via SSH or Linux terminal, not just PowerShell.
- Mention and demonstrate Linux-native tools and workflows for GPU management alongside Windows/PowerShell examples.
- Ensure that examples and instructions are presented in a platform-neutral way, or provide both Windows and Linux variants side-by-side.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-system-requirements.md
...box-online/azure-stack-edge-gpu-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive mention of PowerShell cmdlets (e.g., Set-HcsMacAddressPool) for device configuration, without providing equivalent Linux/CLI commands or guidance. There are no Linux shell or cross-platform examples for device management, and the only explicit command-line example is Windows-specific. Additionally, the documentation refers to the PowerShell interface as the means to interact with the device, with no mention of Linux alternatives or parity.
Recommendations
- Provide equivalent Linux shell (bash) or cross-platform CLI commands for all PowerShell cmdlets mentioned, or clarify if such alternatives are unavailable.
- Explicitly state whether device management and configuration can be performed from Linux hosts, and if so, document the supported tools and workflows.
- Where only Windows tools or patterns are available, acknowledge the limitation and provide guidance or workarounds for Linux users.
- Ensure that all command-line examples are presented in both PowerShell and bash (or other relevant shells) where possible.
- Review all references to management interfaces to ensure Linux users are not excluded or left without clear instructions.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-image.md
...e/azure-stack-edge-gpu-create-virtual-machine-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as PowerShell and Windows command prompt) are presented first and in more detail, while Linux instructions are present but less emphasized. The AzCopy usage section and sample output are shown only in a Windows/PowerShell context, with no explicit Linux shell examples. The download and upload steps reference Windows paths and tools, and the sample output is from a Windows PowerShell session. There is also a lack of parity in showing Linux command-line equivalents for AzCopy and related tasks.
Recommendations
- Provide Linux shell (bash) examples alongside PowerShell/Windows examples for all command-line operations, especially for AzCopy usage.
- Include sample output from Linux environments (e.g., bash shell) to demonstrate parity.
- Avoid presenting Windows instructions and tools first by default; alternate or present both OSes in parallel tabs or sections.
- Explicitly mention Linux tools or methods where relevant (e.g., using AzCopy on Linux, or alternative upload/download methods).
- Ensure that all steps referencing file paths or command prompts include Linux equivalents (e.g., ~/azcopy/ or /usr/local/bin/azcopy).
- Where possible, use OS-agnostic language and screenshots, or provide both Windows and Linux visuals.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md
...tack-edge-gpu-create-virtual-machine-marketplace-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a significant Windows bias. While the initial steps use Azure CLI (which is cross-platform), all variable assignments and command examples are written in PowerShell syntax (e.g., $var = ...), and the output is shown from a PowerShell prompt (PS /home/user>). The VHD export process relies on Azure PowerShell cmdlets (New-AzureStorageContext, Start-AzureStorageBlobCopy, Get-AzureStorageBlobCopyState), which are not available or standard on Linux/macOS. There are no equivalent Bash or Linux-native examples provided, and the documentation assumes a Windows/PowerShell environment throughout, despite referencing Azure CLI.
Recommendations
- Provide equivalent Bash/Linux shell examples for all steps, especially for variable assignment and command execution.
- For the VHD export step, include az storage blob copy or azcopy examples, which are cross-platform and work natively on Linux/macOS.
- Avoid using PowerShell-specific cmdlets (e.g., New-AzureStorageContext) as the only option; if PowerShell is shown, always pair with a Bash/Linux alternative.
- Show output from both PowerShell and Bash shells, or use a neutral prompt (e.g., $ or >) to avoid implying Windows-only usage.
- Explicitly state that the workflow can be performed on Linux/macOS, and provide any prerequisites or differences for those platforms.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-checklist.md
...atabox-online/azure-stack-edge-gpu-deploy-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools (such as WSUS and the default use of the public Windows update server) and omitting Linux equivalents or cross-platform alternatives. There are no explicit Linux or macOS instructions or examples for tasks such as network configuration, proxy setup, or update server configuration. The documentation assumes familiarity with Windows environments and tools, and does not provide parity for Linux users.
Recommendations
- Include instructions for configuring update servers on Linux (e.g., using local Linux-based update mirrors or repositories) alongside WSUS/Windows Update references.
- Mention and provide examples for network configuration on Linux and macOS (e.g., how to change IPv4 settings, set static IPs, configure NTP, etc.).
- If referencing tools like the Azure Stack Network Readiness Checker or Network Readiness Tool, clarify their cross-platform compatibility or provide Linux/macOS alternatives if available.
- When discussing proxy or firewall settings, include command-line examples for both Windows (e.g., PowerShell, netsh) and Linux (e.g., iptables, systemd-resolved, environment variables).
- Avoid defaulting to Windows terminology (e.g., 'public Windows update server') and instead use neutral or cross-platform language, or explicitly call out options for different operating systems.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-add-shares.md
...tabox-online/azure-stack-edge-gpu-deploy-add-shares.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/SMB connection steps and tools (e.g., Notepad, Windows Explorer, File Explorer, 'net use' command) first and in greater detail, while Linux/NFS instructions are provided later and with less visual support. The host file modification example is exclusively for Windows, with no explicit Linux equivalent. Visuals and step-by-step instructions are Windows-centric, and Linux users are expected to infer or adapt steps.
Recommendations
- Provide parallel Linux examples for all steps, including host file modification (e.g., editing /etc/hosts with nano or vi).
- Include screenshots or terminal output for Linux steps, similar to the Windows visuals.
- Present SMB (Windows) and NFS (Linux) instructions in parallel sections, or alternate which platform is described first.
- Mention Linux tools and commands explicitly (e.g., using 'mount', 'nano', 'vi', 'cat') wherever Windows tools are referenced.
- Clarify any platform-specific caveats or differences in both directions, not just for Windows.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-add-storage-accounts.md
...ne/azure-stack-edge-gpu-deploy-add-storage-accounts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell cmdlets and sample outputs from a Windows environment (e.g., 'PS C:\windows\system32>'). It references Windows-specific tools and file formats (e.g., Azure PowerShell, .cer files, Storage Explorer UI steps for Windows), and does not provide equivalent Linux/Unix command-line instructions or examples. There is no mention of Linux tools, shell commands, or how to perform these tasks on non-Windows platforms.
Recommendations
- Provide equivalent command-line examples using Azure CLI (az) for Linux/macOS users alongside PowerShell examples.
- Include sample outputs and instructions for running commands in Bash or other Unix shells.
- Document how to obtain storage account keys and connect to the device using cross-platform tools, not just PowerShell.
- Clarify file format differences and import steps for certificates on Linux/macOS (e.g., PEM, .crt, .pfx handling).
- Ensure Storage Explorer instructions are not Windows-specific and mention Linux/macOS installation and usage where applicable.
- Where screenshots or UI steps are given, provide notes for cross-platform differences.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-configure-certificates.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-configure-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as Azure PowerShell and Windows Server Update Services), showing certificate download examples in Windows File Explorer, and omitting Linux or cross-platform command-line examples for certificate creation, conversion, or installation. There are no explicit instructions or screenshots for Linux or macOS users, nor are alternative tools or workflows mentioned.
Recommendations
- Provide equivalent Linux/macOS instructions and examples for creating, converting, and installing certificates (e.g., using OpenSSL, Linux certificate stores, or CLI tools).
- Include screenshots or terminal commands showing certificate handling on Linux and macOS, not just Windows File Explorer.
- Mention cross-platform tools (such as Azure CLI, OpenSSL, or platform-agnostic certificate import methods) alongside or before Windows-specific tools.
- Clarify that the steps are applicable to all supported client OSes, and provide links or references to OS-specific certificate management documentation.
- When referencing tools like Azure PowerShell or WSUS, also mention their Linux/macOS equivalents or alternatives, if available.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-configure-compute.md
...nline/azure-stack-edge-gpu-deploy-configure-compute.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a Windows bias by referencing the use of the PowerShell cmdlet `Set-HcsMacAddressPool` for configuring MAC addresses, without mentioning equivalent Linux commands or workflows. There are no Linux CLI examples or references to Linux tools for device configuration, and the only command-line example is specific to PowerShell.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using SSH and Linux shell commands) for configuring MAC addresses or other device settings.
- Mention whether the device can be managed from Linux or cross-platform terminals, and if so, provide guidance or examples.
- Clarify if PowerShell is required or if there are REST API or other cross-platform alternatives.
- Ensure that all command-line examples are given for both Windows (PowerShell) and Linux (bash/CLI) where possible.