Reliability

178
Total Pages
159
Linux-Friendly Pages
19
Pages with Bias
10.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

71 issues found
Showing 51-71 of 71 flagged pages
Reliability Reliability in Azure Virtual Machine Scale Sets .../reliability/reliability-virtual-machine-scale-sets.md
Medium Priority View Details →
Scanned: 2026-01-10 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, portal, and ARM templates. PowerShell examples are given equal prominence to CLI, and the CLI examples are generic (not OS-specific). However, in the ARM template section, both Linux and Windows quickstart links are provided, but the example shown is for Linux only. There is a slight Windows bias in that PowerShell (a Windows-centric tool) is given a dedicated section and examples, and the PowerShell examples appear before ARM template examples. The documentation does not provide any Linux-specific shell (bash) or scripting examples, nor does it mention Linux tools or patterns. The CLI examples are cross-platform, but the lack of explicit Linux shell examples and the prominence of PowerShell may be perceived as a Windows bias.
Recommendations
  • Add explicit bash or Linux shell scripting examples for creating and managing scale sets.
  • Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and provide example shell invocations for Linux users.
  • Balance the PowerShell section by adding a section for bash scripting or Linux automation tools (e.g., Ansible, Terraform).
  • In ARM template examples, alternate between Linux and Windows examples, or provide both side-by-side.
  • Consider mentioning Linux-specific considerations or best practices where relevant.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/availability-zones-overview.md ...in/articles/reliability/availability-zones-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for interacting with the ARM API, but the PowerShell example is given equal prominence and detail as the CLI example. The mention of Azure PowerShell as a primary tool, alongside Azure CLI, may suggest a slight Windows bias, as PowerShell is traditionally associated with Windows environments. However, there are no examples or instructions that are exclusively Windows-specific, and Linux users are not excluded from following the guidance. No Windows-only tools or patterns are mentioned, and the CLI example is provided first, which is cross-platform.
Recommendations
  • Clarify that Azure PowerShell is available on Linux and macOS, not just Windows, to avoid reinforcing the Windows association.
  • Consider including Bash or shell script examples where appropriate, especially for tasks that could be performed outside of Azure CLI or PowerShell.
  • Explicitly mention cross-platform compatibility for all tools and commands, reassuring Linux users that they are fully supported.
  • If referencing PowerShell, note that it is open source and available on multiple platforms.
  • Continue to provide Azure CLI examples first, as it is natively cross-platform.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/asm-retirement.md ...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows some evidence of Windows bias. The migration link for 'Classic Virtual Network' specifically references PowerShell in its URL, which is a Windows-centric tool, and does not mention Linux CLI or Bash alternatives. Additionally, Windows support is listed before Linux distributions in the VM support links, and there is no explicit mention of Linux-native tooling or migration patterns in the main content. No Linux-specific examples or guidance are highlighted, and Windows tools (PowerShell) are referenced directly.
Recommendations
  • Include migration instructions and examples using Azure CLI and Bash scripts, which are cross-platform and preferred by many Linux users.
  • Ensure that Linux support links (Ubuntu, RedHat, SUSE) are listed before or alongside Windows, not after.
  • Explicitly mention Linux-native tools and patterns in migration guides, such as cloud-init, SSH, and Linux package management.
  • Provide parity in documentation for Linux and Windows, including troubleshooting and support resources.
  • Avoid using PowerShell-specific URLs or references as the default; offer alternatives for Linux users.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machine-scale-sets.md .../reliability/reliability-virtual-machine-scale-sets.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating and managing Virtual Machine Scale Sets with availability zones. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and detailed PowerShell examples are provided. The Resource Manager template section references both Linux and Windows, but the PowerShell examples are not explicitly marked as Windows-only, which may imply parity that does not exist for Linux users. There is a slight 'windows_first' bias in the ordering and presentation of PowerShell examples, and the lack of explicit Bash or Linux shell scripting examples may disadvantage Linux users.
Recommendations
  • Explicitly label PowerShell examples as Windows-specific and provide equivalent Bash or shell scripting examples for Linux users where applicable.
  • Ensure that Azure CLI examples include Linux-specific notes (e.g., SSH key generation, file permissions) where relevant.
  • In sections referencing Resource Manager templates, provide clear guidance and links for both Linux and Windows deployments, and ensure parity in example detail.
  • Consider adding a table or summary comparing Windows and Linux deployment options and tooling, to help users choose the best approach for their environment.
  • Review the ordering of example tabs to ensure Azure CLI (cross-platform) is presented before PowerShell (Windows-specific), and clarify tool applicability in introductory text.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/availability-zones-overview.md ...in/articles/reliability/availability-zones-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 interacting with the ARM API, but the PowerShell example is given equal prominence and detail as the CLI example. There is a subtle Windows bias in mentioning Azure PowerShell as a primary tool for resource management, which is more commonly used on Windows systems. The documentation refers to Azure PowerShell before mentioning its cross-platform capabilities or Linux alternatives, and does not provide explicit Linux shell (bash) or scripting examples beyond Azure CLI. No Linux-specific tools, patterns, or troubleshooting guidance are included.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS environments.
  • Provide bash shell scripting examples for Linux users alongside PowerShell examples.
  • Clarify that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
  • Consider including troubleshooting or usage notes relevant to Linux environments (e.g., authentication, environment variables).
  • Avoid implying PowerShell is the default or primary automation tool; present CLI and PowerShell as equal options, with context for platform suitability.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/asm-retirement.md ...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. The migration guidance for 'Classic Virtual Network' specifically links to a PowerShell-based migration guide, which is a Windows-centric tool. There is no explicit mention of Linux CLI or Bash alternatives in the main migration documentation links, and PowerShell is referenced before any cross-platform or Linux-native tooling. However, the support links for VM migration do include Linux distributions (Ubuntu, SUSE, RedHat) alongside Windows, indicating some effort toward parity.
Recommendations
  • Include migration instructions using Azure CLI (cross-platform) and Bash scripts alongside PowerShell examples.
  • Ensure that migration documentation for each resource provides both Windows and Linux command-line examples, with equal prominence.
  • Where PowerShell is referenced, clarify if the instructions are compatible with PowerShell Core on Linux/macOS, or provide alternative commands for Linux users.
  • Audit linked migration guides to verify that Linux users are not forced to use Windows-centric tools or patterns.
  • Add a section explicitly addressing Linux migration scenarios and tooling, to reassure non-Windows users.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machines.md ...n/articles/reliability/reliability-virtual-machines.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. In several sections, PowerShell (a Windows-centric tool) is listed before Azure CLI (which is cross-platform and often preferred by Linux users). For example, in the prerequisites for checking VM SKU availability, PowerShell is mentioned before Azure CLI. Similarly, in migration instructions, PowerShell is listed after CLI, but both are present. There are no sections where only Windows or PowerShell examples are given, and Linux-specific guidance is present where appropriate. However, the ordering and occasional emphasis on PowerShell can be perceived as a mild Windows-first bias.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
  • Where both PowerShell and Azure CLI are mentioned, clarify that both are fully supported and provide equal prominence.
  • Ensure that all command-line examples are provided for both Windows (PowerShell) and Linux (Azure CLI/Bash) where applicable.
  • Consider adding explicit Linux/Bash examples in addition to Azure CLI, especially for tasks commonly performed on Linux.
  • Review linked pages to ensure Linux parity is maintained in referenced documentation.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/asm-retirement.md ...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is generally neutral and high-level, but there is evidence of subtle Windows bias. The migration link for 'Classic Virtual Network' specifically points to a PowerShell-based migration guide, which is typically associated with Windows environments. There are no explicit Linux command-line (e.g., Bash, Azure CLI) examples or migration guides referenced, and PowerShell is mentioned in the URL for the migration guide. Additionally, in the support links for VM (classic), 'Windows' is listed before specific Linux distributions, suggesting a Windows-first ordering.
Recommendations
  • Wherever PowerShell-based migration guides are referenced, also provide links to Azure CLI or Bash-based guides for Linux users, if available.
  • Ensure that migration documentation for each resource includes both Windows and Linux command-line examples, or explicitly states if only one is supported.
  • In support tables or lists, alternate the ordering of Windows and Linux (or use alphabetical order) to avoid implicit prioritization.
  • Audit linked migration guides (e.g., for Classic Virtual Network) to ensure Linux users are not forced to use PowerShell and have clear, supported alternatives.
  • If PowerShell is required for certain migrations, clearly state this and explain any Linux workarounds or cross-platform options.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-container-apps.md ...ticles/reliability/reliability-azure-container-apps.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but it lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and sometimes gives PowerShell examples more detailed coverage (e.g., with variable assignments and object construction). There are no Linux-specific shell examples (such as Bash), and the PowerShell examples may not be as familiar or accessible to Linux users. The documentation does not mention or provide parity for Linux-native tools or patterns, and the use of PowerShell may be perceived as Windows-centric.
Recommendations
  • Ensure all command-line examples are provided in both Azure CLI (Bash/shell) and Azure PowerShell, but default to Azure CLI/Bash as the primary example since it is cross-platform.
  • Clearly indicate that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax for variable assignment and piping where appropriate.
  • If PowerShell is included, clarify that it is available cross-platform, or provide links to installation instructions for Linux/macOS.
  • Consider adding a section or note for Linux users, highlighting any differences or tips for running the commands in a Linux environment.
  • Avoid assuming the use of Windows tools or patterns unless they are required, and provide Linux-native alternatives where possible.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-dns.md ...docs/blob/main/articles/reliability/reliability-dns.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on Azure Portal and Azure CLI for DNS disaster recovery, without providing any Linux-specific or cross-platform command-line examples (e.g., Bash scripts, curl, dig, etc.). While Azure CLI is cross-platform, the absence of Linux-native tools or explicit Linux workflow guidance may disadvantage Linux users. There are no references to Windows-specific tools like PowerShell, but the examples and screenshots are Azure-centric, with no mention of Linux command-line utilities or integration patterns.
Recommendations
  • Include Linux-native command-line examples (e.g., using dig or nsupdate to verify DNS changes).
  • Provide sample Bash scripts for automating DNS failover using Azure CLI on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if relevant.
  • Add troubleshooting steps or verification commands using common Linux tools.
  • Where screenshots are used, consider including CLI output or terminal examples to supplement Azure Portal UI steps.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machines.md ...n/articles/reliability/reliability-virtual-machines.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing PowerShell/Windows methods before Linux/CLI equivalents in several places, and by sometimes referencing Windows-specific tooling (PowerShell) more prominently. However, Linux/CLI options are generally present, and there are dedicated Linux and Windows disaster recovery sections. No major Linux examples are missing, but ordering and emphasis slightly favor Windows.
Recommendations
  • When listing methods (e.g., checking VM SKU availability, migrating VMs), alternate the order so that Linux/CLI and Windows/PowerShell are given equal prominence, or list CLI first as it is cross-platform.
  • Ensure that all examples and links are provided for both Linux (CLI) and Windows (PowerShell) wherever possible.
  • Where possible, use Azure CLI as the default example since it is cross-platform, and mention PowerShell as an alternative.
  • In prerequisite and migration sections, avoid always listing PowerShell/Windows first; consider grouping by tool type or platform.
  • Continue to provide dedicated Linux and Windows guidance for OS-specific procedures, but ensure parity in depth and clarity.
GitHub Create Pull Request
Reliability What are Azure availability zones? ...in/articles/reliability/availability-zones-overview.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 querying zone mappings, but the PowerShell example is given equal prominence and detail as the CLI example. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can create a subtle Windows bias, especially since no explicit Linux/macOS shell examples (e.g., Bash/cURL) are provided. The documentation also references Azure PowerShell before mentioning its cross-platform capabilities, which may reinforce a Windows-first impression.
Recommendations
  • Add explicit Bash/cURL examples for Linux/macOS users to query the ARM API.
  • Clarify that Azure CLI and PowerShell are both cross-platform, and suggest installation guides for Linux/macOS.
  • Present CLI (Bash) examples before PowerShell, or group them together under 'Cross-platform' and 'Windows-specific' headings.
  • Mention that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
GitHub Create Pull Request
Reliability List of Azure regions ...re-docs/blob/main/articles/reliability/regions-list.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 lists both Azure CLI and Azure PowerShell as programmatic methods for retrieving region names, but PowerShell (a Windows-centric tool) is mentioned before REST API, and is given equal prominence to Azure CLI. No Linux/macOS-specific tools or shell examples are provided, and there is no explicit mention of platform parity or differences. However, Azure CLI is cross-platform and listed first, so the bias is minor.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Provide example commands for both Azure CLI (bash/zsh) and PowerShell, showing usage on different platforms.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if referencing PowerShell.
  • Consider listing Azure CLI examples before PowerShell, or grouping them by platform.
  • Add a note about platform compatibility for each tool.
GitHub Create Pull Request
Reliability Reliability Guides for Azure Services .../articles/reliability/overview-reliability-guidance.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is a high-level index of reliability guides for Azure services and does not provide platform-specific examples or instructions. However, there is one instance where a Windows-specific tool (Azure PowerShell) is mentioned in the context of deploying Azure Firewall with availability zones, without reference to Linux/macOS alternatives (such as Azure CLI or ARM templates). This is a minor instance of Windows bias.
Recommendations
  • Where specific deployment instructions are referenced (e.g., 'Deploy Azure Firewall with availability zones by using Azure PowerShell'), add links or notes for equivalent Linux/macOS-friendly tools such as Azure CLI or ARM templates.
  • Ensure that any future updates to this index include parity for Linux/macOS tools when referencing platform-specific guides.
  • Consider adding a general note at the top of the page indicating that most Azure management tasks can be performed using cross-platform tools (Azure CLI, REST API, ARM templates) and linking to their documentation.
GitHub Create Pull Request
Reliability High Availability (Reliability) in Azure Cosmos DB for NoSQL ...in/articles/reliability/reliability-cosmos-db-nosql.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references PowerShell, the Azure CLI, and the Azure portal as tools for managing failover and other operations. PowerShell is a Windows-centric tool, and it is consistently mentioned first in lists of management options. There are no explicit Linux/macOS-specific examples or tool recommendations, and no mention of Linux-native alternatives (e.g., Bash scripts, cross-platform SDK usage). However, Azure CLI is cross-platform, and the portal is web-based, so Linux/macOS users are not blocked from completing tasks.
Recommendations
  • List Azure CLI before PowerShell when presenting management options, as CLI is cross-platform.
  • Explicitly state that Azure CLI and Azure portal are fully supported on Linux/macOS.
  • Provide example commands for both PowerShell and Azure CLI, or link to CLI-specific documentation.
  • Mention that PowerShell Core is available cross-platform, if relevant, or clarify any Windows-only limitations.
  • Consider including Bash or other Linux-native scripting examples for automation tasks.
GitHub Create Pull Request
Reliability Azure Service Manager retirement ...-docs/blob/main/articles/reliability/asm-retirement.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through the use of PowerShell-focused migration guides (e.g., 'Migrate Classic Virtual Network to ARM' links to a PowerShell-based guide) and the presence of Windows-specific support links. While Linux distributions (RedHat, Ubuntu, SUSE) are referenced in support options for VM migration, there is an overall tendency to reference Windows tooling (PowerShell) and examples first, with limited mention of Linux-native tools or CLI workflows.
Recommendations
  • Ensure migration guides include both PowerShell (Windows) and Azure CLI (cross-platform) instructions, with clear parity for Linux/macOS users.
  • Where PowerShell is referenced, provide equivalent Bash/Azure CLI examples and highlight their use for Linux/macOS.
  • Review linked migration documentation to confirm Linux/macOS users can complete all steps without requiring Windows-only tools.
  • Consider listing Linux/macOS options before or alongside Windows options to avoid implicit prioritization.
GitHub Create Pull Request
Reliability Reliability Guides for Azure Services .../articles/reliability/overview-reliability-guidance.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is a service index listing reliability guides for Azure services. While most entries are neutral, one entry ('Azure Web Application Firewall') specifically references deploying Azure Firewall with availability zones by using Azure PowerShell, a Windows-centric tool, without mentioning CLI or Bash alternatives. No Linux/macOS examples or tools are referenced, and Windows tooling is mentioned exclusively in this instance.
Recommendations
  • For entries referencing Windows-specific tools (e.g., PowerShell), add equivalent instructions or links for Azure CLI and Bash to ensure Linux/macOS users have clear guidance.
  • Review all referenced reliability guides to ensure they include cross-platform deployment examples and tooling.
  • Where possible, mention platform-agnostic tools (such as Azure CLI) before platform-specific ones like PowerShell.
GitHub Create Pull Request
Reliability What are Azure availability zones? ...in/articles/reliability/availability-zones-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for interacting with the ARM API, but lists the CLI example first and does not show any Linux-specific shell commands or considerations. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and no explicit Linux/macOS shell (e.g., Bash) examples or notes are given. There is no mention of Windows-only tools, but the absence of Linux/macOS-specific guidance or troubleshooting tips may create mild friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and works on Linux/macOS as well as Windows.
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks like parsing JSON output.
  • Include notes or links about installing Azure CLI and PowerShell on Linux/macOS, or troubleshooting common platform-specific issues.
  • Where PowerShell is mentioned, clarify that it is available cross-platform, or provide alternative command-line examples for Bash users.
GitHub Create Pull Request
Reliability Reliability in Azure Virtual Machine Scale Sets .../reliability/reliability-virtual-machine-scale-sets.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, Azure Portal, and ARM templates. PowerShell examples are given equal prominence as CLI, and Windows-specific tools (PowerShell) are featured in their own tab. The ARM template section references both Linux and Windows, but the PowerShell section is inherently Windows-centric. The ordering of examples (Portal, CLI, PowerShell, Resource Manager) puts Windows tools before explicit Linux references, and no Linux shell-specific guidance is provided outside of the CLI. There are no Linux/macOS-specific troubleshooting tips or parity notes.
Recommendations
  • Add explicit Bash/Linux shell examples where relevant, especially for scripting tasks.
  • Clarify that Azure CLI works cross-platform and highlight usage on Linux/macOS.
  • Add parity notes for PowerShell, indicating that it is primarily a Windows tool, and suggest Azure CLI for Linux/macOS users.
  • Consider reordering example tabs to put cross-platform tools (CLI, ARM templates) before Windows-specific tools (PowerShell).
  • Provide troubleshooting or usage notes for Linux/macOS users where differences may exist.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-app-gateway-v2.md ...ob/main/articles/reliability/migrate-app-gateway-v2.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes migration steps using the Azure portal UI and does not provide any command-line examples. There is no mention of Windows-specific tools, but there is also a lack of parity for Linux users, as no Azure CLI, PowerShell, or scripting examples are provided. This omission can disadvantage users who prefer or require command-line automation, particularly on Linux systems.
Recommendations
  • Add Azure CLI examples for each migration step, as the CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are provided, ensure Azure CLI equivalents are also included and presented first or side-by-side.
  • Explicitly mention that the steps can be performed using the Azure CLI or ARM templates, and link to relevant documentation.
  • Include sample scripts or commands for common tasks (e.g., creating/deleting Application Gateway, updating DNS) using cross-platform tools.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/availability-zones-overview.md ...in/articles/reliability/availability-zones-overview.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying availability zone mappings, but the PowerShell example is presented immediately after the CLI example, and both are given equal prominence. There are no Linux-specific tools or shell (e.g., Bash) examples, but the Azure CLI is cross-platform. There is a slight 'windows_first' bias in that PowerShell is featured as the only alternative to the CLI, and no explicit mention is made of Linux-native scripting or tools.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Consider providing a Bash shell example (using curl/jq) for Linux users to query the REST API, in addition to the Azure CLI and PowerShell examples.
  • Clarify in the documentation that PowerShell examples are primarily for Windows users, while CLI and Bash are suitable for Linux.
  • Where possible, provide command-line examples in the order: Azure CLI (cross-platform), Bash (Linux/macOS), then PowerShell (Windows), to avoid implicit Windows-first ordering.
GitHub Create Pull Request
← Previous Page 3 of 3 Next →