About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools and workflows before or instead of their Linux equivalents. Visual Studio Code and Visual Studio are mentioned as editors, with no explicit mention of Linux alternatives. The only extension referenced is the Azure Resource Manager Tools for VS Code, which is cross-platform but is presented in a way that assumes familiarity with Windows/VS Code workflows. In the 'identity' property, the only example link is for configuring managed identities on a Windows VM. There are no CLI or shell examples, and no explicit Linux or cross-platform editor guidance. In the multi-line strings section, Azure PowerShell is mentioned before Azure CLI, and there is no mention of Bash or Linux-specific considerations.
Recommendations:
- Include explicit references to Linux and macOS environments when discussing editors and tools (e.g., mention that VS Code is available on Linux and macOS, or suggest other editors like Vim, Emacs, or JetBrains IDEs).
- When referencing deployment guides or quickstarts, provide both Windows and Linux examples or links (e.g., for configuring managed identities, link to both Windows and Linux VM guides).
- In sections discussing deployment via CLI or PowerShell, present Azure CLI (which is cross-platform) examples first, or at least in parallel with PowerShell, and clarify that CLI commands work on Linux/macOS/Windows.
- Add notes or examples for common Linux shell environments (e.g., Bash) where relevant, especially when discussing file formats, comments, or multi-line strings.
- Review all tool and workflow mentions to ensure Linux parity, and avoid assuming a Windows-first development environment.
Create pull request