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
⚠️
powershell_heavy
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows tools and patterns, such as Visual Studio and Windows-specific paths, and by providing command-line examples primarily in Windows formats (cmd, PowerShell). There is a lack of explicit Linux/macOS examples or parity in tool installation, file paths, and command usage. Linux equivalents are either omitted or not given equal prominence, which may hinder cross-platform developers.
Recommendations:
- Provide Linux/macOS equivalents for all command-line instructions, including bash/zsh examples alongside cmd and PowerShell.
- Include file path examples using both Windows (\) and Unix (/) separators where relevant.
- When referencing tools like Visual Studio, also mention and provide parity for cross-platform alternatives such as Visual Studio Code and the .NET CLI.
- For installation and usage of Azure Functions Core Tools, explicitly document Linux/macOS installation steps and note any differences in behavior or file locations.
- Avoid using Windows-specific environment variable syntax (e.g., %USERPROFILE%) without also showing the Unix equivalent (e.g., $HOME).
- Ensure that all code and configuration examples (such as ReadyToRun <RuntimeIdentifier>) include both Windows and Linux/macOS targets (e.g., win-x86, linux-x64, osx-x64).
- When showing package installation commands, always provide bash (dotnet CLI) and PowerShell examples together, not just Windows-centric ones.
- Audit all references to Windows-only tools or extensions and provide guidance for Linux/macOS users where possible.
Create pull request