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 176-200 of 890 flagged pages
Databox Online
Azure Stack Edge 2304 release notes
...abox-online/azure-stack-edge-gpu-2304-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools (e.g., robocopy, Explorer, PowerShell, RDP, waappagent.exe) are mentioned as workarounds or examples, often without Linux equivalents or with Windows instructions given first. PowerShell is referenced for device management, and some examples (e.g., mounting NFS shares) use Windows syntax without showing Linux alternatives. In some cases, only Windows VM issues and solutions are described, while Linux VM scenarios are not addressed.
Recommendations
- Provide Linux equivalents for all Windows-specific tools and commands (e.g., show Linux mount syntax alongside Windows, mention rsync/scp instead of only robocopy/Explorer).
- Include PowerShell and Bash/CLI examples side-by-side for device management tasks.
- Document troubleshooting steps for both Windows and Linux VMs where applicable.
- Ensure that workarounds and examples are presented for both platforms, or clarify platform-specific applicability.
- Review and update references to Windows-only utilities to include cross-platform alternatives.
Create Pull Request
Databox Online
Azure Stack Edge 2312 release notes
...abox-online/azure-stack-edge-gpu-2312-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates several instances of Windows bias. Windows-specific tools (e.g., sqlcmd, robocopy, Explorer), commands (PowerShell cmdlets like Get-VM, Start-VM), and troubleshooting steps (RDP, Windows services) are referenced exclusively or before Linux equivalents. Some examples and workarounds only provide Windows instructions, omitting Linux alternatives. In several cases, PowerShell and Windows-centric patterns are described without Linux parity.
Recommendations
- Provide equivalent Linux instructions and examples alongside Windows ones (e.g., show how to connect to SQL Server from Linux, use Linux file copy tools like rsync or cp).
- Include Linux shell commands for device management and troubleshooting (e.g., show how to check VM status or restart services using Linux tools).
- Mention Linux tools and patterns (e.g., SSH instead of RDP, systemctl/service commands instead of Windows services) where relevant.
- Ensure that workarounds and examples are platform-agnostic or include both Windows and Linux steps.
- Review all command-line examples and add Linux alternatives where only Windows commands are shown.
Databox Online
Azure Stack Edge 2309 release notes
...abox-online/azure-stack-edge-gpu-2309-release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. PowerShell cmdlets and interfaces are frequently referenced for troubleshooting and configuration (e.g., Set-HcsKubernetesAzureMonitorConfiguration, Get-VM, Start-VM), with no equivalent Linux shell or CLI examples provided. Windows-specific tools and patterns (such as robocopy, Explorer, RDP, waappagent.exe, WindowsAzureGuestAgent, and Windows VM Guest Agent version checks) are mentioned, often without Linux alternatives. In some cases, Windows instructions are given before or instead of Linux ones, and Linux-centric workflows are underrepresented or missing entirely.
Recommendations
- Provide equivalent Linux shell/CLI commands and examples wherever PowerShell or Windows tools are referenced (e.g., show how to check VM status or restart VMs using Linux commands).
- Include troubleshooting steps for both Windows and Linux environments, especially for VM and Kubernetes operations.
- Mention Linux tools (such as rsync, cp, scp) alongside Windows tools like robocopy and Explorer for file operations.
- Add guidance for connecting to devices using SSH and Linux utilities, not just RDP and Windows interfaces.
- Ensure that instructions for both platforms are presented in parallel, or at least Linux examples are not omitted or relegated to secondary status.
Databox Online
Azure Stack Edge 2403 release notes
...abox-online/azure-stack-edge-gpu-2403-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several examples and workarounds reference Windows-specific tools (e.g., robocopy, Explorer, PowerShell cmdlets, RDP, Windows services), and some instructions are given only for Windows environments or with Windows commands first. Linux equivalents are sometimes missing or mentioned secondarily. There are also references to Windows VM-specific issues and solutions, while Linux VM scenarios are less detailed.
Recommendations
- Provide Linux-specific examples and commands alongside Windows instructions, especially for VM management, troubleshooting, and file operations.
- When referencing tools like robocopy or Explorer, include Linux alternatives such as rsync, cp, or Midnight Commander.
- For PowerShell cmdlets (e.g., Get-VM, Start-VM), offer equivalent Linux CLI commands (e.g., virsh, systemctl, kubectl) where applicable.
- Ensure troubleshooting steps for VM extensions and agent issues are available for both Windows and Linux VMs.
- Review and update documentation to present Linux and Windows instructions in parallel, rather than Windows-first.
- Highlight cross-platform compatibility and limitations for features, tools, and workarounds.
Databox Online
Azure Stack Edge 2501 release notes
...abox-online/azure-stack-edge-gpu-2501-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools (e.g., robocopy, Explorer, PowerShell, Windows VM Guest Agent, RDP) are mentioned as workarounds or examples, often without Linux equivalents. PowerShell commands and interfaces are referenced for device management and troubleshooting, while Linux alternatives are rarely provided or are mentioned later. Some examples and instructions are tailored to Windows environments (e.g., mounting NFS shares from Windows, using Windows-specific utilities), and Linux workflows are underrepresented or missing.
Recommendations
- Provide Linux equivalents for all Windows-specific tools and commands (e.g., suggest rsync or cp instead of robocopy/Explorer, include SSH and Linux service management commands alongside PowerShell/RDP instructions).
- Ensure that examples for mounting NFS shares and other operations are given for both Windows and Linux clients, with Linux examples presented equally or first where appropriate.
- Include troubleshooting steps for Linux VMs and environments, not just Windows VMs (e.g., how to restart services, check agent status, etc.).
- Balance references to PowerShell with Bash or other Linux shell commands for device management.
- Review and update documentation to ensure Linux users have clear, actionable guidance for all major workflows and issues.
Databox Online
Azure Stack Edge 2510 release notes
...abox-online/azure-stack-edge-gpu-2510-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows tools and workflows (e.g., PowerShell, RDP, Explorer, robocopy, Windows VM Guest Agent) are referenced exclusively or before Linux equivalents. Some examples and workarounds are Windows-centric, with missing or less detailed Linux alternatives. PowerShell commands and Windows-specific troubleshooting steps are provided without Linux parity. In several cases, only Windows paths or commands are shown, and Linux users are left to infer their own solutions.
Recommendations
- Provide Linux equivalents for all command-line examples, such as showing both PowerShell and Bash/SSH commands where relevant.
- Include Linux-specific troubleshooting steps alongside Windows instructions, especially for VM management and agent issues.
- Mention cross-platform tools (e.g., rsync, scp) in addition to Windows tools like robocopy and Explorer for file operations.
- Ensure that examples using Windows paths (e.g., C:\Users) also include Linux mount syntax and usage.
- Reference Linux UI and remote access methods (e.g., SSH) alongside Windows RDP.
- Review all workarounds and ensure Linux users are given clear, actionable steps, not just Windows-centric guidance.
Databox Online
Azure Stack Edge 2407 release notes
...abox-online/azure-stack-edge-gpu-2407-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates several instances of Windows bias. Windows-specific tools (e.g., robocopy, Explorer, PowerShell cmdlets) are mentioned without Linux equivalents, and Windows-centric examples (such as mounting NFS shares from Windows paths, troubleshooting Windows VM Guest Agent, and using PowerShell for device management) are provided before or instead of Linux alternatives. Some workarounds and instructions are exclusively for Windows environments, and Linux commands or patterns are missing or less emphasized.
Recommendations
- Provide Linux equivalents for all Windows-specific commands and tools (e.g., show how to mount NFS shares from Linux, use rsync or cp instead of robocopy, and SSH instead of RDP).
- Include Linux command-line examples (bash, systemctl, etc.) alongside PowerShell cmdlets for device management and troubleshooting.
- Ensure troubleshooting steps for VM extensions and agent issues include both Windows and Linux VM scenarios.
- List Linux tools and patterns before or alongside Windows ones to avoid implicit prioritization.
- Review all examples and workarounds to ensure Linux users have clear, actionable guidance.
Databox Online
Azure Stack Edge 2506 release notes
...abox-online/azure-stack-edge-gpu-2506-release-notes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits several instances of Windows bias. Windows-specific tools and commands (e.g., PowerShell cmdlets, Windows VM Guest Agent, RDP, Explorer, robocopy) are referenced without Linux equivalents or alternatives. In multiple workarounds and examples, Windows approaches are described first or exclusively, while Linux methods are omitted or only briefly mentioned. There is a lack of parity in providing Linux-centric instructions, especially for VM management, file operations, and troubleshooting.
Recommendations
- Provide equivalent Linux commands and tools alongside Windows examples (e.g., show how to manage VMs with Linux CLI tools, use SSH instead of RDP, use rsync/scp instead of robocopy/Explorer).
- Ensure that troubleshooting steps for VM extensions and guest agents include Linux VM scenarios, not just Windows.
- When referencing PowerShell or Windows-specific utilities, add parallel instructions for Bash, Linux shell, or cross-platform alternatives.
- In tables and lists, avoid listing Windows approaches first unless there is a technical reason; strive for equal prominence.
- For file copy and blob management, include Linux-native tools and commands (e.g., cp, rsync) and clarify any platform-specific caveats.
- Audit documentation for other areas where only Windows workflows are described and add Linux parity where possible.
Databox Online
Certificates requirements and troubleshooting with Azure Stack Edge Pro | Microsoft Docs
...nline/azure-stack-edge-gpu-certificate-requirements.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (certificate store, 3DES as default on Windows 10/Server 2016), recommending PowerShell cmdlets for certificate creation, and omitting Linux or cross-platform alternatives for certificate management and export. The guidance and examples are tailored to Windows environments, with no mention of Linux commands, OpenSSL usage, or certificate handling on non-Windows platforms.
Recommendations
- Include Linux-specific instructions and examples for certificate creation and export, such as using OpenSSL to generate and export PFX certificates.
- Mention equivalent Linux tools and commands for setting certificate attributes and encryption (e.g., setting 3DES encryption with OpenSSL).
- Provide parity in troubleshooting steps and references for both Windows and Linux environments.
- List cross-platform options before or alongside Windows-specific tools, rather than referencing Windows tools first.
- Clarify whether requirements (such as Microsoft RSA/Schannel provider) are strictly Windows-only, and suggest alternatives for Linux if possible.
Databox Online
Overview of cluster witness on your Azure Stack Edge device
...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 page demonstrates a Windows bias by exclusively referencing Windows Server Failover Clustering, Windows-specific concepts (quorum, witness), and Windows-centric tools (SMB file share, Azure Storage account integration). There are no examples or mentions of Linux clustering technologies, nor any guidance for Linux-based witness setups. All terminology and setup instructions assume a Windows environment.
Recommendations
- Include references to Linux-based clustering solutions (e.g., Pacemaker, Corosync) and explain how quorum and witness concepts apply in those contexts.
- Provide examples or guidance for configuring a cluster witness using Linux tools and file sharing protocols (e.g., NFS, native Linux SMB implementations).
- Clarify whether Azure Stack Edge supports Linux-based clusters and, if so, add parity documentation for Linux witness setup.
- Avoid assuming Windows Server as the default and mention cross-platform considerations where relevant.
Databox Online
Certificates troubleshooting with Azure Stack Edge Pro with GPU| Microsoft Docs
...ne/azure-stack-edge-gpu-certificate-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows PowerShell as the management interface for certificate operations and mentioning the Microsoft RSA/Schannel Cryptographic Provider, which is specific to Windows. There are no examples or guidance for Linux-based management tools or certificate handling, and no Linux-specific troubleshooting steps or tool references are provided.
Recommendations
- Include equivalent Linux command-line examples (e.g., using OpenSSL, certtool, or Linux shell commands) for certificate troubleshooting and management.
- Mention Linux-compatible cryptographic providers and clarify whether non-Windows platforms are supported or not.
- Add troubleshooting steps and error messages relevant to Linux environments, if applicable.
- Provide guidance on managing certificates from Linux or cross-platform environments, not just Windows PowerShell.
- Clarify platform requirements and support in the introduction, specifying if only Windows is supported or if Linux is also an option.
Databox Online
Azure Stack Edge Pro GPU, Pro R, Mini R certificate overview
...x-online/azure-stack-edge-gpu-certificates-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Windows-centric tools for certificate creation and management, mentioning PowerShell-based workflows before any cross-platform or Linux alternatives. There are no explicit Linux or cross-platform command examples, and the only tool-based guidance is for PowerShell or Windows GUI actions. This may hinder Linux users or those on non-Windows platforms from following the guidance effectively.
Recommendations
- Provide equivalent Linux and macOS command-line instructions for certificate creation, such as using OpenSSL, alongside or before PowerShell examples.
- Mention and link to cross-platform tools (e.g., OpenSSL, certbot) for certificate management, not just Windows/PowerShell tools.
- When referencing certificate upload or verification steps, include instructions for Linux (e.g., using command line to inspect certificates) and not just Windows GUI actions.
- Ensure that all referenced tools and scripts are available or have alternatives on Linux and macOS.
- Explicitly state platform compatibility for each tool or script mentioned, and provide parity in documentation structure for all major platforms.
Databox Online
Overview of clustering on your Azure Stack Edge Pro GPU device
...box-online/azure-stack-edge-gpu-clustering-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments. It references Windows Server Failover Clustering as the underlying technology, links exclusively to Windows Server documentation, and describes cluster management primarily via PowerShell and local UI. There are no Linux-specific examples, tools, or alternative clustering patterns mentioned. The terminology, tooling, and operational steps all assume a Windows-centric approach, with no parity for Linux-based management or clustering solutions.
Recommendations
- Explicitly state that Azure Stack Edge clustering is based on Windows Server Failover Clustering, and clarify if Linux-based clustering is unsupported or not applicable.
- If Linux-based management or clustering is possible, provide equivalent examples and instructions for Linux environments (e.g., using Linux CLI, SSH, or relevant Linux clustering tools).
- Include references to Linux documentation or best practices for similar scenarios, even if only to clarify limitations or differences.
- Offer guidance for users who may wish to integrate Linux workloads or management tools, including any interoperability considerations.
- Avoid assuming PowerShell as the only management interface; mention alternatives if available, such as REST APIs, CLI tools, or SSH.
Databox Online
Configure MetalLB via BGP on Azure Stack Edge
...ine/azure-stack-edge-gpu-configure-metallb-bgp-mode.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with all configuration steps and examples provided exclusively using Windows PowerShell cmdlets and tools. There is no mention of Linux-based workflows, nor are any Linux CLI equivalents or cross-platform alternatives discussed. The documentation assumes access to a Windows environment and does not address how Linux users might perform the same tasks.
Recommendations
- Provide equivalent Linux-based instructions, such as using SSH and standard Linux networking tools (e.g., ip, nmcli, bird, FRRouting) for BGP configuration.
- Include examples using kubectl and YAML manifests for MetalLB configuration, which are platform-agnostic.
- Clarify whether the configuration can be performed from a Linux host, and if not, explain the limitations.
- Add a section comparing Windows and Linux approaches, highlighting any differences or platform-specific requirements.
- Reference cross-platform PowerShell (pwsh) usage explicitly if it is supported, and provide examples for both Windows and Linux terminals.
Databox Online
Collect VM guest logs on Azure Stack Edge Pro GPU
...zure-stack-edge-gpu-collect-virtual-machine-guest-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions for collecting VM guest logs, referencing Windows-specific tools and commands, and requiring users to connect to a PowerShell interface. Linux log file locations are mentioned, but there are no Linux command examples or instructions for collecting logs from Linux VMs, and the workflow is centered around Windows tooling.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using SSH and standard Linux utilities) for collecting guest logs from Linux VMs.
- Describe how to access the Linux VM logs directly, including commands to copy or package log files (e.g., using scp, tar, etc.).
- Clarify whether the PowerShell interface is required for Linux VMs or if there are alternative Linux-native methods.
- Present instructions for both Windows and Linux environments in parallel, rather than focusing on Windows tooling first.
- Include references to Linux troubleshooting tools or scripts where applicable.
Databox Online
Connect to Azure Resource Manager on your Azure Stack Edge GPU device
...nline/azure-stack-edge-gpu-connect-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments and PowerShell usage. All examples, instructions, and screenshots are specific to Windows clients, Windows PowerShell, and Windows tools (e.g., Notepad, hosts file at C:\Windows\System32\Drivers\etc, ping.exe). There are no Linux or cross-platform shell examples, nor any mention of how to perform these steps on Linux or macOS clients. The prerequisites and workflow steps assume a Windows client exclusively, and PowerShell is presented as the only automation option.
Recommendations
- Add equivalent instructions and examples for Linux clients, including certificate creation, installation, and management using Linux tools (e.g., openssl, update-ca-certificates, etc.).
- Provide cross-platform PowerShell (pwsh) examples and clarify support for PowerShell Core on Linux/macOS, or explicitly state limitations.
- Include instructions for modifying the /etc/hosts file on Linux/macOS, using editors like nano or vi, and relevant screenshots.
- Show how to verify endpoint resolution using Linux commands (e.g., ping, dig, nslookup).
- Clarify whether Azure CLI or REST API can be used as alternatives to PowerShell, and provide examples if supported.
- Update prerequisites to mention Linux/macOS requirements, such as supported PowerShell Core versions, certificate stores, and network tools.
- Where Windows-specific tools are referenced (e.g., Notepad, Windows Explorer), provide Linux/macOS alternatives.
Databox Online
Create certificates for Azure Stack Edge Pro GPU via Azure PowerShell | Microsoft Docs
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-create-certificates-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows, exclusively using Windows PowerShell cmdlets and tools for certificate creation. All examples and instructions assume a Windows environment, with no mention of Linux or cross-platform alternatives. The Azure PowerShell and Windows PowerShell tools are referenced throughout, and there are no equivalent examples or guidance for Linux users (e.g., using OpenSSL or Azure CLI).
Recommendations
- Add equivalent Linux instructions using OpenSSL for certificate creation.
- Provide Azure CLI examples for certificate management that work cross-platform.
- Explicitly mention Linux support and any prerequisites for non-Windows environments.
- Reorder sections to present both Windows and Linux options equally, or clarify platform-specific instructions.
- Include troubleshooting notes for Linux users, such as file format compatibility and certificate store locations.
Databox Online
Create and manage a Kubernetes cluster on Azure Stack Edge Pro GPU device| Microsoft Docs
...line/azure-stack-edge-gpu-create-kubernetes-cluster.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 bias. All examples and instructions are provided exclusively for Windows clients using PowerShell, with explicit references to Windows paths, tools (curl.exe, Notepad), and file locations. There are no Linux or cross-platform examples, and Windows is consistently mentioned first or exclusively, even when other operating systems are nominally supported.
Recommendations
- Provide equivalent instructions and examples for Linux clients, including shell commands (bash), Linux file paths, and tools (curl, nano/vim for editing hosts file).
- Clarify cross-platform support by listing both Windows and Linux prerequisites and supported tools.
- Include Linux-specific steps for installing kubectl, managing the kube config file, and editing the hosts file.
- Avoid exclusive references to Windows tools (e.g., Notepad, PowerShell) and mention alternatives for other platforms.
- Where PowerShell cmdlets are required, explain if/how these can be run from Linux (e.g., via PowerShell Core) or provide REST API alternatives if available.
Databox Online
Connect to the virtual machine console on Azure Stack Edge Pro GPU device
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-connect-virtual-machine-console.md
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, presenting Windows Remote Desktop instructions before Linux alternatives, and using Windows-centric tools and terminology. Linux instructions (FreeRDP) are present but less detailed, and there are no examples for connecting via Linux-native RDP clients other than FreeRDP. The PowerShell commands are shown with Windows-style prompts and examples, and the creation of .rdp files is described in a Windows context.
Recommendations
- Provide Linux-first or parallel examples for each step, especially for connecting to the PowerShell interface and using remote desktop clients.
- Include instructions for other popular Linux RDP clients (e.g., Remmina, KRDC) alongside FreeRDP.
- Show PowerShell command examples using Linux/Mac terminal prompts to demonstrate cross-platform usage.
- Clarify how to create and use .rdp files on Linux and macOS, or provide alternative connection methods.
- Balance the order of instructions so that Linux and macOS users are not secondary to Windows users.
- Explicitly mention and link to Linux/macOS documentation for prerequisites and troubleshooting.
Databox Online
Create certificates for Azure Stack Edge Pro GPU via Azure Stack Hub Readiness Checker tool
...nline/azure-stack-edge-gpu-create-certificates-tool.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively targets Windows environments, requiring Windows 10/Server and PowerShell for all steps. All examples use PowerShell commands, and there is no mention of Linux or cross-platform alternatives. The Azure Stack Hub Readiness Checker tool is distributed via the PowerShell Gallery, further reinforcing Windows bias. No Linux shell or tool equivalents are provided, nor is there guidance for non-Windows users.
Recommendations
- Provide instructions and examples for Linux and macOS environments, including supported shell commands (e.g., Bash) and prerequisites.
- Clarify whether the Azure Stack Hub Readiness Checker tool can run on Linux (e.g., via PowerShell Core or .NET) and provide installation steps if possible.
- Include Linux file path examples alongside Windows paths.
- If the tool is Windows-only, explicitly state this limitation and suggest alternative methods for Linux users (such as using OpenSSL for CSR generation).
- Offer parity in certificate management steps, including import/export and validation, using Linux-native tools where applicable.
Databox Online
Create custom VM images for your Azure Stack Edge Pro GPU device
...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 Windows bias in several ways: Windows examples and instructions are often presented before Linux equivalents (windows_first), PowerShell is used as the default CLI for cross-platform tasks (powershell_heavy), and Windows-specific tools and patterns (e.g., sysprep, PowerShell, Windows file paths) are emphasized. Linux instructions are present but sometimes less detailed, and Linux-specific CLI examples (e.g., Bash, azcopy on Linux) are missing (missing_linux_example). The AzCopy section only provides PowerShell/Windows command examples, and sample output is from a Windows environment (windows_tools).
Recommendations
- Provide Linux/Bash equivalents for all PowerShell commands, especially for AzCopy usage and sample output.
- Present Windows and Linux instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Include Linux-specific details for common tasks, such as file paths, shell commands, and troubleshooting.
- Add sample output from Linux environments to demonstrate parity.
- Clarify when instructions are platform-agnostic and when they are platform-specific.
- Ensure that prerequisites and tool installation steps include Linux package manager instructions (e.g., apt, yum) for AzCopy.
Databox Online
Enable Azure Arc on Kubernetes on Azure Stack Edge Pro GPU device| Microsoft Docs
...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
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments, with instructions and examples primarily using Windows PowerShell and referencing Windows clients. Linux or macOS equivalents are not provided, and Windows tools and patterns are mentioned first and exclusively in many sections. The procedure assumes a Windows client, and PowerShell commands are used throughout without Bash or Linux alternatives.
Recommendations
- Provide parallel instructions and examples for Linux/macOS clients, including Bash shell commands and az CLI usage outside of PowerShell.
- Explicitly mention and demonstrate how to perform key steps (such as connecting to the device, running az CLI commands, and managing service principals) from Linux/macOS environments.
- Replace or supplement PowerShell-specific commands (e.g., Set-HcsKubernetesAzureArcAgent, GetAzResource) with REST API, az CLI, or Bash equivalents where possible.
- Clarify in the prerequisites and throughout the guide that non-Windows clients are supported, and link to or include the relevant steps for those platforms.
- Ensure screenshots and UI instructions are not Windows-specific, or provide alternatives for Linux/macOS users.
Databox Online
Use Azure Marketplace image to create VM image for Azure Stack Edge Pro GPU device
...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 page exhibits a strong Windows bias. Most command-line examples use PowerShell syntax and variables (e.g., $urn, $diskName), and Windows-specific Azure PowerShell cmdlets (New-AzureStorageContext, Start-AzureStorageBlobCopy, Get-AzureStorageBlobCopyState) are used exclusively for key steps. The workflow and examples prioritize Windows images and tools, with Windows Server images listed first and in greater detail. There are no equivalent Linux shell (bash) examples or instructions for performing the same tasks using cross-platform tools, and Linux images are mentioned only briefly.
Recommendations
- Provide equivalent bash shell examples for all steps, using standard Azure CLI commands and Linux shell variable syntax.
- Include instructions for copying VHDs using az storage blob copy or other cross-platform tools, rather than only PowerShell cmdlets.
- List Linux images (e.g., Ubuntu, CentOS) alongside Windows images in tables and examples, and ensure parity in detail and guidance.
- Clarify which steps are platform-agnostic and which require OS-specific tools, and offer alternatives for Linux/macOS users.
- Add a note or section explicitly addressing Linux/macOS users, guiding them through the workflow using their native tools.
Databox Online
Tutorial to transfer data to storage account with Azure Stack Edge Pro GPU| Microsoft Docs
...ne/azure-stack-edge-gpu-deploy-add-storage-accounts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples use Azure PowerShell cmdlets, with sample outputs shown from a Windows PowerShell prompt. The instructions for obtaining storage account keys and certificates reference Windows paths and formats, and Storage Explorer usage is described in a Windows-centric manner (e.g., referencing Base-64 encoded .cer as PEM format 'on Windows system'). There are no Linux or cross-platform CLI examples, nor any mention of Linux tools or workflows. The documentation does not provide parity for Linux users or those using Bash/Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) commands and examples for Linux/macOS users to obtain storage account information and keys.
- Include sample outputs from Linux terminals (e.g., bash) alongside PowerShell outputs.
- Clarify certificate formats and import steps for Linux and macOS environments, including OpenSSL usage and file paths.
- Describe how to use Storage Explorer on Linux/macOS, noting any differences in certificate handling.
- Avoid Windows-specific terminology and paths unless necessary; provide cross-platform instructions where possible.
- Explicitly state platform requirements or limitations if any steps are Windows-only.
Databox Online
Predeployment checklist to deploy Azure Stack Edge Pro GPU device | Microsoft Docs
...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 demonstrates Windows bias primarily through references to Windows-specific tools (WSUS, Windows Update server) and the absence of Linux equivalents or examples. Update server configuration defaults to Windows Update, with no mention of Linux update mechanisms. There are no explicit Linux or cross-platform instructions for network readiness, device connection, or certificate generation, and the documentation does not provide parity for Linux environments.
Recommendations
- Include instructions for configuring Linux-based update servers (e.g., apt, yum mirrors) as alternatives to WSUS/Windows Update.
- Provide Linux-specific examples for device connection, such as how to change IPv4 settings on Linux laptops and use common Linux network tools.
- Mention cross-platform certificate generation and management tools, including Linux command-line options (e.g., OpenSSL).
- Clarify whether the Azure Stack Edge Network Readiness Tool is cross-platform, and provide usage instructions for Linux if supported.
- Add notes or sections highlighting differences or additional steps for Linux users throughout the checklist.