Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1251-1275 of 2185 flagged pages
Azure Docs
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 demonstrates a strong Windows bias by exclusively using PowerShell cmdlets and Windows-centric management tools for all configuration and management steps. All code examples, instructions for device access, and VM management are provided only for PowerShell, with no Linux shell or cross-platform CLI equivalents. Even when mentioning Linux VHDs as possible VM images, the operational guidance and examples remain Windows/PowerShell specific. There is no mention of how to perform these tasks from a Linux or cross-platform environment, nor are Linux-native tools or workflows described.
Recommendations
- Provide equivalent command-line instructions using Azure CLI and/or Bash shell where possible, especially for device management and VM operations.
- Include examples for connecting to and managing the device from Linux or macOS systems, not just via PowerShell.
- Document any required tools or prerequisites for Linux users (e.g., SSH, Azure CLI, Python scripts) and show how to use them for common tasks.
- If certain operations are only possible via PowerShell, explicitly state this limitation and suggest workarounds or alternatives for Linux users.
- Ensure that all code samples and screenshots are balanced between Windows and Linux environments, or clearly indicate when steps are OS-specific.
Create Pull Request
Azure Docs
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It assumes the client is a Windows system, specifies Windows PowerShell as a requirement, and all command-line examples are shown in PowerShell with Windows-style paths. There are no Linux/macOS shell examples, and instructions for saving files, running commands, and file paths are all Windows-centric. Linux tools, shell syntax, and file system conventions are not mentioned or demonstrated.
Recommendations
- Provide parallel Linux/macOS instructions and examples alongside Windows ones, including bash shell commands and Unix-style file paths.
- Clarify in the prerequisites that Linux/macOS clients are fully supported and link to any relevant setup guides.
- Show sample outputs from Linux/macOS terminals as well as Windows PowerShell.
- Mention and demonstrate how to install and configure kubectl on Linux/macOS clients.
- Avoid assuming the use of Windows-specific tools (e.g., PowerShell, C:\ paths) in generic Kubernetes command examples.
- Where Windows-specific commands (e.g., New-HcsKubernetesNamespace) are required, note if there are Linux equivalents or clarify if these are only available on Windows.
Azure Docs
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
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples for both Windows and Linux scenarios use PowerShell and Azure PowerShell cmdlets, which are native to Windows and less common on Linux. File paths and sample outputs consistently show Windows-style paths and prompts (e.g., C:\WINDOWS\system32>), even in Linux sections. There are no examples using native Linux tools or shells (e.g., Bash, Azure CLI). The documentation assumes the user is operating from a Windows environment, and Linux parity is only achieved by changing parameter values, not by providing Linux-native workflows.
Recommendations
- Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
- Show Linux shell (bash) command-line examples, including file paths and prompts appropriate for Linux environments.
- Include instructions for installing and using Azure PowerShell on Linux, or clarify that Azure CLI is a recommended alternative.
- Adjust sample outputs to reflect Linux environments (e.g., /home/user/ paths, $ prompt) in Linux sections.
- Explicitly mention that PowerShell examples can be run on Linux if PowerShell Core is installed, but highlight native Linux alternatives.
- Reorder sections or provide equal prominence to Linux and Windows workflows, avoiding a 'Windows-first' presentation.
Azure Docs
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 examples use PowerShell commands, even for Linux VMs. The Windows section appears first and is more detailed, with explicit file paths and output samples. Linux instructions reuse the same PowerShell-centric workflow, and there are no examples using native Linux tools (e.g., Azure CLI on Linux, Bash). File paths and user names in Linux examples (e.g., /home/Administrator) are Windows-like, and there is no demonstration of using Linux-native scripting or command-line environments.
Recommendations
- Provide Linux-native examples using Bash and Azure CLI, not just PowerShell.
- Include Linux file paths and typical user names (e.g., /home/ubuntu, /home/user) in Linux examples.
- Show how to deploy and manage the extension from a Linux management machine, not just from Windows.
- Present Windows and Linux instructions in parallel, or start with a neutral overview before splitting by OS.
- Demonstrate how to check extension status and logs using Linux-native commands (e.g., tail, cat, ls).
- Clarify that PowerShell is not required for Linux VM management and provide alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/includes/register-provider-powershell.md
...es/event-grid/includes/register-provider-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides Azure PowerShell commands for registering the Event Grid resource provider, which are most commonly used in Windows environments. There are no examples or instructions for performing the same task using Azure CLI or other cross-platform tools, which may disadvantage Linux or macOS users.
Recommendations
- Add equivalent Azure CLI examples (e.g., 'az provider register --namespace Microsoft.EventGrid') alongside PowerShell commands.
- Explicitly mention that the task can be performed on any platform using Azure CLI, not just PowerShell.
- Consider presenting Azure CLI examples first or side-by-side with PowerShell to emphasize cross-platform support.
- Clarify any platform-specific requirements or differences, if applicable.
Azure Docs
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 Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions and cmdlets for configuring Azure Monitor on the Azure Stack Edge Pro GPU device. It references connecting to the 'PowerShell interface' and uses a PowerShell-specific cmdlet (Set-HcsKubernetesAzureMonitorConfiguration) without mentioning or providing equivalent steps for Linux or Bash environments. The sample output also shows a PowerShell prompt, and there are no Linux shell or cross-platform CLI alternatives presented.
Recommendations
- Provide equivalent instructions and examples for Linux/Bash environments, including how to connect and configure Azure Monitor from a Linux shell.
- If the device only supports PowerShell, explicitly state this limitation and clarify platform support early in the documentation.
- Where possible, use cross-platform Azure CLI commands instead of or in addition to PowerShell cmdlets.
- Include screenshots or terminal outputs from both Windows (PowerShell) and Linux (Bash) environments to demonstrate parity.
- Mention any platform-specific requirements or limitations, so users on non-Windows systems are aware of their options.
Azure Docs
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 file paths and output. The prerequisites and instructions assume a Windows client, referencing Windows PowerShell and directories like C:\Users\<username>\.kube. There are no Linux or macOS equivalents provided for commands, file paths, or environment setup, and Linux tools or shell conventions are not mentioned.
Recommendations
- Provide parallel Linux/macOS examples for all kubectl commands, using bash syntax and appropriate file paths (e.g., ~/.kube).
- Update prerequisites to explicitly mention supported Linux/macOS environments and tools (e.g., bash, zsh, Terminal).
- Show sample outputs from Linux shells (e.g., $ kubectl get pods) alongside PowerShell outputs.
- Avoid referencing Windows-specific tools (like Windows PowerShell) as the default; instead, present both Windows and Linux options equally.
- Clarify that the procedures apply to non-Windows clients and provide any OS-specific steps or caveats.
- Where file paths are mentioned, provide both Windows and Unix-style equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-templates.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-templates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all command-line examples using PowerShell, explicit references to Windows file paths (e.g., C:\WINDOWS\system32), and instructions for editing the Windows hosts file using Notepad as administrator. Tools like Storage Explorer and AzCopy are mentioned, but their usage is described in a Windows context. There are no CLI or shell examples for Linux/macOS users, and no guidance for Linux-specific workflows (e.g., editing /etc/hosts, using Linux-native editors, or running Azure CLI from Bash). Even when Linux VMs are discussed, the operational steps are Windows-centric.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, with sample outputs from a Bash shell.
- Include Linux/macOS instructions for editing the hosts file (e.g., using sudo nano /etc/hosts) and for certificate management.
- Show file paths and command prompts for both Windows (C:\...) and Linux/macOS (/home/user/...), or use platform-agnostic variables.
- Demonstrate how to use Storage Explorer and AzCopy on Linux/macOS, including installation and usage examples.
- Ensure that all screenshots and sample outputs are balanced between Windows and Linux environments.
- Explicitly state that all steps can be performed from Linux/macOS as well as Windows, and provide any necessary prerequisites or caveats for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-connect-resource-manager.md
...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, with explicit requirements for Windows PowerShell 5.1. There are no Linux or macOS instructions, nor are there any examples using cross-platform PowerShell Core or CLI tools. Windows-specific tools (Notepad, hosts file at C:\Windows\System32\Drivers\etc, ping.exe) are referenced exclusively, and Linux equivalents are not mentioned.
Recommendations
- Add instructions and examples for connecting from Linux and macOS clients, including certificate management, hosts file editing, and endpoint verification.
- Include PowerShell Core (pwsh) examples, which are cross-platform, and clarify any limitations or differences compared to Windows PowerShell 5.1.
- Provide equivalent commands for Linux/macOS, such as using nano/vim for editing /etc/hosts, and using ping or dig for endpoint resolution.
- Document certificate import/export steps for Linux/macOS (e.g., using openssl, update-ca-certificates, or Keychain Access on macOS).
- Clarify whether Azure CLI (az) can be used for any of the steps, and provide CLI examples if possible.
- Explicitly state any platform limitations (e.g., if only Windows is supported, explain why and if Linux support is planned).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-install-update.md
.../databox-online/azure-stack-edge-gpu-install-update.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based update mechanisms (Microsoft Update, Windows Server Update Services, Microsoft Update Catalog) and .exe update packages. There are no examples or instructions for Linux-based management, update tools, or command-line interfaces other than a brief mention of PowerShell. Linux equivalents or cross-platform CLI options are not discussed, and Windows tools are presented as the default or only option.
Recommendations
- Provide instructions for updating Azure Stack Edge devices using Linux-based tools or interfaces, such as Azure CLI or REST APIs, where applicable.
- Include examples of downloading and applying updates from non-Windows environments, such as using curl/wget and tar/zip packages instead of only .exe files.
- Mention and document any cross-platform management options, including how to perform update operations from Linux or macOS hosts.
- If PowerShell is referenced, also provide Bash or shell script equivalents for Linux users.
- Clarify whether the update process is supported or possible from non-Windows systems, and if not, explicitly state the limitation and suggest workarounds.
Azure Docs
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 referencing Azure PowerShell cmdlets exclusively for command-line management, without providing equivalent instructions or examples for Linux users (e.g., Azure CLI or Bash). All command-line tooling guidance is centered on PowerShell, and there are no Linux shell or cross-platform command examples. While the API and SDK samples are platform-neutral, the lack of Linux-specific or cross-platform command-line instructions limits accessibility for non-Windows users.
Recommendations
- Provide Azure CLI examples alongside PowerShell cmdlets for all command-line operations, ensuring parity for Linux and macOS users.
- Explicitly mention cross-platform alternatives (e.g., Bash scripts, REST API usage with curl) where PowerShell is referenced.
- Clarify which tools are supported on which platforms, and recommend cross-platform tools where possible.
- Include notes or links to documentation for installing and using Azure CLI on Linux.
- Review all sections referencing PowerShell to ensure Linux users are not excluded from management workflows.
Azure Docs
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 consistently referencing SMB (a Windows-native protocol) before NFS (a Linux/UNIX-native protocol) when discussing storage options. Examples and diagrams focus on SMB shares, and there are no explicit Linux command-line or configuration examples (e.g., using Linux tools or shell commands). There is also a lack of Linux-specific guidance or parity in example commands, with no mention of Linux-native tools or patterns for managing storage.
Recommendations
- Alternate the order of SMB and NFS mentions, or lead with NFS in some sections to provide balance.
- Provide explicit Linux-focused examples, such as using Linux shell commands to mount NFS shares or manage Kubernetes storage.
- Include example YAMLs or command snippets that demonstrate both SMB (for Windows environments) and NFS (for Linux environments) usage.
- Reference Linux-native tools (e.g., mount, showmount, etc.) and patterns for managing storage alongside any Windows-specific instructions.
- Clarify that both SMB and NFS are supported equally, and provide guidance for Linux users on best practices for storage management.
Azure Docs
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 commands for Linux users (such as Azure CLI). The only programmatic example is Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples (e.g., using 'az resource list') alongside PowerShell examples to ensure Linux and macOS users are supported.
- When referencing command-line tools, mention both PowerShell and Azure CLI, and provide links to both sets of documentation.
- Explicitly state that the steps can be performed from any OS using the Azure CLI, not just from Windows/PowerShell.
- Consider providing Bash shell examples where appropriate, especially for deletion and listing tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-prepare-certificates-device-upload.md
...zure-stack-edge-gpu-prepare-certificates-device-upload.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes certificate preparation using Windows-specific tools (certlm.msc, Certificate Export Wizard) and GUI workflows, with no mention of Linux or cross-platform alternatives. All examples and screenshots are Windows-centric, and there are no instructions for performing equivalent tasks on Linux or macOS systems.
Recommendations
- Add equivalent Linux instructions using common tools such as openssl for exporting and converting certificates.
- Include command-line examples for both Windows (e.g., PowerShell) and Linux (e.g., bash/openssl) to ensure parity.
- Mention and demonstrate how to locate and manage certificates on Linux systems, including file paths and permissions.
- Add a section or note clarifying support for non-Windows environments and linking to relevant cross-platform resources.
- Where possible, use neutral language and ordering (e.g., 'On Windows...' / 'On Linux...') rather than Windows-first phrasing.
Azure Docs
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 (Windows standard) as the default share type and refers to Windows tools (e.g., File Explorer) for managing permissions, while NFS (Linux standard) is mentioned secondarily. There are no concrete Linux command examples or instructions for mounting or managing shares from Linux clients, and no Linux-specific tooling or workflows are described.
Recommendations
- Provide explicit Linux examples for mounting NFS shares, including sample mount commands.
- Include instructions for managing permissions from Linux (e.g., using chmod/chown for NFS shares).
- Balance the order of presentation so that SMB and NFS are given equal prominence, or alternate which is presented first.
- Reference Linux tools (e.g., Nautilus, command-line utilities) alongside Windows tools like File Explorer.
- Add troubleshooting tips or notes relevant to Linux clients, such as SELinux considerations or NFS version compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-manage-access-power-connectivity-mode.md
...e-stack-edge-gpu-manage-access-power-connectivity-mode.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. All command-line examples are given exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. Device access via remote PowerShell is described in detail, but there is no reference to SSH or other Linux-native management methods. Windows-specific tools and technologies (e.g., BitLocker, PowerShell) are referenced without Linux equivalents or guidance for non-Windows users. The documentation assumes a Windows-centric environment and omits Linux workflows entirely.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using Azure CLI, Bash, or SSH) alongside PowerShell commands.
- Document how to access and manage the device from Linux or macOS systems, including remote access methods (such as SSH, if supported).
- If BitLocker is required, clarify its compatibility or provide guidance for Linux users on managing encrypted volumes.
- Mention cross-platform tools and interfaces (such as Azure CLI or REST APIs) where possible, and provide parity in instructions.
- Explicitly state any platform limitations or requirements, and offer alternative workflows for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-manage-storage-accounts.md
...online/azure-stack-edge-gpu-manage-storage-accounts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the primary or only CLI tool for managing local storage accounts, without mentioning or providing examples for Linux or cross-platform alternatives such as Azure CLI or Bash scripts. The instructions for configuring client connectivity and managing storage accounts are centered around PowerShell, which is traditionally associated with Windows environments. There are no Linux-specific examples or guidance, and Windows-centric tools are mentioned before any cross-platform options.
Recommendations
- Include Azure CLI (az) command examples alongside or instead of Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Provide Bash or shell script examples for Linux users where applicable.
- Explicitly mention that management tasks can be performed from Linux, macOS, or Windows, and provide platform-agnostic instructions.
- Where PowerShell is required, clarify that PowerShell Core is available on Linux and macOS, and provide installation guidance if needed.
- Review all references to tools and ensure Linux parity in both instructions and screenshots where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-modify-fpga-modules-gpu.md
...online/azure-stack-edge-gpu-modify-fpga-modules-gpu.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the networking section, where it references using the PowerShell interface to interact with the device and retrieve module information. The PowerShell method is mentioned before any Linux or cross-platform alternatives, and there is no mention of Linux-native tools or CLI commands for similar tasks. The overall documentation assumes familiarity with Windows-centric tools and patterns, with no explicit Linux command-line examples or instructions, despite recommending Linux VMs for IoT Edge deployment.
Recommendations
- Provide Linux-native command-line examples (e.g., using SSH and iotedge CLI) for querying module status and IP addresses.
- Mention cross-platform alternatives (such as Azure CLI, kubectl, or iotedge CLI) alongside or before PowerShell-based instructions.
- Ensure that all references to device management interfaces include both Windows (PowerShell) and Linux (Bash/SSH) options.
- Add explicit Linux usage patterns for common tasks, such as monitoring modules, retrieving logs, and troubleshooting.
- Review and update all sections to avoid assuming the user is operating from a Windows environment.
Azure Docs
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 page demonstrates a Windows bias by referencing Windows-specific tools (e.g., Windows Server Update Services), mentioning Windows update mechanisms before any cross-platform alternatives, and omitting explicit Linux/macOS instructions or examples for key steps such as network configuration, certificate management, and device access. There are no command-line examples or troubleshooting notes for Linux users, and the language assumes a Windows environment for several administrative tasks.
Recommendations
- Provide explicit instructions and examples for Linux and macOS users, especially for steps involving network configuration (e.g., setting static IPs), certificate generation, and device access.
- Mention cross-platform update mechanisms or clarify if WSUS is optional and provide alternatives for non-Windows environments.
- Include command-line examples using Bash or other common Linux shells alongside any PowerShell or Windows GUI instructions.
- Review all references to Windows tools and ensure Linux equivalents or workarounds are documented.
- Add troubleshooting notes for common issues encountered on Linux/macOS clients.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-remote-support-diagnostics-repair.md
...azure-stack-edge-gpu-remote-support-diagnostics-repair.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. All operational examples and remote support instructions are exclusively provided using PowerShell cmdlets, with no mention of Linux shells or tools. The documentation assumes the use of Windows-based management interfaces (PowerShell, Windows paths, Windows-specific cmdlets, and features like JEA). There are no examples or guidance for Linux-based management, nor is there any mention of cross-platform alternatives or parity.
Recommendations
- Explicitly state if Azure Stack Edge remote support is only available via Windows/PowerShell, or clarify Linux support status.
- If Linux management is supported, provide equivalent examples using Bash, SSH, or cross-platform PowerShell Core (pwsh), and document any differences.
- List any Linux-compatible tools or interfaces for remote diagnostics and remediation, or clearly state their absence.
- Where possible, use cross-platform terminology and avoid Windows-specific paths (e.g., use environment variables or note Linux equivalents).
- If only Windows is supported, add a note at the start of the documentation to inform Linux users of the limitation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-manage-certificates.md
...box-online/azure-stack-edge-gpu-manage-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All certificate import instructions are exclusively for Windows clients, using Windows UI and terminology. The only guidance for installing openssl is via Windows tools (Chocolatey and PowerShell), and all command-line examples are shown in PowerShell with Windows paths. There are no Linux or macOS examples or instructions for certificate management, import, or openssl installation, despite the cross-platform relevance of these tasks.
Recommendations
- Provide parallel instructions and screenshots for Linux and macOS clients, including certificate import steps using common tools (e.g., update-ca-certificates, certutil, or keychain access).
- Include openssl installation instructions for Linux (e.g., apt, yum, dnf) and macOS (e.g., Homebrew).
- Show command-line examples in a cross-platform way (e.g., using bash syntax and Linux/macOS file paths, not just PowerShell and Windows paths).
- Clarify in each section whether the steps are specific to Windows, and provide equivalent steps for other platforms.
- Ensure that references to certificate stores and file formats are explained in a platform-neutral way, or provide platform-specific details as needed.
Azure Docs
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 demonstrates a Windows bias primarily by referencing PowerShell-specific cmdlets (e.g., Set-HcsMacAddressPool) for device configuration, without providing equivalent Linux/CLI alternatives or guidance. There are no Linux shell or cross-platform command examples, and the only explicit tooling mentioned is Windows-centric. This may hinder Linux users or those operating in mixed environments.
Recommendations
- For every PowerShell cmdlet or Windows-specific tool mentioned (e.g., Set-HcsMacAddressPool), provide equivalent Linux shell commands or REST API instructions if available.
- Explicitly state whether configuration steps can be performed from Linux or Mac clients, and provide examples.
- When referencing command-line interfaces, clarify if they are available cross-platform or only on Windows, and offer alternatives where possible.
- Include Linux-specific troubleshooting and monitoring guidance alongside Windows/PowerShell instructions.
- Review all included content (from INCLUDES) to ensure Linux parity in examples and tool references.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot.md
...es/databox-online/azure-stack-edge-gpu-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as Windows PowerShell and Microsoft Windows Firewall), providing only Windows log file examples, and omitting any Linux or cross-platform equivalents. Instructions and examples are tailored to Windows environments, with no mention of Linux commands, tools, or log formats. The documentation also refers to Windows-centric patterns (e.g., Bitlocker, pfirewall.log) and does not address how to perform similar diagnostics or log collection on Linux-based Azure Stack Edge devices, if supported.
Recommendations
- Include equivalent instructions and examples for Linux-based Azure Stack Edge devices, if supported.
- Provide Linux command-line examples (e.g., using bash, journalctl, iptables logs) alongside PowerShell/Windows examples.
- Mention Linux log file locations and formats where relevant, such as /var/log/syslog or /var/log/messages.
- Clarify if certain features (e.g., Bitlocker, Windows Firewall) are Windows-only, and suggest Linux alternatives (e.g., LUKS/dm-crypt, iptables/ufw).
- Structure sections so that Windows and Linux instructions/examples are presented in parallel, or clearly indicate OS applicability.
- If Linux is not supported, state this explicitly to avoid confusion.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-iot-edge.md
...x-online/azure-stack-edge-gpu-troubleshoot-iot-edge.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 interfaces and workflows (e.g., 'Debug Kubernetes issues related to IoT Edge' via a PowerShell interface) without mentioning or providing equivalent Linux command-line or tool examples. There are no Linux-specific troubleshooting steps or references, and Windows/PowerShell tools are mentioned first and exclusively.
Recommendations
- Include Linux-based troubleshooting steps and examples alongside or before Windows/PowerShell instructions.
- Reference Linux command-line tools (such as bash, journalctl, systemctl) for managing and troubleshooting IoT Edge services.
- Provide parity in documentation by ensuring that all PowerShell or Windows-specific instructions have clear Linux equivalents.
- Clarify in each troubleshooting section whether the steps apply to both Windows and Linux, or provide separate sections for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-sharing.md
...rticles/databox-online/azure-stack-edge-gpu-sharing.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 exclusively referencing PowerShell for device access and GPU monitoring (e.g., 'connect to the PowerShell interface', 'Get-HcsNvidiaSmi' command), without providing equivalent Linux shell or cross-platform CLI instructions. No Linux or bash examples are given for GPU management, and Windows-specific tools and patterns are mentioned first and exclusively.
Recommendations
- Provide equivalent Linux/bash commands for GPU monitoring and management, such as using 'ssh' to connect and running 'nvidia-smi' directly.
- Include examples of editing deployment YAML files and environment variables from both Windows and Linux perspectives.
- Clarify whether the device supports Linux-based management interfaces, and if so, document their usage.
- Avoid assuming PowerShell as the default interface; mention both PowerShell and bash/shell alternatives where possible.
- Add a section or note for users managing Azure Stack Edge Pro GPU devices from Linux or macOS environments.