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 576-600 of 890 flagged pages
Databox Online
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 Windows bias by exclusively referencing Windows-centric tools and services, such as Windows Server Update Services (WSUS) and time.windows.com as the default NTP server. There are no examples or mentions of Linux equivalents (e.g., Linux update servers, chrony/ntpd, or pool.ntp.org), nor are there instructions or screenshots relevant to Linux environments. The documentation assumes a Windows-based infrastructure for updates and time synchronization, and does not provide parity for Linux-based workflows.
Recommendations
- Include examples and instructions for configuring updates using Linux-based update servers (e.g., apt, yum, or custom HTTP/S update mirrors).
- Mention and provide examples of using public or Linux-friendly NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
- Clarify that WSUS is a Windows-specific solution and suggest alternatives for environments that use Linux or mixed OS infrastructure.
- Add notes or sections that address common Linux administration patterns and tools where relevant.
- Ensure screenshots and step-by-step instructions are not exclusively tailored to Windows-centric setups.
Create Pull Request
Databox Online
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 is heavily biased towards Windows environments and PowerShell usage. Windows clients and PowerShell are assumed as the default throughout, with explicit instructions and examples provided only for Windows and PowerShell interfaces. There are no equivalent Linux or bash examples, and Linux/macOS client workflows are not described, despite the mention that other OSes are supported. All command-line examples use PowerShell syntax, and Windows tooling is referenced exclusively.
Recommendations
- Provide parallel instructions and examples for Linux/macOS clients, including bash/zsh shell commands.
- Include az CLI and kubectl command examples in bash syntax, not just PowerShell.
- Explicitly document how to connect to the device and run required commands from Linux/macOS clients.
- Mention and demonstrate any differences in prerequisites or setup for non-Windows environments.
- Avoid assuming Windows as the default client; structure the documentation to present both Windows and Linux/macOS workflows equally, or provide a clear OS selection at the start.
Databox Online
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 towards 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 (bash) equivalents or instructions for Linux/Mac users, even though tools like kubectl are cross-platform. The documentation assumes a Windows client and does not mention or demonstrate Linux alternatives for connecting, configuring, or managing the device.
Recommendations
- Provide Linux (bash) equivalents for all PowerShell commands, including kubectl usage, file path conventions, and environment setup.
- Include instructions for saving kubeconfig files in Linux home directories (e.g., ~/.kube/config) and using Linux file paths.
- Mention supported Linux distributions explicitly in the prerequisites and provide any OS-specific requirements.
- Demonstrate how to connect to the device and run commands from a Linux terminal, including using SSH and bash.
- Ensure that all screenshots and code snippets are either OS-neutral or have both Windows and Linux versions.
- Clarify that the workflow is cross-platform and highlight any differences or limitations for Linux users.
Databox Online
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 Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific clustering concepts (e.g., cluster witness, file share witness, cloud witness) and links to Windows Server documentation for NIC teaming and failover clustering. PowerShell is mentioned as the CLI method for changing Kubernetes workload profiles, with no mention of Bash or Linux CLI alternatives. The file share witness example uses Windows SMB path syntax. There are no explicit Linux or cross-platform command-line examples, and Windows tools/patterns are referenced before any Linux equivalents (which are absent).
Recommendations
- Provide Linux/Bash command-line alternatives alongside PowerShell instructions for tasks such as changing Kubernetes workload profiles.
- Reference cross-platform or Linux-native clustering concepts and tools where possible, or clarify if only Windows-based clustering is supported.
- When mentioning file share witness, include NFS-based or Linux-compatible file share examples, not just Windows SMB paths.
- Avoid linking exclusively to Windows Server documentation for networking concepts like NIC teaming; include Linux equivalents (e.g., bonding, teaming) or clarify platform support.
- Explicitly state platform limitations or support (e.g., if only Windows-based clustering is supported, clarify this up front).
- Add notes or examples for users managing the device from Linux or macOS environments, especially for CLI-based configuration.
Databox Online
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 and Windows-specific tools (e.g., Remove-AzureRmVMExtension cmdlet) are referenced exclusively for extension removal, with no equivalent Linux/CLI instructions. Troubleshooting and extension installation steps highlight Windows scenarios (e.g., TLS 1.2 on Windows 2016 VHD) and link to Windows-specific guidance before Linux. Linux examples are either deferred, less detailed, or referenced only as an afterthought (e.g., Red Hat GPU extension installation). There are no explicit Linux CLI or Azure CLI examples for common management tasks.
Recommendations
- Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for tasks like removing VM extensions.
- Ensure troubleshooting and installation steps for Linux are as detailed and prominent as those for Windows.
- When referencing OS-specific requirements (e.g., TLS 1.2 for Windows 2016), also mention any Linux-specific prerequisites or considerations.
- Present Linux and Windows instructions in parallel or in clearly separated tabs, rather than listing Windows first or exclusively.
- Include explicit Linux/CLI guidance for common management tasks, not just portal-based workflows.
Databox Online
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
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All command-line examples are shown in PowerShell, with explicit references to Windows paths (e.g., C:\gpu-sharing\...), and all screenshots and outputs are from PowerShell sessions. There are no Linux shell (bash) equivalents, nor are there any references to Linux tools or terminal environments. The documentation assumes the use of Windows clients and PowerShell for all management tasks, and device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are only shown in PowerShell, with no mention of Linux alternatives or how to perform these tasks from a Linux client.
Recommendations
- Provide equivalent Linux shell (bash) command examples alongside PowerShell commands for all kubectl and file operations.
- Include Linux path examples (e.g., /home/user/gpu-sharing/k8-gpusharing.yaml) in addition to Windows paths.
- Clarify whether device management commands (e.g., Get-HcsGpuNvidiaSmi, Start-HcsGpuMPS) are available from Linux clients, and if so, provide Linux usage instructions.
- If device management is only possible from Windows, explicitly state this limitation and suggest workarounds for Linux users (such as using a Windows VM or container).
- Add screenshots or terminal outputs from Linux environments to balance the visual representation.
- Update the prerequisites to explicitly mention supported Linux shells and tools, and provide guidance for Linux users.
Databox Online
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 page demonstrates a strong Windows bias. It assumes the user is on a Windows client, provides only Windows PowerShell command-line examples, and uses Windows file paths (e.g., C:\Users\user). There are no equivalent Linux/macOS instructions, shell commands, or file path examples. Windows-specific tools and commands (such as New-HcsKubernetesNamespace) are referenced without Linux alternatives, and the documentation repeatedly refers to using a Windows client as the primary scenario.
Recommendations
- Provide parallel Linux/macOS instructions and examples for all steps, including shell command syntax and file paths (e.g., ~/user/.kube).
- Include Linux/macOS command-line output samples alongside PowerShell examples.
- Clarify which steps or tools are Windows-only and offer Linux/macOS alternatives where possible.
- Reference cross-platform tools and commands first, or at least equally, rather than prioritizing Windows-specific tools.
- Explicitly state any limitations or differences for non-Windows clients early in the prerequisites section.
- Where Windows PowerShell commands are used (e.g., New-HcsKubernetesNamespace), document if/how these can be run from Linux/macOS, or provide REST API/CLI alternatives.
Databox Online
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 demonstrates a strong Windows bias by exclusively using PowerShell cmdlets (e.g., Add-HcsNetRoute, Get-HcsNetRoute, Remove-HcsNetRoute) for all network configuration tasks, with no mention of Linux command-line equivalents or cross-platform alternatives. The instructions assume access to a PowerShell interface and reference Windows-specific networking concepts (such as Hyper-V virtual switches and Switch Embedded Teaming), without providing guidance for users familiar with Linux networking tools or environments. There are no Linux or kubectl-based examples for managing routes or networking, and the documentation does not address how to perform these tasks if the Kubernetes nodes were running on Linux or in a more standard Kubernetes environment.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using ip route, nmcli, or netplan) for adding, viewing, and removing routes on Kubernetes nodes.
- Include examples using kubectl or standard Kubernetes networking resources for route management, if possible.
- Clarify whether the PowerShell cmdlets are available only on Windows-based Azure Stack Edge devices, and provide alternative instructions for Linux-based environments or for users connecting via SSH.
- When describing networking concepts (e.g., virtual switches, NIC teaming), mention Linux equivalents (e.g., Linux bridges, bonding) or clarify their applicability.
- Consider reordering or supplementing examples so that Linux and cross-platform approaches are presented alongside or before Windows/PowerShell-specific methods.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-kubernetes-storage.md
...abox-online/azure-stack-edge-gpu-kubernetes-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing SMB (a Windows-native protocol) in examples and explanations, mentioning SMB before NFS (the Linux/UNIX equivalent) throughout. There are no explicit Linux command-line or shell examples, and the documentation does not provide parity in terms of Linux-specific tooling or workflows. The focus on Azure portal GUI and SMB shares, with NFS only mentioned as an alternative, further reinforces this bias.
Recommendations
- Provide Linux-specific examples, such as using NFS as the primary example or showing both SMB and NFS usage equally.
- Include command-line examples for both Windows (PowerShell) and Linux (bash/shell) environments for provisioning and mounting storage.
- Clarify that both SMB and NFS are supported equally, and provide guidance for Linux-first users, including troubleshooting tips for NFS.
- Add references to Linux-native tools (e.g., mount, exportfs, etc.) and workflows for managing storage.
- Balance the order of presentation so that NFS and Linux-native methods are not always secondary to SMB/Windows methods.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-stateful-application-dynamic-provision-kubernetes.md
...ploy-stateful-application-dynamic-provision-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are shown as being run from Windows (with PowerShell prompts and Windows file paths). The prerequisites specifically call out Windows clients and PowerShell, and the workflow is described as being performed on a Windows system. There are no Linux or macOS examples, and no mention of Linux-specific instructions, file paths, or shell environments. Windows tooling and conventions (such as C:\ paths and PowerShell) are used exclusively.
Recommendations
- Provide parallel Linux/macOS instructions and examples, including shell prompts (e.g., $) and POSIX file paths (e.g., /home/user/.kube).
- Mention installation steps for kubectl and prerequisites for Linux/macOS clients, not just Windows.
- Show example commands and outputs as they would appear in a bash or zsh shell, not only PowerShell.
- Clarify that the procedure is cross-platform and works on any supported OS, not just Windows.
- Link to or summarize supported OSes and any OS-specific caveats in the prerequisites section.
- Avoid using Windows-specific commands (e.g., New-HcsKubernetesNamespace) unless they are truly unavailable on other platforms; if so, explain alternatives or limitations.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-stateless-application-git-ops-guestbook.md
...dge-gpu-deploy-stateless-application-git-ops-guestbook.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It explicitly assumes a Windows client, requires Windows PowerShell, and all command-line examples are shown in PowerShell context. There are no Linux or macOS command-line examples or instructions, and the documentation does not provide parity for non-Windows users. Windows tools and paths are referenced exclusively, and the workflow is described from a Windows perspective.
Recommendations
- Add parallel instructions and examples for Linux and macOS clients, including shell commands and environment setup.
- Show command-line examples in both PowerShell and Bash (or general shell) formats.
- Avoid assuming the client is Windows by default; instead, present Windows, Linux, and macOS as equally supported options.
- Reference generic tools and paths (e.g., ~/.kube for kubeconfig) alongside Windows-specific ones.
- Explicitly mention any differences or additional steps required for Linux/macOS users.
- Where screenshots or UI steps are shown, clarify that the process is the same regardless of client OS, or note any differences.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-stateless-application-kubernetes.md
...stack-edge-gpu-deploy-stateless-application-kubernetes.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 command-line examples are shown in PowerShell, with Windows-style paths (e.g., C:\Users\<username>\.kube), and sample outputs are from PowerShell terminals. The prerequisites and instructions explicitly refer to Windows PowerShell and Windows client systems, with no Linux or macOS equivalents provided. There is no mention of Linux shell usage, Linux file paths, or cross-platform considerations, despite kubectl being cross-platform.
Recommendations
- Provide equivalent Linux (bash) and macOS command-line examples alongside PowerShell examples.
- Include Linux/macOS file path examples (e.g., ~/.kube) and explain where configuration files are stored on non-Windows systems.
- Update prerequisites to mention supported Linux/macOS environments and required shell versions.
- Show sample outputs from bash or zsh terminals as well as PowerShell.
- Avoid assuming the user is on Windows; use neutral language or clarify when instructions are OS-specific.
- Link to official kubectl installation guides for all platforms, not just Windows PowerShell.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-custom-script-extension.md
...dge-gpu-deploy-virtual-machine-custom-script-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. All deployment and management commands use PowerShell cmdlets, even for Linux VMs. Windows examples and file paths are presented first and in more detail. Linux-specific tools, shell commands, and file paths are either missing or only briefly mentioned. The Linux section reuses Windows-centric PowerShell deployment and tracking commands, and does not provide equivalent Bash/CLI examples or Linux-native workflows.
Recommendations
- Provide Azure CLI and Bash examples for deploying and managing the Custom Script Extension on Linux VMs, rather than only PowerShell.
- Include Linux-native file paths and log locations alongside Windows paths, and explain their significance.
- Show Linux shell commands (e.g., mkdir, touch, cat) in the 'commandToExecute' examples, rather than using Windows-style commands or referencing the /home/Administrator directory, which is not standard on Linux.
- Present Linux and Windows instructions in parallel, giving equal prominence to both, rather than always listing Windows first.
- Demonstrate how to track and remove extensions using Linux-native tools or Azure CLI, not just PowerShell.
- Clarify any differences in publisher/type/typeHandlerVersion for Linux vs. Windows extensions, and provide context for Linux users.
Databox Online
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 page demonstrates a strong Windows bias throughout. All command-line examples, environment variable settings, and certificate management steps are shown exclusively using Windows PowerShell, Windows paths, and Windows-specific tools (e.g., certutil.exe, Notepad, Windows Explorer). There are no equivalent instructions or examples for Linux or macOS users, and references to running commands are always in a Windows context. Even the installation and usage of Azure CLI and Python are shown only for Windows environments.
Recommendations
- Provide parallel instructions and examples for Linux (and optionally macOS) users, including bash shell commands, Linux file paths, and use of common Linux tools (e.g., openssl for certificate conversion, nano/vim for editing /etc/hosts).
- When referencing tools like certutil.exe or Notepad, include Linux alternatives such as openssl and nano/vim.
- Show environment variable setting examples for bash/zsh (e.g., export VAR=value) alongside PowerShell examples.
- Include sample output from Linux terminals (e.g., $ prompt, /home/user paths) in addition to Windows PowerShell output.
- When linking to installation instructions, provide links for all supported platforms, not just Windows.
- Explicitly state that the procedure is cross-platform and highlight any platform-specific differences or requirements.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-high-performance-network.md
...ge-gpu-deploy-virtual-machine-high-performance-network.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. All command-line examples and device management instructions are provided exclusively using PowerShell cmdlets, with no equivalent Linux shell or cross-platform CLI examples. The documentation references Windows-centric tools and patterns (such as PowerShell and Windows-specific NUMA documentation) and does not provide Linux alternatives or parity in workflow or troubleshooting. While there is a brief mention that both Windows and Linux VHDs can be used as VM images, all operational guidance assumes a Windows/PowerShell environment.
Recommendations
- Provide equivalent Linux shell (bash) or Azure CLI examples for all PowerShell cmdlets used (e.g., for querying and setting NUMA policies, managing VMs).
- Reference Linux documentation for NUMA and CPU affinity management, not just Windows.
- Clarify whether the device management interface supports SSH or Linux-native management tools, and provide instructions if so.
- When mentioning prerequisites or workflows, explicitly state and demonstrate steps for both Windows and Linux admin environments.
- Ensure troubleshooting and monitoring guidance includes Linux-compatible tools and commands.
- If PowerShell is required regardless of admin OS, clarify this up front and provide installation guidance for non-Windows platforms.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-iot-edge-api-update.md
...box-online/azure-stack-edge-gpu-iot-edge-api-update.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 referencing Azure PowerShell cmdlets for role management, without providing equivalent CLI or Linux-native command examples. The only command-line tooling discussed is PowerShell, and there is no mention of Azure CLI or Bash scripting. While the API and SDK samples are platform-neutral, the lack of Linux-specific or cross-platform command-line instructions may hinder Linux users.
Recommendations
- Add Azure CLI examples alongside PowerShell cmdlets for all role management tasks.
- Explicitly mention cross-platform support for the SDK and API, and provide Bash/cURL examples for API usage.
- Include Linux/Bash scripting alternatives where PowerShell is referenced, or clarify if PowerShell Core is required and supported on Linux.
- Ensure that documentation sections referencing command-line tools do not assume a Windows environment by default.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-install-password-reset-extension.md
...eploy-virtual-machine-install-password-reset-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is heavily oriented around PowerShell and Windows tooling, even for Linux VM scenarios. All command-line examples (including those for Linux) use Azure PowerShell cmdlets and are shown in a Windows PowerShell prompt. There are no CLI/bash examples, and the instructions assume the use of a Windows client environment. The documentation also references Windows-specific file paths and screenshots, and Windows terminology is prevalent throughout.
Recommendations
- Provide Azure CLI (az) examples alongside or instead of PowerShell for Linux VM scenarios, using bash syntax and Linux file paths.
- Show sample commands and outputs from a Linux shell (e.g., bash prompt), not just Windows PowerShell.
- Clarify that PowerShell Core can be used cross-platform, or explicitly support native Linux workflows.
- Include screenshots and instructions relevant to Linux client environments where appropriate.
- Avoid assuming the user is operating from a Windows machine; balance references to both Windows and Linux client environments.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-disconnected-scenario.md
...x-online/azure-stack-edge-gpu-disconnected-scenario.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing and exclusively mentioning Windows PowerShell and Windows Server Update Services (WSUS) for management and updates. There are no examples or explicit instructions for Linux or cross-platform management tools (e.g., Bash, SSH, Linux CLI), and the local management interface is described as the 'Windows PowerShell interface' without mention of Linux alternatives. Update instructions reference WSUS and manual downloads via the web UI, but do not mention Linux-compatible update mechanisms or tools. VM management is described via Azure PowerShell, with no Linux or cross-platform CLI examples provided.
Recommendations
- Include Linux and cross-platform management instructions, such as using SSH, Bash, or Azure CLI on Linux/macOS.
- When referencing the 'Windows PowerShell interface', also mention SSH or Bash access for Linux users, if supported.
- Provide update instructions that are compatible with Linux environments, or clarify if updates can be applied via Linux tools.
- For VM management, add examples using Azure CLI or REST API that can be run from Linux/macOS, not just Azure PowerShell.
- Avoid referencing Windows-specific tools (like WSUS) without offering Linux equivalents or alternatives.
- Ensure that all code snippets and management workflows are presented in both Windows and Linux contexts, or explicitly state platform limitations.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-edge-container-registry.md
...online/azure-stack-edge-gpu-edge-container-registry.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. All command-line examples use PowerShell syntax, and all screenshots and sample outputs are from Windows environments (e.g., 'PS C:\WINDOWS\system32>'). Instructions for editing the hosts file, installing certificates, and using Docker are written specifically for Windows, with no equivalent Linux or macOS guidance. There is no mention of Linux shell commands, Linux file paths, or Linux-specific Docker installation steps. The use of Windows-specific tools and patterns (e.g., PowerShell cmdlets, Windows file paths) is pervasive, and Linux users are not provided with parallel instructions.
Recommendations
- Provide parallel Linux/macOS instructions and examples for all steps, including editing /etc/hosts, installing certificates, and using Docker.
- Include Linux shell (bash) command examples alongside PowerShell, especially for Docker, kubectl, and HTTP API interactions.
- Show sample outputs from Linux terminals (e.g., bash prompt) in addition to Windows PowerShell.
- Document certificate installation steps for Linux (e.g., using update-ca-certificates or similar tools).
- Reference Linux file paths (e.g., /etc/hosts) and explain any OS-specific differences.
- Clarify that the process is cross-platform and explicitly support Linux/macOS users in the prerequisites and throughout the guide.
Databox Online
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 focusing on PowerShell as the primary interface for Kubernetes RBAC operations on Azure Stack Edge Pro. It mentions using PowerShell to create namespaces and users, with no equivalent Linux shell or cross-platform CLI examples. The instructions and references are tailored to Windows environments, and Linux alternatives are not discussed or shown.
Recommendations
- Provide equivalent Linux shell (bash) examples for all PowerShell commands and operations.
- Clarify whether operations can be performed using standard kubectl commands on Linux/macOS, and provide guidance if so.
- Explicitly mention cross-platform compatibility of tools and interfaces, or note any Windows-specific limitations.
- Include screenshots or command snippets from both Windows (PowerShell) and Linux (bash) environments.
- Reorder examples or explanations to present cross-platform or Linux-native methods before or alongside Windows/PowerShell approaches.
Databox Online
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 referencing PowerShell as the primary method for initial access/user/namespace setup, without mentioning Linux or cross-platform alternatives. There are no Linux shell or cross-platform command examples for these steps, and the initial workflow assumes familiarity with Windows tooling.
Recommendations
- Provide equivalent Linux/bash command-line instructions for configuring access (user, namespace, RBAC) alongside PowerShell examples.
- Explicitly state whether all steps can be performed from Linux/macOS systems, and if not, clarify any platform-specific requirements.
- Include notes or links to cross-platform tools (e.g., Azure CLI, Bash scripts) where possible.
- Reorder or parallelize instructions so that Windows and Linux users are equally supported, rather than presenting Windows/PowerShell first or exclusively.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-manage-shares.md
...s/databox-online/azure-stack-edge-gpu-manage-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently presents SMB (a Windows-centric protocol) as the default and standard, with NFS (the Linux equivalent) mentioned secondarily. There are references to Windows tools (e.g., File Explorer) for managing permissions, but no equivalent Linux instructions or examples are provided. There are no command-line examples or guidance for Linux users on mounting or managing shares, and the documentation lacks parity in practical Linux usage instructions.
Recommendations
- Provide explicit Linux examples for mounting NFS shares, including sample mount commands and configuration steps.
- When discussing SMB and NFS, present both protocols with equal prominence and provide usage examples for both Windows (SMB) and Linux (NFS) clients.
- Include instructions for managing permissions on NFS shares from Linux systems, similar to the File Explorer guidance for Windows.
- Avoid language that positions SMB as the default or standard; instead, clarify that SMB is typical for Windows clients and NFS for Linux, without prioritizing one over the other.
- Add troubleshooting and best practices sections for both Windows and Linux environments.
Databox Online
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 sometimes only) CLI for both Windows and Linux instructions, with all command-line examples and outputs shown in PowerShell sessions on Windows hosts. Windows-specific tools and file paths are referenced first and more extensively. Linux instructions are present but often shown as being executed from a Windows PowerShell environment, and there are no native Linux shell (bash) command examples for deployment or management tasks. Additionally, removal instructions and some troubleshooting steps are only shown using PowerShell, with no Linux-native alternatives.
Recommendations
- Provide native Linux shell (bash) command examples for all deployment, tracking, and removal steps, using Azure CLI or Azure PowerShell Core on Linux where appropriate.
- Show Linux command outputs from a Linux terminal, not from a Windows PowerShell session.
- When presenting instructions for both OSes, avoid always listing Windows first; alternate or present both in parallel.
- Include Linux-native file paths, tools, and troubleshooting steps where relevant.
- Clarify that Azure CLI and Azure PowerShell Core are cross-platform, and provide installation/use instructions for Linux users.
- Ensure that all steps (including removal and troubleshooting) have Linux-native equivalents, not just PowerShell commands.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-enable-azure-monitor.md
...ox-online/azure-stack-edge-gpu-enable-azure-monitor.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions and cmdlets for configuring Azure Monitor on the device. There are no Linux shell (bash) or cross-platform CLI examples for the key configuration steps, and the connection instructions reference only the PowerShell interface. The sample output also uses PowerShell prompts, reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent bash or cross-platform Azure CLI commands for all configuration steps, especially for connecting to the device and setting Azure Monitor configuration.
- Document how to connect to the device using SSH or other Linux-friendly methods, if supported.
- Include sample outputs and command prompts for both Windows (PowerShell) and Linux (bash) environments.
- Clearly state if certain steps or cmdlets are only available on Windows, and suggest alternatives or workarounds for Linux users.
- Review and update screenshots and instructions to reflect parity between Windows and Linux usage where possible.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-local-resource-manager-overview.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-local-resource-manager-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell in the 'Next steps' link, without mentioning or providing equivalent Linux/CLI examples. There are no Linux-specific instructions or examples, and the documentation implicitly assumes the use of Windows tools and patterns.
Recommendations
- Provide equivalent Linux/Bash/CLI examples alongside or before PowerShell instructions.
- Include references or links to Linux-compatible tools (e.g., Azure CLI, curl, bash scripts) for interacting with the local Azure Resource Manager.
- Ensure that 'Next steps' and related links offer parity for both Windows and Linux users.
- Explicitly state that the APIs and templates can be used from any OS, and provide cross-platform guidance where possible.