27
Total Pages
24
Linux-Friendly Pages
3
Pages with Bias
11.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (4)

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. The PowerShell examples are prominent and include references to Windows file paths (e.g., D:\testFiles\textfile.csv) and Windows-centric tooling. There is no mention of Linux-specific tools, shell environments, or file path conventions. PowerShell is presented as a primary automation method, and the PowerShell tab includes instructions for running commands locally or in Azure Cloud Shell, but does not address Bash or Linux-native scripting. The CLI examples are cross-platform, but the PowerShell content and file path examples show a Windows bias.
Recommendations:
  • Add explicit Bash examples alongside PowerShell, especially for automation and scripting tasks.
  • When referencing file paths, use cross-platform examples or provide both Windows (e.g., D:\testFiles\textfile.csv) and Linux (e.g., /home/user/testFiles/textfile.csv) path formats.
  • Mention that Azure CLI commands can be run in Bash on Linux/macOS, and provide guidance for those environments.
  • Clarify that PowerShell Core is cross-platform, but provide Bash alternatives for users who prefer native Linux tools.
  • Avoid referring to Windows-specific folders or drive letters without Linux equivalents.
  • Include links to Linux-specific quickstarts or guides where available.

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides only Azure PowerShell examples for resource cleanup, with no mention of equivalent commands for Linux users (such as Azure CLI or Bash). The use of PowerShell-specific syntax and the lack of cross-platform command options indicate a Windows bias. There is also no reference to Linux or macOS tooling or workflows.
Recommendations:
  • Include Azure CLI (az) command examples for all resource management steps, especially for cleanup, alongside PowerShell.
  • Explicitly mention that the steps can be performed on any OS, and provide Bash or shell script equivalents where relevant.
  • Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
  • Where PowerShell is used, clarify that Azure CLI is also supported and link to relevant CLI documentation.

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell, with significant emphasis on PowerShell and Windows-centric tooling. PowerShell examples are detailed and include references to Windows file paths (e.g., D:\testFiles), and the PowerShell section suggests running commands locally or in Azure Cloud Shell. There is no mention of Linux-specific shell usage, nor are there any Bash or Linux-native command examples. The documentation assumes familiarity with Windows conventions and tools, and does not provide parity for Linux users.
Recommendations:
  • Add explicit Bash examples alongside PowerShell, especially for common tasks like uploading files to Azure Storage.
  • Avoid using Windows-specific file paths (e.g., D:\testFiles) in examples; provide cross-platform alternatives or note Linux equivalents (e.g., /home/user/testFiles).
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands in Bash syntax where appropriate.
  • Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both environments.
  • Where PowerShell is referenced, include a note or section for Linux users on how to install and use PowerShell Core if needed, or suggest equivalent Bash commands.
  • Ensure that documentation does not assume a Windows environment by default, and structure examples so that Linux and Windows users are equally supported.

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation provides extensive PowerShell examples, including file paths and commands that are specific to Windows environments (e.g., D:\testFiles), and references to PowerShell as a primary automation tool. While Azure CLI examples are present (which are cross-platform), the PowerShell sections are more detailed, and there are no explicit Linux shell (bash) or native Linux file system examples. The documentation also references Windows-style file paths and omits Linux-specific guidance for file uploads or scripting, potentially making it less approachable for Linux users.
Recommendations:
  • Add explicit bash/Linux shell examples alongside PowerShell, especially for file operations (e.g., uploading files to Azure Storage using az CLI and Linux file paths like /home/user/testFiles/textfile.csv).
  • Avoid using Windows-specific file paths (e.g., D:\testFiles) in generic examples; provide both Windows and Linux path variants.
  • Clarify that PowerShell commands can be run cross-platform (e.g., in Azure Cloud Shell), but also provide equivalent bash/CLI workflows for Linux users.
  • Ensure that all automation and scripting examples are available in both PowerShell and bash/CLI formats, with equal detail and explanation.
  • Mention Linux tools (e.g., azcopy, curl, or bash scripting) where appropriate, not just Windows-centric tools.