Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in all command examples, and Windows file paths (e.g., c:\certificates) are used in both PowerShell and Azure CLI examples, even when the CLI is cross-platform. There are no explicit Linux shell (bash) examples, and the use of Windows-specific tools and patterns (e.g., ConvertTo-SecureString, Set-AzKeyVaultAccessPolicy) is prevalent. While Ubuntu templates are referenced and the Azure CLI is shown, Linux/macOS users may encounter friction due to the lack of native shell examples and persistent Windows-centric defaults.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI (cross-platform) first.
- Provide native bash/Linux shell examples for all CLI commands, using Linux-style paths (e.g., /home/user/certificates) and environment variable syntax.
- Explicitly note when a command or tool is Windows-only, and provide Linux/macOS equivalents where possible.
- Use OS-agnostic language and file paths in documentation, or provide both Windows and Linux/macOS path examples.
- Highlight any differences in prerequisites or setup steps for Linux/macOS users.
Create Pull Request