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 76-100 of 136 flagged pages
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
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-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 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 'Update scale set to add availability zones'), PowerShell is listed before REST API and after CLI. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no explicit Linux-specific command-line examples (e.g., Bash scripts), and the documentation does not mention Linux tools or patterns. The Resource Manager template section references both Linux and Windows getting started articles, but overall, there is a slight bias towards Windows/PowerShell in example prominence and ordering.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Add explicit Bash shell script examples for Linux users where relevant.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider including a note or section highlighting Linux/macOS parity and recommending CLI for those platforms.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides Azure Portal, Azure CLI, and Azure PowerShell examples for all attach/detach operations. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric, and its inclusion in every section (with full code samples) demonstrates a mild Windows bias. Additionally, PowerShell examples are consistently presented immediately after CLI, which may reinforce a Windows-first impression. However, there are no critical tasks that are Windows-only, and CLI parity is maintained throughout. No Linux/macOS-specific tools or shell examples are missing, but Bash or shell script examples are not explicitly shown.
Recommendations
  • Add explicit Bash/shell script examples for common attach/detach operations, or clarify that Azure CLI commands work identically on Linux/macOS.
  • Consider alternating the order of CLI and PowerShell examples, or explicitly state that CLI is cross-platform and recommended for Linux/macOS users.
  • Where possible, mention that PowerShell Core is available cross-platform, or clarify when examples are Windows PowerShell-specific.
  • Add a short note at the start of the 'Azure CLI' sections indicating that these commands are suitable for Linux/macOS/Windows.
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-08 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 Template. Portal instructions are also present. However, PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash, shell scripting) are provided, but Azure CLI is cross-platform and covers most needs. The ordering of examples (CLI first, PowerShell second) is a minor bias, but no critical functionality is Windows-only.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing Bash shell scripting examples for common tasks, or clarify that Azure CLI commands are suitable for Linux/macOS.
  • If possible, add a short section or callout for Linux/macOS users, confirming that all tasks can be completed with Azure CLI.
  • Review the ordering of examples to ensure CLI and ARM Template are prioritized for cross-platform parity.
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-08 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 templates. The PowerShell example is included alongside CLI and Portal, but CLI is shown before PowerShell. There is a slight bias toward Windows/PowerShell, as PowerShell is a Windows-centric tool, but the CLI example is cross-platform and appears first. No Windows-specific tools or patterns are mentioned exclusively, and Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell scripting examples for CLI usage, or clarifying that CLI commands work on Linux/macOS.
  • If possible, mention that PowerShell Core is available cross-platform, but traditional PowerShell is Windows-only.
  • Ensure that CLI and ARM template examples are always present and shown before PowerShell in future documentation.
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-08 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 (e.g., 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 CLI and PowerShell examples side-by-side or in parallel tabs, rather than consistently listing PowerShell first.
  • Ensure CLI examples are as detailed as PowerShell examples, especially for querying and updating resources.
  • Add explicit notes clarifying that Azure CLI works cross-platform (Linux/macOS/Windows), and PowerShell is available on Linux/macOS as well.
  • Where possible, provide Bash shell script examples for Linux users, especially in sections with only PowerShell code.
  • Review for any missing CLI equivalents and add them if absent.
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-08 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 are several areas where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in some code snippets and REST payloads. The PowerShell section is more verbose and detailed than the Bash example, and Windows-specific extension names/types are used in several places. Linux parity is generally good, but Windows bias is evident in ordering and emphasis.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail. Alternate the order of examples or present them side-by-side.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in all code snippets and REST payloads, and provide explicit Linux-focused examples.
  • Expand Bash/Python examples to match the detail and completeness of PowerShell examples, including troubleshooting and verification steps.
  • Where possible, use generic extension names/types in JSON and REST examples, or provide both Linux and Windows variants.
  • Review sample output and troubleshooting sections to ensure Linux commands and tools are as prominent as Windows/PowerShell equivalents.
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-08 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 the PowerShell section appears before the ARM template section. There is a slight 'windows_first' bias, as PowerShell is a Windows-centric tool, and its inclusion alongside CLI without mention of Bash or Linux-specific commands may create friction for Linux/macOS users. However, the CLI examples are present and fully functional for Linux/macOS users, and ARM templates are platform-agnostic.
Recommendations
  • Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider adding Bash shell script examples for Linux users, or clarifying that Azure CLI is the recommended tool for Linux/macOS.
  • In the 'Use Azure Resource Manager templates' section, clarify that both Linux and Windows images are supported, and link to both quick-create-template-linux.md and quick-create-template-windows.md 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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure CLI, Azure PowerShell, and portal instructions for attaching/detaching VMs to/from VM Scale Sets. While Azure CLI is cross-platform and examples use Ubuntu images, PowerShell examples are given equal prominence and are shown immediately after CLI, which may imply parity but can be seen as Windows-centric since PowerShell is most commonly used on Windows. There is a minor 'windows_first' bias in troubleshooting links, which reference Windows-specific documentation for disk conversion and proximity placement group operations, even though Linux equivalents exist.
Recommendations
  • Clarify that Azure PowerShell is available on macOS/Linux, or provide Bash examples where appropriate.
  • Ensure troubleshooting links reference both Windows and Linux documentation for disk conversion and proximity placement group operations.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all shown commands (CLI/PowerShell) are cross-platform unless there are platform-specific caveats.
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-05 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 a mild Windows bias in several areas. PowerShell examples are consistently present and sometimes shown before or alongside Linux equivalents. Windows-specific extension types (ApplicationHealthWindows) are used in code samples and REST payloads, sometimes before Linux equivalents. The REST and PowerShell sections use Windows extension types by default, and PowerShell is given equal or greater prominence than Bash. However, Linux parity is generally maintained, and CLI/Bash examples are present for all major workflows.
Recommendations
  • When showing extension type in JSON or REST samples, use ApplicationHealthLinux as the default or show both Linux and Windows variants.
  • In REST API examples, clarify that both ApplicationHealthLinux and ApplicationHealthWindows are valid, and provide explicit Linux-focused sample payloads.
  • Ensure Bash/Python examples are shown before or at least equally with PowerShell, especially in sections where Linux is the more common platform.
  • Add a note clarifying that all workflows are supported on both Linux and Windows VMSS, and highlight any platform-specific differences if present.
  • Consider adding more troubleshooting examples for Linux environments (e.g., systemd, firewall configuration) to match the PowerShell troubleshooting depth.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides usage instructions for Azure portal, REST API, Azure CLI, and Azure PowerShell. While all major cross-platform interfaces are covered, the PowerShell example is given its own section and is presented after CLI, which is cross-platform. The documentation does not show Linux-specific tools or shell examples (e.g., Bash/curl for REST API), and the PowerShell section may imply a slight Windows bias by highlighting PowerShell usage, which is most common on Windows.
Recommendations
  • Add explicit Bash/curl examples for the REST API section to demonstrate usage from Linux/macOS.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Consider listing CLI and REST API examples before PowerShell, or grouping them together to avoid implying a Windows-first workflow.
  • Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify when examples are 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-05 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 configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as setting/updating the rolling upgrade policy), the PowerShell tab appears immediately after CLI, which may imply a slight Windows-first orientation. There are no Linux-specific tools or shell script examples, but the Azure CLI commands are fully cross-platform. No critical functionality is locked to Windows-only tools, and ARM template examples are also provided.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Consider listing CLI examples before PowerShell in all sections, or explicitly note CLI is cross-platform.
  • Add a brief note for Linux/macOS users that PowerShell examples are optional and CLI is recommended for cross-platform automation.
  • If possible, provide Bash script snippets for common automation scenarios to further demonstrate Linux parity.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) examples. In some sections, only PowerShell examples are given for querying resources, with CLI shown later or not at all. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and Windows tools/patterns (PowerShell) are sometimes prioritized. However, most tasks can be completed using the CLI, which is cross-platform.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Ensure every PowerShell example has a corresponding Azure CLI example.
  • Where possible, provide Bash script snippets for Linux/macOS users, especially for tasks involving scripting or automation.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS to guide users.
  • Review sections where only PowerShell is shown (e.g., querying public IPs) and add CLI equivalents.
  • Avoid language that implies PowerShell is the default or preferred method unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides usage instructions for Spot Placement Score via Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section and is presented after the CLI example, but both are included. There is a slight 'Windows-first' bias as PowerShell is highlighted as a primary method, and the Azure portal instructions implicitly assume a graphical interface typical of Windows environments. However, Linux parity is generally maintained via REST API and Azure CLI instructions.
Recommendations
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI and REST API instructions before PowerShell to avoid implicit prioritization of Windows tooling.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell documentation.
  • Where possible, include example shell commands (e.g., Bash/curl) for REST API usage to further support Linux/macOS users.
GitHub Create Pull Request
← Previous Page 4 of 6 Next →