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:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation demonstrates a moderate Windows bias, primarily through the use of PowerShell commands and references to Windows-centric tools (such as AzPowershell and Azure PowerShell) in both GitHub Actions and Azure Pipelines examples. While the CI runners are set to 'ubuntu-latest' (Linux), the scripts and authentication steps often rely on PowerShell or Windows-specific patterns, and there is a lack of explicit Linux shell (bash/sh) alternatives. Additionally, Windows tools and patterns are mentioned before or instead of their Linux equivalents, and some examples (such as dotnet CLI usage) are shown only in PowerShell or C# contexts, with no explicit Linux shell or cross-platform alternatives.
Recommendations:
- Provide equivalent bash/sh shell commands alongside PowerShell examples, especially for authentication and setup steps.
- When referencing Azure CLI or PowerShell, clarify cross-platform compatibility and provide both Windows and Linux command variants where applicable.
- Avoid using Windows-centric terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; instead, present both PowerShell and bash options, or use platform-agnostic tools where possible.
- Explicitly state that the examples work on both Windows and Linux runners, or provide separate tabs for each OS where commands differ.
- For .NET/NUnit examples, show both Windows and Linux command-line invocations (e.g., dotnet CLI in bash and PowerShell).
- Ensure that all code snippets and workflow steps are tested and documented for both Windows and Linux environments.
Create pull request