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 101-125 of 136 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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching/detaching VMs to/from scale sets. In each code example section, PowerShell is presented as a primary option alongside CLI, and the PowerShell examples use Windows-centric syntax (backticks, cmdlets). The CLI examples are cross-platform, but PowerShell is Windows-first and not natively available on Linux/macOS. Additionally, in troubleshooting, links for disk migration and proximity placement group removal point to Windows VM documentation, even though the feature is not Windows-specific.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform via PowerShell Core, or provide Bash/shell script equivalents for Linux/macOS users.
  • Where links point to Windows-specific documentation for generic VM features (e.g., managed disk migration, proximity placement group removal), add or reference Linux VM documentation as well.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all operations can be performed on both Windows and Linux VMs, and provide example commands for both where configuration or parameters differ.
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-04 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) ones. In some sections, PowerShell is the only example given for querying resources, or CLI examples are less detailed. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and some verification steps use PowerShell exclusively. However, the majority of configuration is done via Azure CLI, ARM templates, or REST API, which are cross-platform.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to reduce Windows-first perception.
  • Ensure every PowerShell example has an equivalent Azure CLI example, especially for verification and querying tasks.
  • Where possible, include Bash script snippets for Linux/macOS users, especially for tasks that might involve scripting.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Review sections where only PowerShell is used for querying or updating resources and add CLI equivalents.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but there are subtle signs of Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents (e.g., Linux package manager access), and there are no explicit Linux-focused migration examples or CLI commands. All command-line examples use Azure CLI, which is cross-platform, but the documentation does not provide Linux-specific considerations or troubleshooting steps, nor does it mention Linux tools or patterns where relevant.
Recommendations
  • Add explicit Linux migration scenarios, such as handling SSH keys, cloud-init, or Linux-specific VM extensions.
  • When listing outbound connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Include troubleshooting steps or references for common Linux VM migration issues (e.g., hostname changes, network configuration, package updates).
  • Provide examples of Linux VM extension usage or configuration in Flexible orchestration mode.
  • Ensure that any references to PowerShell are accompanied by Bash/Azure CLI equivalents, if 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-04 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 tasks, but PowerShell examples are consistently presented after CLI and before ARM template examples. PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias, especially since Linux/macOS users typically use Azure CLI or ARM templates. However, all CLI examples are cross-platform and presented first, and no Windows-only tools or patterns are used. There are no missing Linux examples, and all instructions are applicable to Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Consider adding Bash script examples for common automation scenarios to further demonstrate Linux parity.
  • Clarify in introductory sections that all features described are available regardless of VM OS, unless otherwise noted.
  • If possible, add a short note for each code tab indicating platform compatibility (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows').
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-04 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 the application health extension response and installation. However, there are several instances where Windows/PowerShell examples are presented before or alongside Linux equivalents, and PowerShell is given equal prominence to Bash, which may create minor friction for Linux/macOS users. The extension installation and querying sections use both Azure CLI and PowerShell, but PowerShell is not relegated to a secondary position, and the REST API is presented last. There are no critical omissions of Linux instructions, and the documentation explicitly supports both ApplicationHealthLinux and ApplicationHealthWindows extension types.
Recommendations
  • Present Linux/Bash/Azure CLI examples before Windows/PowerShell examples in each tabbed section to reflect the majority usage on Azure and avoid implicit prioritization of Windows.
  • Clarify in introductory sections that all steps and features apply equally to both Linux and Windows VMSS instances.
  • Where possible, add explicit macOS notes or examples (e.g., for running the Python HTTP server) to further improve parity.
  • Ensure that REST API examples use ApplicationHealthLinux in at least one snippet to reinforce Linux support.
  • Consider grouping CLI and Bash examples together, and PowerShell separately, to make it easier for Linux/macOS users to follow.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching and detaching VMs to/from scale sets. In each case, Azure PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. The CLI examples use Ubuntu images, showing Linux is supported, but PowerShell is always listed as a primary method, and examples are not explicitly labeled as Windows-only. The troubleshooting section links to some Windows-specific docs (e.g., converting unmanaged disks, proximity placement groups) without Linux equivalents or clarifying applicability.
Recommendations
  • Clearly label Azure PowerShell examples as Windows-only, and note that PowerShell is primarily for Windows users.
  • Provide Bash or shell script equivalents for Linux/macOS users where PowerShell is shown.
  • Ensure troubleshooting links and migration steps reference both Windows and Linux documentation where applicable (e.g., disk migration, proximity placement group removal).
  • Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add a brief note at the top clarifying that Azure CLI is recommended for Linux/macOS users, while PowerShell is for Windows.
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-03 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 creating and updating scale sets with Availability Zones, but PowerShell examples are given equal prominence to CLI, and are shown before REST/ARM template examples. While CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux/macOS, it's less commonly used there). The documentation does not provide any Linux/macOS-specific shell examples (e.g., Bash), nor does it clarify CLI usage on Linux/macOS. The ARM template section does link to both Linux and Windows quickstart articles, but in the main walkthrough, Windows-centric tooling (PowerShell) is featured as a primary method.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider providing Bash shell examples for Linux/macOS users, especially for common operations like az vmss create.
  • If PowerShell is shown, clarify its cross-platform availability, but note that CLI is the recommended tool for Linux/macOS.
  • Ensure that Linux/macOS users are not left to infer that PowerShell is required.
  • In the 'Use Azure Resource Manager templates' section, clarify parity between Linux and Windows deployments, and ensure links to both quickstart guides are equally visible.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and references for both Windows and Linux scenarios, but Windows-specific tasks (such as VM activation and Windows updates) are mentioned before Linux equivalents, and there are no explicit Linux/PowerShell/Bash command examples or Linux migration patterns shown. The CLI example is generic, but the narrative and troubleshooting links prioritize Windows use cases.
Recommendations
  • Include explicit Linux migration considerations and examples, such as package manager connectivity requirements (apt/yum) and troubleshooting steps for Linux VMs.
  • Provide CLI or script examples for Linux environments (e.g., Bash, cloud-init) alongside PowerShell or generic Azure CLI examples.
  • Balance the order of mention between Windows and Linux scenarios (e.g., discuss Linux package manager connectivity before or alongside Windows activation and updates).
  • Reference Linux-specific documentation for troubleshooting and best practices 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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for Azure CLI, PowerShell, Portal, and ARM templates. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and detail, and are presented immediately after CLI in each section. There is a slight Windows-first bias in the ordering and inclusion of PowerShell examples, which are primarily relevant to Windows users. However, all critical tasks (configuring, monitoring, canceling, and restarting rolling upgrades) can be completed using the cross-platform Azure CLI, and no functionality is locked to Windows/PowerShell tools.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI examples before PowerShell in each section to reinforce Linux parity.
  • Add a short note in each PowerShell section clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions for PowerShell on non-Windows platforms.
  • Where possible, clarify that all operations can be performed via CLI, and PowerShell is an alternative for those who prefer it.
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-03 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) equivalents. In some sections, only PowerShell is shown for querying resources, with CLI examples provided separately or later. There is a slight tendency to mention Windows tools or patterns first, and some examples (such as querying public IPs) are more detailed for PowerShell than CLI. No Linux-specific shell examples (e.g., bash scripts) are given, and the documentation does not reference Linux-native tools or patterns outside of Azure CLI.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and managing resources.
  • Add explicit notes or examples for Linux/macOS users where CLI usage may differ (e.g., environment variables, shell syntax).
  • Consider including bash script snippets or references to Linux-native tools where relevant.
  • Clarify that Azure CLI is the recommended tool for cross-platform scenarios.
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-03 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 covers Azure CLI, PowerShell, and REST API for extension installation and querying. However, in several places, Windows/PowerShell examples are presented before Linux/Bash equivalents, and PowerShell scripts are detailed and prominent. The extension installation section lists PowerShell after CLI, but the PowerShell example is more verbose and detailed. The extension type examples use both ApplicationHealthLinux and ApplicationHealthWindows, but the REST API and PowerShell samples default to Windows extension types. There is a slight preference for Windows tools and ordering, but Linux parity is generally maintained.
Recommendations
  • Ensure that Linux examples (Bash, Python) are presented before or alongside Windows/PowerShell examples, especially in sections where ordering implies priority.
  • In REST API examples, alternate between ApplicationHealthLinux and ApplicationHealthWindows for extension type, or explicitly show both.
  • Clarify in introductory sections that all examples are available for both Linux and Windows VMSS instances.
  • Where possible, balance the detail level between Bash and PowerShell scripts, so Linux users have equally comprehensive guidance.
  • Consider adding a table or note summarizing OS-specific extension types and usage patterns for clarity.
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-02 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 responses and installing the application health extension. However, there are several instances of Windows bias: PowerShell examples are often presented before or alongside Linux equivalents, Windows extension types (ApplicationHealthWindows) are shown first in some code blocks, and Windows-specific tools (PowerShell cmdlets) are given equal prominence to cross-platform CLI commands. The REST API and Azure CLI examples are cross-platform, but some sections (such as the PowerShell install and response server) are more detailed than their Linux counterparts.
Recommendations
  • Ensure Linux and Windows examples are presented with equal detail and prominence; consider alternating which is shown first.
  • In code samples where both ApplicationHealthLinux and ApplicationHealthWindows are referenced, clarify which to use for each OS and provide explicit examples for both.
  • Add more troubleshooting and verification steps for Linux environments, such as systemd service setup or firewall configuration.
  • Where PowerShell scripts are provided, ensure Bash/Linux equivalents are equally comprehensive.
  • Review sample outputs and ensure they do not default to Windows extension types unless contextually appropriate.
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-02 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 examples, and in some sections (such as the restart operation), PowerShell is shown after CLI but with detailed scripting. There is a slight 'windows_first' bias in that PowerShell is featured as a primary method alongside CLI, and no explicit mention is made of Linux/macOS shell environments (e.g., Bash), though the Azure CLI commands are cross-platform. No Windows-only tools or patterns are exclusively mentioned, and all tasks can be completed using Azure CLI, which works on Linux/macOS. There are no missing Linux examples, but the documentation could clarify CLI parity and avoid implying PowerShell is required.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is optional.
  • Consider mentioning Bash or shell scripting for Linux/macOS users where appropriate.
  • Add a note in the PowerShell sections that these commands are for users who prefer PowerShell, and that all operations can be performed using Azure CLI on any OS.
  • Ensure that CLI examples are shown first or equally with PowerShell to avoid perceived prioritization of Windows environments.
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-01 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, but both CLI and PowerShell are covered. There is a slight Windows bias in that PowerShell is called out specifically, and the ordering of examples (portal, REST, CLI, PowerShell) puts PowerShell before any Linux/macOS-specific shell scripting examples. However, Azure CLI is cross-platform and is documented with equal detail. No examples are missing for Linux/macOS users, and the REST API is platform-agnostic.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider adding a Bash shell script example for Linux/macOS users to demonstrate calling the REST API directly (e.g., with curl), especially for automation scenarios.
  • Explicitly state that PowerShell examples are for users who prefer PowerShell, and that equivalent functionality is available via CLI and REST API on all platforms.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but there are subtle signs of Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and Linux-specific migration steps or examples (e.g., handling Linux package manager connectivity) are referenced only briefly and without concrete examples. There are no explicit Linux CLI or shell script examples, and the only command-line example shown uses Azure CLI, which is cross-platform, but does not demonstrate Linux-specific patterns or considerations.
Recommendations
  • Add explicit Linux migration scenarios and examples, such as handling Linux VM activation, package manager connectivity, and OS-specific extension installation.
  • Include Linux-focused CLI or shell script examples alongside Azure CLI and PowerShell references.
  • When listing outbound connectivity requirements, provide Linux scenarios with equal detail and order as Windows (e.g., mention Linux package manager access before or alongside Windows activation).
  • Ensure that any references to scripts or templates include both PowerShell and Bash examples where applicable.
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-01 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 included and shown alongside CLI and ARM template examples, which may indicate a slight Windows bias. In several sections, PowerShell is presented immediately after CLI, and before ARM template examples, which could be interpreted as a 'Windows first' ordering. All CLI examples use Azure CLI, which is cross-platform, and there are no exclusive Windows tools or patterns. No Linux-specific examples (such as Bash scripts) are provided, but the CLI commands are suitable for Linux/macOS users.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider adding a short Bash script example for Linux users, or clarify that the CLI examples are intended for all platforms.
  • Where PowerShell is shown, clarify that it is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Ensure ordering of examples does not consistently favor Windows/PowerShell over CLI/ARM template.
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-01 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 in several places, Windows/PowerShell examples are presented before Linux equivalents. The PowerShell examples are detailed and use Windows-specific cmdlets (e.g., Add-AzVmssExtension, Update-AzVmssInstance), and the extension type defaults to ApplicationHealthWindows in some examples. While Linux is supported and shown, there is a slight preference for Windows/PowerShell tools and ordering, which may create minor friction for Linux users.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel tabs or with equal prominence, ideally listing Linux/Bash examples first in some sections.
  • Explicitly clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in extension configuration examples, and provide a Linux-specific example for the REST API payload.
  • Add more context or links for Linux users, such as troubleshooting tips specific to Linux environments.
  • Where possible, use generic or cross-platform CLI examples before platform-specific PowerShell ones.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but shows mild Windows bias in several areas. Windows-specific scenarios (activation, updates) are listed before Linux equivalents (package managers) in the networking section, and no Linux-specific migration examples or references (such as SSH, cloud-init, or Linux VM images) are provided. All CLI and API examples are generic and not OS-specific, but the lack of explicit Linux migration guidance may create friction for Linux users.
Recommendations
  • Add explicit Linux migration scenarios, such as steps for migrating Linux VMs (e.g., handling SSH keys, cloud-init configuration, Linux disk attachment).
  • In networking sections, mention Linux package manager connectivity before or alongside Windows activation and updates.
  • Provide example commands or references for both Windows and Linux VM images when discussing VM creation.
  • Where VM extensions are discussed, mention popular Linux extensions (e.g., Azure VM Agent for Linux, custom script extension) alongside Windows equivalents.
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-01-31 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 consistently presented alongside CLI and Portal, and in some sections, PowerShell is shown before ARM template examples. This may create a subtle Windows-first impression, especially since PowerShell is primarily a Windows tool (though available on Linux/macOS). No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the Azure CLI commands are cross-platform and suitable for Linux/macOS users. There are no critical sections that are Windows-only, and all tasks can be completed using the CLI or Portal.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and are the recommended cross-platform approach.
  • Consider adding a brief note in the introduction or CLI sections highlighting CLI parity for Linux/macOS users.
  • If possible, provide Bash script snippets or mention that CLI commands can be run in Bash, zsh, etc.
  • Ensure PowerShell is not presented as the primary or default automation tool unless the feature is Windows-specific.
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-01-31 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 and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets, but there is a notable Windows bias. PowerShell examples are given equal prominence to Bash, and Windows-specific extension types (ApplicationHealthWindows) are shown before Linux equivalents (ApplicationHealthLinux) in several places. The PowerShell example is more detailed than the Bash example, and Windows tooling (PowerShell) is presented as a primary method alongside Azure CLI and REST, rather than as a secondary or alternative option. In extension configuration JSON, Windows extension types are listed first. However, Linux users can still complete all tasks, and CLI/Bash examples are present.
Recommendations
  • List Linux extension types (ApplicationHealthLinux) before Windows types (ApplicationHealthWindows) in JSON and REST examples, or show both explicitly.
  • Ensure Bash/Linux examples are as detailed and robust as PowerShell/Windows examples, especially for server setup and scripting.
  • Where both CLI and PowerShell examples are given, consider presenting CLI (cross-platform) first, then PowerShell (Windows-specific).
  • Clarify in extension configuration tables and examples that both Linux and Windows are supported, and provide explicit Linux-focused sample values.
  • Add troubleshooting steps or notes for Linux-specific issues if any exist.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides some examples and scenarios that mention Windows-specific tasks (e.g., Windows VM activation, Windows updates) before Linux equivalents, and does not provide explicit Linux-focused examples or commands. While the migration process itself is platform-agnostic, the documentation could better address Linux parity by including Linux-specific migration considerations and examples.
Recommendations
  • Add explicit Linux migration scenarios, such as package manager connectivity requirements (e.g., apt, yum, zypper) and troubleshooting steps for Linux VM activation or updates.
  • Provide example commands for both Windows and Linux VMs where relevant, especially in sections discussing outbound connectivity and VM extensions.
  • Ensure that references to OS-specific requirements (e.g., Windows Activation KMS) are paired with Linux equivalents (e.g., connectivity for package updates).
  • Where PowerShell or Windows-centric tools are mentioned, also mention Bash/Azure CLI or Linux-native tools if applicable.
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-01-30 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. The PowerShell example is given its own section and is presented after the CLI example, but both are included. There is a slight Windows bias in that PowerShell is called out explicitly, and PowerShell is a Windows-centric tool, though it is available cross-platform. No Linux-specific tools (such as Bash scripts) or macOS-specific instructions are provided, but the CLI and REST API examples are platform-neutral and suitable for Linux/macOS users. The order of examples (portal, REST API, CLI, PowerShell) does not strongly favor Windows, but PowerShell is the only shell scripting example shown.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, demonstrating how to call the REST API or use Azure CLI in a shell environment.
  • Clarify that Azure CLI and REST API examples are cross-platform and suitable for Linux/macOS users.
  • Consider mentioning that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
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-01-30 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 related to Azure Virtual Machine Scale Sets, but PowerShell examples are often presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell usage. There are no Linux-specific shell examples (e.g., Bash scripts), and some CLI examples are generic but lack explicit Linux context. The documentation does not mention Linux-specific networking tools or patterns, and Windows/PowerShell is sometimes prioritized in example ordering.
Recommendations
  • Ensure CLI examples are presented before or alongside PowerShell, especially for tasks that are cross-platform.
  • Add explicit Bash/Linux shell examples where relevant, especially for querying and scripting tasks.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample outputs from Linux environments.
  • Where PowerShell is used for querying or scripting, provide equivalent Bash/CLI commands and outputs.
  • Avoid ordering examples so that Windows/PowerShell appears first unless there is a technical reason.
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-01-30 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 or updating the rolling upgrade policy'), PowerShell examples are shown immediately after CLI, which may suggest a slight Windows-first bias. There are no Linux-specific tools or shell examples (e.g., Bash scripts), but the Azure CLI commands are cross-platform and suitable for Linux/macOS users. No critical functionality is locked to Windows-only tools.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest using Azure CLI on Linux/macOS.
  • If possible, add a note about Azure Cloud Shell, which supports both Bash and PowerShell, to highlight cross-platform parity.
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-01-30 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 installing/querying the extension. However, there are several instances of Windows bias: PowerShell examples are given equal or greater prominence than Bash, and Windows-specific extension types (ApplicationHealthWindows) are shown before or alongside Linux types. The PowerShell examples are more verbose and detailed, and Windows extension types are sometimes used as the default in code samples, even when Linux is equally supported. The documentation does not omit Linux examples, but Windows tools and patterns are often presented first or with more detail.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail. For example, alternate the order of Bash and PowerShell tabs, or present Linux examples first in some sections.
  • Use neutral extension type placeholders (e.g., <ApplicationHealthLinux or ApplicationHealthWindows>) consistently, and clarify when to use each based on the OS.
  • Expand Linux/Bash examples to match the depth and clarity of PowerShell examples, including troubleshooting and advanced scenarios.
  • Explicitly state that all features and steps apply equally to both Linux and Windows VMSS, unless a step is OS-specific.
  • Where possible, provide cross-platform scripts or highlight platform-agnostic approaches (e.g., using REST API or Azure CLI).
GitHub Create Pull Request
← Previous Page 5 of 6 Next →