Reliability

297
Total Pages
288
Linux-Friendly Pages
9
Pages with Bias
3.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

21 issues found
Showing 1-21 of 21 flagged pages
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example for associating job definitions to a new agent but does not offer equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The only explicit command-line example is PowerShell, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI or Bash examples alongside the PowerShell example for updating job definitions.
  • Explicitly mention that the same operations can be performed using the Azure CLI or REST API, and provide links or code snippets.
  • Clarify in the relevant sections that PowerShell is not required and that cross-platform tools are supported.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example for updating job definitions but does not offer equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The only explicit command-line example is PowerShell, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all management operations, especially for updating job definitions and agent assignments.
  • Explicitly mention that the same operations can be performed via the Azure portal, Azure CLI, or REST API, and provide links or references to relevant documentation.
  • Where possible, provide Bash or cross-platform scripting examples to ensure parity for Linux/macOS users.
GitHub Create Pull Request
Reliability Migrate an Azure Service Fabric cluster to availability zone support ...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, particularly in the migration steps for clusters using Basic SKU load balancer and IP resources. All command-line examples are provided exclusively in PowerShell, with no equivalent Bash, Azure CLI, or Linux-native instructions. Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows file paths) are used throughout, and the only explicit OS reference in sample templates is a Windows template, with the Ubuntu template merely linked but not shown or explained. This creates friction for Linux/macOS users who may not have access to PowerShell or be familiar with its usage.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for resource deployment, node disabling, and removal steps.
  • Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
  • Show sample templates and migration steps for Ubuntu/Linux clusters inline, not just as external links.
  • Avoid Windows-specific file paths (e.g., D:\\SvcFab) or provide Linux equivalents where relevant.
  • Clarify which steps/tools are OS-agnostic and which require adaptation for Linux/macOS.
GitHub Create Pull Request
Reliability Migrate an Azure Service Fabric cluster to availability zone support ...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a notable Windows bias, particularly in the migration steps for clusters using Basic SKU load balancer and IP resources. All command-line examples are provided exclusively in PowerShell, referencing Windows-centric Azure modules and Service Fabric management patterns. There is no mention of Linux/macOS equivalents, such as Azure CLI or Bash scripts, nor are there instructions for performing the same tasks on non-Windows platforms. Additionally, the sample templates referenced for Linux (e.g., Ubuntu) do not include corresponding Linux command-line instructions for migration, and Windows/PowerShell examples are presented first and exclusively.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell commands, especially for migration and resource management steps.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and how Linux/macOS users can perform the same operations.
  • Add a section or callouts for Linux/macOS users, clarifying any differences in procedure or tooling.
  • Ensure that sample templates for Linux clusters are accompanied by Linux-friendly deployment instructions.
  • Avoid assuming the use of Windows-specific paths or certificate stores in configuration examples; provide alternatives for Linux environments.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell-only example for updating job definitions, with no equivalent CLI or Bash example for Linux/macOS users. The instructions for associating agents to job definitions mention 'Azure portal or PowerShell', listing PowerShell first and omitting Azure CLI or Bash alternatives. There is no mention of Linux-specific tools or cross-platform command options in critical agent management steps.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell for all resource management tasks, especially for updating job definitions.
  • Explicitly mention that agent registration and job assignment can be performed using Azure CLI or REST API, and provide links or examples.
  • Ensure that instructions for granting managed identity access include CLI steps, not just portal or PowerShell.
  • Review all sections for references to Windows-specific tools and provide Linux/macOS equivalents where applicable.
GitHub Create Pull Request
Reliability Reliability in Azure Firewall ...blob/main/articles/reliability/reliability-firewall.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell and the Azure portal as primary tools for configuring Azure Firewall availability zones, with Azure CLI, Bicep, ARM templates, and Terraform mentioned as alternatives. However, PowerShell and portal (Windows-centric tools) are listed first, and example links point to PowerShell-based guides. There are no explicit Linux/macOS-specific examples or guidance, and the CLI is not prioritized. This creates a subtle Windows bias in tooling recommendations and example ordering.
Recommendations
  • Present Azure CLI examples and links alongside or before PowerShell examples, especially for tasks like configuring availability zones.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide direct links to CLI-based deployment guides (e.g., 'Deploy Azure Firewall with availability zones using Azure CLI').
  • Ensure that all configuration steps have both PowerShell and CLI examples, and clarify platform compatibility.
  • Avoid listing Windows-centric tools (PowerShell, portal) before cross-platform tools unless contextually necessary.
GitHub Create Pull Request
Reliability Azure Service Manager retirement ...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page shows evidence of Windows bias, primarily through the use of PowerShell-focused migration guidance (e.g., 'migrate-classic-vnet-powershell') and the presence of Windows-specific support links. While Linux distributions (RedHat, Ubuntu, SUSE) are mentioned in support links for VM migration, the migration documentation itself often references PowerShell, which is traditionally a Windows-centric tool. There are no explicit Linux CLI (bash, Azure CLI) examples or migration guides highlighted, and Windows support is listed before Linux equivalents in some cases.
Recommendations
  • Add explicit Linux/macOS migration examples using Azure CLI or bash scripts in addition to PowerShell.
  • Ensure migration documentation links are platform-neutral or provide clear guidance for both Windows and Linux users.
  • List Linux and Windows support options together or in alphabetical order to avoid perceived prioritization.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, and provide equivalent Azure CLI commands.
GitHub Create Pull Request
Reliability Migrate an Azure Service Fabric cluster to availability zone support ...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in migration steps for Service Fabric nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line examples use PowerShell cmdlets, and Windows-centric tools (e.g., Remove-AzureRmVmss, Connect-ServiceFabricCluster) are referenced exclusively. The sample template for Linux (Ubuntu) is mentioned, but no equivalent Bash/CLI commands or Linux-native instructions are provided. Windows/PowerShell steps are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI and/or Bash equivalents for all PowerShell commands, especially for resource deployment, node disabling, and resource removal.
  • Include explicit Linux/macOS instructions for connecting to Service Fabric clusters and managing nodes.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows/PowerShell tools.
  • Ensure that sample templates for Linux (e.g., Ubuntu) are accompanied by step-by-step instructions using Linux-native tooling.
  • Add notes clarifying which steps are OS-agnostic and which require platform-specific commands.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for updating job definitions, with no equivalent CLI or Linux/macOS instructions. It references 'Hybrid Compute' resources and agent registration patterns that are typically associated with Windows environments, and does not mention or demonstrate Linux agent deployment or management. There is no evidence of Linux or cross-platform command-line examples, nor are Linux-specific tools or instructions provided.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all agent and job management tasks.
  • Explicitly document agent deployment and management on Linux, including prerequisites and troubleshooting.
  • Clarify whether the Storage Mover agent can run on Linux, and provide parity in instructions for Linux/macOS environments.
  • Mention cross-platform alternatives (e.g., Bash, Azure CLI) before or alongside PowerShell.
  • Ensure references to 'Hybrid Compute' or agent registration are not Windows-centric, or provide Linux-specific guidance if differences exist.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references PowerShell as a tool for managing failover and switching write regions, listing it alongside Azure CLI and Azure portal. PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is cross-platform) in several places subtly prioritizes Windows tooling. However, all management actions are also available via Azure CLI and Azure portal, which are cross-platform, and there are no exclusive Windows-only instructions or examples.
Recommendations
  • List Azure CLI before PowerShell when mentioning management tools, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that all management actions (failover, region switching, etc.) can be performed using Azure CLI and Azure portal on any OS, and provide example commands for both CLI and PowerShell where relevant.
  • Consider adding a short note that PowerShell is primarily for Windows users, while Azure CLI is recommended for Linux/macOS users.
  • Where possible, provide direct CLI command examples in addition to PowerShell, especially in sections about manual failover and region switching.
GitHub Create Pull Request
Reliability Reliability Guides for Azure Services .../articles/reliability/overview-reliability-guidance.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 the page itself is largely platform-neutral, there is one instance where a Windows-specific tool (Azure PowerShell) is mentioned for deploying Azure Firewall with availability zones. No Linux/macOS equivalents or cross-platform CLI options are referenced in this context.
Recommendations
  • Where PowerShell is mentioned (e.g., 'Deploy Azure Firewall with availability zones by using Azure PowerShell'), add or link to equivalent instructions using Azure CLI, which is cross-platform.
  • Ensure that any future examples or tool references include both Windows and Linux/macOS options, or use platform-neutral tools like Azure CLI.
  • Consider reviewing linked reliability guides for similar biases, as this index may inherit bias from those documents.
GitHub Create Pull Request
Reliability Reliability in Azure Managed Redis ...main/articles/reliability/reliability-managed-redis.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific examples or instructions, but in the 'Backup and restore' section, it mentions that automation for import/export can be implemented using Azure CLI or Azure PowerShell. However, it does not clarify that Azure CLI is cross-platform and that Azure PowerShell is available on Linux/macOS, nor does it provide Linux/macOS-specific command examples or shell scripts. No explicit Windows tools or PowerShell-heavy bias is present, but the lack of Linux/macOS parity in examples is a minor omission.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS as well as Windows.
  • Provide example commands for both Azure CLI (bash/zsh) and Azure PowerShell, and note their platform compatibility.
  • If automation scripts are referenced, include sample bash scripts for Linux/macOS users.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
GitHub Create Pull Request
Reliability What are Azure availability zones? ...in/articles/reliability/availability-zones-overview.md
Low Priority View Details →
Scanned: 2026-01-12 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 availability zone mappings, but the PowerShell example is shown second, and both are cross-platform tools. There is no evidence of exclusive use of Windows-specific tools or patterns, nor are Windows-only instructions present. However, PowerShell is traditionally associated with Windows, and its inclusion may suggest a slight Windows bias, especially since no explicit Linux/macOS shell examples (e.g., Bash/cURL) are provided.
Recommendations
  • Add explicit Bash/cURL examples for Linux/macOS users to query the ARM API.
  • Clarify that Azure CLI is cross-platform and provide installation links for Linux/macOS.
  • Consider listing CLI (Bash) examples before PowerShell to reinforce platform neutrality.
  • Mention that PowerShell Core is available cross-platform, if relevant.
GitHub Create Pull Request
Reliability Azure Service Manager retirement ...-docs/blob/main/articles/reliability/asm-retirement.md
Low Priority View Details →
Scanned: 2026-01-12 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-centric migration guides (e.g., 'migrate-classic-vnet-powershell') and the inclusion of Windows-specific support links before or alongside Linux distributions. While Linux support links are present for VM migration, other migration guides and references (such as networking) default to PowerShell tooling, which is more native to Windows environments.
Recommendations
  • Ensure migration guides include CLI/bash examples and instructions for Linux/macOS users, not just PowerShell.
  • Where PowerShell is referenced, provide equivalent Azure CLI or REST API steps for cross-platform parity.
  • Explicitly mention Linux/macOS compatibility in migration documentation, especially for networking and resource management tasks.
  • Order support links and examples in a way that does not prioritize Windows over Linux (e.g., alphabetical or by usage statistics).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific tools (PowerShell) alongside cross-platform tools (Azure CLI, Azure portal) when describing manual failover and other management operations. PowerShell is mentioned first or equally with CLI and portal, but there are no Linux/macOS-specific instructions or examples. No explicit Linux/macOS bias is present, but the ordering and tool selection may subtly favor Windows users.
Recommendations
  • Ensure that Azure CLI examples are shown before or alongside PowerShell, as CLI is cross-platform.
  • Provide explicit Linux/macOS instructions or examples where relevant, especially for command-line operations.
  • Clarify that PowerShell is available cross-platform, or note any platform-specific limitations.
  • Consider including bash or shell script examples for Linux/macOS users.
  • Review ordering of tool mentions to avoid implicit prioritization of Windows-centric tools.
GitHub Create Pull Request
Reliability Reliability in Azure Managed Redis ...main/articles/reliability/reliability-managed-redis.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but it does mention automation using Azure CLI or Azure PowerShell for backup/export operations. However, it does not show any actual commands or scripts, nor does it clarify Linux/macOS parity for these tools. The absence of explicit Linux/macOS instructions or examples, especially for automation, may create minor friction for non-Windows users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both Azure CLI and Azure PowerShell.
  • If PowerShell examples are given, also provide equivalent Bash or shell script examples for Linux/macOS users.
  • Clarify any platform-specific limitations or requirements for automation tasks.
  • Add a note about installing and using Azure CLI and PowerShell on Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides parity for both Windows and Linux users in most sections, especially in Azure CLI and Resource Manager template examples. However, there is a mild Windows bias: PowerShell examples are given in detail, and Windows tooling (PowerShell) is presented as a primary method alongside CLI and portal. In the Resource Manager template section, Linux and Windows quickstart links are provided, but the example shown is for Linux only. The ordering of tabs places Azure portal, CLI, PowerShell, and Resource Manager templates, which is a common Microsoft pattern but subtly prioritizes Windows-centric tools (PowerShell) before cross-platform scripting. No critical Linux functionality is missing, and CLI examples (which work on Linux/macOS) are present and complete.
Recommendations
  • Ensure that Linux-specific instructions or examples are included where relevant, especially in PowerShell-heavy sections.
  • Consider reordering tabs so that cross-platform tools (CLI) appear before Windows-specific tools (PowerShell).
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and provide links to installation guides for all platforms.
  • Where PowerShell is shown, clarify that it is Windows-centric and suggest CLI or REST API alternatives for Linux/macOS users.
  • Provide both Linux and Windows examples in Resource Manager template sections, or clarify which OS the example targets.
GitHub Create Pull Request
Reliability What are Azure availability zones? ...in/articles/reliability/availability-zones-overview.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
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. PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a slight Windows bias, especially since Linux/macOS users are more likely to use CLI. However, both examples are present, and no critical functionality is locked to Windows tools. There are no references to Windows-only tools, nor are Windows-specific patterns or instructions prioritized elsewhere in the page.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider listing the Azure CLI example before PowerShell to reduce perceived Windows-first bias.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if relevant.
  • Ensure that all code examples are tested and work on Linux/macOS environments.
  • Where possible, provide bash or shell script equivalents for common tasks.
GitHub Create Pull Request
Reliability Reliability in Azure Firewall ...blob/main/articles/reliability/reliability-firewall.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions multiple deployment tools (Azure PowerShell, Azure CLI, Bicep, ARM templates, Terraform), it consistently lists Azure PowerShell before Azure CLI and other cross-platform tools. The key deployment walkthrough link is to a PowerShell-based guide, with no direct link to an Azure CLI or Linux/macOS example. There are no explicit Linux/macOS instructions or examples, and the page does not clarify parity between PowerShell and CLI workflows.
Recommendations
  • Provide direct links to Azure CLI, Bicep, and Terraform deployment guides alongside PowerShell guides.
  • List cross-platform tools (Azure CLI, Bicep, Terraform) before or alongside PowerShell when describing deployment options.
  • Include explicit examples or code snippets for Azure CLI and other non-Windows tools in configuration sections.
  • Clarify that all deployment options are supported on Linux/macOS and Windows, and note any differences if present.
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-11 06:20
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. While Azure CLI is cross-platform, PowerShell examples are given equal prominence, and Windows-specific tools (PowerShell) are presented as a primary method. In the ARM template section, both Linux and Windows quickstarts are referenced, but the explicit example shown is for Linux. There is a slight 'windows_first' bias in the ordering and inclusion of PowerShell, and the documentation does not explicitly mention Linux/macOS shell alternatives or highlight cross-platform usage in CLI sections.
Recommendations
  • Clearly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend it as the primary cross-platform method.
  • In tabbed examples, list Azure CLI before PowerShell and clarify platform compatibility.
  • Add explicit Bash or shell script examples where relevant, especially for Linux/macOS users.
  • When referencing quickstart templates, ensure parity by showing both Linux and Windows examples, or clarify which OS the example applies to.
  • Add notes for Linux/macOS users where PowerShell is mentioned, suggesting Azure CLI as the preferred alternative.
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-11 06:20
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 region switching. PowerShell is a Windows-centric tool, and its mention alongside the Azure CLI and portal (which are cross-platform) may signal a mild Windows bias. Additionally, in several places, PowerShell is listed first when describing options for manual failover and region switching, which can subtly prioritize Windows tooling over Linux/macOS alternatives.
Recommendations
  • Ensure that examples and instructions for Azure CLI (which is cross-platform) are provided and emphasized equally or before PowerShell.
  • Explicitly state that Azure CLI and portal are fully supported on Linux and macOS, and provide links to Linux/macOS-specific guidance if available.
  • If PowerShell is mentioned, clarify that Azure CLI is recommended for Linux/macOS users, and consider providing Bash or shell script examples where appropriate.
  • Avoid listing PowerShell first in tool lists unless there is a technical reason; alternate the order or group cross-platform tools together.
GitHub Create Pull Request