Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 2176-2185 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-routing.md
...ob/main//articles/expressroute/expressroute-routing.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on network concepts and requirements. However, there is a subtle Windows bias in the section on default route advertisement, where only Windows VM license activation is mentioned as being affected, and the workaround links specifically to a Windows-centric solution. No Linux or cross-platform VM activation issues or solutions are discussed.
Recommendations
- When discussing the impact of default route advertisement on VM license activation, mention whether Linux VMs (and their activation or registration mechanisms) are also affected, or explicitly state if this is a Windows-only concern.
- If Linux VMs have similar requirements or workarounds, provide equivalent guidance or links for Linux users.
- Where possible, use neutral language (e.g., 'VM license activation' instead of 'Windows license activation') unless the issue is truly exclusive to Windows.
- Consider including a brief note or table summarizing the impact of routing changes on both Windows and Linux VM activation/registration processes.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/deploy-aks-cluster.md
...ob/main//articles/extended-zones/deploy-aks-cluster.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all steps and does not provide any command-line examples. There are no Windows-specific tools or PowerShell commands, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users or those who prefer automation and scripting.
Recommendations
- Add equivalent Azure CLI instructions for all major steps, including AKS cluster creation and resource cleanup.
- Ensure CLI examples are provided in a cross-platform manner (e.g., Bash shell), and clarify that the Azure CLI works on Windows, Linux, and macOS.
- If PowerShell examples are ever added, always provide Bash/Azure CLI equivalents and present them in parallel.
- Explicitly mention that all steps can be performed via CLI for users who prefer automation or non-GUI workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/configure-ddos.md
...blob/main//articles/firewall-manager/configure-ddos.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (GUI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users or those who prefer or require automation and scripting.
Recommendations
- Add equivalent Azure CLI command-line examples for each configuration step, ensuring they are platform-agnostic and runnable on Linux, macOS, and Windows.
- Explicitly mention that all steps can be performed using Azure CLI or PowerShell, and provide links to relevant documentation.
- Where possible, provide Bash script snippets for automation to support Linux users.
- Ensure that any screenshots or UI references are supplemented with text-based alternatives for accessibility and cross-platform parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/quick-create-ipgroup-terraform.md
...n//articles/firewall/quick-create-ipgroup-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists the creation of a Windows VM and its password before mentioning the Linux VM in the checklist of resources to be created. However, the rest of the documentation, including code samples and CLI instructions, is platform-neutral or uses cross-platform tools (Terraform, Azure CLI). There are no PowerShell-specific examples, nor are Windows tools or patterns emphasized elsewhere.
Recommendations
- List Linux and Windows VM creation steps together or mention Linux first to avoid the perception of Windows preference.
- Ensure that any example referencing VM creation (such as password generation) is balanced for both Windows and Linux VMs.
- If showing VM-specific configuration, provide parallel examples for both Windows and Linux, or clarify that both are supported.
- Continue to use cross-platform tools (Terraform, Azure CLI) and avoid introducing Windows-only instructions unless absolutely necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/front-door-wildcard-domain.md
...main//articles/frontdoor/front-door-wildcard-domain.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation references using PowerShell and Azure CLI for configuring wildcard domains but does not provide any explicit command-line examples for either Windows (PowerShell) or Linux (Bash/CLI). However, the mention of PowerShell alongside Azure CLI in the note about configuring wildcard domains with Azure DNS could suggest a slight bias if only Windows-centric tooling or ordering is used. There are no explicit Windows-only tools, examples, or patterns, but the lack of Linux/Bash examples and the mention of PowerShell without a corresponding Bash example may be seen as a minor bias.
Recommendations
- When mentioning PowerShell, also explicitly mention Bash or shell scripting for Linux users, especially when referencing Azure CLI, which is cross-platform.
- Provide example commands for both PowerShell (Windows) and Bash (Linux/macOS) when showing how to configure wildcard domains using Azure CLI.
- Ensure that documentation does not imply that PowerShell is the primary or preferred method by always pairing it with Azure CLI and Bash examples where possible.
- Consider adding a table or section that shows equivalent commands for Windows (PowerShell), Linux (Bash), and macOS to improve parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/end-to-end-tls.md
...e-docs/blob/main//articles/frontdoor/end-to-end-tls.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation contains a subtle Windows bias in the section discussing supported cipher suites. It specifically recommends cipher suite configurations for Windows 10 and later, and discusses compatibility with older Windows versions (Windows 8.1, 8, and 7), without mentioning Linux or macOS compatibility or providing guidance for those platforms. There are no command-line examples, but the only OS-specific advice is Windows-centric.
Recommendations
- Include information about cipher suite compatibility and recommendations for popular Linux distributions and macOS, not just Windows.
- If mentioning OS-specific compatibility, provide parity by listing or linking to resources for verifying or configuring TLS cipher suites on Linux and macOS.
- Add a note or section on how to check or update supported cipher suites on Linux servers (e.g., using OpenSSL or relevant configuration files), to ensure cross-platform guidance.
- Avoid phrasing that implies Windows is the default or primary platform for clients; instead, use inclusive language that addresses all major operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/integrate-storage-account.md
.../main//articles/frontdoor/integrate-storage-account.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, the absence of CLI examples is a missed opportunity for Linux parity, as many Linux users prefer or require command-line instructions. There is no explicit Windows bias in terms of tools or order, but the lack of CLI coverage can be seen as an implicit bias toward GUI-centric workflows, which are more familiar to Windows users.
Recommendations
- Add Azure CLI examples for all major steps (creating storage account, configuring Front Door, purging cache, etc.), as Azure CLI is cross-platform and widely used on Linux.
- Where possible, provide both Portal (GUI) and CLI instructions side by side, making it clear that users can choose their preferred method.
- Explicitly mention that all steps can be performed via Azure CLI or PowerShell, and link to relevant documentation for those workflows.
- Ensure that any references to command-line tools or scripts include both Bash (Linux/macOS) and PowerShell (Windows) examples if scripting is discussed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/includes/policy/azure-policy.md
...n//articles/governance/includes/policy/azure-policy.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each scenario, but PowerShell is a Windows-centric tool, and no explicit Linux shell (e.g., Bash) or cross-platform scripting examples are included. However, the Azure CLI commands shown are cross-platform and suitable for Linux, macOS, and Windows. There is no evidence of 'windows_first' ordering, exclusive mention of Windows tools, or missing Linux examples, since Azure CLI is present throughout.
Recommendations
- Explicitly state that Azure CLI examples are cross-platform and suitable for Linux, macOS, and Windows.
- Consider adding Bash shell script examples for common automation scenarios to further demonstrate Linux parity.
- Clarify in the PowerShell sections that PowerShell Core is available cross-platform, or provide guidance for Linux users if there are any differences.
- If relevant, mention any Linux-specific considerations or troubleshooting tips for running these queries.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/attestation-structure.md
...es/governance/policy/concepts/attestation-structure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions PowerShell before Azure CLI when listing supported tools for managing attestations, which may indicate a subtle Windows-first bias. However, both PowerShell and Azure CLI are cross-platform, and no examples are given for either tool. There are no explicit Windows-only tools or patterns, nor are Linux-specific tools or examples missing, as none are provided for any OS.
Recommendations
- List Azure CLI before PowerShell or mention both in a neutral order (e.g., alphabetically) to avoid perceived Windows-first bias.
- Provide example commands for both Azure CLI and PowerShell to ensure parity and clarity for users on all platforms.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and that the REST API can be used from any OS.
- If possible, include a note or example for using the REST API with common Linux tools (e.g., curl) to further demonstrate platform neutrality.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/definition-structure-basics.md
...ernance/policy/concepts/definition-structure-basics.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally avoids platform-specific bias, but in the section discussing the 'mode' property, it mentions Azure PowerShell before Azure CLI and describes default behaviors for both. This ordering and mention of PowerShell first is a subtle form of 'windows_first' bias. There are no explicit PowerShell-heavy examples, exclusive use of Windows tools, or missing Linux examples, but the ordering could suggest a preference for Windows-centric tooling.
Recommendations
- When mentioning both Azure PowerShell and Azure CLI, alternate the order in which they are presented or mention them together (e.g., 'Azure CLI or Azure PowerShell') to avoid implying a preference.
- Wherever possible, provide command-line examples for both Azure CLI and Azure PowerShell, or clarify that both tools are cross-platform.
- Explicitly state that both Azure CLI and Azure PowerShell are available on Windows, Linux, and macOS to reinforce cross-platform parity.
- Review other related documentation to ensure that Linux users are equally represented in examples and tool references.