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 26-50 of 71 flagged pages
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 →
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-native example. It references Azure PowerShell and Hybrid Compute (typically Windows-centric) resources, but does not mention or provide parity for Linux users or tools such as Azure CLI or bash scripts. This creates a bias toward Windows and PowerShell users, making it less accessible for Linux administrators.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for all resource management tasks, especially for updating job definitions.
- Explicitly mention that the agent and management operations can be performed from Linux environments, and provide bash or shell script examples where appropriate.
- Clarify whether Hybrid Compute resources are required to be Windows-based, and if not, provide Linux deployment guidance.
- Ensure that all instructions referencing the Azure portal or PowerShell also include steps for Azure CLI and REST API usage.
- Add a section or note highlighting cross-platform support and linking to Linux-specific agent deployment or management documentation if available.
Create Pull Request
Reliability
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-container-instances.md
...in/articles/reliability/migrate-container-instances.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references PowerShell alongside Azure CLI throughout, and in some cases lists PowerShell before CLI. There are no explicit Linux-specific instructions or examples, and the guidance assumes familiarity with PowerShell, which is more common on Windows. No Linux shell (bash) or cross-platform scripting examples are provided.
Recommendations
- Add explicit Linux/bash examples for all command-line steps, especially for deleting and redeploying container groups.
- List Azure CLI (which is cross-platform) before PowerShell in all tool lists and instructions.
- Clarify that PowerShell is available cross-platform, but provide bash examples to ensure Linux parity.
- Where possible, provide a table or section comparing steps for Windows (PowerShell), Linux (bash), and macOS.
- Avoid assuming the use of PowerShell unless necessary; default to Azure CLI for command-line instructions.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell examples for managing Azure Storage Mover job definitions, with no equivalent examples for Linux environments (such as Azure CLI or Bash). The use of PowerShell and references to Hybrid Compute resources (which are often associated with Windows environments) further reinforce a Windows-centric approach. There are no Linux-first or cross-platform command examples, and no mention of how to perform these tasks on Linux systems.
Recommendations
- Add equivalent Azure CLI (az) or Bash examples alongside PowerShell commands for all resource management tasks.
- Explicitly mention cross-platform compatibility where possible, and clarify if any steps are Windows-specific.
- Provide guidance or links for Linux and macOS users, especially for agent registration and job definition management.
- Where Hybrid Compute is referenced, clarify its cross-platform support or provide Linux-specific instructions if available.
- Ensure that all automation and scripting examples are available in both PowerShell and Bash/Azure CLI to improve accessibility for non-Windows users.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a deployment method without mentioning or providing examples for Linux or cross-platform alternatives such as Azure CLI or ARM template deployment via CLI. The phrase 'deploy the template from portal or PowerShell' suggests a preference for Windows-centric tools, and there are no Linux-specific or cross-platform command examples or instructions.
Recommendations
- Include Azure CLI examples for all deployment steps, as Azure CLI is cross-platform and widely used on Linux.
- When referencing deployment methods, mention both 'PowerShell' and 'Azure CLI' (e.g., 'deploy the template from portal, PowerShell, or Azure CLI').
- Provide explicit Linux shell command examples where relevant, especially for exporting, editing, and deploying ARM templates.
- Review all instructions to ensure they are tool-agnostic or provide parity between Windows and Linux tooling.
- Add a note clarifying that all steps can be performed on both Windows and Linux platforms, and link to documentation for both PowerShell and Azure CLI usage.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is primarily a directory of reliability guides for Azure services, with minimal technical content or examples. However, there is evidence of Windows bias in the form of references to Windows-specific tools (e.g., Azure PowerShell) and deployment guides that mention PowerShell explicitly. For example, the Azure Firewall and Azure Web Application Firewall entries link to guides for deploying with Azure PowerShell, with no mention of equivalent CLI, Bash, or Linux-native instructions. There is also a tendency to mention Windows-oriented tools before (or instead of) cross-platform alternatives.
Recommendations
- For every reference to PowerShell-based deployment or management, include equivalent instructions or links for Azure CLI (az), Bash scripts, or other cross-platform tools.
- Where possible, avoid tool-specific phrasing in the main directory—use neutral language like 'Deploy using Azure CLI or PowerShell' and provide both options in linked guides.
- Audit linked reliability guides to ensure Linux and cross-platform users have parity in examples and instructions, not just Windows/PowerShell.
- Explicitly mention when a guide or tool is Windows-only, and provide alternative guidance for Linux/macOS users.
- Consider adding a column or tags in the directory to indicate platform/tool coverage (e.g., PowerShell, CLI, Bash, Portal) for each guide.
Reliability
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-vm.md
...zure-docs/blob/main/articles/reliability/migrate-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several sections, PowerShell and Windows-centric tools are mentioned before or more prominently than their Linux/Azure CLI equivalents. Some links and examples are Windows-specific, and there is a tendency to refer to Windows/PowerShell resources or documentation first, with Linux/CLI options mentioned second or less visibly. There are also references to Windows-specific tools (such as PowerShell) without always providing Linux/CLI parity in the same context. In some cases, Linux examples are present but less emphasized.
Recommendations
- Ensure that all procedural steps and code examples are provided for both PowerShell (Windows) and Azure CLI (cross-platform), and present them side-by-side or with equal prominence.
- When listing options (e.g., checking VM SKU availability), alternate the order in which Windows/PowerShell and Linux/CLI methods are mentioned, or present them together.
- Avoid linking only to Windows/PowerShell-specific documentation (e.g., 'find unattached disks')—always provide the equivalent Linux/CLI resource or example.
- Where possible, use Azure CLI as the primary example, as it is cross-platform, and supplement with PowerShell/Windows examples as needed.
- Audit all 'Next Steps' and reference links to ensure Linux/CLI parity and equal visibility.
- Explicitly state when a method or tool is Windows-only, and provide a Linux alternative or a note if none exists.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation generally avoids OS-specific instructions, but in the Azure Files section, it lists Azure PowerShell and Windows-centric tools (e.g., Azure File Sync, which is Windows-only) as primary options for file replication and sync. There is a lack of parity in mentioning or providing Linux/CLI alternatives, and the sample script referenced is likely Windows-focused. The order of tools (AzCopy, PowerShell, Data Factory) also puts Windows tools before cross-platform or Linux-native options.
Recommendations
- For every mention of Azure PowerShell or Windows-specific tools (such as Azure File Sync), explicitly mention and provide equivalent Azure CLI or Linux-native alternatives where available.
- In the Azure Files section, clarify which tools are cross-platform (e.g., AzCopy, Azure CLI) and provide example commands for both Windows and Linux environments.
- If referencing sample scripts, ensure there are both PowerShell and Bash (or Python) examples, or at least clarify the OS compatibility of the scripts.
- When listing tools or approaches, avoid always listing Windows/PowerShell options first; alternate or group by platform.
- For features like Azure File Sync, clearly state that it is Windows-only and suggest alternative approaches for Linux-based file servers (e.g., rsync with AzCopy, or third-party solutions).
Reliability
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-sql-database.md
...blob/main/articles/reliability/migrate-sql-database.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation consistently provides PowerShell examples and instructions, often with explicit directions to 'Open PowerShell as Administrator', which is a Windows-specific pattern. PowerShell examples are given equal prominence to Azure CLI, but the language and instructions (e.g., 'as Administrator') are Windows-centric. There is no mention of Bash, Linux shells, or cross-platform scripting environments, and no guidance for Linux users on using PowerShell Core or alternative shells. The ordering of tabs sometimes places PowerShell before CLI, reinforcing a Windows-first approach.
Recommendations
- Clarify that PowerShell examples can be run cross-platform using PowerShell Core, and provide instructions for Linux/macOS users where appropriate.
- Avoid instructions like 'Open PowerShell as Administrator' unless necessary, or provide equivalent Linux/macOS instructions (e.g., 'Open a terminal').
- Explicitly mention that Azure CLI commands can be run in Bash, zsh, or other Linux/macOS shells, and provide example commands for those environments if there are differences (e.g., quoting, environment variables).
- Consider reordering tabs or examples so that Azure CLI (which is cross-platform) appears before PowerShell, or at least alternate the order to avoid implicit prioritization.
- Where possible, add Bash script examples or note that Azure CLI is the recommended tool for Linux/macOS users.
- If PowerShell is required, mention how to install and use PowerShell Core on Linux/macOS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias, particularly in the migration steps for Service Fabric nonmanaged clusters with 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. The only explicit sample template link for Linux (Ubuntu) is not accompanied by Linux-specific command examples, and the main step-by-step migration process assumes a Windows/PowerShell environment. Windows tools and patterns (e.g., PowerShell cmdlets, Windows-style paths) are used throughout, and Windows-based examples are mentioned or linked before Linux equivalents.
Recommendations
- Provide equivalent Azure CLI and/or Bash command examples alongside PowerShell for all resource deployment, node management, and migration steps.
- Explicitly mention and link to Linux/Ubuntu sample templates where relevant, and ensure parity in the depth of instructions for both Windows and Linux.
- When referencing file paths or configuration settings (e.g., dataPath), include both Windows and Linux path formats.
- Avoid assuming the use of Windows tools (such as PowerShell) as the default; clarify that both Windows and Linux environments are supported and provide guidance for both.
- Add a dedicated section or callouts for Linux users, highlighting any differences or additional considerations for Linux-based Service Fabric clusters.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, PowerShell, and ARM templates, but there is a noticeable Windows bias. PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, and Windows terminology (such as 'adminPassword' in ARM templates) is present even in Linux examples. The ARM template section references both Linux and Windows, but the example shown is ambiguous and includes a Windows-style password. There are no explicit Linux shell (bash) or cloud-init examples, and Windows tools/patterns are mentioned at least as prominently as Linux equivalents.
Recommendations
- Add explicit bash/shell scripting examples for Linux users, especially for common tasks such as creating scale sets or configuring network resources.
- In ARM template examples, clearly differentiate between Linux and Windows configurations (e.g., use SSH keys and omit 'adminPassword' for Linux).
- Ensure that Linux-first or cross-platform examples are presented before or alongside PowerShell/Windows-specific examples.
- Where PowerShell is shown, provide equivalent bash/CLI commands or scripts to ensure Linux parity.
- Clarify in each example whether it applies to Linux, Windows, or both, and provide OS-specific guidance where necessary.
- Include references to Linux-native configuration tools (e.g., cloud-init) where relevant.
Reliability
Reliability in Azure Storage Mover
...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell-only example for associating job definitions to a new agent, without offering an equivalent example for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). Additionally, the instructions mention using the Azure portal or PowerShell first, rather than presenting cross-platform options equally.
Recommendations
- Add Azure CLI and/or REST API examples alongside the PowerShell example for updating job definitions.
- Explicitly mention that the Azure portal, PowerShell, Azure CLI, and REST API are all supported methods for agent assignment, and provide links or code samples for each.
- Ensure that instructions do not prioritize Windows-centric tools (PowerShell) over cross-platform alternatives.
- Where possible, clarify any platform-specific limitations or requirements.
Reliability
Migrate an Azure Service Fabric cluster to availability zone support
...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in migration steps for clusters using Basic SKU load balancer and IP resources. All command-line examples are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native instructions. Windows-centric tools and paths (e.g., D:\SvcFab) are referenced, and Windows sample templates are mentioned before Linux equivalents. Linux users are left to infer or adapt steps without direct guidance.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for cluster migration and resource management.
- Reference Linux/Ubuntu sample templates alongside Windows templates, and mention them with equal prominence.
- Include notes or sections explicitly addressing Linux/macOS users, clarifying any differences in process or tooling.
- Replace or supplement Windows file paths (e.g., D:\SvcFab) with Linux equivalents (e.g., /var/svcfab) where appropriate.
- Ensure all resource management steps (disabling nodes, removing resources, updating DNS) have cross-platform instructions.
Reliability
Azure Service Manager retirement
...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally cross-platform, listing migration guidance and support links for both Windows and major Linux distributions (RedHat, Ubuntu, SUSE) for VM migration. However, there is a notable Windows bias in the migration documentation links for networking resources, such as 'Classic Virtual Network', which specifically reference PowerShell-based migration guides. PowerShell is primarily a Windows tool, and the lack of explicit Bash/CLI or Linux-native migration examples suggests a 'powershell_heavy' and 'windows_first' bias. No explicit Linux/macOS command-line examples or parity guidance are provided for these migration tasks.
Recommendations
- Add Linux/macOS-specific migration examples using Azure CLI or Bash scripts alongside PowerShell examples.
- Ensure migration documentation for networking resources (e.g., Classic Virtual Network) includes instructions for Linux users, not just PowerShell.
- Clearly indicate which migration steps are cross-platform and which are Windows-specific.
- Provide parity in support links and troubleshooting guides for Linux/macOS users.
Reliability
Reliability in Azure Storage Mover
...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority
View Details →
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-friendly example. The use of PowerShell and references to 'Hybrid Compute' resources (typically associated with Windows environments) further reinforce a Windows-centric approach. There are no Bash, Azure CLI, or cross-platform instructions for agent/job management tasks.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for all PowerShell commands.
- Explicitly mention cross-platform support for agent registration and management, including Linux and macOS.
- Clarify whether 'Hybrid Compute' resources can be Linux-based and provide relevant instructions if so.
- Ensure that all critical management operations (such as updating job definitions and assigning roles) have platform-neutral or platform-specific guidance for both Windows and Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias in its tooling references and example prioritization. Azure PowerShell is mentioned first or exclusively in several places, and links to deployment guides use PowerShell as the primary example. While Azure CLI, Bicep, ARM templates, and Terraform are mentioned, there are no explicit Linux/macOS-specific instructions or examples, and PowerShell is often listed before cross-platform tools. No Linux/macOS-only tools or shell commands are shown, and the documentation does not clarify platform parity for all referenced tooling.
Recommendations
- Provide explicit Azure CLI examples and links alongside PowerShell for all configuration and deployment tasks.
- Ensure that Linux/macOS users are given equal prominence in instructions, including notes about cross-platform compatibility for CLI, Bicep, ARM templates, and Terraform.
- Add a section or table comparing tool usage across Windows, Linux, and macOS, clarifying which tools are recommended for each platform.
- When referencing deployment guides, link to both PowerShell and CLI versions (where available), and avoid listing PowerShell first unless it is the only option.
- Include sample commands for Azure CLI and/or Bicep in the main documentation, not just in linked articles.
Reliability
Reliability in Azure Virtual Machine Scale Sets
.../reliability/reliability-virtual-machine-scale-sets.md
Medium Priority
View Details →
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 to CLI, and the PowerShell tab is present, which is Windows-centric. The ARM template example is for Linux, but the link to the Windows template is given immediately after, suggesting parity. No Linux/macOS-specific tools or shell examples (e.g., Bash, SSH, cloud-init) are provided, and PowerShell is presented as a primary automation method, which is Windows-biased. The CLI examples are cross-platform, but PowerShell is not available natively on most Linux distributions. The ordering of tabs is Portal, CLI, PowerShell, Resource Manager, which puts Windows-centric tools before Linux-centric ones.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for automation tasks.
- Clarify that Azure CLI commands work equally well on Linux/macOS and Windows.
- Consider adding cloud-init or SSH-based configuration examples for Linux VMs.
- Note that PowerShell is not native to Linux/macOS and provide installation guidance or alternatives.
- Reorder tabs to put CLI (cross-platform) before PowerShell (Windows-centric), or clarify parity.
- Ensure ARM template examples alternate between Linux and Windows, or provide both side-by-side.
Reliability
Reliability in Azure Storage Mover
...rticles/reliability/reliability-azure-storage-mover.md
Medium Priority
View Details →
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. The agent registration and management steps reference PowerShell and Azure portal, but do not mention cross-platform tools like Azure CLI or Bash scripts. There is no explicit mention of Linux agent deployment or management, and no parity for Linux/macOS users in command-line examples.
Recommendations
- Add Azure CLI examples alongside PowerShell for all resource management tasks, especially updating job definitions.
- Explicitly mention that agent deployment and management can be performed from Linux/macOS using Azure CLI or REST API.
- Provide Bash script examples or instructions for Linux users where applicable.
- Clarify platform requirements for agent deployment and management, ensuring Linux/macOS users are supported.
- Order examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
Reliability
Migrate an Azure Service Fabric cluster to availability zone support
...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias, particularly in the migration steps for Service Fabric nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line examples use PowerShell cmdlets, with no equivalent Bash, Azure CLI, or Linux-native instructions. Windows tools and patterns (e.g., PowerShell, Windows-style paths) are referenced exclusively, and the only explicit OS reference in sample templates is a Windows template, even though an Ubuntu template is linked. The ordering of examples and instructions also places Windows/PowerShell first, with no Linux parity in procedural steps.
Recommendations
- Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for resource deployment, node disabling, and removal steps.
- Explicitly mention support for Linux/macOS environments and clarify any OS-specific requirements or differences.
- Reference and highlight Linux sample templates (e.g., Ubuntu) with equal prominence to Windows templates.
- Avoid Windows-specific path conventions (e.g., D:\SvcFab) in generic configuration examples, or provide cross-platform alternatives.
- Where PowerShell is used, add a note or section for Linux users on how to perform the same actions using Azure CLI or REST API.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. While it mentions multiple deployment tools (Azure PowerShell, Azure CLI, Bicep, ARM templates, Terraform), it consistently lists Azure PowerShell first and references a deployment guide specifically for PowerShell. There are no explicit Linux/macOS examples, nor are CLI commands or scripts shown. The page does not provide parity in example walkthroughs or tooling guidance for Linux users, and the linked deployment guide is PowerShell-centric.
Recommendations
- Present Azure CLI examples and links alongside PowerShell, especially in sections about deployment and configuration.
- List cross-platform tools (Azure CLI, Terraform, Bicep) before or alongside PowerShell to avoid Windows-first ordering.
- Add explicit Linux/macOS instructions or examples where scripting or command-line usage is discussed.
- Ensure that referenced guides (such as deployment walkthroughs) have CLI and PowerShell versions, and link to both.
Reliability
High Availability (Reliability) in Azure Cosmos DB for NoSQL
...in/articles/reliability/reliability-cosmos-db-nosql.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page repeatedly references Windows-specific tools (PowerShell) alongside cross-platform options (Azure CLI, Azure portal) for critical operations such as failover and region management. PowerShell is mentioned first or equally with CLI/portal in several places, and there are no explicit Linux/macOS-specific examples or clarifications. This creates a subtle bias toward Windows environments, especially for users seeking command-line automation or scripting guidance.
Recommendations
- Provide explicit Linux/macOS command-line examples using Azure CLI and Bash where PowerShell is mentioned.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, while PowerShell is primarily Windows-centric.
- When listing tools, mention Azure CLI and portal before PowerShell, or group them as 'cross-platform' and 'Windows-specific' options.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Avoid implying PowerShell is required for any operation; ensure parity in instructions and troubleshooting steps.
Reliability
What are Azure availability zones?
...in/articles/reliability/availability-zones-overview.md
Medium Priority
View Details →
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 (which is cross-platform) can signal a Windows bias, especially since no Linux-specific shell examples (e.g., Bash) are provided. Additionally, references to Azure PowerShell are made before clarifying CLI parity, and there is no mention of Linux-specific patterns or tools.
Recommendations
- Ensure that CLI (az) examples are presented first, as it is cross-platform and widely used on Linux and macOS.
- Add explicit Bash or shell script examples where appropriate, especially for Linux users.
- Clarify that Azure CLI works natively on Linux, macOS, and Windows, while PowerShell is more common on Windows.
- Consider referencing Linux-native tools or patterns (e.g., curl for REST API calls) in addition to or before PowerShell.
- Review the ordering and prominence of tool references to avoid implying Windows-first workflows.
Reliability
Azure Service Manager retirement
...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. The migration guide for 'Classic Virtual Network' specifically references PowerShell in its URL, suggesting a Windows-centric approach to migration instructions. Additionally, Windows support links are listed before Linux distributions in the support column for VM (classic), and the overall documentation does not mention Linux-specific tools or CLI examples, nor does it highlight cross-platform migration tooling or parity.
Recommendations
- Ensure migration guides include both PowerShell and Azure CLI/Bash examples for Linux users.
- Where support links for multiple OSes are provided, list Linux distributions before or alongside Windows to avoid Windows-first ordering.
- Explicitly mention cross-platform tools and approaches in migration documentation, such as Azure CLI, ARM templates, and REST APIs.
- Audit referenced migration guides to confirm they provide Linux-specific instructions and troubleshooting steps.
- Add a section summarizing cross-platform migration options and best practices, ensuring equal visibility for Linux and Windows users.
Reliability
Reliability in Azure Container Apps
...ain/articles/reliability/reliability-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell and the Azure CLI as supported tools for deployment, verification, and management tasks. Azure PowerShell is a Windows-centric tool, and its mention alongside Azure CLI (which is cross-platform) is common, but PowerShell is listed before CLI in several places and is tracked as a custom dev experience. There are no explicit Linux-only examples, and no mention of Linux-specific tools or shell commands. The documentation does not provide command-line examples, but the pattern of listing PowerShell and CLI together, with PowerShell often first, and the absence of Linux shell examples, suggests a subtle Windows bias.
Recommendations
- Ensure that Azure CLI is listed before Azure PowerShell in instructions and references, as CLI is cross-platform and more widely used on Linux.
- Provide explicit Bash or Linux shell command examples where relevant, especially for deployment and verification tasks.
- Include notes or sections highlighting Linux compatibility and any Linux-specific considerations for Azure Container Apps.
- Avoid tracking or labeling documentation as 'devx-track-azurepowershell' unless parity is maintained for CLI and Linux shell usage.
- Where possible, add links or examples for Linux users, such as using Bash scripts or integrating with Linux-native tools.
Reliability
Reliability in Azure Virtual Machine Scale Sets
.../reliability/reliability-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, Azure portal, and Resource Manager templates. While the CLI and template examples are cross-platform, PowerShell (a Windows-centric tool) is given equal prominence and detailed examples. In the Resource Manager template section, Linux and Windows links are mentioned together, but the first explicit template example is for Linux. There is no evidence of missing Linux examples, but the presence of PowerShell examples and the explicit mention of PowerShell as a tab may indicate a slight Windows bias, especially for users who expect Bash or Linux shell scripting examples alongside PowerShell.
Recommendations
- Add explicit Bash shell scripting examples for Linux users, especially for automation tasks.
- Clarify in the Azure CLI section that it is fully supported on Linux, macOS, and Windows.
- Consider adding a note or tab for Bash or Linux shell usage, similar to the PowerShell tab.
- Ensure parity in example depth and detail between PowerShell and Linux/Bash scripting.
- Where PowerShell is mentioned, also mention cross-platform alternatives (e.g., Bash, Python, etc.) for scripting and automation.
Reliability
Azure Service Manager retirement
...-docs/blob/main/articles/reliability/asm-retirement.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows evidence of Windows bias, particularly in the migration guidance for Classic Virtual Network, which links to a PowerShell-based migration guide. The use of PowerShell as the primary or only migration tool is a Windows-centric pattern, and the migration link does not mention or provide Linux/CLI alternatives up front. While support links are provided for both Windows and various Linux distributions, the main migration documentation tends to favor Windows tools and patterns, with PowerShell examples appearing before or instead of Linux equivalents.
Recommendations
- Ensure migration guides include both PowerShell (Windows) and Azure CLI/Bash (Linux/macOS) examples, and link to them equally.
- Where PowerShell is referenced, add a parallel section or link for Azure CLI or REST API instructions.
- Review all migration documentation to confirm Linux users are not required to use Windows tools or environments.
- Explicitly mention cross-platform tooling in introductory sections to set parity expectations.
- Audit referenced migration guides for similar bias and update them to include Linux-first or cross-platform examples.