Reliability

84
Total Pages
69
Linux-Friendly Pages
15
Pages with Bias
17.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (20)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-load-balancer.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/overview-reliability-guidance.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/regions-multi-region-nonpaired.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-storage-mover.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machines.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. In several sections, PowerShell (a Windows-centric tool) is listed before Azure CLI (which is cross-platform and often preferred by Linux users). For example, in the prerequisites for checking VM SKU availability, PowerShell is mentioned before Azure CLI. Similarly, in migration instructions, PowerShell is listed after CLI, but both are present. There are no sections where only Windows or PowerShell examples are given, and Linux-specific guidance is present where appropriate. However, the ordering and occasional emphasis on PowerShell can be perceived as a mild Windows-first bias.
Recommendations:
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
  • Where both PowerShell and Azure CLI are mentioned, clarify that both are fully supported and provide equal prominence.
  • Ensure that all command-line examples are provided for both Windows (PowerShell) and Linux (Azure CLI/Bash) where applicable.
  • Consider adding explicit Linux/Bash examples in addition to Azure CLI, especially for tasks commonly performed on Linux.
  • Review linked pages to ensure Linux parity is maintained in referenced documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-container-instances.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-app-gateway-v2.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively describes migration steps using the Azure portal UI and does not provide any command-line examples. There is no mention of Windows-specific tools, but there is also a lack of parity for Linux users, as no Azure CLI, PowerShell, or scripting examples are provided. This omission can disadvantage users who prefer or require command-line automation, particularly on Linux systems.
Recommendations:
  • Add Azure CLI examples for each migration step, as the CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are provided, ensure Azure CLI equivalents are also included and presented first or side-by-side.
  • Explicitly mention that the steps can be performed using the Azure CLI or ARM templates, and link to relevant documentation.
  • Include sample scripts or commands for common tasks (e.g., creating/deleting Application Gateway, updating DNS) using cross-platform tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/asm-retirement.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page is generally neutral and high-level, but there is evidence of subtle Windows bias. The migration link for 'Classic Virtual Network' specifically points to a PowerShell-based migration guide, which is typically associated with Windows environments. There are no explicit Linux command-line (e.g., Bash, Azure CLI) examples or migration guides referenced, and PowerShell is mentioned in the URL for the migration guide. Additionally, in the support links for VM (classic), 'Windows' is listed before specific Linux distributions, suggesting a Windows-first ordering.
Recommendations:
  • Wherever PowerShell-based migration guides are referenced, also provide links to Azure CLI or Bash-based guides for Linux users, if available.
  • Ensure that migration documentation for each resource includes both Windows and Linux command-line examples, or explicitly states if only one is supported.
  • In support tables or lists, alternate the ordering of Windows and Linux (or use alphabetical order) to avoid implicit prioritization.
  • Audit linked migration guides (e.g., for Classic Virtual Network) to ensure Linux users are not forced to use PowerShell and have clear, supported alternatives.
  • If PowerShell is required for certain migrations, clearly state this and explain any Linux workarounds or cross-platform options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-storage-mover.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/availability-zones-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for querying availability zone mappings, but the PowerShell example is presented immediately after the CLI example, and both are given equal prominence. There are no Linux-specific tools or shell (e.g., Bash) examples, but the Azure CLI is cross-platform. There is a slight 'windows_first' bias in that PowerShell is featured as the only alternative to the CLI, and no explicit mention is made of Linux-native scripting or tools.
Recommendations:
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Consider providing a Bash shell example (using curl/jq) for Linux users to query the REST API, in addition to the Azure CLI and PowerShell examples.
  • Clarify in the documentation that PowerShell examples are primarily for Windows users, while CLI and Bash are suitable for Linux.
  • Where possible, provide command-line examples in the order: Azure CLI (cross-platform), Bash (Linux/macOS), then PowerShell (Windows), to avoid implicit Windows-first ordering.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-load-balancer.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/overview-reliability-guidance.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-vm.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/regions-multi-region-nonpaired.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-sql-database.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/migrate-service-fabric.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-azure-container-apps.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but it lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and sometimes gives PowerShell examples more detailed coverage (e.g., with variable assignments and object construction). There are no Linux-specific shell examples (such as Bash), and the PowerShell examples may not be as familiar or accessible to Linux users. The documentation does not mention or provide parity for Linux-native tools or patterns, and the use of PowerShell may be perceived as Windows-centric.
Recommendations:
  • Ensure all command-line examples are provided in both Azure CLI (Bash/shell) and Azure PowerShell, but default to Azure CLI/Bash as the primary example since it is cross-platform.
  • Clearly indicate that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax for variable assignment and piping where appropriate.
  • If PowerShell is included, clarify that it is available cross-platform, or provide links to installation instructions for Linux/macOS.
  • Consider adding a section or note for Linux users, highlighting any differences or tips for running the commands in a Linux environment.
  • Avoid assuming the use of Windows tools or patterns unless they are required, and provide Linux-native alternatives where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-dns.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page focuses exclusively on Azure Portal and Azure CLI for DNS disaster recovery, without providing any Linux-specific or cross-platform command-line examples (e.g., Bash scripts, curl, dig, etc.). While Azure CLI is cross-platform, the absence of Linux-native tools or explicit Linux workflow guidance may disadvantage Linux users. There are no references to Windows-specific tools like PowerShell, but the examples and screenshots are Azure-centric, with no mention of Linux command-line utilities or integration patterns.
Recommendations:
  • Include Linux-native command-line examples (e.g., using dig or nsupdate to verify DNS changes).
  • Provide sample Bash scripts for automating DNS failover using Azure CLI on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if relevant.
  • Add troubleshooting steps or verification commands using common Linux tools.
  • Where screenshots are used, consider including CLI output or terminal examples to supplement Azure Portal UI steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machine-scale-sets.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/reliability/reliability-virtual-machines.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation demonstrates mild Windows bias by listing PowerShell/Windows methods before Linux/CLI equivalents in several places, and by sometimes referencing Windows-specific tooling (PowerShell) more prominently. However, Linux/CLI options are generally present, and there are dedicated Linux and Windows disaster recovery sections. No major Linux examples are missing, but ordering and emphasis slightly favor Windows.
Recommendations:
  • When listing methods (e.g., checking VM SKU availability, migrating VMs), alternate the order so that Linux/CLI and Windows/PowerShell are given equal prominence, or list CLI first as it is cross-platform.
  • Ensure that all examples and links are provided for both Linux (CLI) and Windows (PowerShell) wherever possible.
  • Where possible, use Azure CLI as the default example since it is cross-platform, and mention PowerShell as an alternative.
  • In prerequisite and migration sections, avoid always listing PowerShell/Windows first; consider grouping by tool type or platform.
  • Continue to provide dedicated Linux and Windows guidance for OS-specific procedures, but ensure parity in depth and clarity.