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 1-25 of 71 flagged pages
Reliability Migrate an Azure Service Fabric cluster to availability zone support ...ob/main/articles/reliability/migrate-service-fabric.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. Powershell commands are used exclusively for migration steps, with no equivalent Bash, Azure CLI, or Linux-native examples. Windows-centric patterns (e.g., D:\SvcFab paths, certificate store references) are present in code snippets and explanations. Although a sample template for Ubuntu is linked, all step-by-step instructions and code samples use Windows tools and syntax, and there is no guidance for Linux users on how to perform the migration using their native tools.
Recommendations
  • Add equivalent migration instructions using Azure CLI and/or Bash scripts for Linux users.
  • Provide examples of Linux file paths and certificate handling in code snippets.
  • Include explicit guidance for Linux environments alongside Windows/Powershell instructions.
  • Ensure that references to sample templates for Linux (e.g., Ubuntu) are accompanied by step-by-step instructions using Linux tools.
  • Where Powershell is used, offer parallel examples using Azure CLI or REST API calls.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides only PowerShell examples for agent assignment and references Windows-centric tools (PowerShell, Hybrid Compute), with no equivalent Linux CLI or Bash examples. There is no mention of Linux-specific agent deployment or management workflows, nor are cross-platform alternatives presented for key steps.
Recommendations
  • Include Azure CLI and/or Bash examples alongside PowerShell for all resource management steps.
  • Explicitly mention Linux support for agent deployment and management, including any OS-specific considerations.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows tools like PowerShell.
  • Clarify whether Hybrid Compute and agent registration workflows are supported on Linux, and provide Linux-specific instructions if so.
  • Add a section or callout for Linux users, summarizing parity and differences in disaster recovery and agent management.
GitHub Create Pull Request
Reliability Reliability in Azure Firewall ...blob/main/articles/reliability/reliability-firewall.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. When discussing configuration tooling, Windows-centric tools like Azure PowerShell are mentioned first and most prominently, with Azure CLI (cross-platform) listed second, and no explicit Linux-specific examples or guidance. References to deployment guides and examples link to PowerShell-based instructions, with no parallel Linux/bash examples provided. There is no mention of Linux shell scripting, nor are there examples using bash or Linux-native tools.
Recommendations
  • Provide explicit bash/Azure CLI examples for all configuration steps, especially those currently referencing PowerShell.
  • Ensure that cross-platform tools (Azure CLI, Terraform, Bicep) are mentioned before or alongside Windows-specific tools like PowerShell.
  • Add links to Linux-focused deployment guides or tutorials where available.
  • Clarify that all configuration steps can be performed on Linux, macOS, and Windows, and note any platform-specific caveats.
  • Where examples are given (e.g., in referenced deployment guides), ensure parity between PowerShell and bash/CLI instructions.
GitHub Create Pull Request
Reliability High Availability (Reliability) in Azure Cosmos DB for NoSQL ...in/articles/reliability/reliability-cosmos-db-nosql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias primarily through repeated references to PowerShell as a tool for managing failover and configuration tasks, often listing it before or alongside Azure CLI and Azure Portal. There are no explicit Linux-specific examples or mentions of Linux-native tools or shell commands. The documentation assumes familiarity with PowerShell and does not provide parity for Linux users, such as Bash or shell script equivalents, nor does it clarify cross-platform usage for CLI commands.
Recommendations
  • Provide explicit Bash/shell examples for all CLI operations, especially for failover and region management tasks.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, and provide sample commands in Bash syntax.
  • Avoid listing PowerShell before Azure CLI or portal unless there is a specific reason; consider grouping tools by platform or listing CLI first for parity.
  • Mention Linux and macOS compatibility wherever management tools are discussed, and link to installation guides for those platforms.
  • Add a note or section on cross-platform management, highlighting how Linux users can perform all documented operations without PowerShell.
GitHub Create Pull Request
Reliability Reliability in Azure Virtual Machines ...n/articles/reliability/reliability-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell) and examples are mentioned explicitly and sometimes before Linux equivalents. For instance, the section on creating VMs in availability zones lists the Azure portal, Azure CLI (Linux), and Azure PowerShell (Windows), but the PowerShell/Windows path is called out separately. Additionally, SQL Server (a Windows-centric workload) is highlighted as an example for multi-zone deployments, while Linux workloads or open-source equivalents are not mentioned. There are references to Windows-specific documentation paths, and Linux examples are less visible or not equally emphasized.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and in parallel (e.g., always provide both Azure CLI and PowerShell commands, and clarify which is for Linux and which for Windows).
  • Include examples and references for popular Linux workloads (e.g., MySQL, PostgreSQL, Apache) in sections discussing application-level reliability and multi-zone deployments.
  • Avoid listing Windows/PowerShell tools before Linux/CLI equivalents; alternate the order or present them together.
  • Add explicit links to Linux documentation when Windows-specific links are present (e.g., for SQL Server, also mention guides for MySQL/PostgreSQL on Azure VMs).
  • Review all examples and ensure that Linux users can follow the guidance without needing to translate Windows-specific instructions.
GitHub Create Pull Request
Reliability Migrate an Azure Service Fabric cluster to availability zone support ...ob/main/articles/reliability/migrate-service-fabric.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Powershell is used exclusively for all command-line examples, with no equivalent Bash, Azure CLI, or Linux-native instructions provided. Windows-centric tools and patterns (e.g., Windows file paths, certificate store references) are present in code samples and explanations. Sample templates and migration walkthroughs reference Windows first, and Linux-specific guidance is missing or relegated to links without direct examples. This may hinder Linux users attempting similar migrations.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all Powershell commands, especially for cluster migration, node disabling, and resource management.
  • Include Linux-specific instructions and code samples, such as handling certificates, file paths, and Service Fabric management on Ubuntu or other supported distributions.
  • Reference both Windows and Linux sample templates equally, and ensure that links to Linux templates are accompanied by direct, in-page examples.
  • Avoid Windows-centric terminology (e.g., Windows file paths, certificate store names) in generic instructions, or provide Linux alternatives side-by-side.
  • Explicitly state platform differences and requirements in the prerequisites and migration steps, so users on Linux are aware of necessary adaptations.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides only PowerShell examples for agent assignment and references Hybrid Compute resources, which are primarily associated with Windows environments. There are no CLI or Bash examples, nor is there mention of Linux-native tools or workflows. This creates a bias toward Windows users and may hinder Linux users from following the guidance.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for agent assignment and job definition updates.
  • Clarify whether Hybrid Compute resources are required for Linux agents, and provide Linux-specific deployment and registration instructions if applicable.
  • Include explicit guidance and examples for deploying and managing Storage Mover agents on Linux systems.
  • Ensure that references to tools and workflows are platform-neutral or provide parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Reliability High Availability (Reliability) in Azure Cosmos DB for NoSQL ...in/articles/reliability/reliability-cosmos-db-nosql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation repeatedly references Windows-centric tools (PowerShell) for management tasks such as manual failover and region switching, often listing PowerShell before Azure CLI and the Azure portal. There are no explicit Linux shell or cross-platform CLI examples, and PowerShell is mentioned as a primary method for several operations, suggesting a bias towards Windows environments.
Recommendations
  • Provide explicit Azure CLI examples for all management tasks currently described with PowerShell.
  • List cross-platform tools (Azure CLI, portal) before Windows-specific tools (PowerShell) when enumerating options.
  • Include Linux shell usage notes or examples where appropriate, especially for command-line operations.
  • Clarify that all management operations can be performed equally on Linux, macOS, and Windows using Azure CLI and portal.
  • Avoid implying PowerShell is required or preferred for tasks that can be accomplished with cross-platform tools.
GitHub Create Pull Request
Reliability Reliability in Azure Firewall ...blob/main/articles/reliability/reliability-firewall.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools (Azure PowerShell) are mentioned before or alongside cross-platform tools (Azure CLI, Bicep, ARM templates, Terraform), but Linux-specific patterns or examples are absent. There are no explicit Linux shell (bash) or CLI command examples, nor references to Linux-native tooling or workflows. The documentation assumes familiarity with Windows/PowerShell and does not provide parity for Linux users.
Recommendations
  • Provide explicit Linux/bash examples for key deployment and configuration steps, especially where Azure PowerShell is referenced.
  • When listing tools, mention Azure CLI (cross-platform) before Azure PowerShell, and clarify platform compatibility for each tool.
  • Include sample commands for both Azure CLI and Azure PowerShell in relevant sections, ensuring Linux users have clear guidance.
  • Reference Linux-native automation tools (e.g., shell scripts, Ansible) where appropriate, or link to related resources.
  • Add a table or section comparing deployment options and commands for Windows and Linux environments.
GitHub Create Pull Request
Reliability Reliability in Azure Virtual Machines ...n/articles/reliability/reliability-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific tools and examples (such as Azure PowerShell and SQL Server on Windows) are mentioned before or in greater detail than their Linux equivalents. In the section on configuring availability zone support, the PowerShell (Windows) guide is listed after the portal and CLI, but there is no explicit mention of Linux-specific tools or examples beyond the CLI. The custom multi-zone solutions section highlights SQL Server on Windows VMs, with no mention of popular Linux-based solutions. There is a lack of parity in examples and guidance for Linux users, and Windows-centric terminology and tooling are more prominent throughout.
Recommendations
  • Ensure that Linux-specific examples and guides (such as Bash, Linux VM management, and Linux-based database solutions) are included and given equal prominence to Windows/PowerShell examples.
  • When listing creation guides, alternate the order or explicitly mention both Windows and Linux workflows, e.g., 'Create a VM in an availability zone by using Azure CLI (Linux)' and '...by using Azure PowerShell (Windows)'.
  • Include references to Linux-based high availability and disaster recovery solutions (e.g., MySQL, PostgreSQL, MongoDB, Pacemaker/Corosync clusters) in the custom multi-zone and multi-region sections.
  • Add links to documentation for managing Linux VMs, including backup, restore, and maintenance operations, to match the coverage given to Windows tools.
  • Review terminology to ensure platform-neutral language and avoid implying that Windows is the default or preferred platform.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-cosmos-db-nosql.md ...in/articles/reliability/reliability-cosmos-db-nosql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page repeatedly mentions PowerShell as a tool for managing failover and other operations in Azure Cosmos DB, often listing it first or exclusively alongside the Azure portal and Azure CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or tools discussed. The references to PowerShell and lack of Linux-specific instructions or parity in examples indicate a Windows bias.
Recommendations
  • Add explicit bash/Azure CLI command examples for all operations currently described with PowerShell.
  • When listing management tools, mention Azure CLI and bash scripts before or alongside PowerShell, not after.
  • Include Linux-specific instructions or troubleshooting steps where relevant.
  • Ensure all code snippets and walkthroughs have both PowerShell and bash/Azure CLI equivalents.
  • Review related links and ensure Linux-friendly resources are included.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-storage-mover.md ...rticles/reliability/reliability-azure-storage-mover.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell examples for agent assignment and references Azure portal and PowerShell as the primary management interfaces, with no mention of Linux CLI equivalents (such as Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, and Windows-centric tools and patterns are presented exclusively and first.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, demonstrating usage on Linux and macOS.
  • Explicitly mention cross-platform management options, such as Bash, Azure CLI, and REST API, alongside PowerShell and portal.
  • Include notes or sections on Linux agent deployment, configuration, and management, if supported.
  • Ensure that instructions for exporting and deploying ARM templates are platform-neutral and reference CLI options where available.
  • Review all examples and guidance to ensure parity for Linux users, including troubleshooting and recovery steps.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-service-fabric.md ...ob/main/articles/reliability/migrate-service-fabric.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Powershell is used exclusively for all command-line migration steps, with no equivalent Bash or Azure CLI examples for Linux users. Windows-centric tools and patterns (e.g., Powershell cmdlets, Windows file paths like D:\SvcFab) are referenced before or instead of Linux alternatives. Even though one sample template is for Ubuntu, all step-by-step instructions and code snippets use Windows tools and syntax, and there is no guidance for Linux users on how to perform the migration using their preferred environment.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all Powershell command snippets to support Linux users.
  • Include instructions and code snippets that use Linux file paths and conventions where appropriate.
  • Clearly indicate when a step or tool is Windows-specific and offer Linux alternatives.
  • Reference both Windows and Linux sample templates equally, and ensure parity in documentation coverage.
  • Add a section or callouts for common Linux troubleshooting scenarios during migration.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-firewall.md ...blob/main/articles/reliability/reliability-firewall.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell as a primary tool for advanced configuration and deployment, often listing it before cross-platform alternatives like Azure CLI, Bicep, ARM templates, or Terraform. References to deployment guides and examples are PowerShell-centric, with no explicit Linux or Bash examples provided. The documentation does not offer parity in example commands or tooling guidance for Linux users, and Windows-centric tools and patterns are emphasized throughout.
Recommendations
  • Ensure that Azure CLI (cross-platform) examples are provided alongside or before Azure PowerShell examples, especially for deployment and configuration tasks.
  • Include explicit Bash/Linux shell command examples for common operations, such as deploying or managing Azure Firewall.
  • Reference documentation pages or tutorials that use Linux-native tools (e.g., Azure CLI in Bash) in addition to PowerShell guides.
  • Avoid listing Windows-specific tools (PowerShell) first when describing available deployment/configuration options; alternate the order or prioritize cross-platform tools.
  • Add a section or callout for Linux users, outlining best practices and available tooling for managing Azure Firewall from non-Windows environments.
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
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and examples (such as PowerShell and SQL Server on Windows) are mentioned before or instead of their Linux equivalents. In the 'Configure availability zone support' section, the PowerShell (Windows) guide is listed after the CLI (Linux) guide, but the CLI guide is explicitly labeled as 'linux', while the PowerShell guide is labeled 'windows', suggesting a separation of platform-specific instructions. Additionally, the only application example given for multi-zone resiliency is SQL Server on Windows, with no mention of Linux-based alternatives. There is also a lack of Linux-specific guidance or parity in backup, failover, and application examples.
Recommendations
  • Include Linux-based application examples (e.g., PostgreSQL, MySQL, Apache, NGINX) alongside Windows examples like SQL Server.
  • Provide explicit Linux instructions for PowerShell-heavy or Windows-centric procedures, such as using Bash, Azure CLI, or Ansible for VM management.
  • Mention Linux backup and disaster recovery solutions (e.g., application-consistent backups for Linux workloads, integration with Linux-native tools).
  • Ensure that references to platform-specific guides (CLI, PowerShell) are presented in a neutral order or grouped together, and clarify which instructions apply to which OS.
  • Add links to documentation for managing Linux VMs, including reliability, backup, and failover strategies.
  • Highlight cross-platform tools and patterns (e.g., Azure CLI, Terraform) that work equally well for both Windows and Linux environments.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-storage-mover.md ...rticles/reliability/reliability-azure-storage-mover.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides a PowerShell-only example for updating job definitions, with no equivalent Linux shell or Azure CLI example. It references Windows-centric tools (PowerShell, Hybrid Compute) and omits Linux-native instructions or parity for agent management and resource updates. The lack of cross-platform examples and tool references may make the guidance less accessible to Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash shell commands alongside PowerShell.
  • Explicitly mention Linux support for agent deployment and management, including any platform-specific steps.
  • Reference Linux-native tools or patterns where applicable, such as using Azure CLI for resource management.
  • Ensure that instructions for granting access and managing identities include both portal and CLI methods.
  • Review all code samples and ensure parity between Windows and Linux environments.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-load-balancer.md ...lob/main/articles/reliability/migrate-load-balancer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through references to PowerShell as the deployment method ("deploy the template from portal or PowerShell") without mentioning Azure CLI or other Linux-friendly tools. There are no examples or guidance for Linux users, such as using Azure CLI or Bash scripts, and Windows-centric tools are mentioned first or exclusively. This may make the documentation less accessible to users working on Linux or macOS platforms.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all deployment steps.
  • Explicitly mention that templates can be deployed using Bash, Azure CLI, or Cloud Shell, not just PowerShell.
  • Provide step-by-step instructions or code snippets for Linux/macOS users, ensuring parity with Windows instructions.
  • When listing deployment options, present Azure CLI and portal before or alongside PowerShell to avoid Windows-first ordering.
  • Add a note clarifying that all steps can be performed on Linux, macOS, and Windows platforms.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-service-fabric.md ...ob/main/articles/reliability/migrate-service-fabric.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based migration commands and examples, referencing Windows paths (e.g., D:\SvcFab), and using Windows-centric tooling (AzureRm* PowerShell cmdlets). While there is a brief mention of an Ubuntu sample template, all step-by-step instructions and code snippets for cluster migration use Windows/PowerShell, with no equivalent Bash, Azure CLI, or Linux-native examples. Windows terminology and patterns (e.g., certificate store, Windows file paths) are used throughout, and Linux alternatives are not discussed or linked.
Recommendations
  • Provide equivalent migration instructions using Azure CLI and Bash for Linux users, especially for resource deployment and Service Fabric node management.
  • Include Linux file path examples (e.g., /var/svcfab) alongside Windows paths in configuration snippets.
  • Reference and link to Linux-specific Service Fabric documentation and templates where appropriate.
  • Add notes or sections explaining how Linux users can perform certificate management and node operations without relying on Windows certificate stores or PowerShell.
  • Ensure that sample templates and walkthroughs are available for both Windows and Linux clusters, and mention them equally in the migration steps.
  • Where PowerShell is used, provide side-by-side examples using Azure CLI or REST API for parity.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-cosmos-db-nosql.md ...in/articles/reliability/reliability-cosmos-db-nosql.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias primarily through repeated references to PowerShell, the Azure CLI, and the Azure portal as the main tools for managing failover and region switching. PowerShell is mentioned first or exclusively in several key operational instructions, and there are no explicit Linux-specific examples or mentions of Linux-native tools or shell commands. The documentation assumes familiarity with Windows-centric management patterns and does not provide parity for Linux users in terms of command-line examples or guidance.
Recommendations
  • Provide explicit Linux shell (bash) examples for all operational tasks currently described using PowerShell.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
  • Avoid listing PowerShell first when describing management options; alternate order or group by platform.
  • Mention and link to Azure CLI installation and usage guides for Linux.
  • Add notes or sections for Linux users, including troubleshooting and best practices relevant to Linux environments.
  • Ensure all instructions and code samples are platform-agnostic or include both Windows and Linux variants.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell examples are Windows-centric and presented in full detail. Additionally, the PowerShell tab appears before the ARM template tab, and the ARM template section references both Linux and Windows but links to the Windows template first. There is no explicit Linux shell scripting example (e.g., Bash), and PowerShell is given equal or greater prominence than CLI, which is more cross-platform. There is a slight preference for Windows tools and patterns, and Linux-specific guidance is minimal.
Recommendations
  • Add explicit Bash shell examples for Linux users alongside CLI and PowerShell examples.
  • Ensure Linux references and examples are presented before or alongside Windows equivalents, not after.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows.
  • Provide links to Linux-specific quickstart and template guides before or alongside Windows guides.
  • Reduce reliance on PowerShell examples or clearly mark them as Windows-only.
  • Include troubleshooting or operational notes relevant to Linux environments (e.g., SSH key management, Linux VM configuration).
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-firewall.md ...blob/main/articles/reliability/reliability-firewall.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell and the Azure portal (which is most commonly used on Windows) as primary configuration tools, often listing them before cross-platform alternatives like Azure CLI, Bicep, ARM templates, or Terraform. References to deployment and configuration frequently link to PowerShell-specific guides, and there are no explicit Linux-specific examples or guidance. The documentation does not provide parity in examples or instructions for Linux users, nor does it highlight cross-platform usage patterns.
Recommendations
  • Ensure that Azure CLI, Bicep, ARM templates, and Terraform are mentioned before or alongside Azure PowerShell and the Azure portal when listing configuration options.
  • Provide explicit Linux-based examples and instructions, such as Azure CLI commands run from Bash or Linux shell environments.
  • Include links to cross-platform or Linux-focused tutorials for deploying and managing Azure Firewall.
  • Avoid referencing PowerShell-specific guides as the primary resource; instead, offer parallel guides for Azure CLI and other cross-platform tools.
  • Clarify that all listed tools (PowerShell, CLI, Bicep, ARM templates, Terraform) are available on both Windows and Linux, and provide guidance for installation and usage on Linux systems.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows-specific tools and examples before their Linux equivalents, such as referencing Azure PowerShell and SQL Server on Azure VMs (Windows) before Linux alternatives. Some links and guidance are Windows-centric, and Windows terminology (PowerShell, SQL Server) is more prominent than Linux equivalents. Linux examples and tools are present but often appear after Windows ones or are less detailed.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and in parallel, rather than listing Windows first.
  • Include explicit Linux-focused examples and references (e.g., Bash, Linux SQL Server, Linux VM management) wherever Windows tools or patterns are mentioned.
  • Where PowerShell is referenced, also provide equivalent Azure CLI or Bash examples for Linux users.
  • Highlight cross-platform tools and approaches, and clarify when guidance applies to both Windows and Linux VMs.
  • Add references to Linux-specific documentation (e.g., managing Linux VMs, Linux backup/restore, Linux application failover) alongside Windows resources.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-load-balancer.md ...lob/main/articles/reliability/migrate-load-balancer.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell as a deployment method without mentioning equivalent Linux/CLI options, and by omitting Linux-specific or cross-platform command examples. The guidance assumes use of PowerShell or the Azure Portal, with no explicit mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS platforms.
Recommendations
  • Include Azure CLI (az) command examples alongside or before PowerShell examples for all deployment and migration steps.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI, not just PowerShell or the Portal.
  • Add Bash scripting examples where automation is discussed, to ensure Linux users have parity.
  • Where the Portal is referenced, clarify that it is platform-agnostic, and provide CLI alternatives for users who prefer command-line interfaces.
  • Review the documentation for any implicit assumptions about the user's operating system and update language to be inclusive of all platforms.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/overview-reliability-guidance.md .../articles/reliability/overview-reliability-guidance.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias. For example, in the table, the only explicit tool-based deployment example is 'Deploy an Azure Firewall with Availability Zones using Azure PowerShell', with no mention of Linux CLI equivalents (e.g., Azure CLI or Bash). There is a general preference for Windows-centric tools (PowerShell) and terminology, and no Linux-specific or cross-platform command-line examples are provided. The ordering and selection of examples suggest a Windows-first approach, and Linux parity is lacking.
Recommendations
  • For every PowerShell-based guide or example, provide equivalent Azure CLI (az) or Bash examples to ensure Linux and cross-platform users are supported.
  • Where possible, use neutral, cross-platform tools (such as Azure CLI) in examples and documentation, or present both Windows and Linux approaches side-by-side.
  • Review all linked reliability guides to ensure that Linux and macOS users are not excluded by tool choice or instructions.
  • Explicitly mention cross-platform compatibility in introductory sections and link to platform-specific instructions where relevant.
  • Avoid using Windows-specific terminology or tools as the default unless there is no cross-platform alternative.
GitHub Create Pull Request
Reliability https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/regions-multi-region-nonpaired.md ...articles/reliability/regions-multi-region-nonpaired.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page generally avoids platform-specific instructions, but in the Azure Storage section (especially for Azure Files), it references Windows-centric tools and patterns such as Azure PowerShell and Azure File Sync (which is Windows-only), and provides a sample script that is likely Windows-oriented. There are no explicit Linux/CLI examples or mentions of Linux-compatible tools for file sync or scripting, and Windows tools are listed before cross-platform alternatives.
Recommendations
  • Where Azure PowerShell is mentioned, also provide equivalent Azure CLI commands and examples for Linux/macOS users.
  • When referencing Azure File Sync (which is Windows-only), clearly state its platform limitation and suggest alternative cross-region sync methods for Linux environments (e.g., rsync, AzCopy, or third-party tools).
  • For sample scripts (such as syncing between file shares), provide both PowerShell and Bash (or Python) examples to ensure Linux parity.
  • In lists of tools, avoid always listing Windows tools first; alternate or group by platform, and clarify which tools are cross-platform.
  • Explicitly mention when a feature or tool is only available on Windows, and provide guidance for Linux users where possible.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →