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 176-200 of 274 flagged pages
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-17 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 all major operations (attach, detach, move), but consistently lists Azure PowerShell examples after Azure CLI and before any Linux-specific guidance. There are no explicit Linux/macOS shell examples beyond Azure CLI, and PowerShell is presented as a primary scripting option, which is more relevant to Windows users. However, Azure CLI is cross-platform and the examples use Ubuntu images, so Linux users are not blocked.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
  • Consider providing Bash shell script examples for common operations, or clarify that Azure CLI is the preferred tool for Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
  • Ensure that CLI examples do not assume Windows-specific conventions (e.g., backslashes for line continuation).
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-02-17 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 major operations, but PowerShell examples are consistently presented after Azure CLI, and not before. However, in the PowerShell examples, the Application Health extension is shown using the Windows extension type ('ApplicationHealthWindows'), while the CLI example uses 'ApplicationHealthLinux'. This could cause confusion for Linux users following the PowerShell path. There are no Linux/macOS-specific command-line gaps, and all features are accessible via cross-platform tools (Azure CLI, REST API, Portal).
Recommendations
  • In PowerShell examples, clarify when to use 'ApplicationHealthWindows' vs. 'ApplicationHealthLinux' for the extension type, or provide both variants.
  • Add a note that Azure PowerShell is cross-platform, but that the extension type should match the VM OS.
  • Consider mentioning that Azure CLI is available on Windows, Linux, and macOS, and is recommended for Linux/macOS users.
  • Ensure that Linux-specific extension types are shown in PowerShell examples when the VM image is Linux.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for configuring the application health extension and custom metrics, but there is a mild Windows bias in several areas. In the 'Install the application health extension' section, PowerShell (Windows) and Azure CLI (cross-platform) are both shown, but REST and PowerShell examples use 'ApplicationHealthWindows' as the extension type, while CLI uses 'ApplicationHealthLinux'. In the sample application section, both Bash (Linux) and PowerShell (Windows) scripts are given, but the PowerShell example is more elaborate and prominent. Throughout, Windows tools (PowerShell) are consistently presented alongside cross-platform tools, sometimes before Linux alternatives. However, Linux parity is generally maintained, and the documentation is not Windows-only.
Recommendations
  • Ensure that all examples for extension installation and configuration explicitly show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' types, with clear guidance for each OS.
  • Where PowerShell and Bash examples are given, ensure both are equally detailed and prominent.
  • In REST API examples, provide sample payloads for both Linux and Windows extension types.
  • Where possible, present CLI (cross-platform) examples before PowerShell (Windows-only) examples.
  • Add clarifying notes about OS-specific extension types and commands to help users select the correct option.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation provides migration guidance for Azure Virtual Machine Scale Sets in Flexible orchestration. While the content is generally platform-neutral, there are a few minor instances of Windows bias: Windows/PowerShell is mentioned alongside Azure CLI and ARM templates, and Windows-specific scenarios (such as Windows VM activation and Windows updates) are listed before Linux equivalents. However, Linux scenarios (e.g., access to Linux package managers) are also mentioned, and most examples use Azure CLI, which is cross-platform.
Recommendations
  • Ensure Linux-specific migration scenarios (such as package manager access) are given equal prominence and detail as Windows scenarios.
  • Where PowerShell is referenced, provide Bash/Linux shell equivalents or clarify that Azure CLI is recommended for cross-platform users.
  • When listing common outbound connectivity scenarios, alternate the order or group Windows and Linux examples together to avoid 'windows_first' bias.
  • Consider including explicit Linux migration examples or references to Linux documentation where relevant.
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-17 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 all operations, but PowerShell is featured equally alongside CLI and is presented in a way that may imply parity. However, PowerShell is a Windows-centric tool, and no explicit Linux/macOS shell examples (e.g., Bash, shell scripting) are given. The CLI examples are cross-platform, but PowerShell is given its own section and is not clearly marked as Windows-only. Additionally, in some sections, PowerShell appears immediately after CLI, which may subtly prioritize Windows tools.
Recommendations
  • Clarify that PowerShell examples are intended for Windows users, and Azure CLI is cross-platform.
  • Consider adding explicit Bash or shell script examples where relevant, or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
  • In tabbed sections, consider labeling PowerShell as '(Windows)' and CLI as '(cross-platform)' to reduce ambiguity.
  • If possible, add notes for Linux/macOS users about installing and using Azure CLI, and link to relevant documentation.
  • Ensure that CLI examples are always shown first, or at least clarify their cross-platform nature.
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-17 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 or in greater detail. Portal instructions are also included, but there is no explicit Linux/macOS shell example or mention of Bash scripting, and PowerShell is referenced as a primary scripting method. However, Azure CLI (cross-platform) is present throughout, and ARM templates are used for platform-neutral configuration.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples where relevant, especially for tasks like querying public IPs.
  • Where PowerShell is used, clarify that Azure CLI is the recommended tool for Linux/macOS users.
  • Ensure parity in detail between PowerShell and CLI examples (e.g., if PowerShell shows multiple query methods, show equivalent CLI methods).
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-17 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and describes orchestration modes for Azure Virtual Machine Scale Sets, which support both Linux and Windows VMs. However, there is a minor bias in the example command for assigning a fault domain during VM creation, which uses Azure CLI syntax but does not explicitly show Linux shell or PowerShell alternatives. Additionally, some links reference Windows-specific managed identity configuration, but the overall guidance applies to both Linux and Windows. Windows is mentioned first in some mixed OS contexts, but Linux parity is maintained.
Recommendations
  • Provide explicit Linux shell and PowerShell examples for Azure CLI commands where relevant.
  • Clarify that Azure CLI commands work on both Linux and Windows platforms.
  • When referencing managed identity documentation, include links for both Linux and Windows VMSS setup.
  • Ensure that mixed OS examples alternate the order (e.g., 'Linux and Windows' vs. 'Windows and Linux') to avoid subtle ordering bias.
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-17 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 Linux-specific guidance. Additionally, the CLI examples use --generate-ssh-keys, which is Linux-centric, but there is no explicit mention of Linux/macOS compatibility or shell-specific instructions. The Resource Manager template section references both Linux and Windows getting started articles, but the PowerShell section could be perceived as Windows-centric due to its prominence and detail.
Recommendations
  • Ensure that Azure CLI examples are presented before PowerShell, as CLI is cross-platform and more relevant for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
  • Add bash/zsh shell example blocks where appropriate, especially for update operations.
  • Clarify that PowerShell is primarily for Windows users, and recommend CLI for Linux/macOS.
  • Consider adding a short section or note about Linux/macOS compatibility for each method.
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-16 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 PowerShell examples are always present and shown alongside CLI. PowerShell is a Windows-centric tool, and its inclusion in every section, with detailed parameters, creates a mild Windows bias. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, the Azure CLI is cross-platform and is included throughout, ensuring Linux/macOS users can complete all tasks. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive.
Recommendations
  • Ensure Azure CLI examples are as detailed as PowerShell examples, including all relevant parameters.
  • Consider listing Azure CLI examples before PowerShell examples, or clarifying that Azure CLI is recommended for cross-platform use.
  • Add a brief note explaining that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
  • If possible, provide Bash script examples for advanced scenarios, or link to Azure CLI scripting guides 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-16 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 often detailed. While Azure CLI is cross-platform, PowerShell is primarily used on Windows, and its inclusion may signal a Windows bias. However, Linux/macOS users can fully use the Azure CLI and ARM templates, and no critical functionality is Windows-only. The ordering sometimes puts PowerShell after CLI, but both are always present.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider adding brief notes for Linux/macOS users, e.g., 'Azure CLI commands can be run on Linux, macOS, and Windows.'
  • If possible, include Bash shell script examples for common tasks, or link to Azure CLI Bash usage guides.
  • Ensure that PowerShell is not presented as the default or primary method, but as an alternative for Windows users.
  • Explicitly mention that all features are available via CLI and ARM templates, regardless of OS.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.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 Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples are consistently presented alongside or immediately after CLI examples, and in some cases, the PowerShell extension used is 'ApplicationHealthWindows', which may be confusing for Linux users. The documentation does not provide Linux shell-specific examples (e.g., Bash scripts), but since Azure CLI is cross-platform, Linux users are not blocked. There is a slight bias in the ordering and in the PowerShell-centric explanations, but Linux parity is largely maintained.
Recommendations
  • Clarify in PowerShell examples when the extension is for Windows VMs and provide the correct extension name for Linux VMs if different.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform usage.
  • Consider providing a Bash script example for end-to-end automation on Linux.
  • In PowerShell examples, mention that PowerShell Core is available cross-platform, or clarify if examples require Windows PowerShell.
  • Ensure that the Application Health extension example in PowerShell uses 'ApplicationHealthLinux' when the VM image is Linux, to avoid confusion.
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-16 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, but does not explicitly show Linux-specific commands or mention Linux tools. The only CLI example uses Azure CLI, which is cross-platform, but the documentation does not clarify that it works on Linux/macOS. The mention of Azure Site Recovery 'via PowerShell' in the backup table could imply a Windows bias, as PowerShell is traditionally Windows-centric, though PowerShell Core is cross-platform. There are no explicit Linux/macOS examples or references, and Windows is mentioned first in some contexts (e.g., 'Mix operating systems | Yes, Linux and Windows can reside...').
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Add explicit Linux/macOS command examples where relevant (e.g., bash syntax, shell environment setup).
  • For features like Azure Site Recovery, specify if PowerShell Core is supported on Linux/macOS, or provide equivalent Azure CLI examples.
  • Ensure parity in mentioning operating systems (e.g., 'Linux and Windows' instead of 'Windows and Linux').
  • Where VM extensions or health monitoring are discussed, note any OS-specific requirements or differences.
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-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 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 presented immediately after CLI and before REST API. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), and the documentation does not mention Linux-specific tools or patterns. The ARM template section references both Linux and Windows getting started articles, but does not provide explicit Linux shell commands.
Recommendations
  • Add Bash shell examples alongside PowerShell, especially for update operations.
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider reordering examples to show CLI first, then PowerShell, to reinforce cross-platform parity.
  • Add clarifying notes for Linux/macOS users where PowerShell is referenced, suggesting CLI as the alternative.
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-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
← Previous Page 8 of 11 Next →