Virtual Machine Scale Sets

95
Total Pages
82
Linux-Friendly Pages
13
Pages with Bias
13.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

136 issues found
Showing 51-75 of 136 flagged pages
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-16 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. In some sections, PowerShell examples are more detailed or appear before CLI equivalents. Portal instructions are also included, but there is a slight tendency to present Windows-oriented tools first. No critical features are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by Linux/macOS users.
  • Ensure CLI and PowerShell examples are equally detailed and comprehensive.
  • Where possible, explicitly mention that Azure CLI works on Linux/macOS and provide bash-friendly syntax.
  • Add brief notes clarifying that PowerShell is available cross-platform, but CLI is native to Linux/macOS.
  • Review tab order in tabbed content to ensure CLI is not always after PowerShell.
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-16 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 custom metrics and the application health extension. However, there are several instances where Windows/PowerShell tools and patterns are mentioned or shown first, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. The PowerShell section is detailed and prominent, and Windows extension types are used in REST and PowerShell examples, while Linux types are only referenced in CLI. Overall, Linux parity is mostly present, but Windows bias is evident in ordering and sample emphasis.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, or alternate which is shown first in each section.
  • Explicitly show both ApplicationHealthLinux and ApplicationHealthWindows extension types in all relevant sample code (REST, PowerShell, CLI).
  • Add more Linux-specific troubleshooting and verification steps, such as systemd or firewall configuration examples.
  • Clarify in each example which OS it targets, and provide equivalent Linux and Windows instructions for all steps.
  • Consider adding macOS-specific notes where relevant, especially for Bash/Python scripts.
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-15 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 in greater detail. There is a slight preference for Windows/PowerShell in ordering and example depth, but Linux parity is generally maintained. No critical features are Windows-only, and Linux users can complete all tasks using CLI or ARM templates.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or in parallel, to avoid implicit Windows-first ordering.
  • Ensure CLI and PowerShell examples are equally detailed and comprehensive.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) to reassure non-Windows users.
  • Where possible, add Bash shell script examples for common Linux workflows.
  • Review for any subtle language that implies PowerShell is the default or preferred tool.
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-15 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 as a primary method. Additionally, the PowerShell example is shown before the ARM template example, and the CLI and PowerShell tabs are both present for update operations. There is a minor 'windows_first' bias in the order of examples and the explicit mention of PowerShell, which is primarily a Windows tool, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Ensure that Azure CLI examples are always shown before PowerShell examples, as CLI is cross-platform and PowerShell is primarily Windows-focused.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users, and PowerShell for Windows users.
  • Consider adding Bash shell script examples for Linux users where appropriate.
  • Clarify that all operations shown via PowerShell can also be performed via Azure CLI or ARM templates, and link to those sections.
  • Where possible, add notes about cross-platform compatibility for each tool.
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-15 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), as well as portal instructions. However, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows tool. In some cases, PowerShell examples are more verbose and detailed, which may subtly favor Windows users. Azure CLI is cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor any mention of Linux-specific considerations. PowerShell is presented as a first-class option, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing Bash/zsh shell command examples where relevant, or clarifying that Azure CLI commands work identically on Linux/macOS.
  • Add a note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • If PowerShell is required for some advanced scenarios, explain how Linux/macOS users can install and use PowerShell Core.
  • Review the order of examples: consider listing Azure CLI before PowerShell to reduce Windows-first bias.
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-15 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 presented alongside CLI, and in some cases, PowerShell is given its own section. The use of PowerShell is inherently Windows-centric, and there are no explicit Linux/macOS shell examples (e.g., Bash, zsh), nor are there references to Linux-specific tools or workflows. However, the Azure CLI is cross-platform and is presented first in most cases, mitigating the impact. No critical tasks are Windows-only.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the preferred cross-platform option.
  • Add explicit Bash/zsh shell examples where relevant, or note that Azure CLI commands can be run in Bash on Linux/macOS.
  • Consider grouping PowerShell examples under a 'Windows/PowerShell' heading to reinforce their platform specificity.
  • Add a short note in the 'CLI' sections indicating that these commands are suitable for Linux/macOS users.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM Template. The PowerShell example is present, which is Windows-centric, but the CLI example (az CLI) is cross-platform and appears before PowerShell. There are no exclusive Windows tools or patterns mentioned, and Linux/macOS users can fully complete the task using the CLI or ARM Template. However, the inclusion of PowerShell and its detailed example may slightly favor Windows users, and the PowerShell section is present before ARM Template, which could be seen as a minor ordering bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Consider adding explicit Bash or shell scripting examples for Linux users, if relevant.
  • Ensure parity in detail and explanation between CLI and PowerShell sections.
  • If possible, reorder sections so CLI appears before PowerShell, emphasizing cross-platform tools.
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-15 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 custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is evidence of Windows bias: PowerShell examples are often presented before or alongside Bash, and Windows-specific extension types (ApplicationHealthWindows) are used in several code snippets and REST examples, sometimes without clear Linux equivalents. The PowerShell section is more detailed and prominent, and Windows tools are referenced frequently. Linux examples are present but sometimes less emphasized or detailed.
Recommendations
  • Ensure Linux and Windows examples are equally detailed and prominent in all sections.
  • Where extension types are shown (e.g., ApplicationHealthWindows), also show ApplicationHealthLinux explicitly in REST and PowerShell examples.
  • In REST and CLI examples, clarify which values are for Linux and which for Windows, and provide both where applicable.
  • Consider presenting Bash/Linux examples before PowerShell/Windows examples, or alternate their order.
  • Add troubleshooting and verification steps for Linux (e.g., systemd, netstat, firewall-cmd) alongside Windows-specific guidance.
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-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 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 before CLI. There are no Linux-specific shell examples (e.g., Bash), but CLI commands are cross-platform. The documentation does not reference Windows-only tools or patterns outside PowerShell, and Linux parity is generally maintained, though minor Windows bias is evident in example ordering and tool emphasis.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows bias.
  • Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
  • Where possible, provide Bash shell script examples for Linux users, especially for tasks involving REST API calls.
  • Clarify in introductory sections that both PowerShell and CLI are supported, and highlight CLI as the default for cross-platform usage.
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-14 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 directly after CLI and before ARM templates. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) is appropriate, but the ordering may subtly prioritize Windows users. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks using the CLI. There are no missing Linux examples, but PowerShell is given equal prominence to CLI, which may not reflect the cross-platform usage patterns.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more widely used among Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Windows, Linux, and macOS, while PowerShell is primarily for Windows users (unless using PowerShell Core).
  • If possible, add brief guidance for macOS/Linux users about installing and using Azure CLI.
  • Maintain parity by ensuring all features shown in PowerShell are also available and demonstrated in CLI.
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-14 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 before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are detailed and prominent, and Windows tools/patterns (e.g., PowerShell HTTP server) are included alongside Linux examples. The REST API examples also default to Windows extension types. Overall, Linux parity is present but not always prioritized.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples in each section to avoid 'windows_first' bias.
  • Ensure REST API and JSON configuration samples alternate or default to ApplicationHealthLinux when not OS-specific.
  • Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused samples.
  • Expand troubleshooting and verification examples to include Linux-specific commands (e.g., systemctl, netstat) where appropriate.
  • Review sample output snippets to ensure they reference both Linux and Windows extension types equally.
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-14 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 in some cases, PowerShell examples are shown after CLI but before portal instructions. PowerShell is a Windows-centric tool, and its inclusion may signal a Windows bias, especially since Bash or Linux shell scripting alternatives are not mentioned. However, Azure CLI is cross-platform and the CLI examples use Linux VM images (e.g., Ubuntu2204), indicating some Linux parity. There are no Windows-only tools or patterns, and the documentation does not exclusively mention Windows tools. The bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add brief notes or links for Linux/macOS users clarifying that Azure PowerShell is available on Linux, but Bash scripting is also possible with Azure CLI.
  • Ensure that CLI examples use both Linux and Windows VM images to show parity.
  • If possible, provide Bash shell scripting examples for common tasks, or clarify that Azure CLI commands can be run in Bash.
  • In troubleshooting sections, ensure links to migration guides (e.g., unmanaged to managed disks) include both Windows and Linux documentation.
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-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
← Previous Page 3 of 6 Next →