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 626-650 of 890 flagged pages
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-deploy-configure-certificates.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-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 and workflows (such as Azure PowerShell and Windows Server Update Services), showing screenshots of certificates in Windows File Explorer, and omitting Linux or cross-platform certificate management examples. There are no instructions or examples for Linux users on how to generate, convert, or install certificates, nor are Linux tools or commands mentioned.
Recommendations
- Provide equivalent Linux-based instructions for generating, converting, and installing certificates (e.g., using OpenSSL, Linux CLI commands).
- Include screenshots or walkthroughs for certificate management on Linux systems (such as using Nautilus or command-line tools).
- Mention and link to cross-platform tools (e.g., Azure CLI, OpenSSL) alongside Windows-specific tools like Azure PowerShell.
- When referencing certificate conversion or installation, offer both Windows and Linux command examples and file paths.
- Avoid assuming the client system is Windows; clarify that instructions apply to both Windows and Linux clients, or provide parallel sections for each.
Create Pull Request
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-deploy-configure-compute.md
...ine/azure-stack-edge-pro-2-deploy-configure-compute.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing only the PowerShell interface and the `Set-HcsMacAddressPool` cmdlet for configuring MAC addresses, with no mention of equivalent Linux commands or tools. There are no Linux shell or cross-platform examples provided for device configuration tasks, and the documentation assumes the use of Windows-native tools.
Recommendations
- Provide equivalent Linux shell commands or instructions for configuring MAC addresses and other device settings, if supported.
- Mention whether the device management interface (such as PowerShell) is available or supported on Linux, or provide alternatives (e.g., Azure CLI, SSH).
- Include cross-platform or OS-agnostic instructions where possible, especially for tasks like downloading configuration files or accessing the Kubernetes cluster.
- If certain features are only available via PowerShell/Windows, explicitly state this limitation and suggest workarounds or alternatives for Linux users.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-powershell-based-configuration.md
...ine/azure-stack-edge-powershell-based-configuration.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 and PowerShell. All examples use PowerShell cmdlets, and the prerequisites explicitly require Windows 10/Server and PowerShell 5.1 or later. There is no mention of Linux or cross-platform alternatives, nor are there any Bash, CLI, or Linux-native instructions. The documentation assumes the user is on a Windows system and does not address Linux users at all.
Recommendations
- Add explicit guidance for Linux users, including supported platforms and any limitations.
- Provide equivalent instructions using Azure CLI, Bash, or cross-platform PowerShell Core (pwsh), if supported.
- Clarify whether the PowerShell module can be used on Linux/macOS with PowerShell Core, and provide installation steps for those environments.
- If Windows-only tooling is required, state this clearly at the top and suggest alternative management approaches for Linux users (e.g., Azure CLI, REST API, or web UI).
- Include at least one end-to-end example for Linux users or explicitly document the lack of Linux support.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-deploy-configure-network-compute-web-proxy.md
...-edge-pro-2-deploy-configure-network-compute-web-proxy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation shows evidence of Windows bias, particularly in the clustering and network topology sections. Windows Server concepts and tools (such as NIC Teaming, Failover Clustering, Cloud Witness, File Share Witness) are referenced directly, with links to Microsoft Windows Server documentation. PowerShell is mentioned as the CLI method for certain configuration tasks, and no Linux or cross-platform CLI alternatives are provided. The documentation assumes familiarity with Windows networking patterns and does not mention or provide parity for Linux-based equivalents.
Recommendations
- Provide Linux-based or cross-platform CLI examples (e.g., using Azure CLI, Bash, or REST API) alongside or instead of PowerShell for configuration tasks.
- When referencing clustering, networking, or witness concepts, include Linux-native equivalents (e.g., Pacemaker/Corosync for clustering, Linux bonding/teaming for NIC redundancy) or clarify if only Windows-based approaches are supported.
- Avoid linking exclusively to Windows Server documentation for core concepts; instead, provide neutral explanations or link to cross-platform/Azure-native resources.
- Explicitly state OS requirements or limitations if only Windows-based management is supported, and offer guidance for Linux administrators where possible.
- Add notes or sections addressing how Linux administrators can perform similar tasks, or clarify if the device is managed entirely through the web UI regardless of admin OS.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-deploy-set-up-device-update-time.md
...zure-stack-edge-pro-2-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 update mechanisms (Microsoft Update server, Windows Server Update Services/WSUS), defaulting to time.windows.com as the NTP server, and omitting any mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux-based update servers (such as apt/yum repositories or Linux NTP defaults), nor is there any mention of Linux administration tools or patterns.
Recommendations
- Include examples or references for configuring update servers using Linux-based solutions (e.g., apt, yum, or local Linux update mirrors) if supported by the device.
- Mention alternative, platform-neutral NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
- Clarify whether the device supports integration with non-Windows update infrastructures, and provide guidance if so.
- Avoid defaulting to Windows-centric terminology and tools; provide parity for Linux environments where possible.
- If the device is Windows-only, explicitly state this limitation to set expectations for Linux administrators.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-2-system-requirements.md
...x-online/azure-stack-edge-pro-2-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits some Windows bias, particularly through the mention of the PowerShell cmdlet (`Set-HcsMacAddressPool`) as the only method for configuring MAC addresses on the device. There are no equivalent Linux command-line examples or references, and the only explicit tool for device management is Windows PowerShell. Additionally, the troubleshooting link for Kubernetes issues points to a PowerShell interface, with no mention of Linux-based alternatives. There are no Linux-specific instructions or parity in examples for device management.
Recommendations
- Provide equivalent Linux command-line instructions or tools for configuring device settings (e.g., MAC address pool), or clarify if such functionality is only available via PowerShell.
- If device management is possible via SSH, REST API, or other cross-platform tools, include those options and examples.
- When referencing troubleshooting or management interfaces, mention both Windows and Linux options, or state platform limitations explicitly.
- Ensure that all examples and instructions are provided for both Windows and Linux environments where possible, or clarify platform-specific requirements.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-pro-r-deploy-checklist.md
...abox-online/azure-stack-edge-pro-r-deploy-checklist.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 tools (e.g., WSUS, Windows Update server), omitting Linux equivalents for update management, and generally assuming a Windows-centric environment for device management and network readiness. There are no explicit Linux or cross-platform examples or guidance for users who may be deploying from non-Windows systems.
Recommendations
- Include Linux equivalents for update server configuration, such as mentioning support for Linux-based update mirrors or repositories.
- Reference cross-platform or Linux-compatible tools for network readiness checks, or clarify if the provided tools are Windows-only.
- Provide explicit examples or notes for Linux/macOS users in sections that mention device connection, network configuration, or credential management.
- Avoid assuming the use of Windows Update or WSUS by default; mention alternative update mechanisms where possible.
- Ensure parity in instructions for device setup and management regardless of the administrator's operating system.
Databox Online
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 Tools
Missing Linux Example
Summary
The documentation primarily references PowerShell as the CLI tool for advanced configuration (e.g., changing Kubernetes workload profiles, pod/service subnets), with no mention of Linux shell equivalents or cross-platform CLI options. There are no Linux/Unix-specific instructions or examples, and the only command-line guidance points to PowerShell documentation. The UI instructions are platform-neutral, but the CLI guidance is Windows-centric.
Recommendations
- Provide equivalent Linux shell (bash) or cross-platform Azure CLI examples alongside PowerShell instructions for all command-line operations.
- Explicitly mention and link to Linux-compatible tools (e.g., Azure CLI, az commands) where possible.
- Clarify whether all configuration steps can be performed from non-Windows systems, and if not, provide workarounds or alternatives.
- Add a section or note addressing Linux/macOS users, including any prerequisites or differences in workflow.
- Ensure that all referenced scripts or automation steps are cross-platform or have Linux alternatives.
Databox Online
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 demonstrates Windows bias primarily by only referencing Windows PowerShell for device management in the 'Next steps' section. There are no examples or references to Linux tools, Bash, or cross-platform CLI usage. The documentation does not mention or provide parity for Linux users, nor does it offer alternative instructions or links for non-Windows environments.
Recommendations
- Include equivalent instructions or links for managing Azure Stack Edge devices using Azure CLI or Bash scripts, which are cross-platform.
- Add references to Linux and macOS environments where appropriate, ensuring that examples are not limited to Windows/PowerShell.
- Where PowerShell is mentioned, also mention Azure CLI or REST API usage, and provide links or examples for those methods.
- Review all 'Next steps' and guidance links to ensure Linux users are not excluded and have clear, supported pathways for device management.
Databox Online
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 referencing Windows-specific tools (e.g., Windows Server Update Services, time.windows.com) and update patterns, without mentioning or providing Linux equivalents. The update server configuration focuses on Microsoft Update and WSUS, and the default NTP server is time.windows.com, a Microsoft service. There are no examples or guidance for Linux-based update or time synchronization solutions, nor is there mention of cross-platform alternatives.
Recommendations
- Include references to Linux-compatible update mechanisms or clarify if only WSUS/Microsoft Update are supported.
- When mentioning NTP servers, provide examples of neutral/public NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
- If the device supports Linux-based management or integration, provide examples or notes for Linux admins (e.g., how to configure updates or time sync from a Linux environment).
- Avoid assuming the environment is Windows-centric; mention cross-platform options where possible.
- Add a note clarifying platform compatibility for update and time server configuration, especially if only Windows-based solutions are supported.
Databox Online
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
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-native tools and patterns, such as BitLocker for encryption and Windows Defender Application Control (WDAC) for application whitelisting. Remote management is described only via PowerShell, with no mention of SSH or Linux-based management options. There are no Linux command-line examples or references to Linux-native security tools, and Windows terminology and technologies are presented as the default or only option.
Recommendations
- Provide equivalent Linux-based management instructions, such as using SSH for remote access and Linux-native command-line examples.
- Mention and document Linux-compatible encryption solutions (e.g., LUKS/dm-crypt) if supported, or clarify if the device is Windows-only.
- Include examples or references for managing the device from Linux or cross-platform environments, not just PowerShell.
- If the device is Windows-specific, explicitly state this early in the documentation to set user expectations.
- Reference or provide parity for security tools and practices common in Linux environments, such as auditd for logging or SELinux/AppArmor for application control, where applicable.
Databox Online
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 page demonstrates a Windows bias by referencing Azure PowerShell as the recommended tool for managing blob tiers, and by providing monitoring commands only via the PowerShell interface. There are no equivalent Linux CLI or Bash examples, nor is there mention of cross-platform alternatives such as Azure CLI. This may leave Linux users without clear guidance for performing the same tasks.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside or in place of PowerShell instructions for tasks such as setting blob tiers and monitoring.
- Explicitly mention that both Windows and Linux clients are supported, and provide examples for both platforms where relevant.
- Include Bash or shell script examples for common operations, especially for monitoring and management tasks.
- Clarify when a feature is only available via PowerShell, and suggest workarounds or alternatives for Linux users if possible.
Databox Online
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only command-line interface example for device reset, referencing Windows-centric tools and workflows, and omitting equivalent Linux instructions or tools. The local web UI is mentioned as an alternative, but no Linux CLI or shell examples are provided. Additionally, there is no mention of Linux-native tools or guidance for users operating from non-Windows environments.
Recommendations
- Add equivalent Linux shell (bash) or CLI instructions for device reset and management, alongside PowerShell examples.
- Reference cross-platform tools or provide explicit guidance for Linux/macOS users where PowerShell or Windows-specific tools are mentioned.
- Ensure that any downloadable scripts or automation steps are available in both PowerShell and bash (or other common Linux shells).
- Where possible, use neutral language (e.g., 'command-line interface' instead of 'PowerShell') and provide parity in screenshots and UI walkthroughs for different platforms.
- Explicitly state platform support and provide links to Linux/macOS documentation or troubleshooting guides.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-security.md
...n/articles/databox-online/azure-stack-edge-security.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-specific security tools (e.g., Windows Defender Device Guard, BitLocker) and remote management via PowerShell. There are no mentions of Linux equivalents, nor are Linux-based management or security options discussed. All examples and instructions assume a Windows environment, with no parity for Linux users.
Recommendations
- Include information on whether the Azure Stack Edge Pro FPGA device supports Linux-based management interfaces (e.g., SSH, Linux CLI tools) and, if so, provide equivalent instructions.
- If only Windows management is supported, explicitly state this limitation for transparency.
- Mention Linux security tools or practices where applicable, or clarify if only Windows-based security features (like BitLocker and Device Guard) are available.
- Provide examples or guidance for Linux users where possible, such as how to connect to the device or manage it from a Linux system.
- Ensure that references to tools and procedures are platform-neutral where possible, or provide parallel instructions for both Windows and Linux environments.
Databox Online
Azure Stack Edge 2110 release notes
...abox-online/azure-stack-edge-gpu-2110-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several features and workarounds reference Windows-specific tools (PowerShell, Windows VM Guest Agent, RDP, waappagent.exe, robocopy, Explorer), and provide command examples or instructions only for Windows environments. PowerShell is the primary interface mentioned for device management and configuration, with no equivalent Linux shell or CLI examples. In some cases, Windows-centric instructions are given first or exclusively, and Linux alternatives are missing or only implied.
Recommendations
- Provide equivalent Linux/macOS command examples for all device management tasks, especially where PowerShell is referenced.
- Include Linux-native tools (e.g., shell commands, SSH, SCP, rsync) alongside Windows tools like robocopy and Explorer.
- Document how to connect to and manage the device from Linux/macOS clients, including certificate management and remote support.
- Clarify whether features (e.g., remote support, VM management, custom script extensions) are accessible or manageable from Linux/macOS, and provide guidance if so.
- Where Windows VM-specific troubleshooting is described, add parallel instructions for Linux VMs if applicable.
Databox Online
Azure Stack Edge 2111 release notes
...abox-online/azure-stack-edge-gpu-2111-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several workarounds and examples reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, RDP, Windows VM Guest Agent), and some instructions are tailored for Windows environments (e.g., mounting NFS shares using Windows paths, troubleshooting Windows VM extensions). There is a lack of equivalent Linux/macOS examples or guidance, and Windows tools are often mentioned before or instead of cross-platform alternatives.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific instructions, such as using 'cp' or 'rsync' instead of 'robocopy', and SSH instead of RDP.
- Include PowerShell commands alongside Bash or shell commands for Linux/macOS users.
- When referencing tools like 'sqlcmd', clarify installation steps for Linux/macOS and provide example commands.
- For NFS mounting, show both Windows and Linux mount commands and options.
- For troubleshooting VM extensions, offer guidance for Linux VMs as well as Windows VMs.
- Avoid listing Windows tools or examples first; present cross-platform or OS-specific instructions in parallel.
Databox Online
Azure Stack Edge 2510 release notes
...abox-online/azure-stack-edge-gpu-2510-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Multiple workarounds and examples reference Windows-specific tools (e.g., robocopy, Explorer, RDP, PowerShell cmdlets like Get-VM and Start-VM), and some instructions are given only for Windows environments. In several cases, Linux equivalents are missing or not mentioned, and Windows-centric patterns (such as mounting NFS shares using Windows paths) are shown before or instead of Linux alternatives. This creates friction for Linux/macOS users who may need to adapt or research their own solutions.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific commands and tools (e.g., show how to mount NFS shares on Linux, use Linux file copy tools like cp/rsync instead of robocopy/Explorer).
- Include PowerShell and Bash (or CLI) examples side-by-side for device management tasks.
- Reference cross-platform tools where possible, or clarify platform-specific limitations.
- Explicitly state when a workaround or tool is Windows-only, and offer alternatives for other platforms.
- Reorder examples so that Linux/macOS instructions are presented alongside or before Windows instructions when relevant.
Databox Online
Azure Stack Edge 2105 release notes
...abox-online/azure-stack-edge-gpu-2105-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Many configuration and management tasks are described as being performed via the PowerShell interface, with no mention of Linux/macOS alternatives. Windows tools (e.g., robocopy, Explorer, sqlcmd, RDP) are referenced for workarounds and examples, often without Linux equivalents. In several cases, Windows-specific instructions or tools are provided first or exclusively, and Linux/macOS users are left to infer their own methods. There are also instances where only Windows VM issues are discussed in detail.
Recommendations
- Provide equivalent Linux/macOS command-line examples (e.g., Bash, SSH, Linux-native tools) alongside PowerShell instructions.
- Reference cross-platform tools (e.g., AzCopy, curl, scp) where possible, and clarify their usage on Linux/macOS.
- When mentioning Windows tools (robocopy, Explorer, sqlcmd, RDP), also mention Linux/macOS alternatives (rsync, cp, sqlcmd for Linux, SSH).
- Explicitly state whether management interfaces (PowerShell, local UI) are accessible from Linux/macOS, and provide instructions for connecting from those platforms.
- For VM management and troubleshooting, include Linux VM scenarios and solutions, not just Windows VM issues.
Databox Online
Azure Stack Edge 2501 release notes
...abox-online/azure-stack-edge-gpu-2501-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several workarounds and examples reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell, Windows VM Guest Agent) and provide Windows command syntax or instructions before or instead of Linux equivalents. Some examples (e.g., mounting NFS shares) use Windows paths and commands, and PowerShell is repeatedly referenced for device management and troubleshooting. In some cases, Linux alternatives are missing or only briefly mentioned.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific commands and tools (e.g., show how to mount NFS shares using Linux mount syntax, use rsync or cp instead of robocopy/Explorer).
- Include Linux/macOS troubleshooting steps alongside PowerShell/Windows VM Guest Agent instructions.
- Ensure examples and sample commands are presented for both platforms, or at least alternate between Windows and Linux/macOS.
- Explicitly mention cross-platform tools where possible (e.g., AzCopy, sqlcmd) and clarify installation steps for Linux/macOS.
- Avoid referencing Windows tools or UI elements exclusively; provide parity for Linux/macOS users.
Databox Online
Deploy IoT Edge workload using GPU sharing on Azure Stack Edge Pro GPU device
...ne/azure-stack-edge-gpu-deploy-iot-edge-gpu-sharing.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with all command-line examples using PowerShell, references to Windows file paths, and explicit requirements for PowerShell on the client. There are no Linux/macOS-specific instructions, examples, or file path conventions, and Windows tools and patterns are mentioned exclusively throughout the guide.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell commands, using bash and standard Linux utilities.
- Include instructions for saving Kubernetes config files in Linux/macOS home directories (e.g., ~/.kube/config).
- Clarify whether Linux/macOS clients are supported and, if so, detail any differences in workflow or required tools.
- Show kubectl usage examples from Linux/macOS terminals, including relevant file paths and environment setups.
- Mention any platform-specific prerequisites or limitations explicitly.
Databox Online
Azure Stack Edge 2506 release notes
...abox-online/azure-stack-edge-gpu-2506-release-notes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools (e.g., robocopy, Explorer), commands (PowerShell cmdlets), and troubleshooting steps are mentioned without Linux/macOS equivalents or alternatives. Some examples and workarounds are presented using Windows syntax or tools first, and in some cases, Linux instructions are missing or less detailed. While there are references to Linux (e.g., Ubuntu, AzCopy), the overall pattern prioritizes Windows environments, especially in administrative and troubleshooting contexts.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific tools and commands (e.g., suggest rsync or cp instead of robocopy/Explorer).
- Include PowerShell and Bash (or shell) command examples side-by-side for device management and troubleshooting.
- Ensure troubleshooting steps for VM extensions and agent issues include guidance for Linux VMs, not just Windows VMs.
- Where mounting examples are given, show both Windows (net use, Explorer) and Linux (mount command) syntax.
- Review all workarounds and ensure Linux/macOS users have clear, actionable instructions.
- Avoid presenting Windows examples first when both platforms are supported; use neutral or parallel presentation.
Databox Online
Connect to the virtual machine console on Azure Stack Edge Pro GPU device
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-connect-virtual-machine-console.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation is heavily PowerShell-centric, with all management commands and examples shown in PowerShell syntax. Windows Remote Desktop is presented first and in more detail than the Linux alternative (FreeRDP), and the workflow assumes familiarity with Windows tools and patterns. While Linux and macOS are mentioned as supported platforms for PowerShell and remote desktop, examples and instructions prioritize Windows usage.
Recommendations
- Provide equivalent command-line examples using Bash or other native Linux/macOS shells where possible, especially for connecting to the device and managing VM access.
- Present Linux/macOS remote desktop instructions (e.g., FreeRDP, Remmina) before or alongside Windows Remote Desktop, with equal detail.
- Clarify any platform-specific differences or caveats, such as credential handling or file formats (.rdp files on Linux/macOS).
- Include troubleshooting steps and sample outputs for Linux/macOS clients.
- Explicitly mention how to install and use required tools on Linux/macOS, not just link to their homepages.
Databox Online
Deploy GPU VMs on your Azure Stack Edge Pro GPU device
...ine/azure-stack-edge-gpu-deploy-gpu-virtual-machine.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell is referenced as the primary method for connecting to Azure Resource Manager and for removing GPU extensions, with no mention of Linux/macOS CLI alternatives. The troubleshooting section specifically calls out Windows 2016 VHD requirements. While Linux is mentioned (e.g., Red Hat image note, Linux tab for GPU extension install), Windows tools and patterns are generally presented first or exclusively, and Linux/macOS users may need to infer equivalent steps.
Recommendations
- Explicitly document Linux/macOS alternatives for connecting to Azure Resource Manager (e.g., Azure CLI commands).
- Provide instructions for removing GPU extensions using Azure CLI or REST API, not just Azure PowerShell.
- Ensure that examples and troubleshooting steps are provided for both Windows and Linux VMs where relevant.
- Where Windows-specific requirements are listed (e.g., TLS 1.2 for Windows 2016), add any Linux-specific caveats or confirm none exist.
- Present cross-platform instructions in parallel, or alternate which platform is shown first.
Databox Online
Install GPU extension on GPU VMs on your Azure Stack Edge Pro GPU device
...-edge-gpu-deploy-virtual-machine-install-gpu-extension.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell is used as the exclusive CLI for both Windows and Linux instructions, with all command-line examples and outputs shown from a Windows environment (e.g., PS C:\WINDOWS\system32>). Windows instructions and examples are consistently presented before Linux equivalents, and Windows-specific tools and file paths are referenced. Linux users are expected to use PowerShell and Windows paths for deployment and monitoring, which may not align with typical Linux workflows.
Recommendations
- Provide native Bash/CLI examples for Linux users, using Azure CLI or shell scripts instead of PowerShell.
- Show Linux command outputs from a Linux terminal (e.g., bash prompt), not Windows PowerShell.
- Clarify that PowerShell Core is cross-platform, but also offer instructions for users who prefer Bash or Azure CLI.
- List Linux instructions/examples before or alongside Windows instructions to avoid 'Windows first' ordering.
- Reference Linux file paths and tools (e.g., use /home/user/...) in Linux sections.
Databox Online
Azure Stack Edge Pro GPU device access, power, and connectivity mode | Microsoft Docs
...e-stack-edge-gpu-manage-access-power-connectivity-mode.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias. Remote device access is described exclusively via PowerShell, with no mention of Linux/macOS alternatives (e.g., SSH, OpenSSL, Azure CLI). All command-line examples use PowerShell cmdlets, and BitLocker (a Windows-specific encryption tool) is referenced for disk encryption. There are no Linux/macOS-specific instructions, nor is there guidance for users on non-Windows platforms to perform equivalent tasks. Windows terminology and tools are presented first and exclusively throughout the page.
Recommendations
- Provide equivalent Linux/macOS instructions for remote device access, such as using SSH or Azure CLI.
- Include command-line examples using Bash and Azure CLI alongside PowerShell.
- Clarify whether BitLocker operations can be managed from Linux/macOS, or provide alternative instructions for managing encryption keys on those platforms.
- Explicitly state platform requirements and limitations for each operation.
- Add a section or notes for cross-platform users, highlighting any differences or workarounds.