8
Total Pages
7
Linux-Friendly Pages
1
Pages with Bias
12.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (2)

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. It exclusively references connecting to the Azure Stack Edge device via Windows PowerShell, both in the prerequisites and in the device registration steps. There are no examples or instructions for Linux or cross-platform users, and only Windows tools and workflows are mentioned.
Recommendations:
  • Provide equivalent instructions for connecting to Azure Stack Edge from Linux and macOS clients, including supported shells or tools (e.g., Azure CLI, SSH, or PowerShell Core on Linux).
  • Include Linux/macOS command examples alongside PowerShell, or clarify if only Windows is supported and why.
  • Mention any platform requirements or limitations explicitly in the prerequisites section.
  • If possible, offer a cross-platform registration method (such as via Azure CLI or REST API) and document it.
  • Ensure screenshots and walkthroughs are not exclusively Windows-centric, or supplement them with Linux/macOS equivalents.

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. It exclusively references connecting to the Azure Stack Edge device via Windows PowerShell, both in the prerequisites and in the registration steps. There are no instructions or examples for Linux or cross-platform users, and only Windows tools and patterns are mentioned. The documentation assumes the user is operating from a Windows environment, with no mention of alternatives for Linux or macOS.
Recommendations:
  • Provide equivalent instructions for connecting to Azure Stack Edge from Linux and macOS clients, including supported shells (e.g., Bash, Azure CLI).
  • Include Linux/macOS command-line examples alongside PowerShell, or clarify if cross-platform support is not available.
  • If only Windows is supported, explicitly state this limitation early in the documentation.
  • Reference cross-platform tools (such as Azure CLI or REST API) where possible, and provide examples for those.
  • Review all prerequisite and procedural steps to ensure parity for non-Windows users, or document any platform-specific requirements.