89
Total Pages
84
Linux-Friendly Pages
5
Pages with Bias
5.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

8 issues found
Showing 1-8 of 8 flagged pages
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for 'Standby pools for Azure Container Instances' shows a moderate Windows bias. The provider registration step exclusively uses Azure PowerShell, with no Azure CLI or REST example. In the 'Availability zones' section, PowerShell is presented before CLI and REST, and both CLI and PowerShell examples are given, but the initial registration step is PowerShell-only. There are no Linux-specific tools or patterns mentioned, but the ordering and example selection favor Windows/PowerShell users.
Recommendations
  • Add Azure CLI and REST examples for provider registration, not just PowerShell.
  • Ensure CLI examples are presented before or alongside PowerShell examples in all sections.
  • Explicitly mention that all commands (PowerShell, CLI, REST) can be run from Linux/macOS environments, and provide guidance for non-Windows users where relevant.
  • Consider including bash script snippets or notes for Linux users where appropriate.
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides step-by-step instructions for configuring RBAC permissions using the Azure portal, which is a graphical interface equally accessible from Windows, Linux, and macOS. However, when mentioning SDKs for checking pool health via the Runtime View API, 'PowerShell' is listed before 'CLI', which may subtly prioritize Windows tools. No explicit PowerShell-only commands or Windows-specific tools are used, and all examples (REST API, Kusto query) are cross-platform.
Recommendations
  • When referencing SDKs, mention Azure CLI before PowerShell or list both equally to avoid subtle Windows prioritization.
  • Add explicit Azure CLI command examples alongside REST API calls for checking pool health, as CLI is widely used on Linux/macOS.
  • Consider including links or brief instructions for role assignment using Azure CLI or ARM templates, not just the portal.
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily references the Azure portal for role assignment and troubleshooting, which is a cross-platform web interface. However, when mentioning SDKs for interacting with the Runtime View API, 'PowerShell' is listed before 'CLI', subtly prioritizing Windows tooling. No Linux/macOS-specific examples or tools (such as Azure CLI or Bash scripts) are provided for role assignment or API interaction, and PowerShell is mentioned before CLI in the troubleshooting section.
Recommendations
  • Provide Azure CLI examples for role assignment and API interaction, as CLI is cross-platform and widely used on Linux/macOS.
  • When mentioning SDKs or tools, list Azure CLI before PowerShell or equally, to avoid subtle Windows-first bias.
  • Include Bash or shell script examples where appropriate, especially for API calls.
  • Explicitly note that all steps can be performed on Linux/macOS using Azure CLI or REST API tools.
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure Portal UI instructions for role assignment, which are platform-neutral but often associated with Windows environments. There is a brief mention of PowerShell and CLI in the context of querying the Runtime View API, but no explicit Linux/macOS command-line examples are provided. The documentation does not exclusively reference Windows tools, but it does not offer parity for Linux/macOS users (e.g., Azure CLI commands for role assignment).
Recommendations
  • Add Azure CLI examples for role assignment alongside portal instructions, as CLI is cross-platform and widely used on Linux/macOS.
  • Provide explicit Azure CLI or REST API examples for querying the Runtime View API, rather than referencing PowerShell or CLI generically.
  • Clarify that all instructions are applicable regardless of OS, and highlight cross-platform tools where possible.
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses the Azure portal for role assignment instructions and mentions PowerShell/CLI only briefly and generically. There are no explicit Windows-only tools or PowerShell-heavy examples, but the portal-centric workflow is often associated with Windows users, and there is no parity for Linux/macOS command-line instructions (e.g., Azure CLI or Bash examples). The troubleshooting section references querying Log Analytics via the portal, and REST API usage is shown, but no CLI or Bash examples are provided.
Recommendations
  • Add Azure CLI examples for role assignment and troubleshooting steps, including querying Log Analytics and checking the Runtime View API.
  • Provide Bash or cross-platform command-line instructions alongside portal workflows.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or REST API, and link to relevant CLI documentation.
  • Where REST API is referenced, show how to use curl or az rest for cross-platform access.
Container Instances Quickstart - create a container instance - Bicep ...iner-instances/container-instances-quickstart-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, management, and cleanup steps. However, PowerShell examples are given equal prominence and are presented immediately alongside CLI examples, which may create a slight Windows-first impression. There are no Linux/macOS-specific shell examples (e.g., Bash), but the use of Azure CLI is cross-platform and sufficient for non-Windows users. No Windows-only tools or patterns are mentioned, and the documentation does not omit Linux/macOS equivalents.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
  • Consider listing Azure CLI examples first, as CLI is the default for cross-platform scenarios.
  • Optionally, add a note that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Ensure that screenshots or UI references (if any) do not assume Windows environments.
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is given a dedicated tab and example, which is primarily a Windows tool. The PowerShell example appears before the REST API example, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor any explicit Linux/macOS instructions. However, the Azure CLI example is cross-platform and shown first, mitigating the bias somewhat.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider adding a Bash shell example or explicitly stating that the CLI commands work on Linux/macOS.
  • If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash examples.
  • Ensure that examples and instructions do not imply PowerShell is required unless there is a Windows-only feature.
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is given a dedicated example tab, and is listed before REST API. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no Linux/macOS-specific shell examples (such as Bash/cURL for REST) are provided. The ordering of examples (CLI, then PowerShell, then REST) may subtly prioritize Windows users, and the lack of explicit Linux/macOS shell examples creates minor friction for non-Windows users.
Recommendations
  • Add a Bash/cURL example for querying the REST API, demonstrating how Linux/macOS users can retrieve the health state.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Consider listing REST API and CLI examples before PowerShell, or grouping all examples equally to avoid implicit prioritization.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if relevant.