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 1226-1250 of 2185 flagged pages
Azure Docs
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 First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows tools and patterns (such as PowerShell, RDP, and Windows-specific utilities like 'robocopy' and 'Explorer') are referenced without equivalent Linux alternatives. Examples for mounting NFS shares and troubleshooting VM extensions are given using Windows paths, commands, and tools, with no Linux command-line equivalents provided. PowerShell is referenced as the interface for device management and troubleshooting, but there is no mention of SSH or Bash alternatives. In some cases, Linux is mentioned (e.g., 'Linux VM'), but the instructions and examples are still Windows-centric or Windows-first.
Recommendations
- For every Windows-specific tool or command (e.g., PowerShell, robocopy, Explorer, RDP), provide equivalent Linux commands (e.g., Bash, cp/rsync, Nautilus, SSH).
- When giving example commands (such as mounting NFS shares), include both Windows and Linux syntax side by side.
- Reference Linux management patterns (e.g., SSH access, systemctl for services) alongside PowerShell and Windows patterns.
- When troubleshooting VM extensions or services, provide Linux-based diagnostic steps (e.g., using systemctl, journalctl, or ps commands) in addition to Windows steps.
- Ensure that documentation for tools like sqlcmd includes installation and usage instructions for both Windows and Linux clients.
- Review all examples and instructions to ensure Linux parity and avoid Windows-first ordering.
Create Pull Request
Azure Docs
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 environments. All instructions and examples are provided exclusively for Windows, using PowerShell commands and Windows-specific paths. There is no mention of Linux or cross-platform alternatives, and the prerequisites explicitly require a Windows client. The Azure Stack Hub Readiness Checker tool is only referenced as being installed via the PowerShell Gallery, with no indication of Linux compatibility or usage.
Recommendations
- Clarify whether the Azure Stack Hub Readiness Checker tool is available for Linux or cross-platform use. If not, state this limitation explicitly.
- If the tool is Windows-only, suggest alternative methods or tools for Linux users to generate CSRs and manage certificates, or provide a roadmap for cross-platform support.
- If the tool is cross-platform, provide equivalent Linux instructions, including installation steps (e.g., via pip, apt, or other package managers), command-line examples using bash or compatible shells, and Linux file paths.
- Include a note in the prerequisites section about supported operating systems, and, if possible, remove the hard requirement for Windows if cross-platform support exists.
- Provide sample scripts and usage instructions for Linux environments, ensuring parity with the PowerShell examples.
Azure Docs
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 is heavily biased toward Windows environments. All command-line examples use PowerShell cmdlets, and sample outputs are from Windows PowerShell. The instructions for obtaining storage account keys and certificates reference only Windows tools and paths. Storage Explorer instructions assume a Windows environment, and there are no Linux or cross-platform command-line examples or alternative tools mentioned. There is no guidance for Linux or macOS users on how to perform equivalent tasks.
Recommendations
- Provide equivalent command-line examples using Azure CLI (az) for Linux/macOS users alongside PowerShell examples.
- Include sample outputs from non-Windows environments (e.g., bash shell).
- Mention and link to cross-platform tools (e.g., Azure CLI, Storage Explorer for Linux/macOS) and provide installation instructions.
- Clarify certificate handling steps for Linux/macOS (e.g., PEM vs. CER, import paths, commands).
- Explicitly state that the procedures are cross-platform where possible, and highlight any steps that are Windows-specific.
- Add a section or callouts for Linux/macOS users, describing any differences or additional steps required.
Azure Docs
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 First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell cmdlets), and in some cases, only Windows instructions are provided or are listed before Linux equivalents. There are also instances where Linux alternatives are missing or less detailed, and PowerShell is emphasized for device management tasks.
Recommendations
- For every Windows-specific tool or command (e.g., robocopy, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, bash/ssh commands) and examples.
- When describing procedures (such as mounting NFS shares or managing VMs), include both Windows and Linux workflows, and avoid listing Windows first by default.
- Where PowerShell is referenced for device management, also document how to perform the same tasks using SSH and bash on Linux.
- For file copy and management, mention Linux-native tools (cp, rsync, scp) alongside Windows tools.
- In troubleshooting steps involving Windows VMs or RDP, provide parallel guidance for Linux VMs (e.g., SSH, systemctl/service management).
- Audit all examples and ensure Linux parity in instructions, especially for cross-platform scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-create-kubernetes-cluster.md
...line/azure-stack-edge-gpu-create-kubernetes-cluster.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 environments, with all examples and instructions using PowerShell commands and Windows-specific tools. There are no Linux/macOS equivalents provided for any steps, including connecting to the device, managing the Kubernetes cluster, or installing and using kubectl. The instructions for editing the hosts file and file paths are also Windows-specific, and there is no mention of Linux or macOS workflows.
Recommendations
- Provide parallel instructions and examples for Linux and macOS users, including shell (bash) commands for connecting to the device and managing the cluster.
- Include Linux/macOS equivalents for installing kubectl (e.g., using curl/wget and chmod, or package managers like apt, yum, or brew).
- Show how to edit the hosts file on Linux/macOS (e.g., using sudo nano /etc/hosts).
- Use cross-platform file path examples (e.g., ~/.kube/config for Linux/macOS, %USERPROFILE%\.kube\config for Windows).
- Clarify in the prerequisites and throughout the document that all major client OSes are supported, and link to OS-specific instructions where appropriate.
- Where PowerShell cmdlets are used for device-specific operations, indicate if there are REST APIs or CLI alternatives that can be used from non-Windows clients, or explicitly state if Windows is required for those steps.
Azure Docs
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 examples are consistently presented before Linux equivalents ('windows_first'). PowerShell and Windows command-line tools are emphasized, especially in sections on downloading and copying VHDs ('powershell_heavy', 'windows_tools'). The AzCopy usage example is shown only in PowerShell context, with no explicit Linux shell/Bash example ('missing_linux_example'). References to connecting to VMs and performing actions are often linked to Windows-centric instructions or tools before Linux alternatives.
Recommendations
- Present Linux and Windows instructions/examples in parallel or alternate the order to avoid always putting Windows first.
- Provide explicit Bash/Linux shell examples for AzCopy commands, including sample output from a Linux terminal.
- Include instructions for connecting to VMs using native Linux tools (e.g., SSH from a Linux terminal), not just referencing PowerShell.
- Where possible, use platform-neutral language and tools, or clearly indicate when steps differ between platforms.
- Add screenshots or terminal output from Linux environments where Windows screenshots are shown.
- Ensure that all steps (such as stopping VMs, generating URLs, copying files) have Linux-specific guidance if the process differs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.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. It assumes the user is on a Windows client, prioritizes Windows PowerShell throughout, and provides only PowerShell-based command examples (including custom cmdlets and Azure PowerShell modules). There are no equivalent Linux/bash examples, and Linux/macOS client workflows are not described. Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives.
Recommendations
- Add explicit instructions and examples for Linux/macOS clients, including bash/zsh shell commands.
- Provide az CLI and kubectl command examples in bash syntax, not just PowerShell.
- Document how to connect to the device and run required commands from Linux/macOS (e.g., via SSH or az CLI).
- Clarify which steps are platform-specific and which are cross-platform.
- Where custom PowerShell cmdlets are used (e.g., Set-HcsKubernetesAzureArcAgent), state whether Linux equivalents exist or provide alternative workflows.
- Reorder sections so that cross-platform or platform-agnostic steps are presented first, and platform-specific instructions are clearly separated.
- Link to supported OS documentation more prominently and summarize Linux/macOS support in the prerequisites.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-set-up-device-update-time.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-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 update mechanisms (Windows Server Update Services, Microsoft Update server), using 'time.windows.com' as the default NTP server, and not mentioning or providing Linux equivalents or examples. There are no references to Linux-based update servers (such as apt/yum repositories or Linux NTP defaults), and no Linux-specific instructions or parity in the configuration steps.
Recommendations
- Include examples or references for Linux-based update servers (e.g., how to use a local Linux repository or mirror for updates if supported).
- Mention Linux-friendly NTP servers (such as pool.ntp.org) alongside 'time.windows.com', and clarify that any standards-compliant NTP server can be used.
- If the device supports integration with Linux management tools, provide instructions or links for those workflows.
- Avoid using Windows-specific terminology (like WSUS) without explaining alternatives or noting platform limitations.
- Add a section or notes clarifying cross-platform compatibility, especially for environments where Linux is prevalent.
Azure Docs
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
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by centering the workflow around PowerShell (with all commands and examples in PowerShell), presenting Windows Remote Desktop instructions before Linux (FreeRDP), and providing detailed steps and sample outputs only for Windows tools. Linux instructions are minimal and lack equivalent detail or troubleshooting guidance.
Recommendations
- Provide equivalent command-line examples for Linux shells (e.g., bash) where possible, or clarify PowerShell usage on Linux with explicit instructions.
- Present Linux (FreeRDP) and macOS remote desktop instructions alongside Windows, not after, and with equal detail (e.g., how to create and use RDP files or command-line options).
- Include sample outputs for Linux/FreeRDP commands, not just for Windows/PowerShell.
- Add troubleshooting steps and credential guidance specific to Linux/macOS clients.
- Clarify any differences or prerequisites for using PowerShell on Linux/macOS, including installation and authentication nuances.
Azure Docs
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 primarily through references to Windows-specific tools and update infrastructure (e.g., WSUS, Windows Update server) without mentioning Linux equivalents or alternatives. There are no explicit Linux or cross-platform instructions, examples, or tool references. The guidance assumes familiarity with Windows environments and omits details on how to perform similar tasks on Linux systems.
Recommendations
- Include instructions or references for configuring update servers on Linux (e.g., using local Linux repositories or update mirrors) alongside WSUS/Windows Update.
- Mention cross-platform or Linux-compatible tools for network readiness checks, or clarify if the provided tools are available for Linux.
- Provide explicit examples or notes for Linux users when discussing tasks like changing IPv4 settings, configuring NTP, or connecting via Ethernet.
- Clarify whether device management and initial setup steps (such as web UI access, certificate generation, and network configuration) are supported and documented for Linux clients.
- Where possible, use neutral terminology (e.g., 'update server' instead of 'Windows update server') and provide parity in instructions for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-kubernetes-workload-management.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-kubernetes-workload-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by specifying PowerShell as the primary method for initial access/user/namespace setup, without mentioning Linux or cross-platform alternatives. The phrase 'PowerShell runspace' is used exclusively, and there are no Linux shell or CLI examples for these steps. While later deployment steps reference kubectl (which is cross-platform), the initial configuration guidance is Windows-centric, and Linux users are not directly addressed.
Recommendations
- Provide equivalent Linux/bash shell commands for user, namespace, and access configuration alongside PowerShell instructions.
- Use neutral language such as 'command-line interface' or 'shell' instead of 'PowerShell runspace' when describing steps that can be performed on multiple platforms.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide examples for each where relevant.
- Include links or references to documentation on setting up the required tools (kubectl, Azure CLI, etc.) on Linux.
- If any steps are truly Windows-only, clearly indicate this and provide workarounds or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/handler-service-bus.md
.../blob/main//articles/event-grid/handler-service-bus.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Service Bus queues and topics as event handlers for Azure Event Grid events. While Azure CLI is cross-platform, the inclusion of Azure PowerShell commands (which are most commonly used on Windows and have a Windows-centric history) introduces a Windows bias. Additionally, the PowerShell sections are given equal prominence to CLI, and there are no explicit Linux shell (e.g., Bash) or scripting examples, nor any mention of Linux-specific considerations. The documentation does not mention or demonstrate Linux-native tools or workflows beyond the CLI.
Recommendations
- Clarify that Azure CLI commands are fully supported and tested on Linux, macOS, and Windows.
- Consider providing Bash script examples or explicitly noting that CLI commands work in Linux shells.
- If PowerShell is included, mention that PowerShell Core is cross-platform and provide installation guidance for Linux users.
- Add a brief section or note highlighting Linux compatibility and any differences (if any) when running commands on Linux.
- Ensure that CLI examples appear before PowerShell examples to avoid the perception of Windows-first bias.
Azure Docs
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 tools (such as Azure PowerShell and Windows Server Update Services), showing screenshots of certificate downloads in Windows File Explorer, and omitting Linux-specific instructions or examples for certificate handling. There are no Linux command-line or UI examples, and the only certificate creation guidance points to Azure PowerShell or a Readiness Checker tool (which is typically Windows-based).
Recommendations
- Include Linux-specific instructions for importing and managing certificates, such as using OpenSSL for certificate conversion and installation.
- Provide examples of how to handle downloaded certificates on Linux systems (e.g., using the terminal to move, convert, and install certificates).
- Reference cross-platform tools (such as Azure CLI or OpenSSL) for certificate creation and management, not just Azure PowerShell or Windows-only tools.
- Add screenshots or walkthroughs showing the process on Linux desktop environments (e.g., GNOME Files, KDE Dolphin) or via the Linux terminal.
- Mention Linux equivalents for Windows Server Update Services (WSUS) scenarios, or clarify if certain steps are Windows-only.
Azure Docs
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
Summary
The documentation demonstrates a Windows bias by presenting Windows (SMB) connection instructions and host file editing steps first, with detailed screenshots and explicit references to Windows tools (Notepad, File Explorer, Windows Run dialog). Linux (NFS) instructions are provided later and with less visual emphasis. The host file editing section is written specifically for Windows clients, with no explicit Linux equivalent. The SMB section uses Windows command-line tools and GUI steps, while the NFS section is more concise and lacks comparable visual aids.
Recommendations
- Provide parallel Linux instructions for editing the /etc/hosts file, including example commands and screenshots.
- Present SMB (Windows) and NFS (Linux) connection instructions in parallel sections or with equal prominence, rather than always listing Windows first.
- Include Linux GUI examples (e.g., using Nautilus or Dolphin to browse SMB shares) where appropriate.
- Balance the number and detail of screenshots between Windows and Linux sections.
- Explicitly mention that both Windows and Linux clients are supported for both SMB and NFS, and clarify any limitations.
- If possible, provide PowerShell and Bash command equivalents side-by-side for relevant operations.
Azure Docs
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 demonstrates a Windows bias by referencing the use of the PowerShell cmdlet `Set-HcsMacAddressPool` for configuring MAC addresses, without providing equivalent Linux command-line instructions or alternatives. There are no Linux shell examples or mentions of Linux-native tools for device configuration, and the only command-line interaction described is via PowerShell.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using SSH and standard Linux networking tools) for configuring MAC addresses or other device settings.
- Mention and demonstrate how to perform the same configuration steps from a Linux or cross-platform environment, if supported.
- Clarify whether PowerShell is required or if there are REST APIs, CLI tools, or web UI options that are platform-agnostic.
- Include Linux shell (bash) examples alongside PowerShell examples wherever command-line configuration is discussed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-kubernetes-rbac.md
...databox-online/azure-stack-edge-gpu-kubernetes-rbac.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing the PowerShell interface as a primary method for managing Kubernetes RBAC on Azure Stack Edge Pro devices, without providing equivalent Linux shell (bash) examples or mentioning Linux tools. The instructions and examples focus on PowerShell and Windows-centric workflows, with no explicit guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Linux (bash) command-line examples alongside PowerShell instructions for all RBAC operations.
- Explicitly mention that kubectl and kubeconfig are cross-platform and provide guidance for Linux/macOS users.
- Avoid referencing PowerShell as the only interface; instead, present both PowerShell and bash as options where applicable.
- Include notes or sections specifically addressing Linux/macOS usage scenarios, especially for device-local operations.
- Ensure that all tooling and workflows described are accessible from non-Windows environments, or clearly state any limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-gpu-virtual-machine.md
...ine/azure-stack-edge-gpu-deploy-gpu-virtual-machine.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is referenced as the primary CLI tool for managing VM extensions (e.g., removing GPU extensions), with no mention of Linux CLI alternatives such as Azure CLI or Bash scripts. Troubleshooting and extension removal instructions are Windows/PowerShell-centric, and the only explicit OS-specific troubleshooting note is for Windows 2016 VHD. While Linux is mentioned (notably for Red Hat images and Linux tabs in linked content), Linux-specific examples, commands, or parity in tool usage are missing or deferred to external links. Windows tools and patterns are mentioned first or exclusively in several places.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using Azure CLI or Bash) wherever PowerShell is referenced, especially for tasks like removing GPU extensions.
- Include explicit Linux examples or screenshots alongside Windows ones, particularly in sections about extension management and troubleshooting.
- Ensure that troubleshooting notes and caveats are balanced for both Windows and Linux VMs.
- When referencing external links for Linux steps, summarize key steps inline to improve parity and visibility.
- Adopt a neutral ordering (e.g., 'Windows or Linux') or alternate which OS is mentioned first to avoid implicit prioritization.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-kubernetes-gpu-sharing.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-kubernetes-gpu-sharing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples are shown in PowerShell, with Windows paths and prompts. Device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are specific to PowerShell and Windows. There are no Linux or cross-platform command examples, and Linux tools or shell usage are not mentioned. The workflow assumes a Windows client environment throughout.
Recommendations
- Provide equivalent Linux/bash command examples alongside PowerShell, using standard Linux shell prompts and paths.
- Document how to connect to and manage the Azure Stack Edge Pro GPU device from a Linux client, including any required tools or differences.
- Clarify whether device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are available or have equivalents on Linux, or if they are Windows-only.
- Update the prerequisites and instructions to explicitly support Linux clients, not just Windows.
- Where possible, use cross-platform tools and neutral language (e.g., 'terminal' instead of 'PowerShell interface') and avoid assuming C:\ paths.
- If certain features are Windows-only, clearly state this and provide alternative guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-iot-edge-gpu-sharing.md
...ne/azure-stack-edge-gpu-deploy-iot-edge-gpu-sharing.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 command-line examples use PowerShell, and Windows-specific tools and paths (e.g., C:\ paths, PowerShell cmdlets) are used exclusively. There are no Linux shell or cross-platform command examples, and instructions for Linux or macOS clients are missing or not prioritized. The workflow assumes a Windows client, and Linux alternatives (such as bash commands, Linux file paths, or Linux-native tools) are not mentioned.
Recommendations
- Provide equivalent Linux/bash shell command examples alongside PowerShell commands for all device and Kubernetes interactions.
- Include instructions for saving kubeconfig files in Linux/macOS home directories (e.g., ~/.kube/config) as well as Windows paths.
- Mention and demonstrate the use of cross-platform tools (e.g., kubectl, ssh) in both Windows and Linux contexts.
- Clarify in the prerequisites and throughout the guide that both Windows and Linux clients are supported, and provide OS-specific notes where necessary.
- Where PowerShell cmdlets are used (e.g., Get-HcsGpuNvidiaSmi, New-HcsKubernetesUser), specify if Linux equivalents exist or provide alternative instructions for Linux users.
- Show example outputs from Linux terminals as well as Windows PowerShell to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-install-gpu-extension.md
...-edge-gpu-deploy-virtual-machine-install-gpu-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is used as the primary and often only CLI interface for both Windows and Linux instructions, with all command-line examples (including Linux deployment and verification) shown as PowerShell commands executed from a Windows environment. Windows-specific tools and file paths are referenced first and in more detail. There is a lack of native Linux shell (bash) examples for deploying, tracking, and removing the GPU extension, and Linux users are implicitly expected to use PowerShell or operate from a Windows client.
Recommendations
- Provide native bash/CLI examples for Linux users, including az CLI commands for deployment, tracking, and removal of extensions.
- Show Linux commands being run from a Linux terminal (not PowerShell on Windows), using standard Linux conventions.
- Ensure that Linux instructions and examples are presented with equal prominence and detail as Windows instructions.
- Reference Linux log file locations and troubleshooting steps with the same clarity as Windows paths.
- Clarify whether PowerShell Core (pwsh) is required on Linux, or provide alternatives using bash and az CLI.
- Avoid assuming the user is operating from a Windows machine when managing Linux VMs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md
...ck-edge-gpu-deploy-configure-network-compute-web-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. While most configuration is performed via a cross-platform local web UI, references to Windows-centric concepts and tools are present. Notably, NIC teaming is described with a direct link to Windows Server documentation, and cluster witness configuration references Windows Failover Clustering concepts and documentation. PowerShell is mentioned as the CLI for workload profile changes, with no mention of Linux shell or cross-platform CLI alternatives. There are no explicit Linux examples or references, and Windows terminology is used without Linux equivalents.
Recommendations
- When referencing features like NIC teaming or cluster witness, provide links or explanations relevant to both Windows and Linux environments, or clarify if the underlying implementation is platform-agnostic.
- When mentioning PowerShell for CLI operations, also provide equivalent Bash or Azure CLI commands if available, or clarify if PowerShell Core (cross-platform) is required.
- Avoid linking exclusively to Windows Server documentation for concepts that may have Linux analogs (e.g., clustering, file share witness). Where possible, provide neutral or cross-platform explanations.
- Explicitly state whether the device management and configuration is OS-agnostic, and clarify if any steps are only applicable to Windows-based environments.
- If the device supports SSH or Linux-based CLI management, include examples or references for those workflows.
Azure Docs
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 strong Windows bias. While it uses Azure CLI for some commands, all shell examples are shown in PowerShell syntax, with variables and prompts (PS /home/user>) that are specific to Windows/PowerShell environments. Key steps for exporting VHDs rely on PowerShell-specific Azure modules (e.g., New-AzureStorageContext, Start-AzureStorageBlobCopy, Get-AzureStorageBlobCopyState) with no Linux/Bash equivalents provided. The documentation also lists Windows images first in tables and examples, and references to Linux images are minimal and not used in walkthroughs.
Recommendations
- Provide parallel Bash/Linux command examples for all steps, especially for exporting VHDs (e.g., using az storage blob copy start or azcopy).
- Use generic shell variable syntax (e.g., $VAR or VAR=) or show both PowerShell and Bash variable assignments.
- Include Linux/Bash prompt examples (e.g., $ or user@host:~$) alongside PowerShell prompts.
- List both Windows and Linux images equally in tables and examples, and use Linux images in at least one walkthrough.
- Reference and link to Linux/Bash-specific documentation where available.
- Clarify which steps require PowerShell and which can be performed in Bash, and provide guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-cli-python.md
...azure-stack-edge-gpu-deploy-virtual-machine-cli-python.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias throughout. All command-line examples are shown using Windows PowerShell, with Windows file paths and environment variable syntax. Windows-specific tools (certutil.exe, Notepad, Windows Explorer) are referenced exclusively, and instructions for editing system files (like the hosts file) are given only for Windows. There are no equivalent Linux or macOS instructions or examples, and the workflow assumes a Windows environment by default.
Recommendations
- Provide parallel Linux (and optionally macOS) instructions and examples for all steps, including certificate conversion (using openssl), editing the hosts file (with sudo and a text editor like nano or vi), and setting environment variables (using export).
- Show Azure CLI and Python commands in a cross-platform way, avoiding Windows-only syntax and file paths.
- Reference cross-platform tools (e.g., openssl for certificate conversion, AzCopy for uploads) and avoid assuming the use of Windows Explorer or Notepad.
- Include sample outputs from Linux terminals (bash/zsh) in addition to PowerShell.
- Clearly indicate when a step is platform-specific and provide alternatives for each supported OS.
- Link to Azure CLI installation instructions for Linux and macOS, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-stateful-application-static-provision-kubernetes.md
...eploy-stateful-application-static-provision-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a strong Windows bias. It assumes the user is on a Windows client, specifies Windows PowerShell as a prerequisite, and provides all command-line examples in a Windows context (including PowerShell prompts and Windows file paths). There are no Linux/macOS-specific instructions, examples, or file path conventions, and the use of Windows-specific tools and commands is emphasized throughout.
Recommendations
- Provide parallel instructions and examples for Linux/macOS clients, including shell commands and file paths (e.g., ~/.kube instead of C:\Users\<username>\.kube).
- Mention and demonstrate how to install and use kubectl on Linux/macOS, not just Windows.
- Replace or supplement PowerShell-specific command prompts and output with Bash equivalents.
- Clarify that the procedure is cross-platform and explicitly state any differences or limitations for non-Windows users.
- Where Windows-specific tools (e.g., New-HcsKubernetesNamespace) are mentioned, note if there are Linux equivalents or if these steps must be performed from a Windows system.
- Ensure screenshots and file path references are not exclusively Windows-centric, or provide alternatives for other operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-kubernetes-networking.md
...x-online/azure-stack-edge-gpu-kubernetes-networking.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell cmdlets (e.g., Add-HcsNetRoute, Get-HcsNetRoute, Remove-HcsNetRoute) for network configuration and route management. There are no Linux or cross-platform CLI examples, and the only method described for adding routes is via the PowerShell interface. Windows-specific networking concepts (e.g., Hyper-V, virtual switches, SET) are mentioned without Linux equivalents or alternatives. The documentation does not address how to perform similar tasks on Linux-based systems or with standard Kubernetes/Linux networking tools.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using ip route or nmcli) for route management on Kubernetes nodes, if supported.
- Clarify whether the device supports SSH or Linux shell access for network configuration, and document those workflows if available.
- Mention or link to Linux-native networking concepts (e.g., Linux bridges, NetworkManager, standard Linux routing) where Hyper-V or Windows virtual switches are discussed.
- If route configuration is only possible via PowerShell, explicitly state this limitation and provide guidance for Linux users or alternatives where possible.
- Ensure that all code examples are provided in both PowerShell and bash (or other relevant Linux shells) where feasible.
- Consider reordering explanations to present cross-platform or Linux-native approaches before or alongside Windows-specific instructions.