Virtual Machine Scale Sets

95
Total Pages
80
Linux-Friendly Pages
15
Pages with Bias
15.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

274 issues found
Showing 201-225 of 274 flagged pages
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes examples for the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-centric, and PowerShell is presented as a primary method alongside CLI. Additionally, PowerShell is listed before ARM templates, which may subtly prioritize Windows tooling.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is Windows-centric.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform accessibility.
  • Add explicit notes or guidance for Linux/macOS users, such as recommending Azure CLI or ARM templates.
  • If possible, provide Bash shell scripting examples for common tasks.
  • Ensure parity in documentation structure and visibility for Linux/macOS-friendly tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally neutral and cross-platform, describing orchestration modes for Azure Virtual Machine Scale Sets without explicit Windows bias. However, in the 'Managed Identity' row of the comparison table, the link for configuring User Assigned Identity points to a Windows VMSS-specific guide, and the order of mention for Linux and Windows in 'Mix operating systems' puts Windows first. There are no PowerShell-only examples, Windows tools, or missing Linux examples. The Azure CLI is used for command-line examples, which is cross-platform.
Recommendations
  • Update the 'Managed Identity' link to reference both Linux and Windows VMSS configuration guides, or use a neutral landing page.
  • In 'Mix operating systems', mention Linux first or clarify parity.
  • Review linked guides and ensure Linux parity in referenced documentation.
  • Explicitly state that all features and examples apply equally to Linux and Windows unless otherwise noted.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), Windows-specific tooling is highlighted separately. The ordering of examples sometimes places PowerShell before Linux-focused tools, and there is no explicit Bash or Linux shell example (though Azure CLI is cross-platform). The Resource Manager template section does link to both Linux and Windows quick-starts, but overall, Windows tools and patterns are mentioned as much as Linux equivalents.
Recommendations
  • Ensure that Azure CLI examples are shown first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples where relevant, especially for update operations.
  • Clarify that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
  • Where possible, provide parity in example scripts for Linux and Windows environments.
  • Consider adding a note about cross-platform support for Azure CLI and ARM templates.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension and custom metrics. However, there are several instances where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell usage is prominent, and Windows tools/patterns are referenced alongside their Linux equivalents, but sometimes Windows terminology or examples appear before Linux ones. The REST API examples also default to ApplicationHealthWindows, though ApplicationHealthLinux is mentioned.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail.
  • Alternate the order of examples so Linux/Bash is not always after Windows/PowerShell.
  • In REST and JSON samples, use ApplicationHealthLinux as the default or provide both Linux and Windows variants.
  • Clarify that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide guidance for Linux users where Windows-specific terminology is used.
  • Where possible, avoid Windows-centric language (e.g., referencing Windows extension types first) unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, Portal, and ARM templates. PowerShell examples are present throughout, and in some sections (such as 'Restart a rolling upgrade'), PowerShell is shown before ARM templates or other options. However, Azure CLI is always present and is cross-platform, so Linux/macOS users can complete all tasks. There are no Windows-only tools or commands, but PowerShell is emphasized, which may create friction for non-Windows users.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell script examples where relevant, especially for automation.
  • Where PowerShell is shown, clarify its availability on Linux/macOS (via PowerShell Core), or link to guidance for installing PowerShell on those platforms.
  • Ensure CLI examples are always shown first, as they are most universally accessible.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Scanned: 2026-02-13 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 PowerShell examples for most tasks, but PowerShell examples are often shown before CLI, and some sections (such as querying public IPs) provide more detailed PowerShell usage. Portal instructions are generic and not OS-specific, but PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, CLI and ARM template examples are present throughout, ensuring Linux parity for most tasks.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
  • Ensure all PowerShell examples are matched with equivalent Azure CLI examples, especially for querying and managing resources.
  • Explicitly mention that Azure CLI is available on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Where possible, add Bash shell script examples for advanced scenarios.
  • Review sections where PowerShell is used for querying (e.g., public IPs) and ensure CLI examples are equally detailed.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-13 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 creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence and sometimes appear before Linux-oriented CLI examples. The PowerShell examples are Windows-centric, and there is no explicit mention of Linux/macOS alternatives for PowerShell commands. The CLI examples are cross-platform, but the documentation does not clarify this. There is minor bias in the ordering and prominence of Windows tools.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
  • Consider listing Azure CLI examples before PowerShell examples to prioritize cross-platform guidance.
  • Add a note clarifying that PowerShell examples are for Windows users, and suggest CLI for Linux/macOS users.
  • Ensure parity in example detail and completeness between CLI and PowerShell sections.
  • Where possible, provide bash shell script snippets for Linux users alongside CLI examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides example commands for Azure CLI, Azure PowerShell, and ARM templates. While the Azure CLI and ARM templates are cross-platform, the PowerShell examples are Windows-centric and are presented with equal prominence as CLI examples. The ARM template section references both Linux and Windows getting started articles, but does not provide explicit Linux-specific examples or highlight Linux workflows. In some sections, Windows tooling (PowerShell) is mentioned before Linux-friendly alternatives (CLI), and there is no explicit parity check for Linux/macOS users in PowerShell sections.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add explicit Linux/macOS notes or examples where PowerShell is referenced, clarifying CLI as the preferred method for those platforms.
  • Where ARM templates are shown, provide a brief Linux-specific deployment example (e.g., using Azure CLI or Bicep on Linux).
  • Consider adding a table or section summarizing platform compatibility for each method.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but consistently presents PowerShell examples immediately after CLI and before ARM templates. PowerShell is a Windows-centric tool, and its inclusion (with detailed examples) may create friction for Linux/macOS users who do not use PowerShell. However, Azure CLI is cross-platform and all tasks can be completed using it, so Linux/macOS users are not blocked. The documentation does not reference Windows-only tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
  • Consider explicitly stating that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that PowerShell examples are primarily for Windows users, while Azure CLI works on all platforms.
  • If possible, show Azure CLI examples first, or clarify that the order is not indicative of platform preference.
  • Ensure screenshots and UI instructions are not Windows-specific (they are currently Azure Portal, which is platform-neutral).
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation references both Azure CLI and Azure PowerShell for creating and managing Virtual Machine Scale Sets, but Azure PowerShell (a Windows-centric tool) is mentioned equally alongside Azure CLI. Windows-specific scenarios (activation, updates) are listed before Linux equivalents in the networking section. However, Linux is acknowledged (e.g., package managers), and most examples use Azure CLI, which is cross-platform. No critical migration steps are Windows-only, but minor ordering and tool parity issues exist.
Recommendations
  • Ensure Linux-specific migration scenarios (such as package manager access) are given equal prominence and detail as Windows scenarios.
  • Where Azure PowerShell is referenced, provide equivalent Bash/Azure CLI examples first, or clarify cross-platform support.
  • Explicitly mention that Azure CLI is fully cross-platform and recommend it as the default for non-Windows users.
  • Consider adding links or examples for Linux-specific troubleshooting (e.g., outbound connectivity for apt/yum).
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. In the 'Configure rolling upgrades with MaxSurge' section, the PowerShell example is presented immediately after the CLI example, and both are given equal prominence. However, the CLI example uses Azure CLI, which is cross-platform, and the PowerShell example is Windows-centric. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the Azure CLI example is sufficient for Linux/macOS users. The ordering of examples (CLI first, then PowerShell) is appropriate, but the presence of PowerShell may create minor friction for Linux/macOS users if they are unclear about which tools to use.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Explicitly state that PowerShell examples are for Windows users, and Azure CLI is suitable for Linux/macOS.
  • Consider adding a Bash shell example for invoking Azure CLI commands, or note that Azure CLI commands can be run in Bash or other shells.
  • Ensure that all screenshots and instructions in the Portal section are platform-neutral.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a conceptual overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, there is a minor bias in the 'Managed Identity' row of the comparison table, where the link for configuring User Assigned Identity points to a Windows VMSS-specific guide. Additionally, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, which may imply a Windows-centric tool, though PowerShell is cross-platform. All examples and commands use Azure CLI or Resource Graph, which are platform-agnostic. No critical sections are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Replace or supplement the User Assigned Identity link with a platform-neutral or Linux-specific guide, or clarify that the process is similar for Linux VMSS.
  • Clarify that Azure Site Recovery via PowerShell is supported on Linux/macOS as well, or provide Bash/Azure CLI alternatives if available.
  • Continue to use Azure CLI and Resource Graph for examples, and ensure any links or references are not Windows-specific unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) give more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or at least side-by-side, to avoid implicit Windows-first bias.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and managing resources.
  • Add explicit notes clarifying that Azure CLI commands work cross-platform (Linux, macOS, Windows).
  • Where possible, include Bash shell script snippets for complex CLI operations.
  • Review for any PowerShell-only guidance and provide CLI alternatives.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is evidence of Windows bias. PowerShell examples and Windows-specific extension types (ApplicationHealthWindows) are frequently shown alongside or before Linux equivalents. In several code samples, Windows tools and patterns (PowerShell, Add-AzVmssExtension, ApplicationHealthWindows) are mentioned, sometimes before Linux tools. The CLI and REST examples are neutral, but PowerShell is given equal or greater prominence than Bash, and Windows extension types are referenced in multiple places. The documentation does not omit Linux examples, but Windows-specific terminology and tools are often foregrounded.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with Linux shown first in some sections.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows, and provide explicit Linux-focused extension install examples (e.g., az vmss extension set with ApplicationHealthLinux).
  • Add explicit notes or tables summarizing which commands and extension types are for Linux vs Windows, to avoid confusion.
  • Where PowerShell is used, ensure Bash/Linux alternatives are always present and equally detailed.
  • Review ordering of examples and terminology to avoid defaulting to Windows-first language.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs), but consistently includes PowerShell examples alongside CLI, and sometimes gives PowerShell examples more parameters or detail. The PowerShell examples are Windows-centric, and the documentation refers to Azure PowerShell as a primary tool, which is mainly used on Windows. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), and all operations are possible via CLI. The order of examples (portal, CLI, PowerShell) is neutral, but the presence of PowerShell in every section may subtly signal Windows as a primary platform.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (via PowerShell Core), or explicitly mention Linux/macOS compatibility.
  • Add notes or links for Linux/macOS users about installing and using Azure CLI and PowerShell Core.
  • Ensure CLI examples are as detailed as PowerShell ones, especially regarding networking and advanced parameters.
  • Consider including Bash or shell script snippets for common Linux workflows, or referencing them where appropriate.
  • If PowerShell is included for completeness, explicitly state that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides Azure CLI and Resource Graph examples, which are cross-platform, but does not include any OS-specific commands or tools. However, there is a minor bias in the order and phrasing: Windows and Linux are mentioned together, but Windows is sometimes listed first (e.g., 'Mix operating systems: Yes, Linux and Windows can reside in the same Flexible scale set'). Additionally, the Azure Site Recovery feature is noted as 'Yes (via PowerShell)' for Flexible orchestration, but no Linux equivalent or cross-platform CLI example is provided. Overall, the documentation is largely neutral and cross-platform, but could improve Linux parity by ensuring examples and feature descriptions explicitly mention Linux support and alternatives where relevant.
Recommendations
  • When referencing Azure Site Recovery, provide cross-platform CLI examples or clarify if PowerShell is required for all OS types.
  • Ensure that Linux is mentioned equally or first in mixed OS contexts to avoid subtle Windows-first bias.
  • Explicitly state when features or extensions are supported for Linux VMs, not just Windows.
  • Add sample commands for Linux users where possible, especially for VM extension installation and monitoring.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Scanned: 2026-02-10 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 PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples first or exclusively. Portal instructions are platform-neutral, but there is a slight tendency to favor Windows/PowerShell patterns in example ordering and coverage.
Recommendations
  • Ensure CLI and PowerShell examples are presented side-by-side or with CLI first, as CLI is cross-platform.
  • Where PowerShell is used, always provide equivalent CLI commands, especially for querying and updating resources.
  • Explicitly note that Azure CLI works on Linux/macOS and Windows, and encourage its use for cross-platform scenarios.
  • Review example ordering to avoid consistently placing PowerShell before CLI.
  • Add bash scripting examples where relevant for Linux users.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-02-10 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 PowerShell examples for all operations, but PowerShell examples are always shown after CLI and are present for every task. There are no Linux-specific examples or mentions of Linux tools, but the CLI examples are cross-platform. The documentation does not show explicit Windows bias in critical sections, but the presence of PowerShell examples for every operation and lack of explicit Linux/macOS shell examples (e.g., Bash) may create minor friction for Linux users.
Recommendations
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell script examples for common tasks, or explicitly mention that CLI commands can be run in Bash, Zsh, etc.
  • Where PowerShell is mentioned, note that it is available on Linux/macOS, or provide links to installation instructions for PowerShell Core on non-Windows platforms.
  • Ensure parity in example ordering: consider showing CLI (cross-platform) examples first, or note their cross-platform nature more prominently.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for extension installation. However, there are several signs of Windows bias: PowerShell examples are often shown alongside or before Bash, and Windows-specific extension types ('ApplicationHealthWindows') are used in several code snippets and REST examples, sometimes without clear Linux equivalents. The PowerShell tab is present for nearly every example, and Windows tools (PowerShell, Windows extension type) are referenced frequently. While Linux parity is mostly present, Windows terminology and tools are often prioritized or shown first.
Recommendations
  • Ensure Linux and Windows extension types are both shown in REST and JSON examples, or clarify when to use each.
  • Alternate the order of Bash and PowerShell examples, or show Bash first where possible.
  • Explicitly mention Linux-specific instructions and tools where relevant, such as using 'ApplicationHealthLinux' in extension configuration.
  • Add clarifying notes about OS-specific extension types and settings.
  • Review sample outputs to ensure both Linux and Windows variants are represented.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-10 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 creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), PowerShell is presented before ARM template examples. The CLI examples are cross-platform, but PowerShell is Windows-centric. There is minor bias in the ordering and prominence of PowerShell, but Linux users can complete all tasks using the CLI or ARM templates. No Linux-specific shell examples (e.g., Bash) are provided, but the CLI covers Linux needs.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are primarily for Windows users.
  • Add a note that all tasks can be completed on Linux/macOS using Azure CLI and ARM templates.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of migrating to Azure Virtual Machine Scale Sets in Flexible orchestration, but in the 'Create scalable network connectivity' section, Windows scenarios (activation, updates) are listed before Linux scenarios (package managers). There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; Azure CLI is used for code snippets, which is cross-platform.
Recommendations
  • When listing common outbound connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates.
  • Explicitly state that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
  • Consider adding a brief example or note for Linux-specific migration considerations if relevant (e.g., SSH key handling, package updates).
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs). However, PowerShell examples are always present and shown alongside CLI, which is cross-platform but often associated with Linux/macOS users. The PowerShell examples are more verbose and detailed, sometimes including Windows-centric parameters (e.g., OpenPorts 3389 for RDP). In most sections, Azure CLI is shown before PowerShell, but both are always included. There are no missing Linux examples, as Azure CLI covers Linux/macOS scenarios. No Windows-only tools or patterns are mentioned, and the documentation is not Windows-specific.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Consider adding explicit Bash or shell script examples where relevant, especially for automation scenarios.
  • Review PowerShell examples for Windows-centric parameters (e.g., OpenPorts 3389) and add Linux-relevant ports (e.g., SSH 22) or notes for Linux users.
  • Ensure parity in detail between CLI and PowerShell examples; if PowerShell includes extra networking or security group parameters, add similar CLI examples.
  • Add a short section or note for Linux/macOS users confirming that all operations are supported via Azure CLI and portal.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but PowerShell examples are consistently shown alongside CLI and portal, and are sometimes more detailed. There is a mild 'windows_first' bias in that PowerShell is presented as a primary scripting option, but Azure CLI is cross-platform and is always included. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using the Azure CLI. There are no missing Linux examples, but the PowerShell presence may suggest Windows-centric workflows.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Consider explicitly mentioning Bash or shell scripting in CLI examples to reinforce Linux parity.
  • Add a note that PowerShell examples are for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Ensure that CLI examples are as detailed as PowerShell ones, if any discrepancies exist.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Scanned: 2026-02-09 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 PowerShell examples for most tasks, but PowerShell examples are often listed before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or exclusively. There is a slight preference for Windows/PowerShell tooling in example ordering and coverage, but Linux parity is generally maintained through CLI and ARM template examples.
Recommendations
  • Ensure CLI examples are always provided alongside PowerShell, especially for tasks like querying public IP addresses.
  • Present CLI and PowerShell examples in parallel tabs, or alternate their ordering to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) and highlight this in introductory sections.
  • Where possible, add Bash scripting examples for advanced scenarios to further support Linux users.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and application health extension responses. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and PowerShell is given equal or greater prominence. The REST and Azure CLI examples are platform-neutral, but the PowerShell sections are detailed and appear before Bash in some places. The documentation also uses Windows-centric extension names (e.g., ApplicationHealthWindows) in some sample code, though Linux equivalents are mentioned.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples, or alternate their order for parity.
  • Ensure that both ApplicationHealthLinux and ApplicationHealthWindows are equally referenced in sample code and explanations.
  • Clarify in sample code comments which extension type to use for Linux vs. Windows VMSS instances.
  • Expand Bash/Python examples to match the detail level of PowerShell examples.
  • Add explicit notes for macOS users where Bash/Python examples are applicable.
GitHub Create Pull Request
← Previous Page 9 of 11 Next →