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 476-500 of 890 flagged pages
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-recover-device-failure.md
...-online/azure-stack-edge-gpu-recover-device-failure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by listing Microsoft Azure Recovery Services (MARS) agent for Azure Backup, which is Windows-only, as the first and only detailed backup solution for VM file/folder recovery, while Linux support is only mentioned in third-party solutions. There are no Linux-specific examples or instructions, and no mention of Linux-native tools or patterns. The documentation also references Windows tools (MARS agent) without Linux equivalents.
Recommendations
- Provide Linux-specific backup and recovery examples, including native Linux tools or Azure-supported Linux backup agents.
- List Linux and Windows solutions in parallel, rather than Windows-first, and clarify OS support for each tool.
- Include command-line examples for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) where relevant.
- If Azure does not offer a first-party Linux backup agent, explicitly state this and recommend best-practice alternatives for Linux users.
- Ensure parity in documentation depth for both Windows and Linux recovery workflows.
Create Pull Request
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 page demonstrates a strong Windows bias. All command-line examples and device interactions are shown using PowerShell, with explicit references to Windows paths (e.g., C:\Users\<username>\.kube), and no Linux or cross-platform equivalents are provided. The instructions for connecting to the device, managing Kubernetes config files, and running kubectl commands are all shown from a Windows environment. There is no mention of how to perform these steps from a Linux or macOS client, nor are there any bash or shell examples. Windows-specific tools and patterns (such as PowerShell cmdlets and Windows directory structures) are used exclusively throughout the guide.
Recommendations
- Provide equivalent Linux/macOS instructions and examples for all steps, including connecting to the device, managing Kubernetes config files, and running kubectl commands.
- Include bash or shell command examples alongside PowerShell examples, especially for kubectl and file operations.
- Mention Linux and macOS as supported client platforms where applicable, and link to any prerequisites or setup guides for those systems.
- Show Linux file paths (e.g., ~/.kube/config) in addition to Windows paths when instructing users where to save configuration files.
- If device management cmdlets are only available on Windows, explicitly state this limitation and, if possible, suggest alternatives for Linux/macOS users.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-deploy-check-network-readiness.md
...ine/azure-stack-edge-deploy-check-network-readiness.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and tooling are based on PowerShell, with explicit references to Windows-only features (e.g., PowerShell 5.1, Windows Update/WSUS, Windows file paths). There are no Linux or cross-platform instructions, nor any mention of running the tool or equivalent checks on Linux or macOS systems.
Recommendations
- Provide explicit information about Linux and macOS support: State whether the Azure Stack Network Readiness Checker can be run on non-Windows platforms, and if not, clarify this limitation early in the documentation.
- If the tool is Windows-only, suggest alternative methods or scripts for Linux users to perform similar network readiness checks (e.g., using curl, dig, traceroute, or custom scripts).
- If cross-platform PowerShell (PowerShell Core/7+) is supported, include installation and usage instructions for Linux and macOS, with corresponding examples.
- Include Linux/macOS file path examples for log and report locations, if applicable.
- Rephrase sections that assume a Windows environment (e.g., references to C:\Users\..., Windows Update, etc.) to be more inclusive or to provide Linux/macOS alternatives where possible.
- Add a note in the prerequisites section about platform compatibility and any required dependencies for non-Windows users.
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 Windows PowerShell as the primary local management interface, referencing Windows-specific tools (such as WSUS for updates), and omitting Linux or cross-platform CLI examples for device management. There are no examples or mentions of using Linux shells or tools for local management, nor is there guidance for Linux users on connecting or managing the device.
Recommendations
- Include equivalent Linux/Bash shell instructions and examples for local device management, such as using SSH or cross-platform Azure CLI.
- Mention cross-platform tools (e.g., Azure CLI, kubectl) before or alongside Windows PowerShell, and clarify which management interfaces are supported on Linux.
- Provide update instructions for Linux users, including how to manually apply updates without WSUS or Windows tools.
- Explicitly state whether the local web UI and other management interfaces are accessible from Linux clients, and provide any necessary prerequisites or troubleshooting steps.
- Ensure all feature tables and instructions present both Windows and Linux options where applicable, or clearly note if a feature is Windows-only.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2008-release-notes.md
...abox-online/azure-stack-edge-gpu-2008-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page shows a moderate Windows bias. Several examples and workarounds reference Windows tools (e.g., robocopy, Explorer), Windows command syntax, and PowerShell interfaces, with little or no mention of Linux equivalents. In some cases, only Windows-centric instructions are provided, and Linux alternatives are missing or less prominent.
Recommendations
- For file copy operations, provide Linux equivalents (e.g., rsync, cp) alongside Windows tools like robocopy and Explorer.
- When giving mount command examples, include both Windows and Linux syntax (e.g., show 'mount -o nolock ...' for Linux, and 'net use' or Windows mount for Windows).
- For PowerShell-specific instructions (e.g., connecting to the device), add equivalent bash/ssh or Linux-native instructions.
- Ensure all command-line examples are cross-platform or provide parallel examples for both Windows and Linux users.
- Mention Linux tools and patterns (e.g., bash, Linux file managers) wherever Windows tools are referenced.
- Review all steps and workarounds to ensure Linux users are not left without guidance.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2205-release-notes.md
...abox-online/azure-stack-edge-gpu-2205-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits several signs of Windows bias. Windows tools and workflows (e.g., robocopy, Explorer, RDP, PowerShell commands) are mentioned or exemplified, sometimes without Linux equivalents or with Windows examples given first. Some workarounds and instructions are specific to Windows environments, and Linux alternatives are either missing or less detailed. This can make it harder for Linux users to follow or apply the documentation effectively.
Recommendations
- For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell), provide equivalent Linux commands (e.g., rsync, cp, bash commands) and examples.
- When giving example commands for mounting NFS shares, include both Windows and Linux syntax, and present them side by side or in parallel sections.
- If referencing Windows-specific troubleshooting (e.g., using RDP, Get-Process), add Linux-based troubleshooting steps (e.g., SSH, ps, systemctl) where applicable.
- Avoid listing Windows tools or workflows before Linux equivalents; alternate or group them by platform.
- Review all sections for implicit assumptions of a Windows environment and clarify when instructions are platform-specific.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-cluster-witness-overview.md
...nline/azure-stack-edge-gpu-cluster-witness-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clustering concepts, terminology, and tools, with no mention of Linux-based clustering, commands, or alternative witness mechanisms. All examples, requirements, and explanations assume a Windows environment, and there are no Linux equivalents or cross-platform considerations provided.
Recommendations
- Include a section clarifying whether Linux-based clustering is supported or not on Azure Stack Edge, and if so, provide equivalent guidance for Linux clusters.
- If Linux is not supported, explicitly state this early in the documentation to set user expectations.
- If Linux is supported, add Linux-specific examples for setting up cluster witnesses (e.g., using corosync/pacemaker, NFS shares, or other Linux-native mechanisms).
- Mention Linux-compatible file sharing protocols (such as NFS) alongside SMB, or clarify SMB support on Linux if relevant.
- Avoid using Windows-specific terminology (such as 'Windows Server Failover Clustering') exclusively; instead, use more generic clustering terms where possible, or provide cross-references to Linux equivalents.
Databox Online
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 provided exclusively for Windows and PowerShell. There are no Linux or cross-platform command examples, and Windows-specific tools and file paths are referenced throughout. The installation and usage of kubectl are shown only for Windows, and even basic steps like editing the hosts file are described only for Windows systems.
Recommendations
- Provide equivalent Linux (and macOS, if possible) instructions and examples for all steps, including connecting to the device, managing namespaces/users, and installing kubectl.
- Include Linux shell command examples (e.g., bash, curl, cp, nano/vim for editing hosts file) alongside PowerShell commands.
- Reference Linux file paths (e.g., ~/.kube/config) and explain how to save and use the config file on Linux systems.
- Mention Linux package managers (e.g., apt, yum, snap) for installing kubectl, and provide download links for Linux binaries.
- Clarify any platform-specific requirements or limitations, and ensure that all supported client OSes are treated equally in the documentation.
- Add screenshots or terminal outputs from Linux environments where appropriate.
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 refers to Windows-centric tools and patterns (such as PowerShell, Windows cmdlets, and references to Windows documentation like NUMA support), and Linux is only mentioned in passing (e.g., 'Windows or Linux VHD'), with no Linux-specific operational guidance or examples. There are no instructions for performing these tasks from a Linux environment or using cross-platform tools like Azure CLI or SSH.
Recommendations
- Provide equivalent Linux shell (bash) commands for all PowerShell cmdlet examples, or clarify if device management is only possible via PowerShell.
- Include instructions for connecting to the device and managing NUMA/vCPU reservations from a Linux or cross-platform environment (e.g., via SSH, Azure CLI, or REST API if available).
- If PowerShell is required, explicitly state this requirement and provide guidance for Linux users (e.g., using PowerShell Core on Linux, or alternatives).
- Reference both Windows and Linux documentation for NUMA concepts and VM image preparation.
- Ensure that any prerequisites or workflows that are platform-specific are clearly marked, and provide parity in documentation for both Windows and Linux users.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-configure-metallb-bgp-mode.md
...ine/azure-stack-edge-gpu-configure-metallb-bgp-mode.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Windows PowerShell and Windows-specific cmdlets for configuring MetalLB via BGP on Azure Stack Edge. All examples, instructions, and sample outputs are based on the Windows environment, with no mention of Linux equivalents or cross-platform alternatives. There is no guidance for users who may want to perform similar tasks from a Linux or non-Windows environment.
Recommendations
- Provide equivalent Linux-based instructions, such as using SSH and standard Linux networking tools (e.g., ip, nmcli, or BGP daemons like FRR or Bird) for configuring BGP sessions if supported.
- Include examples using cross-platform PowerShell Core (pwsh) and clarify any differences in command usage or prerequisites.
- Explicitly state if configuration is only possible via Windows PowerShell, and if so, explain why and suggest workarounds for Linux users (e.g., using a Windows jump host or container).
- Add a section comparing Windows and Linux approaches, or at least acknowledge the lack of Linux support and provide links to relevant Linux-native MetalLB/BGP configuration guides.
- Where possible, use platform-neutral language and tools, or provide parallel instructions for both Windows and Linux environments.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2312-release-notes.md
...abox-online/azure-stack-edge-gpu-2312-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell cmdlets like Get-VM and Start-VM, RDP, waappagent.exe), and instructions often assume a Windows environment or provide Windows examples first. In some cases, Linux alternatives are missing or only mentioned in passing, leading to incomplete guidance for Linux users.
Recommendations
- For every Windows-specific tool or example (e.g., robocopy, Explorer, PowerShell cmdlets), provide equivalent Linux commands (e.g., rsync, cp, SSH, systemctl, ps, etc.).
- When showing command-line examples, include both Windows and Linux syntax side by side.
- Avoid referencing only Windows utilities (e.g., sqlcmd, robocopy) without mentioning how to perform the same tasks on Linux.
- In sections discussing connecting to VMs or devices (e.g., RDP), mention SSH and Linux-native tools as alternatives.
- For PowerShell-heavy troubleshooting steps, provide bash or shell equivalents for Linux-managed devices.
- Review all examples and ensure Linux parity, especially in troubleshooting and workaround sections.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge.md
...ine/azure-stack-edge-deploy-aks-on-azure-stack-edge.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 focusing on PowerShell-based management, referencing Windows clients and tools first, and omitting Linux-specific instructions or examples. All command-line examples use PowerShell syntax, and there is no mention of Linux shell equivalents or guidance for Linux users. The documentation assumes or prefers a Windows environment for device management and configuration.
Recommendations
- Provide equivalent Linux/bash command-line instructions for all PowerShell examples, especially for device management and configuration tasks.
- Explicitly mention support for Linux clients where applicable, and clarify any OS-specific requirements or limitations.
- Include screenshots or walkthroughs using Linux terminals or Azure CLI in bash, not just PowerShell or Windows UI.
- When referencing tools (e.g., PowerShell interface), also describe how to access and use these tools from Linux systems.
- Avoid assuming the user is on Windows; structure prerequisites and instructions to be OS-agnostic or to present Linux and Windows options equally.
- Add a section or callouts for Linux users, highlighting any differences or additional steps required.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2105-release-notes.md
...abox-online/azure-stack-edge-gpu-2105-release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. Most configuration and management instructions reference the PowerShell interface, Az cmdlets, and Windows-specific tools or workflows. Examples and workarounds often assume a Windows environment (e.g., use of robocopy, Explorer, and Windows command syntax), with little or no mention of Linux equivalents. Linux tools, shell commands, or alternative workflows are rarely provided, and when present, are not given equal prominence or detail.
Recommendations
- Provide equivalent Linux/bash command examples alongside PowerShell commands for all device management and configuration tasks.
- Mention Linux-native tools (e.g., rsync, cp, scp) wherever Windows tools like robocopy or Explorer are referenced.
- Document how to connect to and manage the device from Linux systems, including remote management, VLAN configuration, and Az module usage.
- Ensure that instructions for features like AzCopy, SQL connectivity, and NFS mounting include both Windows and Linux command-line examples.
- Where PowerShell cmdlets are referenced, indicate if and how the same functionality can be achieved from a Linux shell or via cross-platform tools.
- Review all troubleshooting and workaround sections to ensure Linux users are not excluded or left to infer their own solutions.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2203-release-notes.md
...abox-online/azure-stack-edge-gpu-2203-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer), commands (PowerShell, Get-Process), and workflows (RDP, Windows services) without providing Linux equivalents. In some cases, Windows paths and mounting syntax are shown, while Linux alternatives are omitted or only briefly mentioned. Linux tools and workflows are underrepresented or missing in scenarios where cross-platform parity would be expected.
Recommendations
- For every Windows-specific example (e.g., robocopy, Explorer, PowerShell commands), provide equivalent Linux commands (e.g., rsync, cp, systemctl, ps).
- When showing mount commands, include both Windows (e.g., net use, Explorer) and Linux (e.g., mount -t nfs) syntax.
- For troubleshooting steps involving Windows services or processes, add parallel instructions for Linux (e.g., using systemctl, service, or kill commands).
- When referencing tools like sqlcmd, clarify installation and usage for both Windows and Linux clients.
- Avoid referencing Windows tools or patterns (e.g., RDP, Windows Guest Agent) as the only option; mention SSH or Linux agents where applicable.
- Review all examples and ensure Linux parity, especially in sections involving file operations, mounting, and VM/cluster management.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-configure-certificates.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-configure-certificates.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (such as Azure PowerShell and Windows Server Update Services) and includes screenshots showing certificate downloads in Windows File Explorer. There are no explicit Linux or cross-platform command-line examples for certificate creation, management, or installation, and no mention of Linux tools or workflows. The guidance for certificate conversion and installation is generic, but the only concrete tool references are Windows-centric. The order of tool recommendations (PowerShell before Readiness Checker) also subtly prioritizes Windows environments.
Recommendations
- Provide explicit Linux and macOS examples for certificate creation, management, and installation (e.g., using OpenSSL or Linux CLI tools).
- Include screenshots or instructions for downloading and handling certificates on Linux and macOS systems, not just Windows File Explorer.
- Mention cross-platform tools (such as OpenSSL) alongside or before Windows-specific tools like Azure PowerShell.
- Clarify that the procedures are applicable to all supported client OSes, and add notes or links to platform-specific instructions where workflows differ.
- When referencing tools for certificate creation, list cross-platform options first or in parallel with Windows tools.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2403-release-notes.md
...abox-online/azure-stack-edge-gpu-2403-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several types of Windows bias. Windows tools and patterns (e.g., PowerShell, RDP, Windows-specific services and commands) are referenced frequently and sometimes exclusively, especially in troubleshooting and workaround steps. In several cases, only Windows command-line examples (e.g., PowerShell cmdlets, Windows paths) are provided, with no equivalent Linux commands or steps. Windows-specific terminology and tools (e.g., Explorer, robocopy, RDP, waappagent.exe) are mentioned before or instead of Linux alternatives, and Linux parity is sometimes only mentioned as an afterthought or not at all.
Recommendations
- For every Windows-specific command or tool mentioned (e.g., PowerShell cmdlets, robocopy, Explorer, RDP), provide equivalent Linux commands or tools (e.g., bash/ssh, cp/rsync, Nautilus, SSH).
- When describing troubleshooting steps for Windows VMs, also include parallel steps for Linux VMs where applicable.
- Avoid using Windows paths or syntax exclusively in examples (e.g., show both C:\ paths and /mnt/ paths for NFS mounts).
- Mention Linux tools and workflows alongside Windows ones, and do not assume Windows as the default environment.
- Where PowerShell is referenced for device management, provide bash/CLI alternatives if supported.
- Review all examples and workarounds to ensure Linux users are not left without guidance.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-2202-release-notes.md
...abox-online/azure-stack-edge-gpu-2202-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation shows evidence of Windows bias in several areas: Windows-specific tools and commands (e.g., robocopy, Explorer, PowerShell, RDP) are mentioned without Linux equivalents or before them; some examples and workarounds are only provided for Windows environments; and Linux alternatives or parity are often missing or underexplained. This may hinder Linux users from effectively following the guidance.
Recommendations
- For every Windows-specific tool or command mentioned (e.g., robocopy, Explorer, PowerShell, RDP), provide equivalent Linux commands or tools (e.g., rsync/cp, Nautilus/Thunar, SSH, Linux shell commands).
- When giving command-line examples (such as mounting NFS shares or using sqlcmd), include both Windows and Linux syntax side by side.
- Avoid referencing Windows tools or patterns (e.g., 'use robocopy or Explorer') without also mentioning Linux alternatives.
- If a workaround or procedure is only described for Windows (e.g., PowerShell commands, RDP), add clear, step-by-step Linux alternatives.
- Review all troubleshooting and workaround sections to ensure Linux users are equally supported, especially for VM management, file operations, and connectivity.
- Consider reordering examples so that neither platform is always presented first, or present both together.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-certificate-requirements.md
...nline/azure-stack-edge-gpu-certificate-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific certificate providers (Microsoft RSA/Schannel Cryptographic Provider), defaulting to Windows export behaviors (3DES as default from Windows 10/Server 2016), and only providing next steps for certificate creation using Azure PowerShell cmdlets and the Azure Stack Hub Readiness Checker tool (both Windows-centric). There are no examples or guidance for Linux or cross-platform certificate management, export, or creation.
Recommendations
- Include equivalent Linux/OpenSSL commands and workflows for certificate creation, export, and management.
- Mention and provide examples for Linux-compatible cryptographic providers and how to ensure compatibility with Azure Stack Edge Pro.
- Clarify whether certificates generated on Linux (e.g., with OpenSSL) are supported and, if so, provide explicit instructions.
- List both Windows and Linux tools in parallel when discussing certificate export, password requirements, and encryption algorithms.
- Add troubleshooting steps and references for common Linux certificate management scenarios.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-add-shares.md
...tabox-online/azure-stack-edge-gpu-deploy-add-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows (and specifically Windows Server) instructions and screenshots first and in greater detail, especially for SMB shares. Windows-specific tools and workflows (Notepad, File Explorer, net use, Windows Run dialog) are emphasized, while Linux instructions are more concise and lack equivalent visual aids or troubleshooting tips. The 'hosts' file modification is described only for Windows, and there is no mention of macOS clients or cross-platform alternatives for SMB access.
Recommendations
- Provide Linux (and optionally macOS) instructions and examples alongside Windows instructions, not after them.
- Include Linux-specific screenshots (e.g., editing /etc/hosts, using Nautilus or command-line tools to access SMB shares).
- Offer SMB connection instructions for Linux clients (e.g., using smbclient, mount.cifs) and not just NFS.
- Balance the level of detail and troubleshooting tips between Windows and Linux sections.
- Mention cross-platform tools and approaches where possible (e.g., using the same share from different OSes).
- Clarify that the 'hosts' file modification applies to Linux (/etc/hosts) and provide the relevant steps.
- Consider including a table summarizing steps for Windows, Linux, and macOS clients for both SMB and NFS.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-image.md
...e/azure-stack-edge-gpu-create-virtual-machine-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and PowerShell usage are prioritized or exclusively shown in several sections, such as the AzCopy example and output, and the steps for downloading and copying VHDs. Linux-specific instructions are present for image preparation, but parity is lacking for subsequent steps (e.g., AzCopy usage and output are only shown for Windows/PowerShell). The documentation also references Windows tools and patterns (e.g., command prompt, PowerShell) more prominently than Linux equivalents.
Recommendations
- Provide parallel Linux/bash examples for all command-line operations, especially for AzCopy usage (e.g., show azcopy commands and sample output in a Linux shell).
- Include instructions for navigating to directories and running commands in Linux (e.g., using bash or sh instead of PowerShell/cmd).
- When showing sample output, include both Windows (PowerShell/cmd) and Linux (bash) outputs where relevant.
- Avoid using Windows paths (e.g., C:\azcopy\...) exclusively; show Linux path equivalents (e.g., ~/azcopy/...).
- Ensure that Linux instructions are given equal prominence and not relegated to secondary tabs or notes.
- Where possible, mention cross-platform tools and clarify that AzCopy is available for both Windows and Linux, with download links for both.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-manage-edge-resource-groups-portal.md
...zure-stack-edge-gpu-manage-edge-resource-groups-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell (Get-AzResource) example for listing Edge resource groups but does not mention or provide equivalent CLI or Linux-native commands. The only command-line example uses Azure PowerShell, which is most commonly used on Windows, and there is no mention of Azure CLI or Bash alternatives. This results in a bias towards Windows users and leaves Linux users without clear guidance.
Recommendations
- Add Azure CLI examples (e.g., using 'az resource list') alongside PowerShell examples to ensure Linux and cross-platform parity.
- Explicitly mention that Azure PowerShell can be used on Linux and macOS, or provide installation links for non-Windows platforms.
- Wherever PowerShell is referenced, provide equivalent Bash or shell command examples if possible.
- Review the documentation for other places where only Windows-centric tools or instructions are given and ensure Linux alternatives are included.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-monitor.md
...in/articles/databox-online/azure-stack-edge-monitor.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows (e.g., Hyper-V, YouTube video for adding a hard drive to a Hyper-V VM) without providing equivalent Linux or cross-platform instructions. There are no Linux-specific examples or mentions of Linux hypervisors (like KVM or VMware), and the guidance for expanding device capacity is tailored to Windows environments. The documentation also omits Linux command-line or UI examples for monitoring or managing the device.
Recommendations
- Provide equivalent instructions for adding data disks and expanding capacity using popular Linux hypervisors (e.g., KVM, VMware, VirtualBox).
- Include Linux-specific examples or references for device monitoring and management, such as using Linux browsers or command-line tools to access the local web UI.
- Replace or supplement the Hyper-V/Windows-specific YouTube video with cross-platform or Linux-focused tutorials.
- Explicitly mention supported Linux distributions and tools in relevant sections, ensuring parity with Windows coverage.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-quickstart.md
...cles/databox-online/azure-stack-edge-gpu-quickstart.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 (such as WSUS for updates), mentioning Windows-centric patterns (like referencing Microsoft Update and WSUS before any cross-platform update options), and omitting Linux-specific instructions or examples for key steps (such as configuring network settings or connecting to the device). There are no PowerShell commands, but the overall workflow assumes a Windows environment and does not provide Linux alternatives or parity.
Recommendations
- Include explicit instructions or examples for Linux and macOS users, especially for steps like configuring network adapters, connecting to the device, and managing certificates.
- Mention cross-platform update mechanisms (such as using public NTP servers or Linux-compatible update solutions) alongside or before Windows-specific options like WSUS.
- Provide command-line examples (e.g., using ip, nmcli, or ifconfig for network setup) for Linux and macOS, not just GUI/browser-based steps.
- Clarify that the procedure is cross-platform where possible, and highlight any steps that are platform-specific.
- Add troubleshooting tips for Linux/macOS environments, such as browser certificate warnings or network configuration nuances.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. Device management and remote access are described exclusively in terms of Windows tools and patterns, such as PowerShell and BitLocker. There are no Linux command-line examples or references to Linux-compatible management methods. Security features like BitLocker and Windows Defender Application Control are mentioned without Linux equivalents or alternatives. The documentation assumes a Windows-centric environment for both administration and security, with no guidance for Linux users.
Recommendations
- Provide Linux-based management and remote access instructions, such as using SSH or Linux CLI tools, alongside PowerShell examples.
- Mention and, where possible, support Linux-compatible encryption and security tools (e.g., LUKS/dm-crypt) or clarify if only BitLocker is supported.
- Include examples for connecting to the device from Linux clients, such as mounting SMB/NFS shares from Linux, and managing certificates using Linux tools (e.g., OpenSSL).
- Clarify any platform limitations and explicitly state if certain features are Windows-only, while suggesting workarounds or alternatives for Linux environments.
- Ensure that documentation sections referencing logs, password management, and device access include Linux workflows and commands where applicable.
Databox Online
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-system-requirements.md
...box-online/azure-stack-edge-gpu-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits some Windows bias, primarily through the exclusive mention of a PowerShell cmdlet (Set-HcsMacAddressPool) for configuring MAC addresses, with no equivalent Linux/CLI example or mention. There are no Linux shell commands or tools referenced, and the only command-line example is Windows-specific. While the document is otherwise platform-neutral in many sections, the lack of Linux parity in command-line instructions and tooling is notable.
Recommendations
- Provide equivalent Linux shell commands or instructions wherever PowerShell cmdlets are mentioned (e.g., show how to configure MAC addresses using Linux tools or REST APIs if available).
- Include examples or references to cross-platform CLI tools (such as Azure CLI) when discussing device management.
- Explicitly state whether certain configuration steps (like setting MAC addresses) are only possible via PowerShell, or if there are Linux alternatives.
- Review all command-line and tooling references to ensure Linux administrators have clear, actionable guidance.
- Consider adding a section or table summarizing management options for both Windows and Linux clients.